Question re Embperl memory usage

2000-12-22 Thread Neil Gunton
Gerald, this question has been bugging me for a few days. In one of your previous emails you said the following: > > I use __PACKAGE__ because I have global variables which are set up in > > various different files (such as init.html and constants.html) which are > > executed before '*', and it i

Re: calling methods within EmbperlObject (was: Possible bug with EmbperlObject and [$ sub $])

2000-12-22 Thread Gerald Richter
Neil, > > Gerald, when I try to move the above Execute statement into a [! !] > block, before the rest of the action, Embperl gives me an error on the > line where I call Execute ('subs.html#NEW', \$req->{subs}): > without haveing actualy tried it, I would say it should work. I can't see at the

Re: calling methods within EmbperlObject (was: Possible bug with EmbperlObject and [$ sub $])

2000-12-22 Thread Gerald Richter
>and I will also make a start on some kind of EmbperlObject > tutorial Great! > do you have any > particular preference that would make it easier for you to integrate? pod, please write everything in pod. All the Embperl docs are written in pod and I have a script that generates the whole Embpe

Re: calling methods within EmbperlObject (was: Possible bug with EmbperlObject and [$ sub $])

2000-12-22 Thread Neil Gunton
Gerald Richter wrote: > > base.html > > [- > > # Setup other packages > > $req = shift; > > Execute ({inputfile => 'subs.html', import => 0}); > > You could move the import in a [! !] block, so it will only be executed once > at compile time > Gerald, when I try to move the above Execute state

Re: calling methods within EmbperlObject (was: Possible bug with EmbperlObject and [$ sub $])

2000-12-22 Thread Neil Gunton
Gerald, thanks for the feedback on my EmbperlObject code. I will be re-working my sites to use the new methodology over Christmas (bah, humbug), and I will also make a start on some kind of EmbperlObject tutorial (I will see how it goes, at least it will be a start). I don't know what format you w

Re: embperl + oracle sessions -- solved.

2000-12-22 Thread Michael Smith
When I investigated this whole thing, it turned out that DBD-Oracle doesn't autocommit BLOBs - to get it to work I had to get a patch to DBD-Oracle from Tim Bunce. Mike - Original Message - From: "Gerald Richter" <[EMAIL PROTECTED]> To: "Eitan Suez" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]

Re: ANNOUNCE: Embperl 2.0b1

2000-12-22 Thread Gerald Richter
> > > Since it's not yet ready for production use, it's only available from my ftp > > server at > > Hmm, with unstable software I prefer to use cvs upd more often, isn't > there a cvs repository anywhere? A stable version can also be fetched > from an FTP archive, but for development versions thi

Re: ANNOUNCE: Embperl 2.0b1

2000-12-22 Thread Jens-Uwe Mager
On Fri, Dec 22, 2000 at 07:51:36AM +0100, Gerald Richter wrote: > Since it's not yet ready for production use, it's only available from my ftp > server at Hmm, with unstable software I prefer to use cvs upd more often, isn't there a cvs repository anywhere? A stable version can also be fetched f

ANNOUNCE: Embperl 2.0b1

2000-12-22 Thread Gerald Richter
After long time of talking, designing, developing, codeing and testing I am now happy to announce the first beta of Embperl 2.0. It has a totaly rewritten core and makes the way free for a lot of new possibilities... At the moment it's mainly a speed improvement and introduces caching of the (com

Re: calling methods within EmbperlObject (was: Possible bug with EmbperlObject and [$ sub $])

2000-12-22 Thread Gerald Richter
> It > seems to me that I will now effectively be referencing all my (formerly > global) variables through a hash, which seems like it could introduce a > certain amount of additional overhead (because of the hash lookup every > time I refer to the variable). Will this appreciably affect performan

Re: embperl + oracle sessions -- solved.

2000-12-22 Thread Gerald Richter
hi, > > a co-worker here solved the mistery of oracle + sessions using embperl. Great! > apparently, somehow Store::Oracle was not setting autocommit to true > and not committing its insert's. so each time the store was used, any > sql commands would be rolled back while still returning