"The fate of reduce() in Python 3000"

2005-03-13 Thread A. Pagaltzis
Hi all, so Guido is talking about his reasoning behind dropping lambda, reduce(), filter() and map() in the next generation of Python: http://www.artima.com/weblogs/viewpost.jsp?thread=98196 [Prime quote: "I think having the two choices side-by-side just requires programmers to think about m

Re: Semantics of vector operations

2004-01-22 Thread A. Pagaltzis
* Larry Wall <[EMAIL PROTECTED]> [2004-01-22 18:40]: > You might argue that we should force people to think of it one > way or the other. I wouldn't, because if I did I'd should've been talking to Guido rather than you in the first place. :-) And because I'm talking to you, I'll wonder whether ma

Re: Semantics of vector operations

2004-01-21 Thread A. Pagaltzis
Gah. Not a good combination do heavy editing and insufficient proofreading make. * A. Pagaltzis <[EMAIL PROTECTED]> [2004-01-22 03:55]: > Good point; however, this means a > different way to think of the vector ops than we had so far. > Basically, we're moving from the realm o

Re: Semantics of vector operations

2004-01-21 Thread A. Pagaltzis
* Piers Cawley <[EMAIL PROTECTED]> [2004-01-21 23:33]: > And once you go to an image based IDE and have access to the > bytecode of the code you're writing there's all *sorts* of > interesting things you can do. And that's before one starts to > imagine attaching the IDE/debugger to a running proce

Re: Semantics of vector operations

2004-01-21 Thread A. Pagaltzis
* Larry Wall <[EMAIL PROTECTED]> [2004-01-21 20:35]: > On Wed, Jan 21, 2004 at 03:21:01PM +0100, A. Pagaltzis wrote: > > It seems to me that this is too big a semantic choice to make > > merely by omission of a single (and quite dainty) character. > > I'd rather e

Re: Semantics of vector operations

2004-01-21 Thread A. Pagaltzis
* Larry Wall <[EMAIL PROTECTED]> [2004-01-21 01:44]: > Note that if we do take this approach, we'll have to require the > space after = in > > @list = «a b c d e»; This shouldn't be a problem. The whitespace rule changes I believe should be avoided (Abigail does have a point there) is if whit

Re: run-once code

2004-01-14 Thread A. Pagaltzis
* Luke Palmer <[EMAIL PROTECTED]> [2004-01-14 19:03]: > Let's not mention that that has way more overhead than a > short-circuiting test, but I guess "the idea's the important > thing". How about a calculated goto? *grin* -- Regards, Aristotle "If you can't laugh at yourself, you don't take li

Re: This week's summary

2004-01-05 Thread A. Pagaltzis
* Lars Balker Rasmussen <[EMAIL PROTECTED]> [2004-01-05 20:42]: > I'm confused, are you optimistic or pessimistic in that last > sentence? Sounds carefully optimistic to me. At least it certainly doesn't sound pessimistic per se, no? -- Regards, Aristotle "If you can't laugh at yourself, you d

Re: This week's summary

2003-12-20 Thread A. Pagaltzis
* The Perl 6 Summarizer <[EMAIL PROTECTED]> [2003-12-16 11:57]: > bear in mind that the authors of the paper use the term > 'trait' for what we're calling a 'role' (We already have > traits you see). > > http://www.cse.ogi.edu/~black/publications/TR_CSE_02-012.pdf > -- Traits p

Re: s/// in string context should return the string

2003-11-21 Thread A. Pagaltzis
* A. Pagaltzis <[EMAIL PROTECTED]> [2003-11-21 13:16]: > But that without nested for modifiers (will those work?) this > isn't be applicable in the middle of a map map map map chain.. I shouldn't edit my stuff so heavily.. what a mess. -- Regards, Aristotle "If

Re: s/// in string context should return the string

2003-11-21 Thread A. Pagaltzis
* Smylers <[EMAIL PROTECTED]> [2003-11-20 11:50]: > This, however, is irritating: > > my @new = map { s:e/$pattern/$replacement/; $_ } @old; > > I forget the C<; $_> far more often than I like to admit and > end up with an array of integers instead of modified strings. > So I'd like a more eleg