public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mumit Khan <khan@NanoTech.Wisc.EDU>
To: N8TM@aol.com
Cc: kris.thielemans@csc.mrc.ac.uk, anorland@hem.passagen.se,
	cygwin@sourceware.cygnus.com
Subject: Re: LARGE_INTEGER in w32API 0.1.5
Date: Sat, 29 Jan 2000 11:46:00 -0000	[thread overview]
Message-ID: <Pine.HPP.3.96.1000129134410.25597O-100000@hp2.xraylith.wisc.edu> (raw)
In-Reply-To: <5b.1341403.25c2f83d@aol.com>

On Fri, 28 Jan 2000 N8TM@aol.com wrote:

> When this has been sorted out, the gcc distribution of 
> libf2c/libU77/[de]time_.c needs the corresponding fix.  Will there be 3 
> commonly distributed variations in LARGE_INTEGER?
> 

My local tree has the fix. The next w32api snapshot from my site will
default to _ANONYMOUS_UNION and _ANONYMOUS_STRUCT and unfortunately that
will create a few transient problems. But we need to look at the future,
and do it right before it's too late (ie., before it breaks too many 
code that uses the .u hack for lack of anon struct/union support).

Note that my recent changes to w32api (will be in the snapshot this
weekend and hopefully in Cygwin's next net release) will only turn on
this feature if the compiler supports it.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-01-29 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-28  5:50 N8TM
2000-01-29 11:46 ` Mumit Khan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-01-29 12:21 N8TM
2000-01-28  6:34 Earnie Boyd
2000-01-28  4:19 Kris Thielemans

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=Pine.HPP.3.96.1000129134410.25597O-100000@hp2.xraylith.wisc.edu \
    --to=khan@nanotech.wisc.edu \
    --cc=N8TM@aol.com \
    --cc=anorland@hem.passagen.se \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=kris.thielemans@csc.mrc.ac.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).