[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>

13 messages 2000/10/02

[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>

OK, here is what I think I know.

14 messages 2000/10/11

[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>

18 messages 2000/10/11
[#5427] RE: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — OZAWA -Crouton- Sakuro <crouton@...> 2000/10/11

At Thu, 12 Oct 2000 03:49:46 +0900,

[#5429] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...> 2000/10/11

Thanks for the input.

[#5432] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Yasushi Shoji <yashi@...> 2000/10/11

At Thu, 12 Oct 2000 04:53:41 +0900,

[#5516] Re: Some newbye question — ts <decoux@...>

>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:

80 messages 2000/10/13
[#5531] Re: Some newbye question — matz@... (Yukihiro Matsumoto) 2000/10/14

Hi,

[#5544] Re: Some newbye question — Davide Marchignoli <marchign@...> 2000/10/15

On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:

[#5576] Re: local variables (nested, in-block, parameters, etc.) — Dave Thomas <Dave@...> 2000/10/16

matz@zetabits.com (Yukihiro Matsumoto) writes:

[#5617] Re: local variables (nested, in-block, parameters, etc.) — "Brian F. Feldman" <green@...> 2000/10/16

Dave Thomas <Dave@thomases.com> wrote:

[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>

There has been discussion on this list/group from time to time about

16 messages 2000/10/20
[#5712] Re: Dynamic languages, SWOT ? — Charles Hixson <charleshixsn@...> 2000/10/20

Hugh Sasse Staff Elec Eng wrote:

[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>

Hello fellow rubyists,

21 messages 2000/10/26

[ruby-talk:5714] Re: Dynamic languages, SWOT ?

From: Hugh Sasse Staff Elec Eng <hgs@...>
Date: 2000-10-20 16:30:38 UTC
List: ruby-talk #5714
On Sat, 21 Oct 2000, Charles Hixson wrote:

> Sorry, I feel the need for clarification here.  Ruby is strongly typed
> AND dynamic.

I think from what you say below, I may be using the terms imprecisely.

> Weakly typed, statically bound languages are things like
> Fortran60.  There the language couldn't tell the type of the item upon
> which you were operating, so it made assumptions based on the name.

OK, I through K [?] as INTEGER, all others FLOAT.

> Strongly typed, statically bound languages are like Eiffel and Ada.  
> The language knows what the type MUST be at compile time (except when

All functions, parameters, and variables have types defined at compile
time.  Yes, I can see that is static.

> unusual procedures are invoked). Weakly typed, dynamically bound
> languages are ... well, there's assembler. Can't think of anything

Perl4?  I'm not sure.

> else off the top of my head. Strongly typed, dynamically bound
> languages are, among others, Ruby, Python, Common Lisp, Smalltalk, ...

This is the area I'm thinking about where the typing is not so strong 
as would ease error detection.  OK, types can be dynamic, but for
parameters it only make sense for them to be in a subset of the 
class heirarchy.   There is no way to express this constraint in Ruby
or Python.  I have not really used Lisp or Smalltalk.  What I mean is
that it is a weakness [in typing?] to allow a parameter to be of *any*
class, for example when you know it must be a Numeric 
or descendent of Numeric.  So does this weakness create a different
strength which outweighs the inability to type-check at compilation time?
I can see that supporting polymorphism is a strength, so that subclasses
can be handled, but at the moment there is nothing wrong with passing in
superclasses of the originally intended type.

> Java seems to sit (un?)comfortably in the center, leaning towards sort
> of strongly typed, and sort of dynamically bound.
> 
> -- (c) Charles Hixson
> --  Addition of advertisements or hyperlinks to products specifically
> prohibited
> 
	Hugh
	hgs@dmu.ac.uk


In This Thread