From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.6-pre2 IDE cleanup 16
Date: Wed, 6 Mar 2002 20:36:14 +0000 (UTC) [thread overview]
Message-ID: <a65uju$be7$1@penguin.transmeta.com> (raw)
In-Reply-To: <3C85F872.7050306@evision-ventures.com> <Pine.LNX.3.96.1020306105428.386A-100000@gatekeeper.tmr.com>
In article <Pine.LNX.3.96.1020306105428.386A-100000@gatekeeper.tmr.com>,
Bill Davidsen <davidsen@tmr.com> wrote:
>
> Can't disagree, I never understood how people who can understand
>inheritance can be fuddled by pointers to functions.
One thing I'd love to see in C is default values for structure members
in initializers.
Pretty much everything else is trivially done with structures and
function pointers - once you allocate things dynamically you can (and
should) trivially and logically just make the allocator initialize the
needed fields too. But for static allocations and static initializers
you cannot cleanly do the same thing - you have to add explicit code
that knows about each statically allocated entry.
That's basically the only piece of object constructors that I consider
really _useful_, with the rest just being syntactic fluff.
Linus
next prev parent reply other threads:[~2002-03-06 20:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 7:54 [PATCH] per-cpu areas Rusty Russell
2002-03-05 10:51 ` [PATCH] 2.5.6-pre2 IDE cleanup 16 Martin Dalecki
2002-03-05 11:07 ` Zwane Mwaikambo
2002-03-05 11:28 ` Jens Axboe
2002-03-05 11:54 ` Martin Dalecki
2002-03-05 12:04 ` Jens Axboe
2002-03-05 12:09 ` Martin Dalecki
2002-03-06 0:33 ` Alan Cox
2002-03-06 9:51 ` Martin Dalecki
2002-03-05 11:48 ` Martin Dalecki
2002-03-06 0:34 ` Alan Cox
2002-03-05 12:36 ` Anton Altaparmakov
2002-03-05 12:36 ` Martin Dalecki
2002-03-05 12:35 ` Zwane Mwaikambo
2002-03-06 0:28 ` Alan Cox
2002-03-05 12:47 ` Anton Altaparmakov
2002-03-05 12:52 ` Martin Dalecki
2002-03-06 1:40 ` Alan Cox
2002-03-06 8:56 ` Zwane Mwaikambo
2002-03-06 9:43 ` Martin Dalecki
2002-03-06 0:27 ` Alan Cox
2002-03-06 10:15 ` Martin Dalecki
2002-03-05 11:37 ` Arjan van de Ven
2002-03-05 11:51 ` Martin Dalecki
2002-03-05 21:19 ` Vojtech Pavlik
2002-03-05 21:42 ` Jeff Garzik
2002-03-05 21:46 ` Vojtech Pavlik
2002-03-06 9:19 ` Martin Dalecki
2002-03-06 1:08 ` Alan Cox
2002-03-06 9:45 ` Martin Dalecki
2002-03-06 0:41 ` Alan Cox
2002-03-06 9:15 ` benh
2002-03-06 11:07 ` Martin Dalecki
2002-03-06 11:12 ` Zwane Mwaikambo
2002-03-06 11:59 ` Martin Dalecki
2002-03-06 12:02 ` Meelis Roos
2002-03-06 12:11 ` Martin Dalecki
2002-03-06 16:01 ` Bill Davidsen
2002-03-06 20:36 ` Linus Torvalds [this message]
2002-03-06 17:00 ` benh
2002-03-06 9:49 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 13:46 Ronnie Sahlberg
2002-03-13 15:55 Rick A. Hohensee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='a65uju$be7$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox