Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
From: "Ayhan Ulusoy" <ayhan@drexel.edu>
To: "'Geoffrey Young'" <geoff@modperlcookbook.org>
Cc: <dev@perl.apache.org>
Subject: RE : RE : [mp2] PERLIO_K_RAW in apr_perlio.c
Date: Wed, 1 Oct 2003 20:12:45 +0200
Message-ID: <001301c38847$a14e88c0$a500a8c0@galileo>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Importance: Normal
In-reply-to: <3F7A0AA7.4060602@modperlcookbook.org>


Yupp. It is probably better to stick close to the way httpd does things.

Besides, that VMS behaviour must be a real buggy one if it is the way
that snippet suggests  :)

Cheers,

Ayhan


-----Message d'origine-----
De=A0: Geoffrey Young [mailto:geoff@modperlcookbook.org]=20
Envoy=E9=A0: mercredi 1 octobre 2003 00:59
=C0=A0: Ayhan Ulusoy
Cc=A0: dev@perl.apache.org
Objet=A0: Re: RE : [mp2] PERLIO_K_RAW in apr_perlio.c


> # Define the CRLF sequence.  I can't use a simple "\r\n" because the
> meaning
> # of "\n" is different on different OS's (sometimes it generates CRLF,
> sometimes LF
> # and sometimes CR).  The most popular VMS web server
> # doesn't accept CRLF -- instead it wants a LR.  EBCDIC machines don't
> # use ASCII, so \015\012 means something different.  I find this all=20
> # really annoying.

randy and I have discussed this before, IIRC...

while apache itself makes the distinction between ascii and ebcdic, it
does=20
not distinguish between vms and the rest of ascii land.

I say we punt just follow the lead of httpd, exporting their constants.

patch attached.  I'll clean up the test tomorrow if people like the
idea.
--Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org