absolutely maximum
speed, particularly if you have good tools to parse it and turn it back
into a native format again.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
with seconds since
epoch.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
is grossly deficient in this respect, but that's an internals
rather than a language issue.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
constructs or characters, just
identifiers, function calls, and # at the beginning of a line. It still
causes a few problems where it recognizes something it shouldn't, but it's
trivial to deal with compared to m4.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
particular topic.
Instead, what about a temporary freeze when each list is created? Give it
a day or two after it's created before it will accept traffic; have the
traffic be held for that long while people subscribe. Would that help
this problem?
--
Russ Allbery ([EMAIL PROTECTED])
at's being done here is in other languages often
called shadowing. What about Cshadow?
shadow $/ = "\n";
seems to have the right implications to me.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
that there's a lot to be said for using /* ... */ for multiline
comments, but then I'm a C programmer.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
nough power for most of what people want to do and if you
want to deal with the rest you have to deal with time zone naming.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
s" and it
chops the head off.
Why do you need one-time matching here? /^$/ should work fine.
I've very rarely found cases where ?? was useful and // didn't work, and
never in regular code.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
oppose the
notion that Perl 6 will magically handle all this.
-John
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
f you call localtime
in C, you should get back local time, whatever the local time zone. The
whole point is to not try to duplicate that information in Perl core.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
that it be passed as a string, but writing something like
the above would be a *very* common new user mistake.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Jarkko Hietaniemi [EMAIL PROTECTED] writes:
s/gmt/ut/
IIRC GMT got obsoleted in the 70s by UT (Universal Time).
Officially called UTC, so utcdate would be a better name I think.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
with corrections for UT1).
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
skud [EMAIL PROTECTED] writes:
I don't think this is a language issue. However, I don't believe
there's a -doc working group yet, either.
Is it time for a -doc group to form?
[EMAIL PROTECTED] already exists; maybe it should be blessed as a Perl 6
working group as well?
--
Russ Allbery
';
@args = split (' ', $args);
my $i = 0;
%args = map { $_ = ++$i } @args;
This is very Perlish to me; the punctuation is part of the variable name
and disambiguates nicely. I'd be very upset if this idiom went away.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org
that don't start
with @, that's the mistake.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
ut context makes it quite
clear what's going on.
This strikes me as the same sort of meaningless style guideline as "all
variables must have names that are at least five characters long."
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
k by xntpd or something, but
in practice time on a Unix clock is monotonic.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
may be different (maybe
garbage collection happened behind the scenes, the hash was reorganized
due to an observation of how you were using it, etc.).
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
John Porter [EMAIL PROTECTED] writes:
Russ Allbery wrote:
$args = 'first second third';
@args = split (' ', $args);
my $i = 0;
%args = map { $_ = ++$i } @args;
This is very Perlish to me; the punctuation is part of the variable
name and disambiguates nicely.
No, it's
and could well have a
separate solution.
Perhaps @-$$hash{value} as has been proposed before, and Perl 6 can deal
with the issue of the @- array in some other way.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
g the *one* @ in that expression isn't going to make it look any
simpler.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Tim Jenness [EMAIL PROTECTED] writes:
On 14 Aug 2000, Russ Allbery wrote:
Day resolution is insufficient for most purposes in all the Perl
scripts I've worked on. I practically never need sub-second precision;
I almost always need precision better than one day.
MJD allows fractional days
Glenn Linderman [EMAIL PROTECTED] writes:
Russ Allbery wrote:
I agree with Tom; I think it's pretty self-evident that they're the
same thing. undef means exactly the same thing as null; that's not the
problem. The problem is that Perl doesn't implement the tri-state
logic semantics
e other hand, are specific to Perl and
the default is chosen to be friendly to quick and dirty scripts. Changing
those semantics to propagate undef makes perfect sense to me.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
tion
and I thought I was back in grad school. I don't think it's the fault of
the writing either; I think that Quantum::Superpositions is trying to do
something that's rather too complicated to explain clearly to the average
programmer.
It's a neat idea, but I don't expect to see it ever widely used.
, at least).
Hm, yeah, good point.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
ls to RFC 263, along the lines of "use tristate", seem to
overlook this sort of situation.
I'm not overlooking it; I just don't agree with you. There *is* a
difference.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
or not. As a matter of
fact, I find them very interesting and fully do expect to use those
semantics if they're implemented in Perl, particularly given that I'm
likely to be doing a lot more database and SQL coding in the future than I
am currently.
--
Russ Allbery ([EMAIL PROTECTED]) http
ould have been
nice. But that's just me.
As long as it's possible to get the current "perl" behavior; I actually
use that a lot.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Glenn Linderman [EMAIL PROTECTED] writes:
Russ Allbery wrote:
Perhaps I don't use those warnings in the same way that you do. I
*very* rarely have undefined value warnings in my programs, and when I
do they're usually not actually bugs, just things that require a
different way of writing
agree with you are saying that only European scripts matter. But please
don't escalate the argument as part of being offended.
I'll now stop replying to this thread. Sorry for sticking my nose in; it
really bugs me when this happens in i18n discussions.
--
Russ Allbery ([EMAIL PROTECTED
ile before realizing they're weird use English things.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
ress the syntactical points of Perl that
make it hard to read for someone who doesn't know Perl; it strikes me, and
always has struck me, as a bad partial solution to a problem that may not
need to be solved and that only makes things more complicated in the long
run.
--
Russ Allbery ([EMAIL PROTECTE
that need to do UID fiddling need to load.
I guess the exception is getpwuid($), which is probably done more than
any other operation on UIDs, but maybe just keep that single variable.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
David Olbersen [EMAIL PROTECTED] writes:
From: Russ Allbery [mailto:[EMAIL PROTECTED]]
Just out of curiosity, and I'm not objecting to this RFC, has anyone
reading this mailing list actually intentionally used a vertical tab
for something related to its supposed purpose in the past ten years
out of pack and putting it plus those
other things into a standard module.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Python.
the TIL speedup over pure interpretation might win that back and
more.
If that's true, that's a different ballgame of course.
If at all possible, Perl 6 should be *faster* than Perl 5. Perl is
already too slow IMO.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org
So since when did perl6-language become perl-advocacy? Rephrased: Could
people please take the advocacy traffic elsewhere where it isn't noise?
Thanks.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
and ended up
just being stupid and grating.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
all. sort { $a = $b } contains two functions to extract the keys.
Functions don't have to be complicated, you know.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
guaranteeing that Perl 6
would be YAPH-compatible anyway.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Uri Guttman [EMAIL PROTECTED] writes:
"RA" == Russ Allbery [EMAIL PROTECTED] writes:
RA Uri Guttman [EMAIL PROTECTED] writes:
map { $_-[0] } sort { compare($a-[1], $b-[1]) } map { [$_, f($_)] } data
^^^ ^^^
RA Then you need to
as much work anyway.
Less mental effort is the important part, not how many characters have to
be typed. I don't want to be thinking about that extra level of arrays,
and until you've written *lots* of ST's, you can't ignore it.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
t sub are called" then life
becomes much easier.
I am strongly in favor of that approach. I see no reason to allow for
weird side effects in Perl 6. (Perl 5 would be a different matter, of
course.)
Not only is it simpler to deal with, it's simpler to *explain*, and that's
important.
--
Ru
in the way
of optimizing C.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
will be fairly rarely used and that most of your gains will come
from managing to teach the compiler to figure out that information for
itself.
This will probably be harder in Perl than in C because C can afford to
take more time to do global optimization passes.
--
Russ Allbery ([EMAIL PROTECTED
Dan Sugalski [EMAIL PROTECTED] writes:
Doesn't have the right ring to it, unfortunately. It's not really
immutable, it just has no side-effects.
gcc and the literature both use "pure"; I'd recommend that.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
nst" (a la C++). I think
"pure" was proposed for the somewhat relaxed version of that that allowed
memory references but not side effects.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
, so I didn't have much additional response, apart from saying
that that was rather more Perl 5 compatibility than I was expecting.
Interesting.
Oh, and I wholeheartedly approve of the approach to handling objects.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
for running those old scripts. No biggie.
There's quite a lot more Perl 5 code out there than there was Perl 4 code.
And it's rather annoying to still be maintaining a perl4 installation at
this point for the stragglers, although I suppose that can't be helped.
--
Russ Allbery ([EMAIL PROTECTED
syntax of:
PATH=/some/long:/bunch/of:/stuff
PATH=${PATH}:/more/stuff
would really be a shame.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
-class entities rather than pointers; think
about a struct versus a pointer to a struct.
- makes you remember that things are pointers.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
David M Lloyd [EMAIL PROTECTED] writes:
On 24 Apr 2001, Russ Allbery wrote:
The switch from - to . makes perfect sense from a C perspective if we're
turning objects into first-class entities rather than pointers; think
about a struct versus a pointer to a struct.
- makes you remember
dereferencing), then using . to access object
members is entirely compatible with C.
I tried to make this point before, but I don't think people understood
what I was getting at.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
to make
practical ideas already explored in other practical and experimental
languages.
Perl is far more practical than experimental.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
nearly everything that was proposed back to C, Lisp,
or Generic Object-Oriented Language, if not in inspiration than at least
in fundamental similarities.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
I, actually... it's sort of growing on me.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
raptor [EMAIL PROTECTED] writes:
I was looking at Interbase SELECT syntax and saw these two handy
shortcuts :
operator = {= | | | = | = | ! | ! | | !=}
! and !
How is ! different from =?
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Sterin, Ilya [EMAIL PROTECTED] writes:
From: Russ Allbery [mailto:[EMAIL PROTECTED]]
How is ! different from =?
It's just more syntax just like foo != bar
is the same as (foo bar || foo bar).
It might prove convenient to express the expression.
It's the same number of characters. How
language I've ever seen uses = and =. I think
adding additional comparison operators not found in any other language and
identical to (and harder to type than!) existing operators is a really bad
idea.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
of that.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
63 matches
Mail list logo
