Re: [ROOT] root as extension language

From: Valeriy Onuchin (Valeri.Onoutchine@cern.ch)
Date: Tue Mar 25 2003 - 12:31:32 MET


 Brett Viren wrote:

>Do you actually need all of the ROOT features or are you just looking
>for an extension language?  
>
>If your goal is to *just* provide an extension language, frankly, I
>wouldn't consider ROOT/CINT.  If you need to use, specifically, C++ as
>the extention language or you need object I/O, histograms, drawing,
>and all the good stuff ROOT provides then ROOT/CINT is an okay choice,
>but if you simply want to provide users a way to write scripts for
>your main compiled app I'd suggest using SWIG (www.swig.org) to
>generate the necessary wrappers for whatever your favorite interpreted
>language is (Scheme, Perl, Python, etc).

 Hi Brett,
I saw many times why (Scheme, Perl, Python, etc).
should be used instead of using interpreted C/C++, e.g.

".. but C++'s strict typing, pointers, memory
managment etc. simply doesn't lend itself very to a scenario where an end
user wants to control his app with simple commands at a high abstraction
level without a degree in CS."

The opposite argument is => if  you want simplicity, do not use C++ in full range,
use C which is "as simple as possible language". If you  do not need ROOT's
"object I/O, histograms, drawing" => do not load/(compile against) these libraries.

Thank you for interesting link about SWING, but "in the Carrot context (http://carrot.cern.ch)"
I'm currently thinking about "anti-SWIING" solution, i.e. possibility to create converter of 
PHP (http://www.php.net), Perl,Python scripts into C/C++ scrtipts, 
possiblity to reuse exisitng  PHP(Perl etc.) modules  in ROOT enviroment. 

If you/somebody have/has ideas about how to do it in better way 
or know about existing software which allows to do it => please, let me know.

Thanks. Regards. Valeriy
 


 



This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:10 MET