On 22 August 2013 17:05, Glenn Fowler <[email protected]> wrote:
>
> On Thu, 22 Aug 2013 11:54:10 +0200 Cedric Blancher wrote:
>> Glenn, when is the next alpha/beta due for AST and for UWIN? Is there
>> a roadmap what you are planning long-term for AST and UWIN?
>
> I've been working on an ast-open pre-alpha that will (hopefully) clean up
> pseudo devs, O_XATTR extended attributes, and *at() usage across ast by
> these pseudo paths
>
>         /dev/<IP-PROTOCOL>/<HOST>/<PORT>
>         /dev/fd/<FD>[/...]
>         /proc/<PID>/fd/<FD>[/...]
>         /dev/file/<FLAG>[,<FLAG>...]:/<ABSOLUTE-PATH>
>         /dev/file/<FLAG>[,<FLAG>...]:<RELATIVE-PATH>
>         /dev/@/:/<ABSOLUTE-PATH>[/@/<RELATIVE-ATTRIBUTE-PATH>]
>         /dev/@/:<RELATIVE-PATH>[/@/<RELATIVE-ATTRIBUTE-PATH>]
>
> currently ast + patches for the non-path variant of these pseudo paths
> is morphing into an #ifdef mess making some portions unreadable and very 
> fragile
>
> the idea is to concentrate all of it in libast so it will be easy to
> debug and extend -- in the current situation a bug fix for say O_XATTR
> might involve a half-dozen or more files and that doesn't include the
> ones that have yet to be patched for O_XATTR -- and these patches are rife
> warnings that would surely get botched in future patches
>
> the current pre-alpha has all ast commands, including cd, working
> on a single O_XATTR entity without any patches to the commands
> (of course making commands aware of the solaris-ish -@ options will
>  involve patches, but that's not part of the pre-alpha experiment)
> "single O_XATTR entity" is key here too, e.g., pax does not yet handle
> archiving a hierarchy+O_XATTR-counterparts, but the idea is that it
> might be able to with a minimal patch involving a new FTS_XATTR
> flag for ast::fts_open() detailed below
>
> this is all in line with novel idea from 1970 that places as many arcane apis
> as possible behind unix filesystem pathnames
>
> dgk is concurrently working on ksh patches
> there should be an ast-ksh package this week with those changes

Are there details of the changes for ast-ksh? I'm running with Roland
Mainz's patch for integer and floating-point constants and I'm quite
happy with it (except that I have to define the constants manually for
each project script).
I'd like to have it included for the next ast-ksh.

Tina
-- 
Tina Harriott  - Women in Mathematics
Contact: [email protected]
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers

Reply via email to