[GiNaC-list] Python wrapper for a GiNaC derived library

[Richard B. Kreckel]

Ondrej Certik wrote:

>> The point is that your Python data types are already doing for you
>> automatically what GiNaCs exes are doing in C++: being a reference to a
>> garbage-collected data type. I don't think it is possible to do without
>> that.
>
>
> I am not sure I understand. Why cannot we use it like in the following
> example? I compiled it and it works as expected:
>
[snip leaky code]

Question: Why don't you explicitly free the memory you're explicitly 
allocating?
Answer: Because it is a damn pain in the neck! (And, maybe, because 
you're not used to, since Python does such things for you.)

See, with wrapped objects, there're no such problems.

Regards
  -richy.

-- 
Richard B. Kreckel
<http://www.ginac.de/~kreckel/>