Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

Re: RFC:A brief tutorial on Perl's native sorting facilities.

by holli (Monsignor)
on Feb 06, 2007 at 09:34 UTC ( #598504=note: print w/replies, xml ) Need Help??


in reply to RFC:A brief tutorial on Perl's native sorting facilities.

By using the built-in cmp function
cmp is not a function, it's an operator. And your link does not lead to the perldoc of cmp, but to the homenode of the user cmp.

Besides that, good job.


holli, /regexed monk/

Replies are listed 'Best First'.
Re^2: RFC:A brief tutorial on Perl's native sorting facilities.
by BrowserUk (Pope) on Feb 06, 2007 at 13:51 UTC

    Thanks. Corrected above.

    Now the $64,000 questions:

    • Is there anything in the OP that is not covered elsewhere?
    • Or does it stand alone sufficiently for it to warrent it's addition to Tutorials?
    • If so, where?
    • And how is that done?

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
      Thanks. Corrected above.

      But now you have:

      "By using the built-in perlopcmp operator [...]"

      ITYM something like "By using the built-in cmp operator [...]"

        How stable is that link? I fell into the trap of using references to the Perl docs on perldoc.org for a while as they were more up to date than those on PM, but it was a mistake. Initially, the site was fine, but after a short while it became flacky, spending more time down than up. And then it simply disappeared.

        Of course, if it was possible to produce properly indexed HTML using pod, we be able to link directly to the section of perlop entitled "Equality operators", which would be a significant improvement. But that ain't gonna happen anytime soon.


        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://598504]
help
Chatterbox?
[ambrus]: Corion: push_write is in the higher level abstraction of AnyEvent::Handle, not in the watcher
[Corion]: ambrus: Hmm - rereading Prima::File, that merrily coincides with what Prima does - it tells you "you can read", and you're supposed to read from the fh yourself. I thought it called you with the data already read, which would've been harder to integrate
[ambrus]: you just need an io watcher, created by &AnyEvent::Impl:: Whatever::io(...)
[Corion]: So after talking it through with you even while I'm still not entirely clear on where AE ends and my implementation begins, I think I understand that I only need to implement some smaller parts for each functionality I want to support.
[Corion]: Yeah... and you might even be able to mix and match additional functionality if you have additional async suppliers, like from a separate thread
[ambrus]: You hvae to be careful with the timer, because apparently Prima::Timer insists on being periodic, wheras AnyEvent::Impl:: Whatever::timer should give a one-shot timer watcher
[ambrus]: I think the minimal implementation here is just a timer and io function, plus pushing to the @REGISTRY.

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (3)
As of 2016-12-08 12:26 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (141 votes). Check out past polls.