[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [BusyBox] bb ash IFS behaviour
From:       "Vladimir N. Oleynik" <dzo () simtreas ! ru>
Date:       2001-08-29 6:27:30
[Download RAW message or body]

Arne,

> i just figured out a strange behaviour of IFS in ash, that is not the same
> as it is in bash or the orig (0.3.5) ash:
> 
> her is my example script:

Yes, you are right. POSIX it is difficult for understanding. 
P1003.2, draft 11, 3.5.2
POSIX.2, 3.6.5, (3)(b).
Ohhhh...

Therefore the correct behaviour ash will be, if in the beginning to ash.c add a
line:

#define IFS_BROKEN

;-)
I am not sure, that it will solve all problems of compatibility with bash 
(there this code is simply huge to enter search IFS on initial source bash
enough), 
but as primary ash source will work as.    


--w
vodz



[prev in list] [next in list] [prev in thread] [next in thread]