* A nested MIME multipart message with a sub-part piped through an external
program (such as HTML with w3m) caused nail to abort after SIGPIPE if the
PAGER command terminated before reading the whole message.
* A 'next' command following a 'hold' command displays the next message
after the one the 'hold' applies to (Bugreport by Mike Sipser). This
might not be exactly what POSIX specifies, but it makes sense and is
consistent with traditional behavior. If you actually favor 'next'
not to advance after 'hold', contact me and I'll add a configuration
option for this.
* If the value of the 'record' variable started with an environment
variable reference such as '$HOME' or with a tilde and the 'outfolder'
variable was set, it was not expanded correctly (Bugreport by Volker
Kuhlmann).
dot uji dot es> in PR 23635.
User-visible changes between 0.6.1 and 0.6.2:
Bug fixes (in particular, gforth-0.6.2 compiles with gcc-3.3)
New words: LATEST, LATESTXT (LASTXT deprecated)
Operating environment: Added optional support for a C interface built
on the ffcall libraries (more portable and powerful than the old
one, but still not documented). To use it, the ffcall libraries
have to be installed before building Gforth (see INSTALL).
Miscellaneous: Gforth-fast now uses static superinstructions (some
speedup on some platforms); generally this is transparent (apart
from the speedup), but there are lots of command-line options for
controlling the static superinstruction generation.
User-visible changes between 0.6.0 and 0.6.1:
Bug fixes (installation on big-endian machines sometimes did not work)
User-visible changes between 0.5.0 and 0.6.0:
Changes in behaviour:
S": interpreted use now ALLOCATEs the string (they live until BYE).
Long word names (512MB on 32-bit systems) are now supported (change to
the header format).
New threaded code execution method: primitive-centric (allows the
following), hybrid direct/indirect threaded (easier portability),
with dynamic superinstructions (typical speedup on Athlon: factor
2). New engine gforth-itc for dealing with some potential
backwards-compatibility problems (see "Direct or Indirect Threaded?"
in the manual).
Operating environment:
Default dictionary size is now 4MB.
Large file support on OSs that support them (i.e., files with more
than 2GB on 32-bit machines).
Gforth can now deal well with broken pipes in most situations.
vi tags files can be built with tags.fs (usage like etags.fs).
gforth.el mostly rewritten.
New image file format.
New words:
Keyboard input: EDIT-LINE K-PRIOR K-NEXT K-DELETE
File input: SLURP-FILE SLURP-FID
Programming tools: ID. .ID WORDLIST-WORDS SIMPLE-SEE
Conditional execution: [DEFINED] [UNDEFINED]
Defining Words: CONST-DOES> ]]
Input stream: PARSE-WORD EXECUTE-PARSING EXECUTE-PARSING-FILE
String comparison: STR= STR< STRING-PREFIX?
String literals: S\" .\" \"-PARSE
Floating point output: F.RDP F>STR-RDP F>BUF-RDP
Miscellaneous:
Generalized prims2x.fs into Vmgen (see README.vmgen etc.); used the
new capabilities in prims (e.g., automatic handling of the return
stack and instruction stream).
- neon to 0.24.4
- subversion to 0.33.1nb1
- subversion-base to 0.33.1nb1
- p5-subversion to 0.33.1nb1
- ap2-subversion to 0.33.1nb2
- py-subversion to 0.33.1nb1
And also the name change of subversion-python to py-subversion.
collection.
The goal of CGI::FormBuilder (FormBuilder) is to provide an easy way
for you to generate and process CGI form-based applications. This
module is designed to be smart in that it figures a lot of stuff out
for you. As a result, FormBuilder gives you about a 4:1 ratio of the
code it generates versus what you have to write.
For example, if you have multiple values for a field, it sticks them
in a radio, checkbox, or select group, depending on some factors. It
will also automatically name fields for you in human-readable labels
depending on the field names, and lay everything out in a nicely
formatted table. It will even title the form based on the name of the
script itself (order_form.cgi becomes "Order Form").
Plus, FormBuilder provides you full-blown validation for your fields,
including some useful builtin patterns. It will even generate
JavaScript validation routines on the fly! And, of course, it
maintains state ("stickiness") across submissions, with hooks provided
for you to plugin your own sessionid module such as Apache::Session.
And though it's smart, it allows you to customize it as well. For
example, if you really want something to be a checkbox, you can make
it a checkbox. And, if you really want something to be output a
specific way, you can even specify the name of an HTML::Template or
Template Toolkit (Template) compatible template which will be
automatically filled in, statefully.
The program mph tries to generate an order preserving minimal perfect
hashing (MPH) function for the set of keys, one per line, on stdin.
Each key can be at most 4095 characters long (see keys.h to increase
this limit), and the keys must be unique. If mph terminates, it emits
a language independent binary or text representation of the MPH
function on stdout. To generate a usable hash function, this output
should be fed to a language dependent filter, like emitc.
e.g.
% mph <foo | emitc >hash.c
The algorithm used by mph is probabilistic - it iterates until it
finds a MPH function. For each failed iteration, it prints a
(cryptic) reason on stderr. There is no no guarantee that mph will
terminate. In practice this is unlikely, unless the constants
specified with options -c or -m are too small.
"This is awf, the Amazingly Workable Formatter -- a "nroff -man" or
(subset) "nroff -ms" clone written entirely in (old) awk.
It is slow and has many restrictions, but does a decent job on most
manual pages and simple -ms documents, and isn't subject to AT&T's
brain-damaged licensing that denies many System V users any text
formatter at all. It is also a text formatter that is simple enough
to be tinkered with, for people who want to experiment.
Type "make r" to run a regression test, formatting the manual page
(awf.1) and comparing it to a preformatted copy (awf.1.out). Type
"make install" to install it. Pathnames may need changing.
I don't know whether awf will run on 16-bit machines. Data requirements
are modest, but I fear the programs are probably big enough to run awk
out of space.
I can't believe I really wrote this.
Henry Spencer at U of Toronto Zoology
henry@zoo.toronto.edu utzoo!henry
13 July 1990"
