- Subject: [slang-users] slang 2.0.6 released
- From: "John E. Davis" <davis@xxxxxxxxxxxxx>
- Date: Sun, 5 Feb 2006 17:33:38 -0500
Version 2.0.6 has been released--- it is primarily a bug-fix release.
See <http://www.jedsoft.org/slang/download.html> for download options.
Here are the relevant MD5 sums:
efed417548c1c6bd7ff8cbf0165103df 2.0.5__2.0.6.diff.bz2
e87d632be3c618cbe3826ca9d08db46a 2.0.5__2.0.6.diff.bz2.sig
3a44ef4ccd557ba527c74aca0a9df9c9 2.0.5__2.0.6.diff.gz
37ce724df3f9365dbed726e4bcf58fd4 2.0.5__2.0.6.diff.gz.sig
efb055000636f312d5c3de56f3c70d12 slang-2.0.6.tar.bz2
1214405732547eb641d78794316e4235 slang-2.0.6.tar.bz2.sig
fb8ab2dfc3d8f44b9161b9b0e0c94141 slang-2.0.6.tar.gz
fe751335066708642fd66385cc4e8985 slang-2.0.6.tar.gz.sig
Enjoy. --John
Changes since 2.0.5
1. src/slmath.c: nint was returning the wrong value for numbers 0.5<=x<1.
2. src/slarrfuns.c: sum(Double_Type[0,0],1) was generating an access
error.
3. src/*.c: Removed some unused variables.
4. src/slcommon.c: '=' instead of '==' was being used in the
utf8_enable function.
5. doc/tm/*.tm: corrected some documentation typos (Nelson Beebe,
beebe at math, utah, edu).
7. src/sltime.c: times function was returning a structure containing
incorrect values (cstawarz at head, cfa, harvard, edu).
8. src/sldisply.c: Writing a multi-byte character to the lower-right corner
of terminals with automatic margins was not working (Vladimir
Nadvornik nadvornik at suse, cz).
9. src/slwclut.c: Allow \\^ in character set specifications to
represent a literal '^'. See the documentation for strtrans for
more information.
10. src/slcommon.c: Some systems that have nl_langinfo do not have
CODESET. The configure script now checks for both.
11. autoconf/Makefile.in: Added ".PHONY" and "check" targets.
12. src/slstrops.c: "%c" in an sprintf style format descriptor made to
work with wide-character arguments. It is nolonger necessary to
use "%lc".
13. src/slmisc.c: Semantics of "\x{...}" changed to be more useful
when the interpreter is running in non-UTF8 mode. Previously,
"\x{...}" always expanded to a UTF-8 encoded string, regardless of
the UTF-8 mode. Now, in non-UTF8 mode, \x{...} will expand to a
UTF-8 encoded string when "..." consists of 3 or more characters,
and for less than 2 characters, it specifies a byte. The behavior
in UTF-8 mode has not changed: \x{...} always returns a UTF-8
encoded string. The upshot is that "\x{FF}" will produce the byte
0xFF when not in UTF-8 mode, and the 2 byte UTF-8 encoding when
run in UTF-8 mode. "\x{FFF}" will expand to the apropriate UTF-8
encoding regardless of the mode. Note that the behavior of the
non-brace form such as \xAB has not changed--- the result is still
a single byte 0xAB.
14. src/slmisc.c: \u{...} may be used in string literals to specify a
unicode character, regardless of the UTF-8 mode (on or off).
Previously, \x{...} had this behavior. (See #13).
15. src/test: Tests are run in both UTF-8 and non-UTF-8 modes.
16. src/slvideo.c: djgpp version of write_attributes was broken (Gisle
Vanem giva at bgnett, no)
17. slsh/readline.c: Call SLang_handle_interrupt if a read was
interrupted by a signal. This will ensure that signal handlers
will execute at the prompt.
18. src/sldisply.c: Added a check for buffer-overflow by tgetstr on TERMCAP
based systems.
19. autoconf/: Updated config.sub and config.guess
20. slsh/readline.c: Added slsh_readline_noecho function. Also, strip
trailing newline from string returned by slsh_readline* when in
--no-readline mode.
_______________________________________________
To unsubscribe, visit http://jedsoft.org/slang/mailinglists.html
[2006 date index]
[2006 thread index]
[Thread Prev] [Thread Next]
[Date Prev] [Date Next]