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

thp@cs.ucr.edu
26 Nov 2002 22:15:23 -0500

          From comp.compilers
Related articles
[41 earlier articles]
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-11-26)
Re: Pointers to "why C behaves like that ?" Nicola.Musatti@ObjectWay.it (Nicola Musatti) (2002-11-26)
Re: Pointers to "why C behaves like that ?" nmm1@cus.cam.ac.uk (Nick Maclaren) (2002-11-26)
Re: Pointers to "why C behaves like that ?" peter_flass@yahoo.com (Peter Flass) (2002-11-26)
Re: Pointers to "why C behaves like that ?" fjh@students.cs.mu.OZ.AU (Fergus Henderson) (2002-11-26)
Re: Pointers to "why C behaves like that ?" daniel_yokomiso@softhome.net (Daniel Yokomiso) (2002-11-26)
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-11-26)
Re: Pointers to "why C behaves like that ?" vugluskr@unicorn.math.spbu.ru (Roman Shaposhnick) (2002-11-26)
Re: Pointers to "why C behaves like that ?" vugluskr@unicorn.math.spbu.ru (Roman Shaposhnick) (2002-11-26)
Re: Pointers to "why C behaves like that ?" vugluskr@unicorn.math.spbu.ru (Roman Shaposhnick) (2002-11-26)
Re: Pointers to "why C behaves like that ?" whopkins@alpha2.csd.uwm.edu (Mark) (2002-12-01)
Re: Pointers to "why C behaves like that ?" nmm1@cus.cam.ac.uk (Nick Maclaren) (2002-12-01)
Re: Pointers to "why C behaves like that ?" joachim_d@gmx.de (Joachim Durchholz) (2002-12-01)
[19 later articles]
| List of all articles for this month |
From: thp@cs.ucr.edu
Newsgroups: comp.compilers
Date: 26 Nov 2002 22:15:23 -0500
Organization: University of California, Riverside
References: 02-11-059 02-11-071 02-11-083 02-11-097 02-11-119 02-11-131
Keywords: types
Posted-Date: 26 Nov 2002 22:15:23 EST

Fergus Henderson <fjh@cs.mu.oz.au> wrote:
+ "Manos Renieris" <er+cc@cs.brown.edu> writes:
[...]
+>There is a common misconception that because types are inferred, they
+>are hidden. In fact, the result of the type inference can be
+>presented to the the user.
+
+ Certainly they can be presented to the user, but ...
+
+ So the point is not that inferred types are completely hidden, just
+ that in practice they are much less visible than explicit type
+ declarations in the source code.


Good point. So what would it take to make such helpful and inferrable
information conveniently visible? Perhaps compilers could
(optionally) be required to annotate the source code that is submitted
to them with such information.


More generally, source code could be seen as a database that needs to
support a spectrum of views and queries. Those views could be
tailored to individual tastes and objectives. In particular, views
that are best for a development programmer may not be appropriate for
maintenance programmers.


Tom Payne

Post a followup to this message

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