Re: Perl 6's for() signature

2003-07-31 Thread attriel
params between, and assuming there was no ambiguity ... Ow, my head hurts now :o --attriel

Re: Apocalypses and Exegesis...

2003-08-14 Thread attriel
considered 'slushy', which may not be as good as frozen, but it's closer :o That's my take on it, of course; I could be entirely wrong, too --attriel

Re: AW: AW: AW: nag Exegesis 2

2003-01-04 Thread attriel
t somewhere else and have separate declarations and initializations. the example in (1) looks like it's beind declared as a "size(4)" , with "human" and "DNA" being somehow modifiers on "size(4)" (admittedly, if it were the stated style, people would be expected to understand it, but it would still be counterintuitive, IMO) --attriel

Re: 'my int( 1..31 ) $var' ?

2003-01-04 Thread attriel
.. variable property (?) that the program sets, but once it's read, I'm not sure the information exists in any meeans to produce the information FOR the property, so it would have to be set in the input functions themselves ... Admittedly, the value-type is goin to be more interesting in a large majority of the cases, so it probably SHOULD continue being the default low-effort result ... I had a point. I think I made it in there. --attriel

Re: 'my int( 1..31 ) $var' ?

2003-01-05 Thread attriel
as a "useful case" ... But since it is user-garnerable information, and no cases are springing to mind, I retract my earlier comments and say that it might be interesting in some case, but in the same case it is feasible to simply allow the programmer to generate it rather than killing ops generating it automatically ... --attriel (I'll quit posting just before I go to bed now :o)

Re: L2R/R2L syntax (was Re: Everything is an object.)

2003-01-08 Thread attriel
... More of a @a ~> grep (...) ~> apply <~ sort <~ @b ; So that the grep'd elements of @a are applied, 1:1, to the sorted @b ... ala apply (grep (..., @a), sort(@b)); (again, more useful for a longer chain) --attriel

RE: L2R/R2L syntax (was Re: Everything is an object.)

2003-01-08 Thread attriel
ly, then this should print "FOO" on standard out: DOH! All the examples were using @'s, and somehow that translated to "this is an array opthingy" :o > $foo ~> print <~ STDERR; That makes a fair amount of sense (and certainly more than any of my array-based flawed examples :) Thanks for clearing up my fogginess :o --attriel

RE: L2R/R2L syntax (was Re: Everything is an object.)

2003-01-08 Thread attriel
ably not what you wanted. OTOH, I'm still new at posting here, and I may not be following all the bits that came before :o --attriel

Re: Variable Types Vs Value Types

2003-01-09 Thread attriel
Apple yes? (I'm trying to make sure I didn't miss a majikal mystery conversion step that seems contradictory but somehow exists anyway :o) --attriel

Re: L2R/R2L syntax (was Re: Everything is an object.)

2003-01-09 Thread attriel
on, |> reads as a forward gate "Do not continue unless the previous item was true; if it was, feed the result here" ... <| doesn't read like much, and |< looks like some 1337 h4xx0r trying to be cool, honestly :o It just looks broken! As an op, I would expect it to translate to "OR Less Than" and I can't come up with how to use that "$a == 7 |< 200" I guess :o And would the consistency rules require them to be: ~> ~< ? so that the ops look similar? (If so, I'm gonna vote that ~< looks like a fish and is just weird :) --attriel

Re: L2R/R2L syntax (was Re: Everything is an object.)

2003-01-10 Thread attriel
... } and grep { ... } with <~'s, so I guess the indirect object would work the same for sort { ... }, but now I'm not real sure on what the indirect object IS in all these calls ... Could someone explain how to know what's the indirect object? (who knew the "sentence diagramming" would be USEFUL!!) --attriel

Re: Arrays: Default Values

2003-01-28 Thread attriel
lt, maybe, but i don't care. this is REALLY undef" is that possible? aside from it being disturbing to write "undef but undef" :o --attriel (the first suggestion is serious, but the syntax is flawed; the second suggestion has better syntax but is tongue-in-cheek suggested ... )

Re: Arrays: Default Values

2003-01-29 Thread attriel
, although it doesn't help in this case b/c I'm wanting to set it to 0, and saying "attendees[23] = 0 but really" looks wrong ... so maybe the "but really" would be for setting to default ('empty value') if you had need and used it in assignment (but undef @attendees[23] would, i think, still make it 'empty val' b/c i'm not assigning a value to it, i'm unassigning the value I've given it, which is a distinction that I think may be relevant ...) --attriel

Re: newline as statement terminator

2003-02-03 Thread attriel
hink they're mandated, but not dictated by the language) or is it just there to help people ? And why is there a "; there? i presume the " is a typo, but since this whole discussion is getting rid of the ;, I cna't see why it's there ... Summary: ;'s good, indentation necessary but not parser-graphically dicatated :o --attriel (parsergraphically?)