printf/fprintf in mod_perl sources

2001-06-27 Thread Stas Bekman
I've a C question :) Why cannot I use: printf(%s\n, IT WORKS); and have to use: fprintf(stderr, %s\n, IT WORKS); in the mod_perl sources? Doug, I've figured what was my problem :) Here is the relevant part of the trace (it was segfaulting when I was using printf): (gdb) where #0

Re: printf/fprintf in mod_perl sources

2001-06-27 Thread Doug MacEachern
On Thu, 28 Jun 2001, Stas Bekman wrote: I've a C question :) Why cannot I use: printf(%s\n, IT WORKS); and have to use: fprintf(stderr, %s\n, IT WORKS); in the mod_perl sources? something todo with PerlIO, turns printf, fprintf, etc. into macros. i always use

Re: cvs commit: modperl-2.0/Apache-Test/lib/Apache TestSort.pmTestHarness.pm

2001-06-27 Thread Doug MacEachern
On Thu, 28 Jun 2001, Stas Bekman wrote: what happens if $args-{order} is defined, but is none of rotate|random|repeat when somebody mistypes the value or --order? This code will die. My original code was just silently ignoring this option if it's an unknown one. i don't think an unknown

Re: cvs commit: modperl-2.0/Apache-Test/lib/Apache TestSort.pmTestHarness.pm

2001-06-27 Thread Stas Bekman
On Wed, 27 Jun 2001, Doug MacEachern wrote: On Thu, 28 Jun 2001, Stas Bekman wrote: what happens if $args-{order} is defined, but is none of rotate|random|repeat when somebody mistypes the value or --order? This code will die. My original code was just silently ignoring this option if

make source_scan

2001-06-27 Thread Stas Bekman
Ok, here is the summary of the 'make source_scan' issue. using the Scan.pm from Doug's site with the patch: --- /home/dougm/tar/Scan.pm Mon Jun 25 16:38:02 2001 +++ /home/dougm/perl/C-Scan-0.75/Scan.pmWed May 2 20:57:45 2001 @@ -914,7 +914,7 @@ } my $stream = $class-new(@_);

Re: .cvsignore in ./t

2001-06-27 Thread Doug MacEachern
i have a script to automate that (below). i left the generated .t's out for the moment, wondering if some might become non-autogenerated and checked in, not that it would hurt if that happened and they were also in .cvsignore #!/usr/bin/perl -w #handy to generate .cvsignore entries #e.g. #

Re: make source_scan

2001-06-27 Thread Doug MacEachern
On Thu, 28 Jun 2001, Stas Bekman wrote: So if I add a new feature and want to add it via source_scan, only you can do that if don't want to overwrite each others version of xs/tables/current/Apache/FunctionTable.pm. Do you think we should make sourcescan produce an identical code, no matter

Re: .cvsignore in ./t

2001-06-27 Thread Stas Bekman
On Wed, 27 Jun 2001, Doug MacEachern wrote: i have a script to automate that (below). i left the generated .t's out for the moment, wondering if some might become non-autogenerated and checked in, not that it would hurt if that happened and they were also in .cvsignore the cool thing is

Re: .cvsignore in ./t

2001-06-27 Thread Doug MacEachern
On Thu, 28 Jun 2001, Stas Bekman wrote: so may be: system cvs add .cvsignore; system cvs ci -m 'ignore these' .cvsignore; i just do the commit by hand, after doing another diff to make sure i the script didn't break something. Will you make it a part of the rep or do you plan

Re: make source_scan

2001-06-27 Thread Stas Bekman
On Wed, 27 Jun 2001, Doug MacEachern wrote: On Thu, 28 Jun 2001, Stas Bekman wrote: So if I add a new feature and want to add it via source_scan, only you can do that if don't want to overwrite each others version of xs/tables/current/Apache/FunctionTable.pm. Do you think we should make