On Fri, 1 Nov 2002, it was written:
On Fri, Nov 01, 2002 at 10:35:08AM -0800, Ed Peschko wrote:
So again, I don't see the difference between the two. ^[+]= and ^+= are synonyms
as far as I can see, and hence no need for the first form.
Only in the absence of overloading, and only because
Larry Wall writes:
On Fri, Nov 01, 2002 at 11:51:17AM -0700, John Williams wrote:
Right. ^= is rather pointless, because = already understands list
context.
They're not quite the same because list assignment truncates first. To wit:
a = [1,2,3];
b = [4,5];
a
On Sat, Nov 02, 2002 at 02:18:44AM +0200, [EMAIL PROTECTED] wrote:
snip ...
in that case the vectorization is *compleatly* orthogonal to the
details of op and we even can have something like
@a ^[{ $^a $^b ?? 1 :: ($^a,$^b) := ($^b,$^a) }] @b
I agree with all that you said
Ed Peschko writes:
I agree with all that you said above, I'm just saying we should make typing []
*optional*. 99% of the time, people are not going to need it, as they are not
defining their own operators as you did above.
Ed
long ago ( when xor was ! and ^ was called hyper )
On 2002-10-31 at 12:45:23, David Wheeler wrote:
Plus, it turns out not to be at all hard to type on Mac OS X. ;-)
Well, the angle quotes happen to fall within Latin-1, and so they're
easier to get to. On Windows you can either set up special key mappings or
just type ALT+171 for « and ALT+187
On 31 Oct 2002 at 15:59, Mark J. Reed wrote:
Once you wander away from Latin-1 into the more general world
of Unicode, you start running into trouble on the input side.
On Windows you pretty much have to use the Character map accessory.
Emacs and vim still work on UNIX, but I don't know of a
Markus Laire:
# Emacs and vim also works on Windows, not just UNIX.
So does DOS 'edit'. That doesn't mean Windows users use it. Windows
users want tools that look and act like Windows tools--if they didn't,
they'd be using another OS. Neither GNU emacs nor xemacs fits the bill,
and I doubt vim
actually , ones we decide that ^ *is necessary for vectorization , we
can allow other brackets , optional brackets ( where unambiguous ) ,
and spaces inside the brackets :
a ^+= b
a ^[+]= b
a ^(+)= b
a ^( + )= b
a ^{ + }= b
a ^{+}= b
a ^[ + ]= b
right, and what does this
