On 19 Sep 2000, Perl6 RFC Librarian wrote:
Distinguish packed binary data from printable strings
What defines a "printable" string? What if I'm working in an environment
that can "print" bytes that yours can't? Specifically I'm wondering how
this proposal handles Unicode.
Perl should fly
Tom Christiansen wrote:
Perl should fly far and fast from starting down the bumpy road where
that data is strongly typed in the mythical and deceptive text-vs-binary
sense ... Heed the wisdom of the Unix ...
Tom's exactly right. Data should be data, at least by default.
One of the
Nathan Wiger wrote:
One thing that Nat will soon be releasing is an RFC on strict typing.
I'll also have one (hopefully) on an embedded tie-like solution that
will allow you to create your own variable types. With these you would
conceivably be able to say:
use strict 'types';
my packed
Nathan Wiger wrote:
Tom Christiansen wrote:
Perl should fly far and fast from starting down the bumpy road where
that data is strongly typed in the mythical and deceptive text-vs-binary
sense ... Heed the wisdom of the Unix ...
I shouldn't have used the term "binary" in the proposal
Perhaps what you're truly looking for is a generalized tainting mechanism.
--tom
Tom Christiansen wrote:
Perhaps what you're truly looking for is a generalized tainting mechanism.
Sounds cool, but I have only the vaguest idea what you (may) mean. Pointers?
RFCs? Examples? Hints?
--
-- Tim Conrow [EMAIL PROTECTED] |
Tim Conrow wrote:
Tom Christiansen wrote:
Perhaps what you're truly looking for is a generalized tainting mechanism.
Sounds cool, but I have only the vaguest idea what you (may) mean. Pointers?
RFCs? Examples? Hints?
Sorry for the clutter, but I didn't want to come off too clueless. I
Tim Conrow wrote:
Tom Christiansen wrote:
Perhaps what you're truly looking for is a generalized tainting mechanism.
Sounds cool, but I have only the vaguest idea what you (may) mean. Pointers?
RFCs? Examples? Hints?
Sorry for the clutter, but I didn't want to come off too clueless. I
