i added a function to 9load's lib.h today declared incorrectly.
9load uses lib.h so one doesn't haul in the entire c library by
accident. there were no link errors. it didn't crash, but did some
difficult to explain things.  now fixed.

i believe other times i've declared an extern function incorrectly
and the linker has given me diagnostics.  but when i looked at
/386/lib/libc.a, there are no type signatures and it turns out the
default is that they are not generated.

so, am i wrong that i have seen diagnostics for incompatable
type signatures?  and, why aren't the signatures put into
object files by default?

- erik

Reply via email to