On Thu, 26 Apr 2012 23:36:30 +0200 Lionel Cons wrote: > On 23 April 2012 23:29, David Korn <[email protected]> wrote: > > Currently, the delimiter must be a one byte character. We plan to > > update this in a release later this year.
> What exactly is the difficult part? ksh93 already supports one byte > delimiters. Non-ASCII characters can both be represented by a wchar_t > or a multibyte sequence. The multibyte sequence could be used as C > string and this C string could be used as delimiter, i.e. you search > for a C string as delimiter instead of a single byte. I'll add to what dgk said in general the difficult part of changes in ast is not getting a test case or patch to work the difficult part is to do it in a way that * builds on all target architectures * works the same on all target architectures * does it "the ast way" (implement once use everywhere) a lot of the underlying libraries have already taken care of the difficult parts so if we can leverage new features on top of proven features we can save ourselves a lot of work in some cases, like this one, extending a library api, even though it may take longer to code and test, will pay off when the second and so on ast command needs the same feature _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
