rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Tim Goodwin <tgoodwin@cygnus.co.uk>
To: rc@hawkwind.utcs.toronto.edu
Subject: New rc snapshot available (1998-10-28)
Date: Wed, 28 Oct 1998 09:54:32 -0500	[thread overview]
Message-ID: <imAAAD0wNzaoJgkA@jacuzzi.cygnus.co.uk> (raw)

A new snapshot of rc is available from here.

     ftp://ftp.cygnus.com/pub/tgoodwin/rc/snap/rc-1.5s19981028.tar.gz

Nothing too major has changed, although rc has just acquired its first
idiom from C 9x!  (With suitable autoconfiscation for older systems.)
Relevant ChangeLog entries are appended.

Thanks to Bengt Kleberg and Jeremy Fitzhardinge for reporting problems
with the previous snapshot.

Tim.


1998-10-22

  Tidiness: makenonblock() was a rather poor choice of name for
  a function which makes a file descriptor *not* nonblocking :-).

1998-10-26

  Portability: apparently some systems declare `char *basename(const
  char *)' in system header files.  Changing our basename() (in
  history.c) to match this prototype allows it to be compiled on such
  systems, and is harmless.  (Harmless, that is, if no system declares
  `char *basename(char *)'.)

1998-10-28

  Bug: system-bsd.c needs to include "wait.h".

  Warnings: some versions of gcc warn about "ambiguous" `else' clauses.

  Portability: assigning va_list objects doesn't work everywhere (Linux
  on the PowerPC, specifically).  Use the C 9x invention va_copy()
  instead, if it exists, otherwise fall back to assignment.

  Documentation: help HP-UX users by mentioning that you need `cc -Ae'.
  Also, HP-UX make will build rc in a separate directory.

  Tidiness: remove unused functions from print.c.  Anybody wanting to
  use this library in another project should follow the pointer in the
  documentation to an improved version.


                 reply	other threads:[~1998-10-28 23:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=imAAAD0wNzaoJgkA@jacuzzi.cygnus.co.uk \
    --to=tgoodwin@cygnus.co.uk \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /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 NNTP newsgroup(s).