Related articles |
---|
[26 earlier articles] |
Re: Pointers to "why C behaves like that ?" whopkins@alpha2.csd.uwm.edu (Mark) (2002-11-24) |
Re: Pointers to "why C behaves like that ?" whopkins@alpha2.csd.uwm.edu (Mark) (2002-11-24) |
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-11-24) |
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-11-24) |
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-11-24) |
Re: Pointers to "why C behaves like that ?" stephen@dino.dnsalias.com (Stephen J. Bevan) (2002-11-24) |
Re: Pointers to "why C behaves like that ?" cgweav@aol.com (Clayton Weaver) (2002-11-24) |
Re: Pointers to "why C behaves like that ?" joachim_d@gmx.de (Joachim Durchholz) (2002-11-24) |
Re: Pointers to "why C behaves like that ?" joachim_d@gmx.de (Joachim Durchholz) (2002-11-24) |
Re: Pointers to "why C behaves like that ?" jacob@jacob.remcomp.fr (jacob navia) (2002-11-26) |
Re: Pointers to "why C behaves like that ?" jacob@jacob.remcomp.fr (jacob navia) (2002-11-26) |
Re: Pointers to "why C behaves like that ?" jacob@jacob.remcomp.fr (jacob navia) (2002-11-26) |
Re: Pointers to "why C behaves like that ?" david.thompson1@worldnet.att.net (David Thompson) (2002-11-26) |
[34 later articles] |
From: | "Clayton Weaver" <cgweav@aol.com> |
Newsgroups: | comp.compilers |
Date: | 24 Nov 2002 18:35:46 -0500 |
Organization: | AOL http://www.aol.com |
References: | 02-11-122 |
Keywords: | types, design |
Posted-Date: | 24 Nov 2002 18:35:45 EST |
(re: type declarations)
What I want to know when programming or looking at other people's code
is:
What exactly is happening to which data in what order?
Do type declarations enhance or impede that
specification/comprehension?
That is the only interesting question about them. The time/space to
specify them in the code is trivial whether you have to spend it or
not.
Regards,
Clayton Weaver
<mailto: cgweav@aol.com>
Return to the
comp.compilers page.
Search the
comp.compilers archives again.