On 24 May 2013 08:54, Glenn Fowler <[email protected]> wrote: > > the AT&T Software Technology ast alpha 2013-05-24 source and binary release > has been posted to the download site > http://www.research.att.com/sw/download/alpha/ > the package names and md5 checksums are > INIT ed29bc9017e7bed828b66977c474f3dc > ast-ksh ec93af891a10071d65afe581be31df30 > the md5 sums should match the ones listed on the download page > if not then don't download > > this alpha includes updated -last { aso cdt vmalloc } > which should be in much better shape in multi-threaded apps > > these updates represent a flurry of activity surrounding the > retirement of long time ast colleague Phong Vo (moving on to google) > and making sure all of his latest stuff is properly merged into ast > > since a lot of his code touches the heart of ast the merging is > a meticulous process and has taken up most of my ast time > the biggest effect w.r.t. the list has been to make note of but > not act on any non-ksh patches -- once the merge is done we'll start > looking at those patches (we've learned over the years that even the > smallest innocent patch has the ability to wreak havoc on a release -- > debugging kpv merged code is hard enough -- adding in other changes > at the same time could tip the process into chaos) > > the next ast-open alpha will be early next week > that will include updated -lvcodex and vczip > > a corresponding uwin alpha will be about 2 weeks away
Is the update going to include the fma() function on UWIN? Ced ---------- Forwarded message ---------- From: Cedric Blancher <[email protected]> Date: 2 April 2013 13:54 Subject: Re: [uwin-developers] Beginner and usability problems with uwin beta To: ольга крыжановская <[email protected]>, [email protected] On 2 April 2013 12:36, ольга крыжановская <[email protected]> wrote: > David and Glenn, I have collected some usability problems, from both > beginner, programmer and usability stand points, which might be nice > to address: > > -- Documentation: > - Documentation needs a general update > - /usr/doc should not contain *.ico files > - /usr/doc should have sub directories, one per topic or application > - Intro manual page for each populated section, i.e. Intro(1) and > Intro(8), as POSIX requires, is missing > - man ksh does not work if only the base uwin package is installed > - man -b ksh prints warnings like man[148]: mktemp: not found [No such > file or directory] > - man vi does not work > > -- Usability: > - /usr/bin/vi does not have cursor keys, which work. This is > confusing, for the beginner. Cygwin does not have the same issue. > - Characters out side ASCII do not work, even on machines with extra > language packs installed. My test machine has Cyrillic installed but > still does not support Cyrillic characters. A read -N1 c ; print > character-number shows that ksh93 always operates in single-byte mode, > even if LC_ALL is set to en_US.UTF-8 or C.UTF-8 > - The default editor mode of vi in uwin ksh93 is a pain, for > beginners. Please consider using gmacs like SUN did for Solaris 11 to > aid beginners. That should be set in /etc/ksh.kshrc > - There should be a reasonable PS1 prompt which displays $LOGNAME and > the last characters of the pwd, defined via /etc/ksh.kshrc > - ksh93 in uwin does not support /etc/ksh.kshrc > > -- Programmer issues: > - There is no alternative to vi, like emacs, installed. If vi is > busted, there is no way to recover > - No default version control management is available in the base > package, neither svn, my preference, or git > - A lot of the utilities, like getent and pagesize, used by autoconf > or other auto build and config systems, are missing > - shcomp is missing > - newgrp is missing, to switch the primary group of a process Olga, thanks for compiling the list of issues. Here's my take on urgent problems: - grep is not available as shell builtin - poll is not available as shell builtin - ksh93 does not support the fma() (fused multiply add) math function in (( ... )) - Code page in Windows console does not default to UTF-8 - The uwin beta can not be uninstalled using Control Panel->Add or Remove Programs in Windows NT, XP and 7 - That Windows console cursor keys are not supported by vi is a pest - Windows console uses vt100 as default terminal. Can this be updated to vt220 or is that not possible? Cygwin uses its own terminal type TERM="cygwin" which is near vt220 * If the Windows console problems (UTF-8, cursor keys!!!!) are to hard to fix, could you ship http://www.chiark.greenend.org.uk/~sgtatham/putty/ (MIT licensed!!)? Ced -- Cedric Blancher <[email protected]> Institute Pasteur -- Cedric Blancher <[email protected]> Institute Pasteur _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
