Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 12 Dec 2002 17:36:51 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: MS_types and addr_t name polution Message-ID: <20021212223651.GA19444@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20021212072201 DOT 389F83BDA AT sitemail DOT everyone DOT net> <3DF90C1C DOT 19C5683 AT mvista DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DF90C1C.19C5683@mvista.com> User-Agent: Mutt/1.5.1i On Thu, Dec 12, 2002 at 02:22:20PM -0800, Michael Eager wrote: >Elfyn McBratney wrote: >>The addr_t type is used in memory managment (memory addresses??) in >>/usr/include/sys/mman.h. If you plan on using this (or is already on >>the code, mman.h i mean) you may have problems. What is the type of >>your addr_t? is it type char of * (pointer)? > >Actually, mman.h uses caddr_t, not addr_t, at least in the cygwin >1.3.15 system I have installed. Nothing in /usr/include appears to use >addr_t. > >My typedef of addr_t is for 64-bit int. > >>If the code is open source you can just change the addr_t typedef name >>(in your source) to something else eg. addr2_t in all of your source >>files (a simple search and replace). > >Yes, I renamed all references to addr_t to a different name. It's just >a nuisance and appears to be unnecessary name polution. AFAICT, this header comes from newlib. Perhaps an inquiry in that mailing list would be beneficial. You might also want to think about more creative ways of dealing with this type of situation than just renaming every occurrence of addr_t. Like involving macros maybe? For the record, addr_t is apparently used on some older UNIX systems. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/