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

"Nicola Musatti" <Nicola.Musatti@ObjectWay.it>
26 Nov 2002 22:07:12 -0500

          From comp.compilers

Related articles
[36 earlier articles]
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)
Re: Pointers to "why C behaves like that ?" ajo@andrew.cmu.edu (Arthur J. O'Dwyer) (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 ?" 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)
[24 later articles]
| List of all articles for this month |
From: "Nicola Musatti" <Nicola.Musatti@ObjectWay.it>
Newsgroups: comp.compilers
Date: 26 Nov 2002 22:07:12 -0500
Organization: Compilers Central
References: 02-11-059 02-11-087 02-11-089 02-11-130 02-11-144
Keywords: design, types
Posted-Date: 26 Nov 2002 22:07:12 EST

thp@cs.ucr.edu wrote:
> Nicola Musatti <nicola.musatti@objectway.it> wrote:
[...]
> It may be possible to have our cake and eat it too -- most of it,
> anyway. To accomodate generic programming, C++ must do a lot of type
> inference, especially in the case of function templates, whose type
> parameters are statically inferred from the types of the arguments.
> And, it's clear that C++ could do a lot more type inferencing without
> giving up any of its relatively strong static typing. Now consider a
> Python compiler that behaves somewhat like a C++ as long as it can
> statically infer types and that generates warnings and less efficient
> code when it can't. A lanuage designed for static typing with dynamic
> fallback could perhaps be useful both as a scripting language and as a
> language for the development of multi-megaline software systems.


I see more promise in the kind of two level system that languages such
as Python already are: a very high, level dynamically typed language
built on top of a lower level statically typed language. What I
contend is that C++ would make a much better lower level than C.


Cheers,
Nicola Musatti


Post a followup to this message

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