On Sat, 13 Sep 2014, Nicholas Boel wrote to mark lewis:

 NB> I've only been participating in Fidonet for a few years now, and I 
 NB> could've sworn I remember perl hooks being implemented during that 
 NB> time. That's why I was asking, as unless it was added into the 
 NB> stable branch, I thought it was only something fully implemented 
 NB> in the 1.1 alphas.

 NB> Unless they finally documented it during the past few years and it 
 NB> was there all along. *shrug*

like i said before, AFAIK it is a compile time option... the following are the
different compile time options of the 20 or so binkds i have here...

Comp flags: gcc (emx), https, ntlm, amiga_4d_outbound.
Comp flags: watcom, zlibdl, https, ntlm, amiga_4d_outbound.
Comp flags: gcc (emx), zlib, https, ntlm, amiga_4d_outbound, bwlim.
Comp flags: gcc (klibc), https, ntlm, amiga_4d_outbound, bwlim.
Comp flags: gcc (klibc), zlib, https, ntlm, amiga_4d_outbound, bwlim.
Comp flags: gcc (klibc), zlib, bzlib2, https, ntlm, amiga_4d_outbound, bwlim.
Comp flags: gcc (emx), zlib, bzlib2, perl, https, ntlm, amiga_4d_outbound,
bwlim.

not that only one of those listed above shows perl in it... i can't even run it
because none of the emx ones will operate on my system without having some kind
of interference with other tasks... i don't think i was able to run the watcom
ones either for the same or similar reasons...

i actually excpect that my system could get by with zlib, bzlib and bwlim
only... it certainly doesn't need perl, https, ntlm, or amiga_anything since it
is an OS/2 eCS system... not to mention that in the case of the amiga_schtuff,
it isn't even operational on any system other than an amiga... perl is the
perlhooks thing that started us down this road... i don't tunnel binkd stuffs
via httpanything and have no need to do such... i certainly don't use NT Lan
Manager (ntlm) ;)


)\/(ark

If you think it's expensive to hire a professional to do the job, wait until
you hire an amateur.

--- FMail/Win32 1.60