Linus Nordberg <[EMAIL PROTECTED]> writes:
| Akim Demaille <[EMAIL PROTECTED]> wrote
| 17 Mar 2000 16:05:33 +0100:
|
|I preferred the former order because so that the white chars are never
|last on the line.
|
|IFS="
| "
|
|is more explicit than
|
|IFS="
|"
Av
I've spent the last few months working on improving OpenBSD m4.
I've committed the final patch a few days ago.
So I am very happy to announce that our m4 is now able to handle a large
enough subset of builtins to substitute for gnu-m4 in autoconf.
I believe this to be of benefit to everybody...
On Mar 18, 2000, Jim Meyering <[EMAIL PROTECTED]> wrote:
> How about defining
> ac_nl='
> '
How about:
IFS=" """"
"
BTW, this won't work as expected if `configure' is generated on
platforms that use CR+LF as line separators. We should probably try
to find some way that does the right
Alexandre Oliva <[EMAIL PROTECTED]>:
> BTW, this won't work as expected if `configure' is generated on
> platforms that use CR+LF as line separators. We should probably try
> to find some way that does the right thing even in such contexts.
how about
IFS=`echo 'abc' | tr 'abc' '\040\011\012'`
Akim Demaille <[EMAIL PROTECTED]> writes:
>> "Jim" == Jim Meyering <[EMAIL PROTECTED]> writes:
> Jim> I for one am strongly in favor of requiring Perl 5 (and -w and
> Jim> `use strict', of course). autoscan is definitely a
> Jim> maintainer-only tool, and Perl 4 is just too limiting these da
On Mar 18, 2000, Felix Lee <[EMAIL PROTECTED]> wrote:
> Alexandre Oliva <[EMAIL PROTECTED]>:
>> BTW, this won't work as expected if `configure' is generated on
>> platforms that use CR+LF as line separators. We should probably try
>> to find some way that does the right thing even in such contex
Alexandre Oliva <[EMAIL PROTECTED]>:
> This assumes ASCII. We've just removed the latest assumptions of
> ASCII, so it wouldn't be wise to re-introduce them :-)
oh. hmm. then how about using awk?
IFS=`awk 'BEGIN { printf " \t\n" }' /dev/null`
--
On Mar 19, 2000, Felix Lee <[EMAIL PROTECTED]> wrote:
> Alexandre Oliva <[EMAIL PROTECTED]>:
>> This assumes ASCII. We've just removed the latest assumptions of
>> ASCII, so it wouldn't be wise to re-introduce them :-)
> oh. hmm. then how about using awk?
> IFS=`awk 'BEGIN { printf " \t\n"
Alexandre Oliva <[EMAIL PROTECTED]>:
> > IFS=`awk 'BEGIN { printf " \t\n" }' /dev/null`
> Did you know that shells do eat up trailing new-lines, and that's why
> we can't do it this way? :-)
so reverse it.
IFS=`awk 'BEGIN { printf "\n \t" }' /dev/null`
--
On Mar 19, 2000, Felix Lee <[EMAIL PROTECTED]> wrote:
>> Did you know that shells do eat up trailing new-lines, and that's why
>> we can't do it this way? :-)
> so reverse it.
I think awk is overkill for that, since it can be done with plain
echo. Moreover, I'm not really sure `\t' and `\n' ar
Alexandre Oliva <[EMAIL PROTECTED]>:
> I think awk is overkill for that, since it can be done with plain
> echo. Moreover, I'm not really sure `\t' and `\n' are portable AWK.
well, I'm not fond of embedding tabs in scripts. \t and \n
should be portable awk. they were in the original awk.
--
11 matches
Mail list logo
