> "John" == John Porter <[EMAIL PROTECTED]> writes:
John> No special name, huh? Maybe that's the way it ought to be.
That's the way I feel occasionally about the Schwartzian Transform,
actually. Having to explain that it was named *for* me but not *by*
me (in fact, actually to spite me, if
Uri Guttman wrote:
> records can be strings, or any perl [LH]o[LH].
y/L/A/;
> for a schwartz (drop the 'ian') or GR transform.
Why? So it conforms with the "Guttman-Rosler" naming standard?
--
John Porter
Hey,
I just have a couple of ideas that may either make me look like a fool
or provoke some discussion:
Personally, I have never used the Schwartzian Transform (but I have
heard, looked at it), so I may not be fully knowledgeable of its
usefulness. However, do the advantages of including it o
On Wed, 21 Mar 2001 15:40:20 -0500, John Porter wrote:
>Uri Guttman wrote:
>> JP> y/L/A/;
>>
>> tell that to perllol :)
>
>I do, through clenched teeth, every time I see it.
IMHO, it is:
HoA
HoH
LoA
LoH
--
Bart.
> "JP" == John Porter <[EMAIL PROTECTED]> writes:
JP> Uri Guttman wrote:
>> records can be strings, or any perl [LH]o[LH].
JP> y/L/A/;
tell that to perllol :)
>> for a schwartz (drop the 'ian') or GR transform.
JP> Why? So it conforms with the "Guttman-Rosler" naming standard
Bart Lateur wrote:
> IMHO, it is: HoA, HoH, LoA, LoH
But that's only two levels, when the number of levels
can really be unbounded. Only the *top* level can be
a list, rather than an array.
Since any two levels can have a relationship
...->[0]->[0]->...
...->[0]->{X}->...
> Loooking over dev.perl.org/rfc, only two RFCs mention sorting:
> RFC 124: Sort order for any hash
> RFC 304: sort algorithm to be selectable at compile time
>
> and none mentioning the Schwartz. :-)
>
> This message is not an RFC, nor is it an intent to add a feature
> to Perl or
John Porter declared:
Adam Turoff wrote:
> This message is not an RFC, nor is it an intent to add a feature to Perl
or specify a syntax for that feature[*].
Yay.
> We're all for making easy things easy, but the complexities of
> "map {} sort {} map {} @list" has always been befuddling to newbies,
On Wed, Mar 21, 2001 at 10:24:05AM -0500, John Porter wrote:
> Uri Guttman wrote:
> > records can be strings, or any perl [LH]o[LH].
>
> y/L/A/;
>
>
> > for a schwartz (drop the 'ian') or GR transform.
>
> Why? So it conforms with the "Guttman-Rosler" naming standard?
Which *I* would call
Jarkko Hietaniemi wrote:
> (John Macdonald suggested the trick to me at least a year before
> the GR paper, and it's there in the Sorting chapter, though it is
> not called by any special name...)
Very interesting indeed.
No special name, huh? Maybe that's the way it ought to be.
--
John Porte
Uri Guttman wrote:
> JP> y/L/A/;
>
> tell that to perllol :)
I do, through clenched teeth, every time I see it.
"Perl: Laughing Out Loud" :-)
> the 'ian' suffix is overkill. think
> about all the classic mathematical transforms and they don't append
> 'ian' to the person's name. fourier,
Adam Turoff <[EMAIL PROTECTED]> writes:
> We're all for making easy things easy, but the complexities of
> "map {} sort {} map {} @list" has always been befuddling to newbies,
> especially when reading the code left-to-right.
I've always thought that the purpose of the Schwartzian transform was
> "JH" == Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
JH> On Wed, Mar 21, 2001 at 10:24:05AM -0500, John Porter wrote:
>> Uri Guttman wrote:
>> > records can be strings, or any perl [LH]o[LH].
>>
>> y/L/A/;
>>
>>
>> > for a schwartz (drop the 'ian') or GR transform.
>
13 matches
Mail list logo
