Arch Robison wrote:
>
> Certainly, removing aliasing from a language that supports abstract data types
> is impossible, because by definition an abstract data type is a black box inside.
> Knowing whether two black box's internal guts cause aliasing requires knowing
> their guts.
Yes, and this is a critical issue if we want to take advantage of something like
the "restrict" keyword in the context of expression templates. I believe it can
be done as long as
a) The user is willing to put up with "special" types that imply that the data
that they control is not aliased.
b) These special types allow their guts to be sufficiently exposed (e.g., loops
can be written on the contained data using raw data pointers, which can then
be labeled as restricted).
Regards, Julian C.
-- Julian C. Cummings Advanced Computing Laboratory Los Alamos National Laboratory (505) 667-6064 julianc@acl.lanl.gov--------------------- Object Oriented Numerics List -------------------------- * To subscribe/unsubscribe: use the handy web form at http://oonumerics.org/oon/ * If this doesn't work, please send a note to owner-oon-list@oonumerics.org
This archive was generated by hypermail 2b29 : Wed Feb 20 2002 - 03:20:11 EST