Re: static typing
Nathan Baum wrote:
On Mon, 7 Aug 2006, Pascal Bourguignon wrote:
As for type inference, what more do you want than:
* (defun k (x) (car (+ 1 x)))
; in: LAMBDA NIL
; (CAR (+ 1 X))
;
; caught WARNING:
; Asserted type LIST conflicts with derived type (VALUES NUMBER &OPTIONAL).
; See also:
; The SBCL Manual, Node "Handling of Types"
;
; compilation unit finished
; caught 1 WARNING condition
Sure, but that isn't a requirement of the standard.
Now if only we didn't /have/ a standard, that problem would nicely go
away.
.
Relevant Pages
- IA64 (2.6.3 - 2004-02-20.17.30) - 309 New warnings (gcc 3.3.1)
... make: warning: Clock skew detected. ... :10306: Warning: This is the location of the conflicting usage ... {standard input}:10315: Warning: Only the first path encountering the conflict is reported ...
(Linux-Kernel) - 2.6.22-rc3-mm1: IA64 make allnoconfig broken
... {standard input}:12494: Warning: Only the first path encountering the conflict is reported ... :12493: Warning: This is the location of the conflicting usage ...
(Linux-Kernel) - IA64 (2.6.4-rc1 - 2004-02-28.17.30) - 165 New warnings (gcc 3.3.1)
... :10487: Warning: This is the location of the conflicting usage ... {standard input}:10489: Warning: Only the first path encountering the conflict is reported ...
(Linux-Kernel) - Re: Inconsistent Program Results
... including one of them might trivially slow down compilation, ... I wrote the above (starting with "The standard headers"). ... return void, but there's no advantage in using that. ... You're cheating yourself by ignoring warning messages. ...
(comp.lang.c) - Re: vista update
... Do you disagree that it should have that warning? ... you are being silly - that is not a standard reboot! ... rebooting from either OS X or Windows in their normal ways... ...
(comp.sys.mac.advocacy) |
|
