Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

Re: !0 is not necessarily 1 (was Re: Secret Perl Operators: the boolean list squash operator, x!!) (Larry)

by tye (Sage)
on Aug 01, 2006 at 14:47 UTC ( #565010=note: print w/replies, xml ) Need Help??


in reply to !0 is not necessarily 1 (was Re: Secret Perl Operators: the boolean list squash operator, x!!)
in thread Secret Perl Operators: the boolean list squash operator, x!!

Quoting elsewhere in this very thread:

it's mentioned in the Camel, in the "Ideographic Unary Operators" section, page 92:
Unary ! performs logical negation, that is, "not". See not for a lower precedence version of logical negation. The value of a negated operand is true (1) if the operand is false (numeric 0, string "0", the null string, or undefined) and false ("") if the operand is true.

So I guess that boat has sailed not just practically (which it did a long, long time ago) but also as far as being officially documented. Larry did have some editorial control over "the Camel", no?

- tye        

  • Comment on Re: !0 is not necessarily 1 (was Re: Secret Perl Operators: the boolean list squash operator, x!!) (Larry)

Replies are listed 'Best First'.
Re^2: !0 is not necessarily 1 (was Re: Secret Perl Operators: the boolean list squash operator, x!!) (Larry)
by merlyn (Sage) on Aug 01, 2006 at 14:58 UTC
    The camel is a derived text, not an authoritative text, because it's never viewed as "a required doc" for Perl development.

    When the patch is made to perldoc, I'll shut up about my claim. The evidence in the camel is a hint that the perldoc should indeed be patched.

    -- Randal L. Schwartz, Perl hacker
    Be sure to read my standard disclaimer if this is a reply.

      Could you shut yourself up (would you submit the patch)?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://565010]
help
Chatterbox?
[Corion]: perldigious: That seems to be more the export and likely it's the recipients of that export that like the titles changes
[Corion]: ... "changed"
[Corion]: I usually expect fixed header names, but am sometimes lenient in the order of columns. But changing the report titles often sounds to me as if you are not the sole consument of the export ;)
[shmem]: perldigious: as always - if it ain't broke, don't fix it. Ther must be a very compelling reason for changing column names in a database. Those are rare.
[Corion]: If you have whitespace in the column names in the database, whap the DBAs ;)

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (9)
As of 2017-05-25 13:35 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?