Re: [PATCH GIT 0.6] make use of register variables & size_t

From: Linus Torvalds (torvalds_at_osdl.org)
Date: 04/25/05

  • Next message: Luben Tuikov: "Re: [RFC] SAS domain layout for Linux sysfs"
    Date:	Mon, 25 Apr 2005 10:23:40 -0700 (PDT)
    To: Matthias-Christian Ott <matthias.christian@tiscali.de>
    
    

    On Mon, 25 Apr 2005, Matthias-Christian Ott wrote:
    >
    > "register" and "auto" variables aren't relicts of the 60's, they're a
    > part of the ISO-C 99 standard, I'm following, "man".

    They _are_ relicts of the 60's. It's just that the C standard hasn't ever
    had the reason to remove them.

    > And if you think "register" variables are outdated, please remove the
    > CONFIG_REGPARM option from the Kernel source.

    That does something totally different. And doesn't use "register" at all.

    Pass the toke, you've been hogging the drugs for way too long.

                    Linus
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Luben Tuikov: "Re: [RFC] SAS domain layout for Linux sysfs"

    Relevant Pages

    • Re: patch to fix set_itimer() behaviour in boundary cases
      ... I don't see a valid reason to restrict/reject input that is accepted now ... and dealt with reasonably because some standard says so (if you design a ... reject a condition that can reasonable be dealt with" as a good reason ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH GIT 0.6] make use of register variables & size_t
      ... > What kind of ancient C standard are you working against? ... And if you think "register" variables are outdated, ... CONFIG_REGPARM option from the Kernel source. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: patch to fix set_itimer() behaviour in boundary cases
      ... > design a new api, following the standard is nice of course). ... > as a good reason to go double ABI at all. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: patch to fix set_itimer() behaviour in boundary cases
      ... > I don't see a valid reason to restrict/reject input that is accepted now ... > and dealt with reasonably because some standard says so (if you design a ... These are probably better reasons against fiddling with ABI shifts and ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RFC] Splitting kernel headers and deprecating __KERNEL__
      ... > Christoph Hellwig wrote: ... > there any reason to not allow such links? ... Briefly it's preferable not to need the kernel source nor a particular ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)