http://qs1969.pair.com?node_id=78304

Disclaimer: I'm putting this here because this is where my last post got put.
That being said, perllibv2.01 is now available at SourceForge. I've made so many improvements over v1 that it isn't funny, and there's more to come! Download and be merry! (or not, and email me about it at stormwolf@linuxfreemail.com)

Out of curiosity, AgentM(this is directed at everybody else, too), when I announced the initial release you said in this post that you couldn't see any advantage over perlxs. What would you like to see in a library such as the perllib (besides regexes, which I will implement thanks to tilly's suggestion, and overloads, which I will implement when I'm satisfied with the C version)?

~Cybercosis

Replies are listed 'Best First'.
Re: perllibv2.01
by AgentM (Curate) on May 06, 2001 at 04:56 UTC
    Here's my opinion about perlxs: it is obviously complete but not easy to use or learn. Often, it's simply too easy to throw something together with blatant memory leaks without obvious solutions. I'd like to see an API as close as possible to perl's own built-in functionality, specifically memory cleanup and less stack twiddling. Over course, in order to build an API over this, one must be very familiar with perlxs, perlguts, and beyond what is described in any docs. I would love to use something simplistic like: 
    //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

    [download]
    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.

    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!

    AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.
[reply]
[d/l]
      Hrm... this is not an idea I had considered. Email me (stormwolf@linuxfreemail.com) and we'll talk about it!

      ~Cybercosis

[reply]

Back to Meditations