sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Alistair Crooks <>
Subject: libutf-2.9 and ssam-1.8
Date: Wed, 16 Jul 1997 12:16:06 -0400	[thread overview]
Message-ID: <> (raw)

I've finally got around to doing some things that were on the back
burner - changes outlined below, but they're just bug fixes, with some
extra tests added for good measure.
The new versions have been uploaded to:

As usual, the correct way to install the software is as follows:
% tar xvzf libutf-2.9.tar.gz
% cd libutf-2.9
% ./configure
% make tst
% make install
% cd ..
% tar xvzf ssam-1.8.tar.gz
% cd ssam-1.8
% ./configure
% make tst
% make install
A list of the changes appears at the end of this mail.
This has been tested on UTS 4.3.2 (S390 mainframe), Solaris 2.4 (SS5),
and NetBSD/i386 1.2G.
Sorry about the bugs,
ssam-1.8 changes
+ Alan Watson ( pointed out a bug whereby two
sequential commands cause changes to happen, and these changes cause
the carefully ordered stack to be unordered.  This only manifests
itself where more than one pass over the file takes place.  Added code
to sort the changes into `from' address order, and order on deletion
and insertion within that.
+ Added symbolic constants to the parse tables. This pushes column
indentation out a bit, at the expense of making things much more
+ Byron Rakitzis ( pointed out an anomaly with sam,
whereby a nul-byte terminated expression was allowed in sam, but
produced an error in ssam.  Eventually found time to fix this. 
Removed UnterminatedArg error constant and message, and change tests
libutf-2.9 changes
+ zero-byte terminate the arrays we copy in utfcpy
+ sort out utf_snprintf so that stdargs are handled correctly - I
don't know if it's just gcc, but shorts and chars are put on the
stack as ints, so, when we pop them off the stack, pop them off as

                 reply	other threads:[~1997-07-16 19:58 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).