> It's been rumoured that James A. Treacy said: > > > However, I wonder----could we mitigate the problems you describe by allow > ing > > > users who don't want it to turn off the option at compile time, and by be > ing > > > 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. Are there plans for phasing out the eperl stuff and using something else for report generation? dave -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
- Java implementation jools enticknap
- Re: Java implementation Derek Atkins
- Re: Java implementation Rob Browning
- Re: A bit off topic---Java as "SUN's ... Rob Browning
- Re: Perl in internals (was Re: A bit o... Rob Browning
- Re: Perl in internals (was Re: A ... James A. Treacy
- Re: Perl in internals (was Re... linas
- Re: Perl in internals (wa... Dave Peticolas
- Re: Perl in internals (wa... Rob Browning
- Re: Perl in internals (wa... Dave Peticolas
- Re: Perl in internals (wa... Rob Browning
- Re: Perl in internals (wa... Dave Peticolas
- Re: Perl in internals (wa... Rob Browning
- Re: Perl in internals (wa... linas
- Re: Perl in internals (wa... Dave Peticolas
- Re: Perl in internals (wa... linas
- Maybe Coming Time to XML? Christopher Browne
- Re: Perl in internals (wa... Rob Browning