Re: [PATCH] Support AC_CONFIG_LIBOBJ_DIR

[Stepan Kasal]

On Mon, Apr 18, 2005 at 03:59:05PM -0700, Paul Eggert wrote:
> The advantage of expr is that it does the right thing even if
> $ac_config_libobj_dir contains a backslash or other weird character.

I know that some shells interpret `echo "foo\c"' as ``don't print newline.''
Are there other cases?

Moreover, using expr instead of the echo|sed pipe saves two processes
(at least with bash).

And why is it necessary to try to handle AC_CONFIG_LIBOBJ_DIR(/)?
(Perhaps autoconf could complain if it sees it?)

What would be wrong if we replaced the three lines

> >> ac_libobj_dir=
> >> test "X${ac_config_libobj_dir-.}" != X. &&
> >>   ac_libobj_dir=`expr "X$ac_config_libobj_dir/" : 'X\(.*[^/]\)' '|' 'X/' : 
> >> 'X\(/\)'`

with one line:

  ac_libobj_dir=`expr "X$ac_config_libobj_dir" : 'X\(.*[^/]\)'`

Have a nice day,
        Stepan Kasal