On Fri, 30 Aug 2013 05:11:55 +0200 Cedric Blancher wrote: > On 29 August 2013 19:45, Glenn Fowler <[email protected]> wrote: > > > > the AT&T Software Technology ast alpha 2013-08-29 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 132e0403af573fa1cb1e202267fedeb8 > > ast-open 334615fb3a652575106194c281d27b5c > > ast-ksh ebcc56d9ab673aaafbb163d6eee1a93c > > the md5 sums should match the ones listed on the download page > > > > this is still a work in progress, but we are getting closer to a beta > > we are interested in verification that new features work > > and at this point not interested in quibbles about naming > > once the underlying features work then naming discussions can commence > > > > a big chunk of time was spent porting to the various combinations of > > architectures X os X compilers X build options > > a lot of it due to differing levels of support for the *at() syscalls > > which then kicked in different parts of the -last emulation code > > > > with adoption of *at() file descriptor leaks pop up all over the place > > to see how bad *at() coverage is on different os/release combinations > > compare > > $INSTALLROOT/src/lib/libast/FEATURE/atdev > > produced by > > $PACKAGEROOT/src/lib/libast/features/atdev.c > > on different os/release combinations > > > > one file descriptor leak in 3d+ksh brought down the entire build system > > it took a day to figure everything out and recover, including code checkins > > that sometimes did the opposite (keep old drop new) > > so once again there is no such thing as a simple patch > > > > don't use this alpha on linux.ia64 -- looks like *at() problems are lurking > > there > > > > look for ast runtime debugging tips in a separate message > > > > changes since 2013-08-14
> Another bug (still trying to calm down over the cd -@ disaster): > namespaces don't work for compiled shell scripts: > test namespace begins at 2013-08-30+04:43:32 > test namespace passed at 2013-08-30+04:43:32 [ 21 tests 0 errors ] > test namespace(shcomp) begins at 2013-08-30+04:43:32 > /tmp/tmpdQ9k6Kl.MdM/shcomp-namespace.ksh: line 127: .a.b.x_t: not found > /tmp/tmpdQ9k6Kl.MdM/shcomp-namespace.ksh: line 128: var.pi: not found > discipline functions for types in namespace not working > /tmp/tmpdQ9k6Kl.MdM/shcomp-namespace.ksh: line 138: > .com.foo.test1.y_t: not found > /tmp/tmpdQ9k6Kl.MdM/shcomp-namespace.ksh: line 139: v.x.pr: not found > shcomp-namespace.ksh[139]: _.__ not working with nested types > in a namespace > test namespace(shcomp) failed at 2013-08-30+04:43:32 with exit code 1 > [ 21 tests 1 error ] speaking for dgk here he's on holiday for the long us end of summer weekend celebrating his birthday typical progression for new ksh features is to first get them working in scripts then after they soak for a while the compiler is brought up to speed i.e., why update the compiler for a feature that isn't totally fleshed out and tested? _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
