TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"W. Wesley Groleau x4923" <[log in to unmask]>
Reply To:
W. Wesley Groleau x4923
Date:
Thu, 1 Oct 1998 12:44:21 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
>   Perhaps this is why people say that "Ada is hard to learn"...
>
>   Aliasing (on the surface) seems like a pretty
>   straight forward concept.

Yes, "on the surface" it is pretty simple.  But "under the hood" it makes
it pretty easy to screw things up.

Ada only allows this kind of aliasing* when the _programmer_ decides the
benefits of pointers outweigh the risks for a particular data structure.

Java's designers apparently decided for us that the benefits of pointers
outweigh the risks for almost all data structures.

Decide for yourselves which approach is better.

*There is another kind that is in most languages--aliasing within a
routine when the caller uses the same entity for two parameters.

ATOM RSS1 RSS2