On Sat, 16 Dec 2000, Sascha Schumann wrote: > I had too much free time today, so I created make_export.awk. > During that I noticed that I either lack some awk knowledge > or that the awk's expression mechanism lacks a useful feature > (backreferencing). I've worked around that by using two sub's > in the respective block.
I dislike this idea. I realize (now) that awk is available on Windows, but Perl is already required to build Apache on Windows, and all of a sudden we are going to add the requirement of awk too. Why? We already require Perl on every platform when building Apache, but we do not currently require awk. Unless there is a really good reason to change this to awk, I would much rather use Perl. That is a -1 (vote not veto) for the awk version. I would also point out that we have always expected developers to have Perl installed on their machines, and people who download the binary will not need it. > The script is a direct port of the Perl script, we just leave > the file handling to awk. I've tested it with gawk and mawk > and it behaves fine. > > Are these functions supposed to be exported? Yes, all of these are supposed to be exported, and they are by the Perl version. At least they are on my machine. Ryan > > --- apr.exports.perl Fri Dec 15 17:52:38 2000 > +++ apr.exports Sat Dec 16 18:45:44 2000 > @@ -96,2 +96,9 @@ > apr_MD5Encode > +apr_MD5Init > +APR_HAS_XLATE > + apr_MD5SetXlate > +/APR_HAS_XLATE > +apr_MD5Update > +apr_MD5Final > +apr_MD5Encode > APR_HAS_MMAP > @@ -260,2 +267,6 @@ > apr_strftime > +apr_get_home_directory > +apr_get_uuid > +apr_format_uuid > +apr_parse_uuid > apr_get_home_directory > > - Sascha > _______________________________________________________________________________ Ryan Bloom [EMAIL PROTECTED] 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------
