In short, I'm trying to find a way to direct the ideas and enthusiasm
generated in this thread back onto the core before launching off in
experimental directions.


On Mon, Sep 30, 2013 at 5:30 PM, Matthew Rocklin <mrock...@gmail.com> wrote:

> I like Joachim's suggestion of de-dynamizing the codebase.  I suspect it
> would help not only with future attempts at translation, but also with
> Cython or PyPy ports.  It would probably even help the pure Python
> implementation (which remains my top priority) and encourage growth.
>
> Efforts to remove magic without reducing performance would probably have
> significant positive impact both in increasing portability to other
> languages and also in supporting growth within the existing codebase.
>
>
> On Mon, Sep 30, 2013 at 5:16 PM, Joachim Durchholz <j...@durchholz.org>wrote:
>
>> Am 30.09.2013 23:07, schrieb F. B.:
>>
>>
>>> By the way, what about trying to force static typing in sympy's core
>>> through the usage of decorators?
>>>
>>
>> Can any IDE make use of that?
>>
>>
>> > Or maybe even try to define a standard to
>>
>>> write Python code in order to make it easy to translate it to C++ through
>>> code generators? I am fascinated by the idea of sympy being written in
>>> C/C++, but I am also very skeptical about the time needed for a
>>> translation
>>> by hand.
>>>
>>
>> One of the problems in Sympy is that it's making quite liberal use of
>> Python's ability to add class members long after the classes are declared.
>> The C and S classes are examples of this, and probably the most
>> significant ones in the Sympy codebase. I've been working on eliminating C
>> for a quite a while, and it's so pervasive and sometimes interwoven with
>> other parts of Pyhon that I sometimes found it hard to make any progress at
>> all; an automatic translation would probably have face more problems.
>>
>> So to prepare for translation to C++, I guess the whole codebase would
>> need to be de-dynamized quite a bit.
>> This would probably also make the various code analysis plugin more
>> reliable.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sympy" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to 
>> sympy+unsubscribe@**googlegroups.com<sympy%2bunsubscr...@googlegroups.com>
>> .
>> To post to this group, send email to sympy@googlegroups.com.
>> Visit this group at 
>> http://groups.google.com/**group/sympy<http://groups.google.com/group/sympy>
>> .
>> For more options, visit 
>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>> .
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sympy+unsubscr...@googlegroups.com.
To post to this group, send email to sympy@googlegroups.com.
Visit this group at http://groups.google.com/group/sympy.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to