From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3311 invoked by alias); 15 Dec 2003 17:36:16 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 3281 invoked from network); 15 Dec 2003 17:36:14 -0000 Received: from unknown (HELO thing2.hypercom.com) (208.248.82.254) by sources.redhat.com with SMTP; 15 Dec 2003 17:36:14 -0000 Received: from Azphxn01.hypercom.com (azphxn01.hypercom.com [10.0.2.70]) by thing2.hypercom.com (8.12.7/8.12.7) with ESMTP id hBFHUesS000414; Mon, 15 Dec 2003 10:35:09 -0700 (MST) To: andrew@lunn.ch Cc: ecos-discuss@sources.redhat.com Message-ID: From: "Steve Strublic" Date: Mon, 15 Dec 2003 17:56:00 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: Re: [ECOS] No zlib crc32 support? X-SW-Source: 2003-12/txt/msg00217.txt.bz2 I'll leave the resolution up to the maintainers. Steve -------- "Space is almost infinite. In fact, we think it is infinite." -- Dan Quayle andrew@lunn.ch To: SStrublic@hypercom.com 12/14/03 01:51 PM cc: ecos-discuss@sources.redhat.com Subject: Re: [ECOS] No zlib crc32 support? On Fri, Dec 12, 2003 at 09:49:39AM -0700, Steve Strublic wrote: > > Andrew, that's why I chose zlib's crc32 algorithm. So you have chosen the algorithm. That algorithm happens to be implemented by zlib as crc32 on unix like platforms. On eCos its implemented by, according to you, cyg_ether_crc32_accumulate. So we have no problems here. > Andrew, you state... "The maintainers have no intention of changing > these functions unless somebody can prove they are broken, which i > think it very unlikely." > I think I may have just proved that there's an issue. I don't think > it's proper to have to #define 'crc32' as' > cyg_ether_crc32_accumulate'. I'd prefer to hear the maintainers' > position firsthand. Why don't you think this is proper? As far as im aware there is no standard covering this issue. The proprietary library zlib is polluting the namespace by declaring this function. This may cause problems in the future if POSIX do decide to have a function called crc32() and decide to uses the POSIX crc algorithm. By using the names cyg_* i've deliberately avoided this namespace pollution leaving the application and POSIX the ability to do what it wants. Andrew -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss