Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!elroy.jpl.nasa.gov!jpl-devvax!lwall
From: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: openlog(3), syslog(3) in perl
Message-ID: <7445@jpl-devvax.JPL.NASA.GOV>
Date: 16 Mar 90 23:57:48 GMT
References: <39461@apple.Apple.COM> <100571@convex.convex.com> <1990Mar15.212147.2978@chinet.chi.il.us>
Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 13

In article <1990Mar15.212147.2978@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes:
: Hey, good idea there.  How about it Larry, at least for shared-library
: machines it shouldn't add much overhead?

You'd still have to put the calls in there, unless someone's written a shared
library fasl'er.  It would be possible, of course, for Configure to generate
a list of library routine names, and build a calls.c file and compile it in,
but that seems a bit of a kludge.

Maybe there's a tricky way to to build a jump-table on the fly, but I don't
know of it yet.

Larry