Re: Distinguish between code and data symbols on every system

[Ralf Wildenhues]

* Gary V. Vaughan wrote on Wed, Sep 15, 2004 at 12:45:47AM CEST:
> 
> Hallo Ralf,
> 
> On 14 Sep 2004, at 18:36, Ralf Wildenhues wrote:
> >2004-09-14  Ralf Wildenhues <address@hidden>
> >
> >     * m4/libtool.m4 (_LT_CMD_GLOBAL_SYMBOLS): Simplification:
> >     distinguish between data and code symbols on every system.
> >     Actually use the last computed value of $symcode for the
> >     transformations.
> 
> Thanks, applied.  I dropped the last sentence of your ChangeLog
> entry though, `cos it always worked that way (the $symcode is in
> single quotes), just the order of the code was wierd before.

I don't think so:

lt_cv_sys_global_symbol_to_cdecl="sed -n -e 's/^T .* \(.*\)$/extern int 
\1();/p' -e 's/^$symcode* .* \(.*\)$/extern char \1;/p'"
lt_cv_sys_global_symbol_to_c_name_address="sed -n -e 's/^: \([[^ ]]*\) $/  
{\\\"\1\\\", (void *) 0},/p' -e 's/^$symcode* \([[^ ]]*\) \([[^ ]]*\)$/  
{\"\2\", (void *) \&\2},/p'"

Single quotes lose their special meaning when within double quotes:

$ foo=bar
$ frob="'$foo'"
$ foo=baz
$ echo $frob
'bar'

One could do something like
  frob="before"'${foo}'"after"
because the expression will be eval'ed.  But in this case it's not worth
it, since symcode will not change anyways.

Regards,
Ralf