Path: utzoo!utgpu!watmath!clyde!att!rutgers!gatech!gt-eedsp!baud
From: baud@gt-eedsp.UUCP (Kurt Baudendistel)
Newsgroups: comp.lang.c++
Subject: Re: Continuing efforts ...
Message-ID: <575@gt-eedsp.UUCP>
Date: 29 Nov 88 20:01:44 GMT
References: <2042@windy.dsir.govt.nz>
Reply-To: baud@gt-eedsp.UUCP (Kurt Baudendistel)
Organization: School of Electrical Engineering, Ga. Tech, Atlanta, GA  30332
Lines: 25

In article <2042@windy.dsir.govt.nz> srwmrbd@windy.dsir.govt.nz (ROBERT) writes:
>In my attempts to write an array package to solve this problem I have
>two classes of array, eg IA and tIA. The IA class has the usual constructors
>and destructors. However the tIA class has no destructor and the rule is
>that anything that uses a tIA object must destroy it or recycle its space.
>...

well, this is a passable method for implementation, but it gets out of hand
very quickly. try adding sub-array constructs to this method---to do it you
have to add yet another data type. then there are vectors. how many vector
types do you need? how about all of those conversions and dummy member
functions?!!!

after some experiment, i've decided that a run-time (rather than a compile-
time) method is easier to implement and much less costly in terms of
complexity of the class definition. hopefully, the gnu c++ library
will release a good array package to the masses early next year
(january?) so we can forget about these types of discussions.

kurt
-- 
Kurt Baudendistel --- GRA
Georgia Tech, School of Electrical Engineering, Atlanta, GA  30332
uucp:  ...!{allegra,hplabs,ulysses}!gatech!gt-eedsp!baud
internet: baud%gt-eedsp@gatech.edu