From: Dmitry A. Kazakov on
On Sun, 13 Jan 2008 16:54:16 +0000, S Perryman wrote:

> S Perryman wrote:
>
>> Ignoring syntax issues ... compare C to its peers (Ada, Modula 2 etc) .
>
> 5. Bounds enforcement for enumerated type operations (incrementation etc)
> 6. Bounds definition (non-zero lower/upper bounds etc) or enforcement for
> array types.

7. Complex types returned from functions (arrays for example)
8. Dynamically constrained object on the stack (local arrays for example)
9. Parameter modes (in, out, in out) instead of wild use of pointers
10. Nested subprograms and types

--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
From: S Perryman on
Dmitry A. Kazakov wrote:

> On Sun, 13 Jan 2008 16:54:16 +0000, S Perryman wrote:

>>5. Bounds enforcement for enumerated type operations (incrementation etc)
>>6. Bounds definition (non-zero lower/upper bounds etc) or enforcement for
>> array types.

> 7. Complex types returned from functions (arrays for example)
> 8. Dynamically constrained object on the stack (local arrays for example)
> 9. Parameter modes (in, out, in out) instead of wild use of pointers
> 10. Nested subprograms and types

Right. So, apart from 1-10 :

what have the (C) Romans done to us !!?? :-)



Regards,
Steven Perryman
From: Patrick May on
ram(a)zedat.fu-berlin.de (Stefan Ram) writes:
> Nick Keighley <nick_keighley_nospam(a)hotmail.com> writes:
>>What is a good procedural language?
[ . . . ]
> To know what a good procedural language is, one would
> need to know what a good language is. There does not
> seem to be agreement about this.
>
> A good procedural language should support or enforce
>
> * structured programming
>
> * a powerful static type system, yet one that helps
> to detect many possible errors

So only statically typed languages are good?

Regards,

Patrick

------------------------------------------------------------------------
S P Engineering, Inc. | Large scale, mission-critical, distributed OO
| systems design and implementation.
pjm(a)spe.com | (C++, Java, Common Lisp, Jini, middleware, SOA)
From: Phlip on
Patrick May wrote:

>> * a powerful static type system, yet one that helps
>> to detect many possible errors
>
> So only statically typed languages are good?

Is that why so many statically typed languages then bend over backwards to
also provide some kind of "Duck Typing"?

--
Phlip
From: Daniel T. on
Patrick May <pjm(a)spe.com> wrote:
> ram(a)zedat.fu-berlin.de (Stefan Ram) writes:

> > A good procedural language should support or enforce
> >
> > * a powerful static type system, yet one that helps
> > to detect many possible errors
>
> So only statically typed languages are good?

And down the road we once again go. :-)