Announcement

Collapse
No announcement yet.

Unified sizeof_member() Re-Proposed For Linux 5.5

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unified sizeof_member() Re-Proposed For Linux 5.5

    Phoronix: Unified sizeof_member() Re-Proposed For Linux 5.5

    After not being merged for Linux 5.4, the new sizeof_member() macro as a unified means of calculating the size of a member of a struct has been volleyed for Linux 5.5 for possible inclusion on this last day of the merge window...

    http://www.phoronix.com/scan.php?pag...Size-Of-Member

  • #2
    Why don't they just fix the name.

    Comment


    • #3
      Originally posted by microcode View Post
      Why don't they just fix the name.
      I propose to change it to sizeof_genitals...

      Comment


      • #4
        Originally posted by timofonic View Post

        I propose to change it to sizeof_genitals...
        I am offended! OMG!
        On a side note. I'm betting this is exactly why Linus is stalling...
        Last edited by milkylainen; 12-08-2019, 02:26 PM.

        Comment


        • #5
          I don't get it why they don't just consistently use one of those three macros instead of come up with the fourth one.

          Comment


          • #6
            ...coming here expecting dirty minds, again.
            I wasn't disappointed...

            Comment


            • #7
              It's not the sizeof the struct that matters, it's what you do with it. (Or so I hear)

              Comment


              • #8
                Originally posted by perpetually high View Post
                It's not the sizeof the struct that matters, it's what you do with it. (Or so I hear)
                Some say that the padding of a struct is more important than its length.

                Comment


                • #9
                  Originally posted by milkylainen View Post
                  On a side note. I'm betting this is exactly why Linus is stalling...
                  He said that explicitly with a recent LKML post ("the 13-year old in me").

                  What we seem to be arguing is not whether there should be one name (that seems to be a general agreement at this point), but what the rose should be called ("a rose by any other name would smell as sweet"). In the end the only person's opinion that matters is the decider (Linus), and he does not like member, regardless that the term is what is used on the C standard.

                  Comment


                  • #10
                    i wanted to mention my attitude to lowercase macros, but it seems offtopic here

                    Comment

                    Working...
                    X