On Fri, 14 Sep 2012 15:27:35 +0200 Simon Toedt wrote: > On Wed, Aug 29, 2012 at 5:07 PM, David Korn <d...@research.att.com> wrote: > > Subject: Re: Re: [ast-developers] libcmd builtin wish: iconv > > -------- > > > > > >> We need a single ksh binary with grep builtin. If we deploy multiple > >> files with .paths then we have to convince at least 11 groups at our > >> site that this makes sense, doesn't affect them and is worth to put > >> this on the agenda of lots of meetings. Not to mention the yapping > >> about using perl instead. > >> > > > > We want to do this as a compile option but we would like to associate > > grep with a path, most likely the one found in the standard path. > > This will allow a user to override the one we provide.
> You do have /opt/ast (or /usr/ast on some platforms) for that. > Sorry for asking a question which may have been discussed: Why does it > take that long to add grep to ksh93? the coding could be and has been done in minutes but although ast grep (or other ast command => builtin candidates) may be posix compliant they are not necessarily <your-favorite-vendor-variant-here> compliant providing a PATH-based way for users to explicitly enable ast builtins is an opt-in users finding incompatibilities between ast-builtin-foo and native-standalone-foo can deal with that by selectively opting-in and opting-out via PATH manipulation using the same mechanism that has been used since 1970 to dance between different standalone foo implementations using PATH compiling a builtin directly into a ksh executable is an entirely new vector the implications of which are not completely understood *and in addition and reiterating* the conversion of formerly stanadlone commands to builtins is not yet a bug-free process there are still interactive problems with signals that are being worked out its much better working those problems out with experienced users who explicitly opt-in rather than using the m$ model of making everyone a debugger by default and its much easier to change PATH than to apply a patch and redeploy ksh and, for the purposes of testing new vectors, its much easier to be able to separate builtin problems from ksh proper Roland has provided a patch for those users who want to opt-in at compile time but at the moment we would rather not add compiled-in-builtins to the debugging todo list so the patch is not the default _______________________________________________ ast-developers mailing list ast-developers@research.att.com https://mailman.research.att.com/mailman/listinfo/ast-developers
