Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of andy@hexten.net designates
 75.127.65.154 as permitted sender)
Message-Id: <E98578BE-D648-4052-BAE6-E3554511142F@hexten.net>
From: Andy Armstrong <andy@hexten.net>
To: mod_perl list <modperl@perl.apache.org>
In-Reply-To: <4A4A0F76.70307@ice-sa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: quick pure perl question
Date: Tue, 30 Jun 2009 14:33:22 +0100
References: <4A478F38.6070805@ice-sa.com>
 <16f65d000906280933p3b0b94a0g840e849c46d1c1d6@mail.gmail.com>
 <C40B2EB8-C83D-45C4-B9C8-15C8B98DB7E3@hexten.net> <4A4A0F76.70307@ice-sa.com>

On 30 Jun 2009, at 14:13, Andr=E9 Warnier wrote:
> I /would/ have expected it if I was /not/ specifying an encoding, =20
> like using simply '>'.  But not when I am explicitly specifying =20
> '>:raw', which in my mind, and according to my interpretation of the =20=

> on-line documentation, is equivalent to saying "output whatever you =20=

> have as bytes in that string variable right now, as is, I know what =20=

> I'm doing".


You have that bit right - but the string doesn't contain bytes[1] - it =20=

contains characters. Strings can either be an octet stream or a stream =20=

of wide characters. By reading utf8 into a string you've turned it =20
into the latter. Perl's warning that you're pushing character data =20
into an octet hole.

[1] of course it's /made/ of bytes but that's not how Perl sees it.

--=20
Andy Armstrong, Hexten