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

"Peter Flass" <peter_flass@yahoo.com>
1 Dec 2002 22:37:13 -0500

          From comp.compilers

Related articles
[48 earlier articles]
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)
Re: Pointers to "why C behaves like that ?" peter_flass@yahoo.com (Peter Flass) (2002-12-01)
Re: Pointers to "why C behaves like that ?" fjh@students.cs.mu.OZ.AU (Fergus Henderson) (2002-12-01)
Re: Pointers to "why C behaves like that ?" thp@cs.ucr.edu (2002-12-01)
Re: Pointers to "why C behaves like that ?" dot@dotat.at (Tony Finch) (2002-12-01)
Re: Pointers to "why C behaves like that ?" dot@dotat.at (Tony Finch) (2002-12-01)
Re: Pointers to "why C behaves like that ?" sander@haldjas.folklore.ee (Sander Vesik) (2002-12-01)
Re: Pointers to "why C behaves like that ?" fjh@students.cs.mu.OZ.AU (Fergus Henderson) (2002-12-03)
[12 later articles]
| List of all articles for this month |

From: "Peter Flass" <peter_flass@yahoo.com>
Newsgroups: comp.compilers
Date: 1 Dec 2002 22:37:13 -0500
Organization: Road Runner
References: 02-11-059 02-11-071 02-11-083 02-11-091 02-11-155
Keywords: types, practice
Posted-Date: 01 Dec 2002 22:37:13 EST

David Thompson wrote:
> In PL/I also, as already noted, declarations can be omitted if the
> default is correct, but if present can occur anywhere even after
> reference; I don't recall seeing any good use for this except nested
> PROCs.


There are lots, but one significant one is to allow declarations and
executable code in macros, which can be placed anywhere in a program.
Since we're talking about not forcing humans to do what can be done by
machine, I would count not forcing a specific placement of
declarations here also.


Post a followup to this message

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