On Wed, Aug 09, 2000 at 06:37:07PM -0700, Jon Ericson wrote:
=item 33 (v1): Eliminate bareword filehandles. (language)
No discussion.
Using "$fh = open()" accomplishes this. I think everyone is in
agreement that bareword filehandles must go.
=item 39 (v1): print operator
No
Nick Ing-Simmons [EMAIL PROTECTED] writes:
Graham Barr [EMAIL PROTECTED] writes:
On Wed, Aug 09, 2000 at 11:41:42AM -0500, Jonathan Scott Duff wrote:
How about this?
open '/etc/passwd'; # file
OK
open '/usr/local/bin/'; # directory (note the trailing
N. Hao Ching [EMAIL PROTECTED]:
The default input record separator is not safe for all input files
on all platforms. There should also be support for Unicode line
separator (U+2028) and paragraph separator (U+2029).
I disagree. Perl should provide the greatest ease for the greatest
number
On Thu, 10 Aug 2000, Perl6 RFC Librarian wrote:
Given this input file:
D O S CR LF0044 004F 0053 000D 000A
U n i x LF0055 006E 0069 0078 000A
M a c CR 004D 0061 0063 000D
l i n e LS006C 0069 006E 0065 2028
p a r a PS0070 0061 0072 0061 2029
How about this?
open '/etc/passwd'; # file
open '/usr/local/bin/'; # directory (note the trailing '/')
open 'ftp://ftp.perl.org/'; # ftp
open 'http://www.yahoo.com/'; # http
open 'ldap://ldap.bigfoot.com/';# ldap
I think
This is nutso... shall we open-ssh and open-telnet and
open-any_protocal_under_the_sun in the core?
Well, just because the hooks are there doesn't mean all the member
modules have to be in core. The idea would be, as Tom Hughes suggests:
That is if the core provides a way for modules to
I completely disagree. How do you know that I want 5 lines.
Perhaps I want only 3?
You are assuming that within my file I will want all possible line
endings to be line endings. That is simply not true.
You might want to argue for the perl IO subsystem to intuit the line
ending (note the
