in reply to perllibv2.01
This would allow nearly instant integration with ANY C++ program. Furthermore, you need to be careful about multiple perl interpreters which needs a great deal of informing on pthreads (I can help you out in this and any other UN*X dept.) This would be massive undertaking. I imagine it could be entirely done as a wrapper class around perlxs. Let me know what you think and if you need help (you will). I'd also like to be able to pipe to various Perl interpreters, regardless of the interpreter's status. Currently, one can pass and environment and whole bunch of stuff that's quite confusing and difficult to get right on the first time.//your code class PerlScalar { //overloads on assignment, operators, etc. ~PerlScalar(){...} //just say NO to memory leaks! } class PerlArray{...} class PerlHash{...} //my code PerlScalar myScalar="This is text."; PerlScalar myScalar2=123; //integer, double, etc. PerlScalar myScalar3(bitblob); //assigns any random info
perlxs is also a pain in the ass when trying to fiddle with the perl stack. They're just some macros, but can be easily forgotten and often annoying. I would suggest throwing a wrapper around that, too. Essentially, I'm looking for a wrapper for perlxs that wouldn't cut into performance nor flexibility. Sir, you have a winner idea, I hope it evolves into something popular! Hell, I'd use it!
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: perllibv2.01
by Cybercosis (Monk) on May 06, 2001 at 08:03 UTC |