Re: Interesting effects in array renaming

[Georg Bauhaus <sb463ba@d2-hrz.uni-duisburg.de>]

Dmitry A. Kazakov <mailbox@dmitry-kazakov.de> wrote:
: It is same in both GNAT and ObjectAda, but it is absolutely legal according 
: to ARM. The problem is ARM itself. Which opens such a hole. What sense have 
: our complains about buffer overruns in C/C++, in presense of this? It is 
: also a range check optimization problem, because the compiler cannot rely 
: on subtype information. Very bad.

I don't think it is so bad, it is much more an issue of what
renaming means, maybe? Most prominently, you give another name
to an entity, you don't make a new entity. Why should the new
name denote an entity wich has its bounds changed, despite
being "just another name"?

-- georg