From: Toon Moene <toon@moene.indiv.nluug.nl>
To: law@cygnus.com
Cc: Dave Love <d.love@dl.ac.uk>, egcs@cygnus.com
Subject: Re: libf2c/configure.in change
Date: Sun, 15 Feb 1998 22:54:00 -0000 [thread overview]
Message-ID: <9802160645.AA24803@moene.indiv.nluug.nl> (raw)
In-Reply-To: <3448.887602846@hurl.cygnus.com>
Dave wrote:
> I didn't know the following libf2c change had gone in (good), but I
> presume it should have a corresponding configure change.
>
> Mon Jan 19 17:19:27 EST 1998
> [...]
> libi77: backspace.c: for b->ufmt==0, change sizeof(int) to
> sizeof(uiolen). On machines where this would make a
difference, it is
> best for portability to compile libI77 with -DUIOLEN_int, which will
> render the change invisible.
>
> 1998-02-15 Dave Love <d.love@dl.ac.uk>
>
> * configure.in: Define UIOLEN_int per dmg advice for Jan 18
> backspace.c change.
> I don't really follow what's going on here. But if you
> & Toon think it's the right change, then please install
> it. (Toon submitted the backspage.c fix if I remember
> correctly).
The problem with this change is that it is makes a compatibility
break on systems where sizeof(long) != sizeof(int), e.g. Alpha's.
With this change, people won't be able to read the sequential
unformatted files they created with previous versions of the
compiler. OTOH, with this change, they could freely exchange such
files with Digital Fortran on Digital UNIX.
I have no strong feeling either way, but if we're going to break
backwards compatibility, we should write that down in the release
notes.
Cheers,
Toon.
next prev parent reply other threads:[~1998-02-15 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-15 11:33 Dave Love
1998-02-15 20:19 ` Jeffrey A Law
1998-02-15 22:54 ` Toon Moene [this message]
1998-02-16 14:21 ` Dave Love
1998-02-17 23:59 ` Jeffrey A Law
1998-02-18 14:54 ` Craig Burley
1998-02-18 17:12 ` Jeffrey A Law
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=9802160645.AA24803@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=d.love@dl.ac.uk \
--cc=egcs@cygnus.com \
--cc=law@cygnus.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).