On 02/26/2011 09:36 PM, Jeff Trawick wrote:
> On Sat, Feb 26, 2011 at 2:44 PM, Stefan Fritsch wrote:
>> Hi,
>>
>> looking at PR 50824, I have noticed that ap_cfg_getline() and
>> ap_cfg_getc() are rather limited in that they do not allow the caller
>> to distinguish between EOF and an error (e.g
On Sat, Feb 26, 2011 at 2:44 PM, Stefan Fritsch wrote:
> Hi,
>
> looking at PR 50824, I have noticed that ap_cfg_getline() and
> ap_cfg_getc() are rather limited in that they do not allow the caller
> to distinguish between EOF and an error (e.g. line too long, IO
> error). ap_cfg_getline returns
Hi,
looking at PR 50824, I have noticed that ap_cfg_getline() and
ap_cfg_getc() are rather limited in that they do not allow the caller
to distinguish between EOF and an error (e.g. line too long, IO
error). ap_cfg_getline returns 0 on success and 1 if there was EOF or
an error, ap_cfg_getc re