In summary:
1. I don't like ~ for concat
2. But if it does become concat, then we still
shouldn't
change ~'s current unary meaning
Thanks for listening.
-Nate
I agree completely. However, this is no longer really a
topic for -internals, it's really a purely language
At 05:17 AM 6/22/2001 -0700, Benjamin Stuhl wrote:
In summary:
1. I don't like ~ for concat
2. But if it does become concat, then we still
shouldn't
change ~'s current unary meaning
Thanks for listening.
-Nate
I agree completely. However, this is no longer
From: Nathan Wiger [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, June 21, 2001 4:41 PM
Subject: ~ for concat / negation (Re: The Perl 6 Emulator)
Does anyone else see a problem with =~ ? Plus, it makes the
pre-plus-concat that many desire impossible, since =~ is
This is from the latest python-dev summary. It might be of interest
to folks considering how to store strings.
* Adding .decode() method to Unicode * Marc-Andre Lemburg asked for
opinions on adding a .decode method to unicode objects:
DS == Dan Sugalski [EMAIL PROTECTED] writes:
DS At 01:13 PM 6/13/2001 +0200, Bart Lateur wrote:
On Tue, 12 Jun 2001 18:12:35 -0400, Dan Sugalski wrote:
'Kay, here's a question to ponder. Should the op dispatch loop handle
argument decoding, or should that be left to the opcode
DS == Dan Sugalski [EMAIL PROTECTED] writes:
DS At 11:45 PM 6/14/2001 -0400, Bryan C. Warnock wrote:
=head1 The opcode loop
This is a tight loop. All it does is call an opcode function, get back
a pointer to the next opcode to execute, and check the event dispatch
flag.
DS == Dan Sugalski [EMAIL PROTECTED] writes:
How does this port to a TIL form?
DS Badly. :) We'll need to insert event checking code into the
DS generated TIL, or figure out some way to wedge into the platform
DS interrupt/async system. (I'd bet on the former, though)
again, two
