Spec#, nullables and more

["Jérôme M. Berger"]

Gary Whatmore wrote:
> Pelle M�nsson Wrote:
> 
>> On 11/05/2010 12:43 PM, Gary Whatmore wrote:
>>> bearophile Wrote:
>>>> - A way to list what attributes are modified in a method (similar to my @outer).
>>> The compiler should do this itself.
>> Doesn't make sense.
>>
>>>> My reference issue:
>>>> http://d.puremagic.com/issues/show_bug.cgi?id=4571
>>> Walter, please close this as wontfix. We don't need those. These extra runtime checks will slow down my code. I know myself when my pointer is null.
>>>
>>>   - G.W.
>> How, exactly, do you know when your references are null? Without 
>> runtime checks, of course.
> 
> Good code design makes the null pointer exceptions go away. I carefully ponder what code goes where. Simple as that. That language just introduces a boatload of unnecessary cruft in forms of runtime null checks. I don't need to know the exact temporal location of nulls, it's enough if the code takes care of handling it at run time.

	Who said anything about runtime checks? Non-nullable types are
enforced at compile-time anyway...

		Jerome
-- 
mailto:jeberger at free.fr
http://jeberger.free.fr
Jabber: jeberger at jabber.fr

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20101105/47e65355/attachment.pgp>