What about Hexane? Arthropod (or some insect)?
These do habve meaning, Hexane is a six carbon hydocarbon.
Anthropods(esp. insects) have six legs...
perl object-oriented language
horrible!
a) you're using an acronym within an acronym:
Practical Extraction and Report Language
How about:
scratch #doesn't really imply what it's doing
overload#accurate, kinda long though some might say this is good
dup/duplicate #nasty for the compiler, and perhaps for the newbies,
#but dup'ing var's makes sense, esp. from the C stance
clone/mycopy
Perl, which allows object oriented syntax, written in C++ language,
^^
Did I miss something, or did the world go *totally* gaga overnight?
I think he's referring to Topaz.
All together now: Topaz is dead, Topaz never was (public).
--
How about the traditional birthstone for the 6th month (June)? That would
be Alexandrite. This has the added advantage of being named after Tsar
Alexander I, who, like Perl, was ruler over a vast domain.
Ha ha ha, obscure pun
http://www.birthstones.com/stone_jun.html
However come perl 7
Personally I think this is probably a bad idea.
But if such a thing WERE to be implemented, I don't see why you have to have
two words...
header(a1, b=2); #options list, returns a string with formatted headers
header($foo); #scalar option $foo is parsed and a list is returned
You suggested:
file($file, 'w'); # is it writeable?
Not that I'm advocating it but you do something like:
test($file, WRITEABLE);
test($file, WRITEABLE READABLE);
...
where constants are defined for various "attributes" to be tested for...
Currently 23, or 3 bytes... (not that
What's wrong with extending current syntax such that:
$a = "Hello";
print q(@{[$a]} World), "\n";
outputs
Hello World
instead of
@{[$a]} World
yes, it's a few extra char's but IMHO
it's a logical extension
it makes you think twice before doing it, do you really need to do
Oh yeah I forget to outline what it currently does for those whom may not have
seen it...
It's usally used for evaluation and interplation of code/subroutines
in "", qq() and HERE. And of course works fine on hashes, scalars, and
arrays.
So it's simply changing perl to check for this in q().
Pardon my repetitiousness, but I'm puzzled at the total lack of response
AFAICS to my proposal for a second argument to next/last/redo. Was it so
stupendously moronic as to be beneath anyone's dignity to rebut, or
what? Either I'm out of it, or it looks a whole lot more appealing than a
new
It's called meta shell
ftp://www.guug.de/pub/members/truemper/metash
--
#!/usr/bin/perl -nl
BEGIN{($,,$0)=("\040",21);@F=(sub{tr[a-zA-Z][n-za-mN-ZA-M];print;});
$_="Gnxr 1-3 ng n gvzr, gur ynfg bar vf cbvfba.";{$F[0]};sub t{*t=sub{};
return if rand().5;$_="Vg'f abg lbhe ghea lrg, abj
Since everyone seems intent on breaking backward compatibility
I don't think this is at all true, but I also don't think the overall
you seem to have ignored the paranthetical clause
idea of a Perl5 module is necessarily a bad one.
However, my hope would be that we do Perl 6 smoothly enough and
Wohoo! REBOL-isous
sub foo : doc( EOS )
Function: Foo
In:scalar - int - foo identifier
Out:array - decomposed foo
Effects: Queries Foo DB
Exceptions: DBI, "bad foo id"
EOS
{
And the liste alternatives really seem rather ugly though
How about
sub foo ($$,DOC) {
}
Not a huge issue, but I hadn't seen anyone else bring it up.
If in fact:
bareword filehandles are ditched
globs are killed
prototypes are potentially touched.
perlsub
sub myopen (*;$) myopen HANDLE, $name
sub mypipe (**) mypipe
Since everyone seems intent on breaking backward compatibility
(Okay, so no one is explicitly setting out to do so, it is merely often
dismissed as a non-issue). How about an RFC be done proposing that
perl6 ship with a module named Perl5. Which one can use to remedy
most breakings between the
In reply to your message from the not too distant future: next Monday AD
Reply-to: [EMAIL PROTECTED]
Return-receipt-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Tue, 22 Aug 2000 10:15:48 EDT
From: Jerrad Pierce belg4mit
In reply to your message from the not too distant future: next Tuesday AD
Reply-to: [EMAIL PROTECTED]
Return-receipt-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Tue, 22 Aug 2000 11:06:21 EDT
From: Jerrad Pierce belg4mit
In reply to your message from the not too distant future: next Tuesday AD
Reply-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Tue, 22 Aug 2000 12:58:38 EDT
From: Jerrad Pierce belg4mit
I think you are still confused
In reply to your message from the not too distant future: next Tuesday AD
Reply-to: [EMAIL PROTECTED]
Return-receipt-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Tue, 22 Aug 2000 13:48:36 EDT
From: Jerrad Pierce belg4mit
In reply to your message from the not too distant future: next Monday AD
Reply-to: [EMAIL PROTECTED]
Return-receipt-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Mon, 21 Aug 2000 19:04:27 EDT
From: Jerrad Pierce belg4mit
. | * . . . * / ;M\_ .
..oo. . .. . /\. / :IMM\
....oo. Jerrad Pierce /\ / \ / ;IIWMM
..oo... 209 North Street +/ \ / \ . / ;WM
In reply to your message from the not too distant future: next Friday AD
Reply-to: [EMAIL PROTECTED]
Return-receipt-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Fri, 18 Aug 2000 14:47:44 EDT
From: Jerrad Pierce belg4mit
21 matches
Mail list logo
