public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Ian Lance Taylor <ian@zembu.com>
Cc: geoffk@ozemail.com.au, binutils@sourceware.cygnus.com
Subject: Re: elf32.em
Date: Wed, 03 Nov 1999 08:24:00 -0000	[thread overview]
Message-ID: <25953.941645870@upchuck> (raw)
In-Reply-To: <19991027234806.10154.qmail@daffy.airs.com>

  >    Shouldn't the variable be called 'filename'?
  > 
  > Actually, I think the uses of it should be filname, to avoid
  > shadowing.  Or we should just remove the declaration of filname, and
  > use the existing filename local.
One last thing.  Yes, the "filname" variable should just disappear.  I'll
take care of that too.

I'm testing the changes now..

jeff

      parent reply	other threads:[~1999-11-03  8:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27 16:33 elf32.em Geoff Keating
1999-10-27 16:48 ` elf32.em Ian Lance Taylor
1999-10-27 23:27   ` elf32.em Jeffrey A Law
1999-11-03  7:49   ` elf32.em Jeffrey A Law
1999-11-03  7:49     ` elf32.em Jeffrey A Law
1999-11-03  8:24   ` Jeffrey A Law [this message]

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=25953.941645870@upchuck \
    --to=law@cygnus.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=geoffk@ozemail.com.au \
    --cc=ian@zembu.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).