On Wed, 25 Apr 2001 15:52:47 -0600 (MDT), Dan Brian wrote:
the idea of a dereference operator dumbfounds lots
of folks. What's an object got to do with a reference, much less a
pointer? A p5 object is very confusing to others for this reason, and so
is the syntax.
So you want a method
On Wed, Apr 25, 2001 at 07:23:47PM -0700, Edward Peschko wrote:
On Thu, Apr 26, 2001 at 03:16:46AM +0100, Simon Cozens wrote:
SPACE SENSITIVE and SOME OF US HAVE TO TEACH IT. Do you understand yet?
Just for the record, I'm totally with Simon here. Having . do triple
duty (decimals, method
On Thu, 26 Apr 2001 10:15:14 +0200, Bart Lateur wrote:
For example, in
-3.4
and in
2-3.4
the - sign is a *different* kind of operator. No conflict.
Well alright, in the first line, the - might be part of the number.
Replace 3.4 with a variable and it does hold:
-$x
On Wed, Apr 25, 2001 at 12:36:33AM -0500, David L. Nicol wrote:
Ah.. I knew I'd find the thread in here somewhere.
The problems go away if you allow white space to signify.
[...] Consider
print Foo
foo(bar);
Did the author forget a semi-colon, or did
On Wed, Apr 25, 2001 at 12:10:10AM -0500, David L. Nicol wrote:
That means, if you have a long list of scalars rou want to cat
together and it will run over the edge of your line
you can do this:
$onethroughten = $one$two$three$four$five
On Wed, 25 Apr 2001 18:19:40 GMT, Fred Heutte wrote:
Yes, I know ~ is the bitwise negation operator. Have you EVER used it?
Yes. A lot.
But there is no conflict. ~ is currently just an unary operator, while
your use would be as a binary operator (are those the correct terms?).
For example, in
On Wed, Apr 25, 2001 at 08:33:33AM -0400, Stephen P. Potter wrote:
How about symbolic refs to function names?
$a = $x ? hop : skip;
$b = $y ? scotch : soda;
$a.$b;# call one of hop.scotch, skip.scotch, hop.soda, skip.soda
5.005_03 and under required parens after the method
At 09:16 AM 4/26/2001 +0100, Michael G Schwern wrote:
On Wed, Apr 25, 2001 at 08:33:33AM -0400, Stephen P. Potter wrote:
| Alternately, we can overload . to do a deref on (blessed?) references,
| and
| concat otherwise.
I think this would lead to hard to find bugs when someone mispelled
Bart Lateur's response summarizes well what I've heard so far
from responses both to the list and privately:
(1) Yes, ~ *is* somewhat used in its current role as the bitwise
negation (complement) operator.
(2) No, that doesn't appear to overlap my proposal for its use
as a successor
Bart Lateur [EMAIL PROTECTED] writes:
On Wed, 25 Apr 2001 15:52:47 -0600 (MDT), Dan Brian wrote:
So why not
$object!method(foo, bar);
In my opinion, because it doesn't provide sufficient visual
distinction between $object and method(). At a glance, especially on
a crowded page, it's
On Wed, 25 Apr 2001 06:09:56 -0700 (PDT), Larry Wall wrote:
Bart Lateur writes:
: Er... hip hip hurray?!?!
:
: This is precisely the reason why I came up with the raw idea of
: highlander variables in the first place: because it's annoying not being
: able to access a hash passed to a sub
At 03:02 PM 4/26/2001 -0500, David L. Nicol wrote:
Dan Sugalski wrote:
What if the decision in-vtable or not-in-vtable is deferred?
That's doable, I think, though I can see some issues.
how about a two-tiered vtable, where a single high bit, if set,
indicates extended handling, or at
=head1 The Perl6 Debugger
=head2 Perl-level Debugging
=head3 Existing Functionality
The following is a list of the functionality in the existing Perl5
debugger; this functionality should, of course, be maintained for
backwards compatibility.
=over 4
=item T
Stack trace.
You list the particular commands as 'existing functionality'. I think
this is a mistake, even if you didn't mean it that way, if it was just
an artifact of your presentation format. I know that breaking
debugging habits that have been ingrained in at the spinal level may
be hard to break, but
On Thu, Apr 26, 2001 at 06:25:03PM -0500, Jarkko Hietaniemi wrote:
In a sick way I kinda liked how compilers were able to give out error
messages not unlike:
foo.ada: line 231: Violation of sections 7.8.3, 9.11.5b and 10.0.16: see the LRM.
Ever used the Mac C compiler?
--
Language shapes
Nathan Wiger writes:
: Now, it may be that all the We should use . people are just keeping
: quiet, or think it's obvious why this is a benefit, but I'm unconvinced.
: Again, I'm open-minded, but the only argument I've really heard is to
: make Perl more Java/Python-like. This doesn't sway me at
$foo = [$one, $two, $three]; # creates an anonymous list.
$foo = [$object method(foo, bar)];
This would interpret as
$foo[0] == $object, etc...
Ilya
-Original Message-
From: Buddha Buck [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 11:20 PM
To: Piers Cawley
Cc: Bart
On Fri, Apr 27, 2001 at 02:28:58AM +0100, Simon Cozens wrote:
On Thu, Apr 26, 2001 at 06:25:03PM -0500, Jarkko Hietaniemi wrote:
In a sick way I kinda liked how compilers were able to give out error
messages not unlike:
foo.ada: line 231: Violation of sections 7.8.3, 9.11.5b and
Piers Cawley [EMAIL PROTECTED] writes:
Buddha Buck [EMAIL PROTECTED] writes:
Bart Lateur [EMAIL PROTECTED] writes:
On Wed, 25 Apr 2001 15:52:47 -0600 (MDT), Dan Brian wrote:
So why not
$object!method(foo, bar);
In my opinion, because it doesn't provide sufficient
To me this whole thing looks like bike shedding at it's worst at
this point. Please stop and read this
http://www.freebsd.org/doc/en_US.ISO_8859-1/books/faq/misc.html#BIKESHED-PAINTING
and possibly this
I have a different suggestion:
replace - with ~
~ is already Perlish for glues to something related.
That's a different construct than concatenates.
Fred
Buddha Buck [EMAIL PROTECTED] writes:
Bart Lateur [EMAIL PROTECTED] writes:
On Wed, 25 Apr 2001 15:52:47 -0600 (MDT), Dan Brian wrote:
So why not
$object!method(foo, bar);
In my opinion, because it doesn't provide sufficient visual
distinction between $object and method().
Fred Heutte [EMAIL PROTECTED] writes:
A vote against the proposed switches, for an unbearably lazy (ok,
selfish) reason. Having to use the shift key with any non-alphanumeric
keypress always feels like a lot of extra work. This is why I have long
avoided underscores in variable names.
Eric Roode writes:
: John Porter wrote:
: IIUC, this ability is precisely what Larry was saying Perl6 would have.
:
: I may have my history wrong here, but didn't Ada try that?
Not at all. The syntax of Ada was nailed down tighter that almost any
language that ever existed.
: Super-flexible,
Dan Sugalski writes:
: And on the other hand you have things like Forth where every program
: essentially defines its own variant of the language, and that works out
: reasonably well. (Granted it's more of a niche language, especially today,
: but that's probably more due to its RPN syntax)
On Thu, Apr 26, 2001 at 04:13:30PM -0700, Larry Wall wrote:
Eric Roode writes:
: John Porter wrote:
: IIUC, this ability is precisely what Larry was saying Perl6 would have.
:
: I may have my history wrong here, but didn't Ada try that?
Not at all. The syntax of Ada was nailed down
A vote against the proposed switches, for an unbearably lazy (ok,
selfish) reason. Having to use the shift key with any non-alphanumeric
keypress always feels like a lot of extra work. This is why I have long
avoided underscores in variable names. (This is the same reason
I avoid = which not
On Thu, Apr 26, 2001 at 03:35:24AM +, Fred Heutte wrote:
Bart Lateur's response summarizes well what I've heard so far
from responses both to the list and privately:
(1) Yes, ~ *is* somewhat used in its current role as the bitwise
negation (complement) operator.
(2) No, that
At 05:14 PM 4/25/2001 -0500, David L. Nicol wrote:
Dan Sugalski wrote:
2) Anyway, even resizing vtables we would need some more indirection to
determine in which position of the vtable is which operator.
No. Each operator goes in a fixed position in the vtable, and it's the same
for
Bart Lateur writes:
: Yeah. But no cheers then. The problem still remains: you can access a
: hash in the normal way in plain code, but inside a sub, you can mainly
: only access a passed hash through a reference.
Won't be a problem.
: It's annoying to basically having two ways of doing
Graham Barr wrote:
You don't get it.
We are not looking for a single char to replace -
We WANT to use .
With complete respect here, I'm still not convinced this is true.
Specifically, what the value of we is. It hardly sounds like
everyone's united on this point. In fact, I've counted
31 matches
Mail list logo
