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

"Roman Shaposhnick" <vugluskr@unicorn.math.spbu.ru>
26 Nov 2002 22:18:02 -0500

          From comp.compilers

Related articles
[45 earlier articles]
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)
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)
[16 later articles]
| List of all articles for this month |

From: "Roman Shaposhnick" <vugluskr@unicorn.math.spbu.ru>
Newsgroups: comp.compilers
Date: 26 Nov 2002 22:18:02 -0500
Organization: St.Petersburg University
References: 02-11-095 02-11-103 02-11-128 02-11-150
Keywords: types, design
Posted-Date: 26 Nov 2002 22:18:01 EST

On 24 Nov 2002 18:38:19 -0500, Joachim Durchholz wrote:
>jacob navia wrote:
>>
>> fn(a)
>> {
>> b = a;
>> }
>>
>> How can you know what "a" is?
>
>No. Hindley-Milner typing is simple and efficient.


  But I suppose they require all pieces of code that has anything
  to do with "a" to be available at once. Note, that we're not
  talking about interpretation, but rather about translation.


  Indeed, environments like Oberon or Java can tackle such problems
  ( though not always with ease ), but the trouble with them is
  that they effectively make themselves a lowest common denominator,
  for the programmer, and I'm really against it. Since in my opinion
  hardware is supposed to be your lowest common denominator.


  So, what I'm really saying is, that while dynamic typing is great
  in theory, I have yet to see a nice practical implementation,
  suitable for big software projects.


Thanks,
Roman.


Post a followup to this message

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