From: Gary Thomas <gthomas@redhat.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sources.redhat.com, tsmith@megaroms.co.uk
Subject: Re: [ECOS] comment about header files
Date: Thu, 26 Jul 2001 16:15:00 -0000 [thread overview]
Message-ID: <XFMail.20010726171451.gthomas@redhat.com> (raw)
In-Reply-To: <3B6053BF.2916DDEE@redhat.com>
On 26-Jul-2001 Jonathan Larmour wrote:
>> there is also a lack of 'standard' (at least in my eyes) defines such as CLSIZE and
>> getdtablemax() for example.
>
> Well, AFAIK Linux doesn't even have those so I don't know how standard they
> are.
>
They aren't very standard at all - in fact they are very much Unix (BSD) legacy.
>> not that i'm going on but if anyone has time it would make eCos application developers lives
>> much easier if the
> header files were tidied up as well as helping further development.
>>
>> having a tangle of header files in code is stupid
>
> Agreed.
We all have to live within our means. In this case, when we imported the
BSD networking code, the [initial] decision was to try and keep the code
as pristine as possible. This decision was based on the hope/anticipation
of keeping up with the BSD networking as a separate, maintainable component
with influences from outside. However, it also meant living with their
include files, however ugly.
If anyone wants to rewrite all of those headers, and validate the stack
afterwards, feel free to do so. After all, this is open source :-)
next prev parent reply other threads:[~2001-07-26 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 6:26 tsmith
2001-07-26 10:31 ` Jonathan Larmour
2001-07-26 16:15 ` Gary Thomas [this message]
2001-07-27 1:00 tsmith
2001-07-27 6:18 ` Jonathan Larmour
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=XFMail.20010726171451.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
--cc=tsmith@megaroms.co.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).