Stas Bekman wrote:
> Doug MacEachern wrote:
>
> > On Fri, 14 Dec 2001, Stas Bekman wrote:
> >
> >
> >>Is there a way for SourceScan to tell where it borks? I mean on which
> >>file (line?).
> >>
> >
> > not that i know of, that'd be up to C::Scan.
>
>
> more problems with C::Scan:
>
>
Doug MacEachern wrote:
> On Fri, 14 Dec 2001, Stas Bekman wrote:
>
>
>>Is there a way for SourceScan to tell where it borks? I mean on which
>>file (line?).
>>
>
> not that i know of, that'd be up to C::Scan.
more problems with C::Scan:
#ifndef MP_SOURCE_SCAN
#include "apr_optional.h"
Doug MacEachern wrote:
> you can put #ifndef MP_SOURCE_SCAN around the trouble makers.
that works. Thanks.
Is there a way for SourceScan to tell where it borks? I mean on which
file (line?).
_
Stas Bekman JAm_pH
It also explodes on:
#include "apr_optional.h"
_
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://ticket
I've these function declarations in apr_perlio.h:
PerlIO *apr_perlio_apr_file_to_PerlIO(pTHX_ apr_file_t *file,
apr_pool_t *pool);
APR_DECLARE_OPTIONAL_FN(PerlIO *,
apr_perlio_apr_file_to_PerlIO,
(pTHX_ apr_
