make bfd_target symbol_leading_char variable?

[Hans-Peter Nilsson]

> Date: Thu, 7 Sep 2000 12:54:24 -0700
> From: Nick Clifton <nickc@redhat.com>

> : Another approach could be to make a different bfd_target with
> : only a different symbol_leading_char.  No other targets would be
> : affected.  But I think it would be, um, less clean, and I'm not
> : really sure it is a realistic change.
> 
> Actually this is the way that I would recommend.  To my mind, object
> files containing symbols with leading underscores are different from
> object files without leading underscores.  You cannot link them
> together for instance.  (Well, you can, but it takes some work...)

I thought one purpose of stating symbol_leading_char was to
simplify such linkage.  Uh, it looks indeed it would need some
work.  Never mind.

> Why do you see this as "less clean" ?

[Reading up on assumptions...]  Hohum, because I'm mixing up
bfd_arch_info_type (and machine type differences) with struct
bfd_target. 8-)  Sorry.

I'll have to draw me some inheritance diagram over various bfd
entities and staple it to my forehead or something.

brgds, H-P