From: Nick Garnett <nickg@ecoscentric.com>
To: "Steve Strublic" <SStrublic@hypercom.com>
Cc: andrew@lunn.ch, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] No zlib crc32 support?
Date: Mon, 15 Dec 2003 19:52:00 -0000 [thread overview]
Message-ID: <m3ad5thopa.fsf@miso.calivar.com> (raw)
In-Reply-To: <OF4986D169.3A0DE40A-ON07256DFD.0054E063-07256DFD.0055403E@hypercom.com>
"Steve Strublic" <SStrublic@hypercom.com> writes:
> I'll leave the resolution up to the maintainers.
>
> Steve
Since Andrew is a maintainer, and the CRC stuff is his baby then I'm
quite happy to accept his judgement on this issue.
To largely reiterate what Andrew said: We cannot, as a general rule,
litter eCos with unqualified symbols like "crc32", we need to ensure
that the name space is a clean as possible for application
code. crc32() is not a standardized API function name, so we must call
it something else. Also, since there are several different CRC32
algorithms, selecting any specific implementation to be called crc32()
would never satisfy everyone. Making the user select the
implementation explicitly by means of a #define renders this choice
obvious.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-12-15 19:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 17:56 Steve Strublic
2003-12-15 19:52 ` Nick Garnett [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 22:35 Steve Strublic
2003-12-15 8:33 ` Andrew Lunn
2003-12-10 16:22 Steve Strublic
2003-12-10 16:14 Steve Strublic
2003-12-10 16:20 ` Gary Thomas
2003-12-11 0:38 ` Andrew Lunn
2003-12-09 21:08 Steve Strublic
2003-12-09 21:27 ` Gary Thomas
2003-12-10 8:39 ` Andrew Lunn
2003-12-09 20:29 Steve Strublic
2003-12-09 20:45 ` Gary Thomas
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=m3ad5thopa.fsf@miso.calivar.com \
--to=nickg@ecoscentric.com \
--cc=SStrublic@hypercom.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
/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).