Re: [Simulavr-devel] Python again ;-) and some other things

[address@hidden]

On Sat Jun 27  5:52 , ThomasK  sent:

>So my second question: is there interrest to implement such? Connected 
>with that: How to send in patches? Is there a programming style guide 
>for simulavr, means, how to write, indent and so one code? What's with 
>code documentation? (I have seen, that sometimes somebody has inserted 
>doxygen comments) Especially, what's with tab usage?

Evil things.

>This brings me to a next hotspot. ;-) I have seen, that there was a 
>discussion about python extension. In the moment it's commented out in 
>makefiles and, if python modul will be built, then it's not usable: an 
>import error raises, because of an missing symbol! (I havn't really 
>analysed, why, because it looks so, that nobody use this in the moment)

I think that there is a missing -liberty on a link line somewhere.

>So my first tests on this area was to "replace" main.cpp by an python 
>module (by using SWIG also, but not simulavr.i) and a little python 
>script. I think, this could be a base for a "restart" of a python extension.
>
>For such work it's to know, what are the goals for such? Who want's to 
>use it and for what? I think, it's not a real good idea, only to put 
>"all" into such extension module like the current module does. 
>Especially if some features (methods and class members) aren't usable 
>without special preparations.

The minimal goal would be to be able to use the simulator as a python module.
Informative examples would also be good things.
One might rewrite the standalone executable in python.

I'm working on it, but my C++/python expertise isn't yet.
The swig site looks like it might be more helpful than my Programming Python 
book.

--
Michael Hennebry
address@hidden
"War is only a hobby."

---- Msg sent via CableONE.net MyMail - http://www.cableone.net