From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <80c1297bd7bfb8fa14b4b7ef659d1673@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 18 Jan 2008 19:45:01 -0500
To: 9fans@cse.psu.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] type signatures
Topicbox-Message-UUID: 325acd24-ead3-11e9-9d60-3106f5b1d025

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