Peter Scott wrote:
Only one of them needs to be right. As long as one is right,
there is no problem.
Right, I was just pointing out that it's harder for people to divine which
one we picked without recourse to the documentation.
Yes; unfortunately, this problem exists generally,
or AUTOLOAD can be defined in terms of Ccatch
and overloaded that way, rather than being its own
kind of magic.
catch "AUTOLOAD-$classname-$polymorphicsignature" {...
Jonathan Scott Duff wrote:
On Wed, Aug 16, 2000 at 12:15:30PM -0500, David L. Nicol wrote:
If "catch" can be
At 07:00 PM 8/16/00 -0400, Chaim Frenkel wrote:
Perhaps, throw can carry a return value?
throw {"return value"} $exception;
If there is an active try/catch context then the $exception would
be propogated, otherwise $@ would get loaded with $exception and
the return value would be the
At 07:10 PM 8/16/00 -0400, Chaim Frenkel wrote:
"PS" == Peter Scott [EMAIL PROTECTED] writes:
PS 1. When an exception is thrown perl looks for the enclosing try block; if
PS there is none then program death ensues.
Err, if there isn't one. Don't throw the exception. Stop processing but
don't
"DLN" == David L Nicol [EMAIL PROTECTED] writes:
DLN =head2 eval/die remains perfectly workable
DLN as "die" is a perfectly serviceable method or raising an exception.
Actually, die is pretty nasty. Modules can't use it.
Another mechanism that means, short circuit, but let the user know
"PS" == Peter Scott [EMAIL PROTECTED] writes:
PS At 07:00 PM 8/16/00 -0400, Chaim Frenkel wrote:
Perhaps, throw can carry a return value?
throw {"return value"} $exception;
If there is an active try/catch context then the $exception would
be propogated, otherwise $@ would get loaded with
"PS" == Peter Scott [EMAIL PROTECTED] writes:
PS At 07:10 PM 8/16/00 -0400, Chaim Frenkel wrote:
"PS" == Peter Scott [EMAIL PROTECTED] writes:
PS 1. When an exception is thrown perl looks for the enclosing try block; if
PS there is none then program death ensues.
Err, if there isn't one.
Peter Scott wrote:
If that were so, even without the ignore() function, I could just say
sub Exception::IO::throw { 'do nothing' }
and kill it that way.
Right. Just like overriding core die. At that point you can
change the semantics in such a way as to turn your code into
Executive summary: I no longer want catch blocks to "daisy chain"
after a exception is thrown in a catch block. Thanks to everyone
who has helped me see the light on this.
Peter Scott wrote:
At 01:16 AM 8/16/00 -0600, Tony Olekshy wrote:
The proposed omnibus Exceptions RFC uses the
Peter Scott wrote:
Tony Olekshy wrote:
[snip]And the following output was generated:
Exception
$ = Try::throw('Exception') called from scott2.pm[8].
$ = main::pling('Test') called from scott2.pm[4].
$ = main::bar('Test') called from scott1.pl[1].
$ =
On Wed, Aug 16, 2000 at 11:49:03AM +0100, Graham Barr wrote:
if any of the catch or finally throws, it is caught by a
try {} block up the stack.
Keep It Simple
What he said.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
I do not know what advantages the try statement would have in perl.
However, in Java programming it makes exception handling more explicit. It
basically allows the programmer to "try" a certain action and see what the
effects are going to be (i.e. handle the exception) so that some action can
[EMAIL PROTECTED] (Tony Olekshy) wrote on 15.08.00 in
[EMAIL PROTECTED]:
What if we implemented something like the following?
Seems that the basic unwinder is
except { ... } = catch { ... }
and everything else can be written in terms of this:
catch { ... }
except { 1 } = catch
On 16 Aug 2000, Perl6 RFC Librarian wrote:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Implicit counter in Cfor statements, possibly C$#.
=head1 VERSION
Maintainer: John McNamara [EMAIL PROTECTED]
Date: 16 Aug 2000
Version: 1
-Original Message-
From: Barrie Slaymaker [mailto:[EMAIL PROTECTED]]
[EMAIL PROTECTED] wrote:
It basically allows the programmer to "try" a certain action and see what
the
effects are going to be (i.e. handle the exception) so that some action
can
then be taken based on the results
[EMAIL PROTECTED] wrote:
It basically allows the programmer to "try" a certain action and see what the
effects are going to be (i.e. handle the exception) so that some action can
then be taken based on the results of the exception.
Seems like any BLOCK could be an implicit eval {...} or try
I'll try to scrap and rewrite the RFC this weekend.
$/ = qr/[\r\n]/f; # fast ?
How about we use the specialized DFA regex, but also slightly
different notation?
-Hao
Chaim Frenkel [EMAIL PROTECTED] writes:
What about native extensions? I think VMS (and the old TOPS10) had versions
as part of the file name.
Do URIs have this capablity?
And what does a read of a directory return? URIs or Native?
Relative URIs I assume - what are (hopefully) indistinguishable
Michael Fowler [EMAIL PROTECTED] writes:
On Sat, Aug 12, 2000 at 08:49:00AM -, Perl6 RFC Librarian wrote:
In addition, this RFC recommends deprecating select(), since it is no
longer needed with the new fileobject approach described in RFC 14.
You should probably mention here that the
So, what's so portable about file:// URLs again? How do they magically
know that //c/ means / on UNIX? What do they do with //z/?
This is only one example. I'm not sure it's the best way. It's
definitely not the only way. Chaim asked:
Or for that matter "file://u/frankeh/Projects" become?
Graham Barr wrote:
Create a new handle, like $DEFOUT. Then there would be no need
for selectsaver either as you would do the equiv. of
local($DEFOUT) = $newhandle;
Just submitted an RFC on this exact idea.
-Nate
Kai Henningsen wrote:
1. Package variables $package::var, presumably you'd have to declare those
and the default would be
2. lexical variables,
Not bad, but I think #1 violates Laziness if I hear you right. Let's add
a "global" or "your" keyword to do this inside a package:
package
Damian Conway [EMAIL PROTECTED] writes:
Why would anyone want to select a different method based upon the
arguments.
Have you seen Class::Multimethods? This kind of despatch can be very
useful. Of course, the existence of Class::Multimethods proves that it
can be
On Tue, Aug 15, 2000 at 11:46:04PM -0400, Stephen P. Potter wrote:
Why is it silly? Hashes and arrays are *conceptually* very similar (even
if they are extremely different implementation-wise). One of them has
implicit key, the other has an explicit key. They both provide some sort
of
On Tue, Aug 15, 2000 at 10:26:13PM -0600, Nathan Torkington wrote:
I like the idea of adding the context-aware operators, but I don't
think I'd use them as often as I use "the number of things in the
array". I think most Perl programmers would be in the same camp.
Unless you can show a
Mark Cogan wrote:
At 12:39 PM 8/16/00 +1000, Jeremy Howard wrote:
It seems obvious that @a should be the whole array @a, not the size of
the
array. If I want to check the size of @a, I should have to do so
explicitly,
with scalar or $#.
This is non-obvious if you think that || is a flow
At 04:02 PM 8/16/00 +1000, Jeremy Howard wrote:
Nathan Torkington wrote:
Your [Jeremy's] RFC says:
Currently, operators applied to lists in a list context behave
counter-intuitively:
Counter-intuitively is different from consistently. Your title is
misleading. Perl's ops *are*
Damien Neil [EMAIL PROTECTED] writes:
Arrays are ordered. Hashes are not. Sure, you can iterate over a hash,
but add an element to one and you can change the order of everything in
it.
Formally, I believe it's permissable for a hash implementation to return a
different order the second
Mark Cogan wrote:
At 11:11 PM 8/15/00 -0400, Chaim Frenkel wrote:
You are missing the beauty of vector/matrix operations.
No, I'm not; I'm opining that the vast majority of Perl users don't need
to
do vector/matrix ops, and that they don't belong in the core.
The vast majority of Perl 5
Please take this discussion to perl6-language-datetime. Thanks!
K.
--
Kirrily Robert -- [EMAIL PROTECTED] -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949 Fax: +61 3 9614 0948 Mobile: +61 410 664
On Tue, Aug 15, 2000 at 09:27:23PM -0700, Ask Bjoern Hansen wrote:
LIST: perl6-language-objects
CHAIR: Nathan Wiger [EMAIL PROTECTED]
MISSION:Develop RFCs related to objects and OO programming in
Perl, possibly rationalising existing RFCs where they
OK, weekly report. Ugh.
The language group has generated the vast majority of the 100+ RFCs in
existence, and is suffering under the deluge of 100-200 posts a day. I
would prefer this to be down around 50, but no luck yet :-/ Part of the
problem seems to be timezone related... the lag time
Nathan Torkington wrote:
Not every subroutine corresponds to a method call exposing
object-internal data. Most of my subroutines *do* something and make
no sense to be called lvaluably. Explicit marking the compiler pick
up assignments to non-lvaluable subroutines. It makes sense to
"Randal L. Schwartz" wrote:
What would be NICE is to treat @stonehenge here as *always* a variable
So, I'd support a modification to the RFC that does what Larry intended
here:
array interpolation should work exactly like scalar interpolation
That was actually the intent of the
(reply-to set to bootstrap)
On Wed, Aug 16, 2000 at 01:36:47AM -0600, Tony Olekshy wrote:
On this matter, should something like this be a (meta) RFC?
Guidelines for Developing Changes for Perl 6 (v0.1).
There's nothing to stop you writing an RFC on whatever you like :)
However, there's
Nathan Wiger [EMAIL PROTECTED] writes:
Jarkko Hietaniemi wrote:
The $a and $b of the sort comparator were A Bad Idea to begin with.
Ditto. Can we ditch these in Perl 6? Don't see why $_[0] and $_[1] can't
be used, or even a more standard $1 and $2. Either one makes it more
obvious
There's also the cut operator which I didn't see mentioned in the RFC.
It blocks backtracking so that something like this:
B1 andthen B2 andthen cut B3 andthen B4 andthen B5
wouldn't backtrack to B2 once it forwardtracked to B3.
]- I tried minimalistic approach as small as possible
They behave similarly like , ||, and, or operator with one main
distinction they "backtrack" for example:
{ block1 } Bandthen { block2 };
This would be a good use of the to-be-liberated = operator:
{ block1 } = { block2 };
In any case, "andthen" doesn't seem like a good choice.
raptor wrote:
]- I tried minimalistic approach as small as possible additions to the
Perl
language, we get only the "backtrack" mechanism i.e. something that is
harder or slower to be done outside of the perl core.
The rest should be done outside . (I too want all in the core)
I don't
Nathan Wiger [EMAIL PROTECTED] writes:
Nathan Torkington wrote:
Not every subroutine corresponds to a method call exposing
object-internal data. Most of my subroutines *do* something and make
no sense to be called lvaluably. Explicit marking the compiler pick
up assignments to
"J. David Blackstone" [EMAIL PROTECTED] writes:
I find the standard prefix symbols so intuitive I find it hard to
articulate the reasons why I balk at giving them up. It's like
explaining breathing or the ability to distinguish colors.
Bravo! What he said! Hear, hear!
[FX: Waves order
[EMAIL PROTECTED] writes:
Please take this discussion to the new -errors sublist. Thanks in
advance!
Exceptions are not necessarily errors. This belongs in
perl-language-flow surely?
--
Piers
On Tue, Aug 15, 2000 at 05:10:34PM -0400, Dan Sugalski wrote:
Let's not move backwards and force people to work like machines. Instead,
lets force machines to work like us.
I dred to think what kind of machine we would make :)
Graham.
Lightning flashed, thunder crashed and "Jeremy Howard" [EMAIL PROTECTED] whispered:
| No, neither proposal makes sense. Arrays can be stored compactly and
|
| $a[1_000_000_000] = 'oh, really?' # :-)
|
| my int @a: sparse;
| $a[1_000_000_000] = 'Yes, really!' # :P
|
| OK, so I cheated...
On Wed, 16 Aug 2000, [EMAIL PROTECTED] wrote:
The language group has generated the vast majority of the 100+ RFCs in
existence, and is suffering under the deluge of 100-200 posts a day. I
would prefer this to be down around 50, but no luck yet :-/ Part of the
problem seems to be timezone
Stephen P. Potter wrote:
Lightning flashed, thunder crashed and "Jeremy Howard" [EMAIL PROTECTED]
whispered:
| No, neither proposal makes sense. Arrays can be stored compactly and
|
| $a[1_000_000_000] = 'oh, really?' # :-)
|
| my int @a: sparse;
| $a[1_000_000_000] = 'Yes,
This has already been done for Perl 5.6.1. Here is what perldelta.pod
has to say.
=head2 Arrays now Always Interpolate Into Double-Quoted Strings
In double-quoted strings, arrays now interpolate, no matter what. The
behavior in perl 5 was that arrays would interpolate into strings if
the
Lightning flashed, thunder crashed and Jonathan Scott Duff [EMAIL PROTECTED]
whispered:
| Um, it's not guaranteed to blow up in 2038. That's an implementation
| detail. IF we implement our time values as 64-bit integers (for
| instance), we'll long out-live the 2038 deadline.
I don't know
Johan Vromans wrote:
Damian Conway [EMAIL PROTECTED] writes:
As I understand things:
BLOCK1 andthen BLOCK2
evaluates BLOCK1 and then if BLOCK1 evaluates to "true" evaluates
BLOCK2. If BLOCK2 evaluates to "true" we're done. If BLOCK2
evaluates to
On Wed, Aug 16, 2000 at 12:14:09AM -0700, Nathan Wiger wrote:
No problem. In fact, this fits under your rules. HOWEVER, it also
assumes that Lincoln thought that param() was :lvalue-worthy. What if he
forgot? Or didn't think of this case?
Then you email him with a patch, and your reasons why
On Wed, Aug 16, 2000 at 09:49:36AM -0400, Stephen P. Potter wrote:
Lightning flashed, thunder crashed and Jonathan Scott Duff [EMAIL PROTECTED]
whispered:
| Um, it's not guaranteed to blow up in 2038. That's an implementation
| detail. IF we implement our time values as 64-bit integers
On Aug 15, 3:16pm, Russ Allbery wrote:
Wholeheartedly agreed. If something is an array, it should start with @.
If we're adding language changes that introduce arrays that don't start
with @, that's the mistake.
Agreed, but with a slight change of perspective. I don't think it's
so
At 11:46 PM 8/15/00 -0400, Stephen P. Potter wrote:
Lightning flashed, thunder crashed and Dan Sugalski [EMAIL PROTECTED] whispered:
| Doesn't it make more sense to get rid of arrays and just use hashes?
|
| I guess it depends on what you think makes sense; but it seems to me
| that an array
"MC" == Mark Cogan [EMAIL PROTECTED] writes:
is equivalent to
@a = (\$a, \$b, \$c);
rather than what you wrote.
MC Ah, so it is. I'd argue that that's broken and should be handled with map
MC or for.
Err, That's not an accident. Larry designed that in.
chaim
--
Chaim Frenkel
I'm not sure if you are disagreeing with me or not.
The context was the statment that $STDOUT is the _default_ filehandle.
I was pointing out that by _overriding_ the instantaneous meaning of
$STDOUT to the default fail handle, one would lose the immediate
access to the previous value.
I.e.
Lightning flashed, thunder crashed and Russ Allbery [EMAIL PROTECTED] whispere
d:
| Arrays are ordered. Hashes are not. Sure, you can iterate over a hash,
| but add an element to one and you can change the order of everything in
| it.
|
| Formally, I believe it's permissable for a hash
"BB" == Buddha Buck [EMAIL PROTECTED] writes:
BB I am assuming that the system clocks are set accurately to UTC (or some
BB derivative, like (US) Eastern Standard Time). UTC is what time-servers
BB report. UTC has leap seconds, which are inserted (or, theoretically,
BB deleted) at the end
Nathan Wiger wrote:
Ok, here goes. First off, I *did* read the RFC. I never respond before
Thanks, this response is more like it.
reading. Personally, I wish people would quit coming up with these silly
"let's drop the prefixes" RFC's that everyone on this list is completely
familiar with.
Nathan Torkington wrote:
* you misunderstand the purpose of $ and @, which is to indicate
singular vs plural. You say a $ indicates a string or number,
but really it indicates a single thing. Similarly @ isn't just
a variable marker, it's used to indicate that you get multiple
Damien Neil wrote:
On Tue, Aug 15, 2000 at 05:45:04PM -0400, Karl Glazebrook wrote:
I hope people will actually read the RFC before coming back with these
canned responses which I (and presumably everyone else on this list)
am completely familiar with. I used to believe that too!
"J. David Blackstone" wrote:
=head1 TITLE
Less line noise - let's get rid of @%
I understand that with the pervasiveness of object-orientation we
are now more than ever seeing objects that behave like arrays and
hashes and that it seems strange to see these listlike or hashlike
(Not feasible yet, but...)
Would Unicode reduce the problem? Take some operators from the math symbols
and make them the matrix op versions?
Then the 'ascii' versions would remain the scalar ops.
I can see that this would give problems for current editors and displays,
but by the time perl6
Lightning flashed, thunder crashed and Perl6 RFC Librarian [EMAIL PROTECTED]
whispered:
| =head1 TITLE
|
| Builtin: partition
|
| =head1 ABSTRACT
|
| It is proposed that a new function, Cpartition, be added to Perl.
| Cpartition($partition_size, \@list) would return @list broken into
|
Damian Conway wrote:
So how is that different from:
do BLOCK1 until do BLOCK2
???
Because if BLOCK1 ever evaluates to False, the operation terminates.
It's more like
do { r = f1() } until ( not r or f2() );
--
John Porter
Lightning flashed, thunder crashed and Nathan Wiger [EMAIL PROTECTED] whisper
ed:
| I suggest a modification to this RFC: if chomp() is called without args,
| it modifies $_ directly, consistent with its current implementation.
| That way you can write:
If it is called without args, it really is
On Wed, Aug 16, 2000 at 07:42:33PM +1000, Jeremy Howard wrote:
raptor wrote:
]- I tried minimalistic approach as small as possible additions to the
Perl
language, we get only the "backtrack" mechanism i.e. something that is
harder or slower to be done outside of the perl core.
The rest
Darn, I sent this to perl6-announce instead of perl6-language.
Let's try again.
--- Forwarded mail from "Andy Wardley" [EMAIL PROTECTED]
I thought very carefully about this before writing the Highlander
Variables RFC, and came to the conclusion that it's a bad idea.
I've read your proposal,
"Stephen P. Potter" [EMAIL PROTECTED] writes:
Lightning flashed, thunder crashed and Russ Allbery [EMAIL PROTECTED] whispere
d:
| Arrays are ordered. Hashes are not. Sure, you can iterate over a hash,
| but add an element to one and you can change the order of everything in
| it.
|
chomp should have options to define what an EOL is.
Many times, on Solaris, I could not use chomp because I had to use
=~ s/[\n\r ]$//
on files that came from NT or even from MS-oriented unix editors.
On Wed, Aug 16, 2000 at 03:04:19PM -, Perl6 RFC Librarian wrote:
=head1 ABSTRACT
Provide a simple way of giving a count of matches of a pattern.
We already have this:
$count = () = m/foo/g;
=head1 DESCRIPTION
m//gt would be defined to do the match, and return the count of
On Wed, Aug 16, 2000 at 03:05:23PM -, Perl6 RFC Librarian wrote:
=head1 ABSTRACT
With a here doc print ZZZ; the ZZZ has to be at the start of a line and
the text of the here doc, is processed verbatum. This results in Here Docs
that either stick out in the code, or result in unwanted
At 10:37 AM 8/16/00 -0400, Chaim Frenkel wrote:
"BB" == Buddha Buck [EMAIL PROTECTED] writes:
BB If we have to pick and epoch in an OS-neutral way, I think I for one
BB would be happy with something like this in the docs for the time
BB functions:
Would you be happy with the following edits?
On Aug 16, 9:06am, Jonathan Scott Duff wrote:
Passing the lvalue via some other means eliminates this problem. I
forget who suggested it (Buddha Buck?) but
sub foo : lvalue($value) { ... }
That should tie in with function prototypes in general, but I suspect
that the prototype should
Nathan Torkington wrote:
Perl makes easy things easy. Hashes are bloody useful, as the last
decade of Perl has borne out. They deserve syntactic support because
they're used a lot and are worthy of a shorthand.
my @aa :assoc;
$aa['foo'] = 'bar';
Is no one getting my
Chaim Frenkel wrote:
Unless one wants to have a $DEFAULT filehandle and get rid of single
arg select.
Great minds think alike. :-)
I'm in the process of codifying an RFC that will be titled something
like:
"Replace default filehandle / select with $OUTPUT fileobject"
(chose $OUTPUT b/c
Chaim Frenkel wrote:
Would Unicode reduce the problem? Take some operators from the math symbols
and make them the matrix op versions?
(Now, if we add all that APL symbols ...)
Chaim, I think you are on to something here. But before jumping to Unicode or APL
to get more line noise, let's
On 16 Aug 2000, Perl6 RFC Librarian wrote:
Have you ever wanted to count the number of matches of a patten? s///g
returns the number of matches it finds. m//g just returns 1 for matching.
Counts can be made using s//$/g but this is wastefull, or by putting some
counting loop round a
Jarkko Hietaniemi wrote:
Arrays can be stored compactly and
$a[1_000_000_000] = 'oh, really?' # :-)
But that is far less common than
@a{ 0..100 } = (...);
which, if stored in a hash, would not only be significantly less
efficient than an array, but could generally be expected to elicit
And if lvalue access were made the only way of doing assignment of
params in this context then a whole bunch of the code in param could
be removed.
Maybe this is the confusion. I'm not saying subs should ONLY be lvalue.
I think they should be both rvalue and lvalue at the same time.
Peter Scott wrote:
At 05:33 PM 8/15/00 -0400, John Porter wrote:
The thing I don't like about C++/Java try/catch syntax is the way
the blocks are daisychained. That is not intuitive to the flow.
I find it quite intuitive :-)
I note the smiley.
What interpretation should be placed on
On Wed, Aug 16, 2000 at 10:20:28AM -0500, Jonathan Scott Duff wrote:
m//gt would be defined to do the match, and return the count of matches, this
leaves all existing uses consistent and unaffected. /t is suggested for
"counT", as /c is already taken. Using /t without /g would be result
On Aug 16, 8:32am, Nathan Wiger wrote:
Maybe this is the confusion. I'm not saying subs should ONLY be lvalue.
I think they should be both rvalue and lvalue at the same time.
Point noted and understood, but I'm with the general consensus here.
Lvalue subs should have to be explicitly marked
On Wed, Aug 16, 2000 at 04:41:33PM +0100, Graham Barr wrote:
On Wed, Aug 16, 2000 at 10:20:28AM -0500, Jonathan Scott Duff wrote:
m//gt would be defined to do the match, and return the count of matches, this
leaves all existing uses consistent and unaffected. /t is suggested for
Ooops! The author didn't use :lvalue. So even though this makes perfect
sense to be able to do, since the author forgot to use :lvalue, you lose
a really cool syntactic tool. This seems backwards.
Seems right to me. I'd rather assignment to a function work on
purpose rather than on
On Wed, Aug 16, 2000 at 10:27:17AM -0400, Karl Glazebrook wrote:
Nathan Torkington wrote:
* current typing provides rudimentary compile-type checking.
Saying:
$foo = (1,3,5);
gives a warning. Saying:
this would create a $foo array
If () are array constructors, what is
Johan Vromans wrote:
So how is that different from:
do BLOCK1 until do BLOCK2
It's the same.
No, not quite. See my other post.
--
John Porter
On Wed, Aug 16, 2000 at 08:40:18AM -0700, Nathan Wiger wrote:
See, I don't see it as that big a deal, especially not if lvalue and
rvalue subs work identically.
Hrm. Perhaps you aren't explaining yourself clearly. Let's pretend
that there is a magical value called $LVALUE that contains the
On Wed, Aug 16, 2000 at 10:49:16AM -0500, Jarkko Hietaniemi wrote:
On Wed, Aug 16, 2000 at 04:41:33PM +0100, Graham Barr wrote:
On Wed, Aug 16, 2000 at 10:20:28AM -0500, Jonathan Scott Duff wrote:
m//gt would be defined to do the match, and return the count of matches, this
leaves all
print @{ $cars-{$model} };
print "Welcome back, $fullname, to $website!\n";
O.k., I'm convinced.
Only $scalars can hold objects. Now, @arrays and %hashes can
hold groups of objects, but only $scalars can hold objects.
That's not quite correct. @array or %hash can "hold" an object,
Damien Neil wrote:
I like being able to treat arrays and hashes differently from other
things. ... I know, just by looking
at the expression, with absolutely no further knowledge of what the
function and variable involved are, the general nature of what is
going on. I know whether the
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 not. Where are we taught this? It's
On Wed, Aug 16, 2000 at 10:38:30AM -0600, John Barnette wrote:
John Porter wrote:
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
Jonathan Scott Duff wrote:
Gee, I'd hate to lose simple assignment to a hash from a list.
foo %= bar;
Hmm, I think I need to write an RFC!
--
John Porter
At 11:09 AM 8/16/00 -0400, John Porter wrote:
Dan Sugalski wrote:
Numbers and strings really aren't different things, at least not as far as
people are concerned. They are for machines, but computer languages
ultimately aren't for machines, they're for people.
I guess I can't fault you
Karl Glazebrook wrote:
The tie interface is not very useful for multidim arrays, you have
to say
$x[42][44][49]
and do multiple levels of tieing whereas one just desires to say
$x[42,44,49]
But if that is indeed what you desire to say, then there is only
one level, and tie becomes
On Wed, Aug 16, 2000 at 12:44:50PM -0400, John Porter wrote:
Jonathan Scott Duff wrote:
Gee, I'd hate to lose simple assignment to a hash from a list.
foo %= bar;
Hmm, I think I need to write an RFC!
I'll give you my comments right now ... It seems we are eliminating
No, it's not. Where are we taught this? It's a myth.
The punctuation imposes context on the variable expression.
$foo[0]
accesses an array. Where's the "@"?
It accesses an *element* of the array, which is a scalar. This scalar
might be blessed into a class, or a
On Wed, Aug 16, 2000 at 10:24:09AM -0400, Karl Glazebrook wrote:
It was the response which was blithe, it just re-iterated arguments we
are all completely familar with and did not address my point in the RFC.
Then perhaps we need to agree to disagree. I feel that a number of
people have
On Wed, Aug 16, 2000 at 12:44:50PM -0400, John Porter wrote:
Jonathan Scott Duff wrote:
Gee, I'd hate to lose simple assignment to a hash from a list.
foo %= bar;
No, wait, that obviously leaves the modulus of division scalar foo by
scalar bar to foo... No, wait, tha obviously
John Barnette wrote:
John Porter wrote:
The punctuation imposes context on the variable expression.
$foo[0]
accesses an array. Where's the "@"?
It accesses an *element* of the array, which is a scalar.
Still, the "$" does not describe the type of the variable, which
in this
1 - 100 of 194 matches
Mail list logo
