On Tue, 17 Sep 2013 18:45:52 +0200 Lionel Cons wrote:
> On 14 September 2013 00:15, Glenn Fowler <[email protected]> wrote:
> >
> > the AT&T Software Technology ast alpha 2013-09-13 source release
> > has been posted to the download site
> > http://www.research.att.com/sw/download/alpha/
> > the package names and md5 checksums are
> > INIT 327861e49e24dd51079c0a5316a4b2fe
> > ast-open dfb85d1dfb20acb8a1529bdf4b8cb89a
> > ast-ksh 746a556a2259aaa6d75468000e5bc36b
> > the md5 sums should match the ones listed on the download page
> >
> > the change logs below are limited to ksh and libast
> > the libast changes involved a lot of meticulous multibyte code
> > that was hashed out off-list between { gsf roland olga }
> >
> > there is a "news" link in the left side nav bar that will
> > be used to detail implemented and proposed ast features
> > as features mature the news info will migrate to the man pages
> >
> > if your favorite bug/feature is not in the list below then it
> > hasn't been addressed yet and we don't know exactly when it will be
> >
> > changes since 2013-08-29
> >
> > :::::::: ksh93 ::::::::
> >
> > 13-09-13 --- Release ksh93v- ---
> > 13-09-13 +The signal .sh.value variable is now a compound variable with the
> > name
> > value.q corresponding to kill -q signed-integer and value.Q
> > corresponding
> > to kill -Q unsigned-large-integer.
> > 13-09-13 A bug in $(...) command substitution that corrupted a trailing
> > multibyte character in non-UTF-8 locales has been fixed.
> > 13-09-13 Eliminted extranesous output of standard error when ksh is invoked
> > with the -v (verbose) option.
> > 13-09-10 A bug in finding a function defined inside a type that was defined
> > in a namespace has been fixed.
> > 13-09-10 A bug in the binding of function local variables inside arithmeitc
> > expression inside namespaces was fixed.
> > 13-09-10 +A -Q option was added to kill to pass integers as large as
> > pointers.
> > The -q option now only accepts integers as large as typeset -i.
> > 13-09-09 A bug in command substitution has been fixed.
> > 13-09-09 Qualified print format "%([no]unicode)q" added to prefer \u[...]
> > over \w[...] and override LC_OPTIONS=unicode.
> > 13-09-04 +\w[hex] locale-specific code point literals have been added.
> > 13-09-04 +The float(f) math function was added.
> > 13-09-04 +The int(f) math function was fixed to return 0 for floating point
> > numbers larger than the maximum integer.
> > 13-09-04 A bug in which assigning a compound indexed array a value of ()
> > did
> > not preserve the -C attribute has been fixed.
> > 13-09-04 kill -q can now pass numbers as large as typeset -li and
> > .sh.sig.value is typeset -i rather than a compound variable.
> > 13-09-04 kill -q yields the processor and returns 2 when siqueue fails with
> > EAGAIN and yield.
> > 13-09-03 A bug in which $((x.xxx)) where x is a floating point variable and
> > xxx is not one of the known extensions yields a random value has
> > been fixed. It now is unset which has value 0 when set -u is off.
> > 13-09-03 A bug in overriding discipline functions for types defined in
> > namespaces has been fixed.
> > 13-09-03 A bug which on some systems caused a core dump for large <<< here
> > documents has been fixed.
> >
> > :::::::: libast ::::::::
> >
> > 13-09-12 misc/fgetcwd.c: fix stat corruption bug on systems without
> > fdopendir()
> > 13-09-12 path/pathcanon.c: fix bug that added extra / when fgetcwd()
> > returned /
> > 13-09-09 comp/setlocale.c,port/codeset.c: consistent handling of US-ASCII +
> > conformance(0,0) across all os's
> > 13-09-09 string/utf8towc.c,string/wctoutf8.c: add { utf8toutf32()
> > utf8towc() wctoutf8() }
> > 13-09-07 include/ast_std.c,comp/setlocale.c,string/stresc.c: add
> > ast.byte_max for single byte locales
> > 13-09-06 comp/iconv.c: add sfclrerr() to iconv_move() if all input chars
> > not consumed
> > 13-09-06 port/codeset.h,port/codeset.c: internal api for retrieving locale
> > codeset names
> > 13-09-04 string/chresc.c,stresc.c: add \w[hex] support -- thanks Roland
> > 13-09-04 string/utf32stowcs.c,string/wcstoutf32s.c: add -- thanks Roland
> > 13-09-04 sfio/sfsetbuf.c: fix bug where SF_GETR mode was not cleared
> > causing subsequent memory corruption
> > 13-09-04 vmalloc/vmopen.c,vmdcsystem.c,vmstat.c: temporarily set
> > vm->meth.meth=0 to disable vmstat() during init
> > 13-09-04 port/intercept.c: include <ast_standards.h> to ensure fdopendir()
> > prototype if _lib_fdopendir
> > 13-09-04 include/ast_std.h,comp/setlocale.c: add LC_OPTIONS=unicode and
> > AST_LC_unicode
> > 13-09-01 path/pathcanon.c: O_* flags dev path:
> > /dev/file/flags@flag[,flag...]@[/]path
> > 13-09-01 path/pathcanon.c: limit NAMED_XATTR paths to
> > /dev/file/xattr@canonical-path//@//[remainder]
> What happened to the idea of /dev/xattr@? We (after Monday's
> engineering meeting) think that there should be a cleaner separation
> between features:
> 1. /dev/file/flags@path is to add O_* flags to a patch
> 2. /dev/xattr@canonical-path//@//[remainder] is for path manipulation
> Otherwise we risk smearing the boundaries again and revive the concern
> that adding just a flag (xattr) to /dev/file brings back the horrors
> of path normalisation.
I don't like and won't put a variable path component immediately after /dev/
i.e.,
/dev/<variable-name-component>/... not ok
/dev/<some-fixed-name-component>/... ok
/dev/file/ was the consensus fixed prefix
which means the separation between features is in the third component instead
of the second
one feature being "flags" => "open(path,O_flags)"
the other being "xattr" => "fd1=open(path,O_XATTR);openat(fd1,...);close(fd1)"
the only reason for "canonical-path" is to rule out paths that contain //@//
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
