o makes
the ol' perl5
open FH, "|/usr/bin/foo";
make a lot more sense. Using something like
open "p", "/usr/bin/foo";
just wouldn't have the same ring to it. Aside from which, it gets even worse
when you consider how you would have to ch
> > While I don't know if Larry will mandate it, I would like this code:
> >open PAGE, "http://www.perl.org";
> >while () {
> > print $_;
> >}
> > to dump the HTML for the main page of www.perl.org to get
> dumped to stdout.
>
> Well, this seems innocent enough, but how far
> >The same is true for anything... Sometimes a minimalist approach
> >is the right way to do it... The problem is to make sure when
> >using a minimalist approach that you don't make it too small...
> I think the more important thing is to not add completely redundant
> features without a really
> David Whipp wrote:
> > > A language that doesn't have everything is actually easier to program
> > > in than some that do.
> >
> > The obvious reply is: "There's more than one way to do it"
> To which the obvious reply is:
>
> 'Although the Perl Slogan is "There's More Than One Way
> to Do
I was thinking more along the lines of "TMTOWTDI" ;-)
> -Original Message-
> From: Garrett Goebel [mailto:[EMAIL PROTECTED]]
> Sent: Friday, 20 October 2000 10:47 AM
> To: 'iain truskett'; [EMAIL PROTECTED]
> Subject: RE: What will be the Perl6 code name ?!!
>
>
> The only acceptable c
> > Some arguments for XML:
> >
> > - Done right, it could be easier to write and maintain
> Pod is already "done right", and it's already spectacularly
> easy to write and maintain. XML is a hammer in search of nail.
Actually, a better analogy would be a its a sledge hammer
in search of a fin
> > General purpose output formatting: no, nyet, nein, non, "over
> > my dead body".
> I'm guessing you mean "nyet" to "general purpose formatting *only*". :-)
>
> After sending that last email, I was sitting here drinking a beer, and
> it occured to me that tons of headers all the use same form
> > Parse the CGI context, returning CGI variables into %CGI
> Which variables are you talking about? Everything you need is already in
> %ENV, as I'm sure you're aware.
Yeah, but its encoded... %CGI in an unencoded form would be a nice
thing. :)
> If you're talking about splitting up the query
> > Perl programmers happy with the -X syntax will need to get used to the
> > lengthier replacement.
> Blech. I certainly think that long functions are fine and dandy, but I'd
> loathe the day that I'd have to give up my -X stuff. I *love* it. I'm a
> shell-head! Many Perlers are. I would not cla
> > =item perl6storm #0064
> >
> > Do something about microsoft's CRLF abomination.
>
> I think for the case of Microsoft C++ used for the Win32 port, everyone
> would be happy if Perl's sysopen, sysread, etc. did not require binmode.
> Unfortunately, Microsoft made the decision very early on in i
Apologies if these comments have already been noted...
> my $PI : constant = 3.1415926;
> my @FIB : constant = (1,1,2,3,5,8,13,21);
> my %ENG_ERRORS : constant = (E_UNDEF=>'undefined', E_FAILED=>'failed');
>
> Constants can be lexically or globally scoped (or any other new scoping
> lev
11 matches
Mail list logo
