t; so that the default is to call the uri stuff.
Is it just me, but I keep wondering how Uri Guttman gets into this.
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
'm asking, what does one do while switching around file descriptors
and an error is returned. Is there anywhere to report it?
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
re that just writing portable filenames. It means having
NW> Perl understand http://, ftp://, etc, etc, so that it can do something
NW> "really cool" with it. The upcoming v4 of RFC 14 will show how this is
NW> an advantage.
NW> -Nate
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
x27;t think it will
do anything useful on any of my *nix boxes.
PRL>unlink "/local/etc/script.conf"; # non-portable
PRL>unlink "file:///local/etc/script.conf";# portable
Nor this on a dos box.
--
Chaim FrenkelNonlinea
Mr. Dan,
Calling Mr. Dan...)
>>>>> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
NW> Chaim Frenkel wrote:
>>
>> >>>>> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
>>
NW> # Replaced by 'open sys'
NW> sy
ere opened via standard
open. It bypasses the stdio library.
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
>>>>> "DLN" == David L Nicol <[EMAIL PROTECTED]> writes:
DLN> Chaim Frenkel wrote:
>>
>> Sitting on a unix box, and getting to C: on a windows box?
DLN> That implies a whole pile of implementation details. Are you
DLN> suggesting a Perl Or
form-independent naming scheme.
I'm not sure that it covers all the bases.
It covers the universe that web servers are designed to handle. But
what about the universe of devices. Or remote access to mounted
volumes? Sitting on a unix box, and getting to C: on a windows box?
I'll wait
planning to have a direct perl <-> os layer.
(A rewrite/stealing^wborrowing from sfio?)
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
resentation. If you are
JH> opening a file with open() or sysopen(), you supply a string with your
JH> native FS semantics and think no more of it.
What RFC? I couldn't find it on http://dev.perl.org/rfc/
Please explain why internally it needs to be represented as anything
o
:Generic "."
$resource->name = "new name with all other parts left alone";
$fh = open $resource->asNativeFormat()
Blech, but possible.
(Stolen parphrased but liberally from the Symbolics manual)
--
Chaim Frenkel
me"
,Type=>"txt"
,Version=> ":oldest"
);
Seems messy.
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
>>>>> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
NW> Chaim Frenkel wrote:
>>
>> The VMS (and TOPS20) advocates will scream here. Versions are part of
>> the file name. The default is the latest version. But the filesystem
>&g
vers?
Will open take over the work of socket() and family? What is the
resource supposed to look like?
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
file name. The default is the latest version. But the filesystem
automatically versions files.
Hmm, if we support versioning files, will perl have to support emacs
versioned files? /foo/bar/bash.c.~356~
--
Chaim FrenkelNonli
or :: or ?
NW> So trace this call:
NW>$fo = open "C:\Windows\System\IOSUBSYS\RMM.PDR";
NW>$fo->pathdrive = "C:" ;
NW>$fo->patharray = [ Windows, System, IOSUBSYS, RMM.PDR ];
NW>$fo->pathdelim = "\";
NW> So, this would b
gt; :mod=split
BCW> :mod=\&do_some_funky_pre_processing
BCW> That would allow you to do stuff like the following.
BCW> open FOO, "foo_file", :text=ascii, :line=unix, :mod=chomp;
BCW> while ()
BCW> {
BCW># $_ = an ascii line, delimited
blities of the os.
PRL> Given this input file:
PRL> D O S CR LF0044 004F 0053 000D 000A
PRL> U n i x LF0055 006E 0069 0078 000A
PRL> M a c CR 004D 0061 0063 000D
PRL> l i n e LS006C 0069 006E 0065 2028
PRL> p a r a PS 0070 00
ame time.
SH> Why not?
SH> Well, how about this proposal then?
SH> DOS, Mac, Unix:
SH> use newlines "\015\012", "\012", "\015";
SH> OS/390:
SH> use newlines "\r", "\025";
SH> Weird OS
s possible:
PRL> my @lines = ;
PRL> The @lines array should contain five elements.
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
?
>> >>
>> >> open '/etc/passwd'; # file
>> >
>> >OK
>> >
>> >> open '/usr/local/bin/'; # directory (note the trailing '/')
>> >
>> >Portability, not all platf
aid that they would simply
JE> replace the file-globbing mode found in perl 5.
Please adjust that. My concern was for the parsing of some arbitrary
complex expression.
Hmm, I'll offer this as an alternative <{ hairy expression }>
Then the parser can switch to block,
>>>>> "BCW" == Bryan C Warnock <[EMAIL PROTECTED]> writes:
BCW> On Wed, 09 Aug 2000, Chaim Frenkel wrote:
BCW> Isn't that what the nebulous line disciplines are supposed to handle?
>>
>> Has anyone taken on RFCing line disciplines?
BCW>
uld call the function until the results are exhusted.
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
e http and ftp that
TH> it knows how to handle and open's for those types would be handed
TH> off to the registered handler.
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
>>>>> "BCW" == Bryan C Warnock <[EMAIL PROTECTED]> writes:
BCW> Isn't that what the nebulous line disciplines are supposed to handle?
Has anyone taken on RFCing line disciplines?
--
Chaim FrenkelNon
>>>>> "JE" == Jon Ericson <[EMAIL PROTECTED]> writes:
JE> Chaim Frenkel wrote:
>> What does
>>
>> $foo = <"filename">;# 1
>> $bar = <"another">;
>> $gaz = <"filename>; # 2
JE>
>>>>> "BL" == Bart Lateur <[EMAIL PROTECTED]> writes:
BL> On 09 Aug 2000 12:00:55 -0400, Chaim Frenkel wrote:
>> There was no mention of cross-platform line-ending support.
>> I suggested a while ago on p5p an improved binmode(), that might do
ms of intuiting line-endings is an open issue. I don't want
perl getting in my way without being asked.
I suggested a while ago on p5p an improved binmode(), that might do
such magic among other things.
>>>>> "BL" == Bart Lateur <[EMAIL PROTECTED]> writes:
BL&
When the first item returns undef, the next item is read.
PRL> When there are no more items left, undef is returned.
PRL> Inside a while loop (or the conditional section of a for(;;) loop), $_
PRL> is assigned to the next line (or file) and tested for defined-nes
t least match /\015?\012/, so that the following works on as many
PRL> platforms as possible:
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
s C call,
PRL> then the file routines could potentially be highly-optimized, since
PRL> there would only have to be one core set. If possible, this is what I'd
PRL> like to see.
--
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
32 matches
Mail list logo
