Re: \(...)?

2005-09-19 Thread TSa
HaloO, Ingo Blechschmidt wrote: [EMAIL PROTECTED];# Ref to array \(@array); # List of refs to @array's elements, i.e. same as map { \$_ } @array; # Weird (violating the "parens are only for grouping" rule), but # consistent with Perl 5. Correct? I opt for 'no'. () sh

Re: \(...)?

2005-09-19 Thread TSa
HaloO Larry, you wrote: We can do whatever we like with \ since it's really a *macro* that Could you explain me the rational why \ and other ops like =, := are not normal overloadable, possibly MMD operators? imposes lvalue context (or at least, indirection in the abstract, if we were ever

Lazy lists and optimizing for responsiveness

2005-09-19 Thread Yuval Kogman
One thing that is extraordinarily hard to do with the facilities we have today is finding the responsive optimum between laziness and eagerness. Let's use an example. WWW::Mechanize comes with a nice example script for mailing list moderation. This script can be rather easily hacked to work on s

Re: Lazy lists and optimizing for responsiveness

2005-09-19 Thread TSa
HaloO, Yuval Kogman wrote: One thing that is extraordinarily hard to do with the facilities we have today is finding the responsive optimum between laziness and eagerness. Good, that you remind me to this subject! I wanted to ask the "same" question starting from more theoretical grounds. I kn

Re: \(...)?

2005-09-19 Thread Ingo Blechschmidt
Hi, TSa orthogon.com> writes: > Ingo Blechschmidt wrote: > > [EMAIL PROTECTED];# Ref to array > > > > \(@array); # List of refs to @array's elements, i.e. same as > > map { \$_ } @array; > > # Weird (violating the "parens are only for grouping" rule), but > > # consisten

Re: \(...)?

2005-09-19 Thread Jonathan Scott Duff
On Mon, Sep 19, 2005 at 02:21:43PM +, Ingo Blechschmidt wrote: > So...: > > [EMAIL PROTECTED]; # Reference to array, of course > \(@array); # same > \(((@array))); # same > > \(1,2,3);# Reference to a list promoted to an array (!) > \(((1,2,3)));

Re: \(...)?

2005-09-19 Thread TSa
HaloO, Ingo Blechschmidt wrote: So...: [EMAIL PROTECTED]; # Reference to array, of course \(@array); # same \(((@array))); # same \(1,2,3);# Reference to a list promoted to an array (!) \(((1,2,3)));# same The thing that is unclear to me here a

Re: \(...)?

2005-09-19 Thread TSa
HaloO, Ingo Blechschmidt wrote: [EMAIL PROTECTED];# List of references to @array's elements \*(((@array))); # same Yes, and of course \((*((@array; # same \ (* (@array)); # same Well, until someone invents &infix:<(*> :) -- $TSa.greeting := "HaloO"; # mind

Re: \(...)?

2005-09-19 Thread Juerd
Ingo Blechschmidt skribis 2005-09-19 14:21 (+): > \(1,2,3);# Reference to a list promoted to an array (!) > \(((1,2,3)));# same Except that it has to be a reference to a reference, because (1,2) (in scalar context) already evaluates to a reference, because it can't be a pur

Re: \(...)?

2005-09-19 Thread TSa
HaloO, Juerd wrote: Could you think of a formal specification of \ the way you want it, that doesn't exist of only examples? I can't speak for Ingo, but here's mine. What context does it give its RHS? I still have difficulties to understand this concept but I think that \ is simply sub

syntactic, static and dynamic type

2005-09-19 Thread Thomas Sandlass
HaloO, I'm still trying to understand the concept of context in Perl6 from a typing perspective. My current interpretation let me to coin three levels of typing in Perl6: syntactic, static and dynamic. I guess the latter two are well known but the syntactic type is new---at least do I hope so. Ple

Re: \(...)?

2005-09-19 Thread chromatic
On Mon, 2005-09-19 at 13:01 +0200, TSa wrote: > Why shouldn't there be a lvalue traversal that > in the end makes > >($x, $y) = \($a, $b); > > actually mean > >$x = \$a; $y = \$b; Does this not go from one sequence point (evaluate the rhs sufficiently, then perform the lvalue assignmen

Re: \(...)?

2005-09-19 Thread Juerd
TSa skribis 2005-09-19 18:16 (+0200): > sub &*prefix:<\> (Item *$to_enref --> Ref ^ List[Ref]) {...} > # For the type inferencer it were a great thing to leave > # the hint that Item --> Ref and List --> List, but how do > # I write that? Is it (*$t, [EMAIL PROTECTED] --> @rest ?? List !! R

Perl 6 Summary for 2005-09-12 through 2005-09-19

2005-09-19 Thread Matt Fowles
Perl 6 Summary for 2005-09-12 through 2005-09-19 All~ Welcome to another Perl 6 Summary, this time brought to you with a shorter pause (::grumble:: $WORK ::grumble::) and assisted by cookies. Perl 6 Compilers Circular Preludes for Fun and Confusion Yuval Kogman posted a reall

Re: Junctions, patterns, and fmap again

2005-09-19 Thread Stuart Cook
On 19/09/05, Luke Palmer <[EMAIL PROTECTED]> wrote: > Part 1: fmap > > I have a plan for the $x »+« $y form (and also foo(»$x«, »$y«, »$z«)), > but I don't want to go into that right now. It basically involves > zipping the structures up into tuples and applying the function to the > tuples. Doe

Re: Junctions, patterns, and fmap again

2005-09-19 Thread Luke Palmer
On 9/19/05, Stuart Cook <[EMAIL PROTECTED]> wrote: > On 19/09/05, Luke Palmer <[EMAIL PROTECTED]> wrote: > > Part 1: fmap > > > > I have a plan for the $x »+« $y form (and also foo(»$x«, »$y«, »$z«)), > > but I don't want to go into that right now. It basically involves > > zipping the structures

Re: Junctions, patterns, and fmap again

2005-09-19 Thread Luke Palmer
On 9/19/05, Luke Palmer <[EMAIL PROTECTED]> wrote > Well, I've written up the details in a 40 line Haskell program to make > sure it worked. I think I deleted the program, though. Nope. Here it is. And it was 22 lines. :-) http://svn.luqui.org/svn/misc/luke/work/code/haskell/hyper.hs Luke