summaryrefslogtreecommitdiffstats
path: root/RELNOTES
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2016-04-22 20:33:12 -0700
committerKaz Kylheku <kaz@kylheku.com>2016-04-22 20:33:12 -0700
commit8c714ee8ff6eb5e0030a3b12935512b82fd8b00e (patch)
treee7e895e2e30f23e98d2dd1c1df002379e744b4c3 /RELNOTES
parentd02c189c2709291d77cf2c64e03f1b95301815b8 (diff)
downloadtxr-139.tar.gz
txr-139.tar.bz2
txr-139.zip
Version 139.txr-139
* RELNOTES: Updated. * configure, txr.1: Bumped version and date. * share/txr/stdlib/ver.tl: Likewise. * txr.vim, tl.vim: Regenerated.
Diffstat (limited to 'RELNOTES')
-rw-r--r--RELNOTES41
1 files changed, 41 insertions, 0 deletions
diff --git a/RELNOTES b/RELNOTES
index e6fdd2a1..9d862f50 100644
--- a/RELNOTES
+++ b/RELNOTES
@@ -1,3 +1,44 @@
+ TXR 139
+ 2016-04-23
+
+
+ Features
+
+ - Change of rules regarding Lisp variable visibility in TXR
+ Pattern language.
+ - unget-char now allows more than one character of pushback.
+ - The POSIX fnmatch function is now available.
+ - Rules used by object printer for deciding which character objects
+ and string constituent characters to print using hex escapes
+ have been harmonized together, with some changes to both.
+ - path-private-to-me function avoids making unnecessary call
+ to getgrgid, which is somewhat heavy-weight.
+ - A list can now be passed as the path argument to the ftw
+ function; it will recurse over it.
+
+ Bugs
+
+ - Issue of certain macros not expanding in @(output) blocks.
+ - Macro not expanding as argument of @(if) directive.
+ - Newline not being allowed in string fed to regex-parse.
+ - Broken unget-char operation over string input streams.
+ - Rewrite of horribly broken read-until-match function,
+ which also fixes broken record streams feature
+ (record-adapter function).
+ - Fixed optional argument in get-string not defaulting
+ properly.
+ - Out of range character escapes are diagnosed better.
+ - regex-parse was silently returning nil upon syntax
+ errors; now throws exception.
+ - regex-parse was not handling non-UTF-8 bytes in the
+ string: are now mapped to U+DCXX block now and
+ incorporated as literal characters.
+ - Numerous memory leaks fixed which could occur in various
+ functions if a type mismatch exception occurs after
+ some local resource has already been allocated.
+
+
+
TXR 138
2016-04-16