These are chat archives for symengine/symengine

24th
Mar 2017
Isuru Fernando
@isuruf
Mar 24 2017 03:11

I've created symengine/symengine#1230 and symengine/SymEngine.jl#80

Previously you were using Julia's parser and now you are using SymEngine's which is not as powerful as Julia

@prateeksingh0001, commented on the PR
Christopher Rackauckas
@ChrisRackauckas
Mar 24 2017 03:14
hmm, should I revert my changes (getting rid of the @eval in ParameterizedFunctions made it so it no longer uses SymEngine symbols, since the only way to make t = symbols("t") was via @eval)? Or would adding unicode to the parser be a quick change?
Isuru Fernando
@isuruf
Mar 24 2017 03:17
@ChrisRackauckas, you can make a symbol without @eval, but problem is to make an expression t + 1 without @eval
Christopher Rackauckas
@ChrisRackauckas
Mar 24 2017 03:17
I have depvar = :t, how could I make t = symbols("t") without @eval from that?
Isuru Fernando
@isuruf
Mar 24 2017 03:20
This is inside a macro right?
Christopher Rackauckas
@ChrisRackauckas
Mar 24 2017 03:20
in a function
Isuru Fernando
@isuruf
Mar 24 2017 03:22
This is a function that gets a Expr?
Christopher Rackauckas
@ChrisRackauckas
Mar 24 2017 03:23
it takes in Exprs yeah
Isuru Fernando
@isuruf
Mar 24 2017 03:23
Then you need @eval
Or SymEngine's parser
Christopher Rackauckas
@ChrisRackauckas
Mar 24 2017 03:24
:worried:
Prateek Singh
@prateeksingh0001
Mar 24 2017 03:25
@isuruf I've added a test case as it was asked in the PR. kindly review it symengine/symengine#1228
Isuru Fernando
@isuruf
Mar 24 2017 03:28
@ChrisRackauckas, it should be an easy fix for the parser to use unicode. A new release would take some time though
Christopher Rackauckas
@ChrisRackauckas
Mar 24 2017 03:31
okay
Thanks for letting me know
I'll revert my previous release for now then.
(can't believe this case was missed by the tests :worried: )
Isuru Fernando
@isuruf
Mar 24 2017 03:52
Christopher Rackauckas
@ChrisRackauckas
Mar 24 2017 03:56
thanks!
I just put in a release to revert those changes
hopefully it merges before anyone notices :shipit:
I'll wait for the SymEngine release. Those are very infrequent though, right?
(it can wait though, it's not pressing at all. It was just pressing to find out what to do because everything started to segfault!)
Isuru Fernando
@isuruf
Mar 24 2017 04:01
symengine returns error codes and SymEngine.jl ignores those, that's why there are segfaults
It's been 6 months since the last release, so I'm hoping to release one in the near future
I just noticed, it's an odd image choice for shipit. :shipit:
Isuru Fernando
@isuruf
Mar 24 2017 06:28
@bluescarni, do you know why MSVC doesn't like unicode in std::string only in debug mode?
Francesco Biscani
@bluescarni
Mar 24 2017 08:56
@isuruf I was not aware of that behaviour. I don't think I have actually ever used utf8 strings yet
Prateek Singh
@prateeksingh0001
Mar 24 2017 13:47
@isuruf @Sumith1896 @srajangarg This is regarding an idea for my GSoC project. One of the major difficulty that I had to face on entering into SymEngine is that there is no user documentation to refer to. On my introduction to SymEngine I had the design document which is elaborate to some extent but not inclusive of all the portions of the library in its entirety, and thus the only way to enhance my understanding of the engine was to read its source code. If there would have been some user documentation describing the various modules and their functionality in some detail I would have been ready to start in a matter of one or two days. I feel that SymEngine needs a good user documentation and I would like to contribute to it. Would it qualify as a valid GSoC project ?
Isuru Fernando
@isuruf
Mar 24 2017 13:48
Yes, documentation is really lacking, but documentation projects don't qualify for a GSoC project.
Prateek Singh
@prateeksingh0001
Mar 24 2017 18:37
@isuruf I've made changes in the PR symengine/symengine#1228, please review it.