Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

Re^4: Is the documentation for Perl 5.20 'pack' correct?

by BrowserUk (Patriarch)
on Jul 07, 2015 at 00:20 UTC ( [id://1133469]=note: print w/replies, xml ) Need Help??


in reply to Re^3: Is the documentation for Perl 5.20 'pack' correct?
in thread Is the documentation for Perl 5.20 'pack' correct?

Until you define the meaning of the phrase "byteorder is 12345678", the statement is meaning less.

Repetition is not an argument; nor a discussion.

And nothing you've said so far is worth repeating!

  • Comment on Re^4: Is the documentation for Perl 5.20 'pack' correct?

Replies are listed 'Best First'.
Re^5: Is the documentation for Perl 5.20 'pack' correct?
by ikegami (Patriarch) on Jul 07, 2015 at 00:23 UTC

    byteorder: The output of $Config{byteorder}. Also available via perl -V:byteorder.

    "12345678": A string consisting of 8 characters, with respective values 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37 and 0x38.

    This would have been clear to you if you had actually read the docs. You sure love making a fool of yourself.

      "12345678": A string consisting of 8 characters

      Thankyou. You just made my point for me.

      • Nowhere in the context of the quote, is the 12345678 defined to be a string.
      • Nowhere in that context is "byteorders" defined to mean: the value of $Config{byteorder} will vary according to ...

      In other words:

      1. You ignored that I said: "is either misleading or ...";

        and decided to 'challenge' what I said with an out-of-context quote a no-context misinterpretation of what I said.

      2. The documentation is assumptive and ambiguous. The phrasing is such that it is open to misinterpretation.

        It ought to read something to the effect of:

        • On 32-bit, little-endian platforms, $Config{byteorder} returns the string '1234';
        • On 64-bit, little-endian platforms, $Config{byteorder} returns the string '12345678';
        • On 32-bit, big-endian platforms, $Config{byteorder} returns the string '4321';
        • On 64-bit, big-endian platforms, $Config{byteorder} returns the string '87654321';

      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      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.
      I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!

        Nowhere in the context of the quote, is the 12345678 defined to be a string.

        I know. Three times I told you to read the docs instead of relying on that partial quote.

        Nowhere in that context is "byteorders" defined to mean: the value of $Config{byteorder} will vary according to ...

        You mean except in the passage we're discussing? The byteorder on the platform where Perl was built is also available via Config: use Config; print "$Config{byteorder}\n"; [...] Byteorders "1234" and "12345678" are little-endian; "4321" and "87654321" are big-endian.

        What an idiot. For the fourth time, go read the damn docs before mouthing off about how they're wrong.

          A reply falls below the community's threshold of quality. You may see it by logging in.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1133469]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others romping around the Monastery: (3)
As of 2024-04-19 03:26 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found