🚀 go-pugleaf

    After stumping around the distribution disks for long enough, I finally
    located where grep.lib had been hidden. :)

    I want to use these functions, but it seems that they use malloc() and
    exit(), and expect the RAM they allocate with malloc() to be cleaned
    up when the program finishes (in fact, it looks like they can terminate
    the program themselves, if an error occurs. NOT what I want to do...).

    I do not want to use the malloc stuff, nor do I want to use exit or
    MemCleanup. Nor do I want these routines churning out error messages to
    stdout... :)

    I could, maybe, use fake routines for all these - but is there an
    easier way? Has anyone gone in and adjusted the code to remove these
    features? Is it even possible to use fake routines?

    Is that an ok thing to do (changing the code, I mean)?

    Some alternatives are using Dave Haynie's filename matching code (but
    it's not filename matching I'm doing), or writing my own (a simple
    extension of KMP to handle wildcards) which means no [...] type
    expressions.

    Are there other alternatives? Arp, perhaps (I don't have the
    programming parts of the Arp distribution).

    Hm. Replies in email, if you wish. Me-toos in email too, I think.
--
*** John Bickers, TAP, NZAmigaUG.         jbickers@templar.actrix.co.nz ***
***     Let them figure it out, Come on and step across,                ***
***     Just remind yourself,   We are here to code.   - munged Devo    ***