From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Nested Function Patches
Date: Mon, 9 Jan 2006 16:06:03 +0100 [thread overview]
Message-ID: <200601091606.03959.okuji@enbug.org> (raw)
In-Reply-To: <1135757326.25959.10.camel@localhost.localdomain>
On Wednesday 28 December 2005 09:08 am, Peter Jones wrote:
> That's taking the very unrealistic point of view that using nested
> functions isn't broken. It is, in a great many ways which have already
> been discussed in depth, and which you've, rather disturbingly, chosen
> to ignore. Using "features" which require an executable stack is still
> just a bad idea.
>
> It's too bad that the grub project has chosen to ignore the pragmatic
> implications of code structure and style.
I'm sick of your FUD. If you are an engineer or programmer, show a technical
reason. All you have mentioned are:
- Red Hat does not ship programs with nested functions
- You feel that it is safer
- Everybody is going to disable executable stacks
Where is such a discussion in depth? Is this time before renaissance?
I understand the behavior of Red Hat, since Red Hat is after all a commercial
entity, so it must make business from marketing point of view. But GRUB is
not tied with such an activity. We are open to opinions, but you should not
insult the project or the members only because our technical decision is not
compatible with your own desire.
Okuji
next prev parent reply other threads:[~2006-01-09 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 2:53 Nested Function Patches Andre Smith
2005-12-23 8:33 ` Marco Gerards
2005-12-28 8:08 ` Peter Jones
2006-01-09 15:06 ` Yoshinori K. Okuji [this message]
2006-01-09 18:13 ` Peter Jones
2006-01-10 10:17 ` Marco Gerards
2006-01-10 16:14 ` Yoshinori K. Okuji
-- strict thread matches above, loose matches on Subject: below --
2005-12-23 16:30 andre-smith
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=200601091606.03959.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.