Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Originating-IP: [24.27.76.111] From: "Tom Hutto" To: "cygwin" References: <80575AFA5F0DD31197CE00805F650D7602CDD0 AT wilber DOT adroit DOT com> <20001013204948 DOT C3048 AT cygnus DOT com> <39E82265 DOT FE4FC001 AT cygnus DOT com> Subject: Re: RFC: linux compatibility Date: Mon, 16 Oct 2000 09:04:44 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: X-OriginalArrivalTime: 16 Oct 2000 14:04:28.0803 (UTC) FILETIME=[FFC4C530:01C03779] Hmm, back in the 'good old days' we used to write "self modifying" assembler code to take care of this kind of problem. Guess you could do the same in C; just copy the appropriate struct into the exports area? ----- Original Message ----- From: "Corinna Vinschen" To: Sent: Saturday, October 14, 2000 4:07 AM Subject: Re: RFC: linux compatibility | Chris Faylor wrote: | > Hmm. Some OS's have a "personality" model. We could actually adopt | > something like that. New code could default to the "linux personality" | > while older code could stil use the default "cygwin hodge-podge personality". | > This might not be feasible with some things like timezone, etc. | | That could be managed by the header file. | | extern time_t _timezone __declspec(dllimport); | | #if defined (LINUX_PERSONALITY) | #define timezone _timezone | #elif defined (HODGE_PODGE_PERSONALITY) | char *_EXFUN(timezone, (void)); | #endif | | Corinna | | -- | Want to unsubscribe from this list? | Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com | | -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com