code review 161056: cgo now assigns 'void' C name to Size<0 (opaque) types ...

cgo now assigns 'void' C name to Size<0 (opaque) types if dwarf.Common().Type returns nothing.  Ideally, the C name would come from the typedef or pointer that references the Size<0 type, but we can't easily generate this without performing a look-ahead to see if any referencing type will become opaque.  Fixes issue 334.  Fixes issue 281.

[eden.li, 2009-11-26 08:36:38]

Hello rsc,

I'd like you to review the following change.

[rsc, 2009-11-29 23:00:32]

LGTM

I wonder whether the fixes issue comments
need to be on lines of their own.  We'll find out I guess.

[rsc, 2009-11-30 02:14:44]

*** Submitted as http://code.google.com/p/go/source/detail?r=8b51beb7d55a ***

cgo: use C type void for opaque types if dwarf.Common().Type returns nothing

Ideally, the C name would come from the typedef or pointer that
references the Size<0 type, but we can't easily generate this without
performing a look-ahead to see if any referencing type will become opaque.

Fixes issue 334.
Fixes issue 281.

R=rsc
http://codereview.appspot.com/161056

Committer: Russ Cox <rsc@golang.org>