Re: Pointers to "why C behaves like that ?"

"Mark Alexander Wolton" <mwotton@cse.unsw.edu.au>
20 Nov 2002 15:15:59 -0500

          From comp.compilers

Related articles
[4 earlier articles]
Re: Pointers to "why C behaves like that ?" jacob@jacob.remcomp.fr (jacob navia) (2002-11-15)
Re: Pointers to "why C behaves like that ?" christian.bau@freeserve.co.uk (Christian Bau) (2002-11-17)
Re: Pointers to "why C behaves like that ?" Gayev.D.G.=?iso-8859-1?Q?=3Cdg=E0ev=40mail=2Eru=3E (2002-11-17)
Re: Pointers to "why C behaves like that ?" bobduff@shell01.TheWorld.com (Robert A Duff) (2002-11-17)
Re: Pointers to "why C behaves like that ?" jamesp_spam_me_not@silver-future.com (James Powell) (2002-11-17)
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-11-17)
Re: Pointers to "why C behaves like that ?" mwotton@cse.unsw.edu.au (Mark Alexander Wolton) (2002-11-20)
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-11-20)
Re: Pointers to "why C behaves like that ?" marcov@toad.stack.nl (Marco van de Voort) (2002-11-20)
Re: Pointers to "why C behaves like that ?" n368714668.ch@chch.demon.co.uk (Charles Bryant) (2002-11-20)
Re: Pointers to "why C behaves like that ?" peter_flass@yahoo.com (Peter Flass) (2002-11-20)
Re: Pointers to "why C behaves like that ?" peter_flass@yahoo.com (Peter Flass) (2002-11-20)
Re: Pointers to "why C behaves like that ?" er+cc@cs.brown.edu (Manos Renieris) (2002-11-20)
[56 later articles]
| List of all articles for this month |

From: "Mark Alexander Wolton" <mwotton@cse.unsw.edu.au>
Newsgroups: comp.compilers
Date: 20 Nov 2002 15:15:59 -0500
Organization: The University of New South Wales
References: 02-11-059 02-11-071 02-11-083 02-11-097
Keywords: C, design
Posted-Date: 20 Nov 2002 15:15:59 EST

Robert A Duff wrote:
> Declarations make programs easier to understand, presuming you are
> declaring useful information (useful to the human reader).
>
> Somebody mentioned type inference in ML. My opinion is: it's nice
> *within* a single function, but the *interfaces* to pieces of software
> ought to have *explicit* declarations of types, so I can understand
> them without reading all the code.


I agree completely. In the process of development of a module, though,
types can change dramatically, and type inference allows you to avoid
the janitorial jobs. An interface should always be explicitly typed.


mrak


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.