On Sun, Dec 11, 2005 at 06:46:39PM -0200, Alexandre Oliva wrote:
> Err... The above is a bit misleading, in that it at first appeared to
> be referring to the target of the weakref, not to the weakref itself.
> The weakref may alias to something that is static or not (the whole
> point is being able to refer to symbols in other translation units
> with weak and non-weak semantics). The weakref itself could be static
> or extern, and both possibilities could be argued for and match
> certain uses. Since attribute alias has traditionally required the
> extern keyword, I figured it would make sense to keep it as such, but
> if you prefer to change that and adjust all cases in which the use of
> static might cause problems, that's certainly fine with me. I don't
> see that you're taking care of such cases, though.
Yeah, as shown on the s390 bootstrap failure, I suspect there will be
many such corner cases lurking around on various targets.
I prefer weakrefs to be extern too.
Jakub
