[C++-sig] Re: Interest in luabind

[Dirk Gerrits]

Nicodemus wrote:
> Ralf W. Grosse-Kunstleve wrote:
>
>> As a user who (finally!) writes mainly new Python code I really value
>> the safe-but-certain approach. If the interpreter crashes somewhere deep
>> down in the application without printing a backtrace it is often very
>> frustrating and time-consuming to isolate the problem by adding print
>> statements. In a large-scale application it is crucial that all
>> components are rock-solid.
>> Ralf
>>
> 
> We use Boost.Python at our company developing large applications, and I 
> agree with Ralf.
> Plus, I believe it is against Python philosophy to get a core dump, 
> since Python itself goes great lenghts to prevent explicit memory 
> management by the user.

I concur. Anything that has gone wrong with my Python programs so far 
has always resulted in a nice and clear exception with a traceback. If 
only that would have been the case in C++... :P Great libraries like the 
STL and Boost alleviate the pain though.

> BTW, this discussion about LuaBind is really interesting. 8)

I agree! And perhaps some of it can serve as a fine basis for that 
'Boost.Python core documentation'?

Regards,
Dirk Gerrits