It's been rumoured that James A. Treacy said:
> > However, I wonder----could we mitigate the problems you describe by allowing
> > users who don't want it to turn off the option at compile time, and by being
> > careful to control what access is given to the scripting language?
The problem with perl was that it caused all sorts of install headaches
for newbies (it required swig, and also required eperl) and since
stock redhat/debian didn't have these, it was just a long frustrating
story.
> > Baring that, if a scripting language is not a first-class-citizen, what can
> > one expect *not* to be able to do in that scripting language?
> >
> Directly access program internals. This should be deprecated anyway, since
> internals can change.
Even scheme/guile is "not supposed to" access anything but the
architected interfaces. The interface to the engine is designed to
not morph in the future. There are some interfaces into the
GUI that may get this solid after some more experimentation.
--linas
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
