|
|
Blitz Support : |
From: Frank Schimmel (frs_at_[hidden])
Date: 2003-10-13 03:30:41
>> Fernando Perez writes:
[...]
> I'm glad to hear about your integration of tvmet's capabilities into
> blitz. As this is done, any chance of the new TinyVectors supporting
> Range() indexing? As I mentioned in a previous message, this appears
> not to be possible with the current code, yet would make certain shape
> calculations much simpler to write. Anyway, it's a minor point for your
> todo :)
Somebody correct me if I'm wrong...
Shouldn't indexing a TinyVector (i.e. extracting a sub-vector from it)
with a Range object should always be impossible? The length of a
TinyVector is a compile-time constant. But you can construct a Range
object of any, well, range at run time. So you can't have a constructor
TinyVector(const TinyVector&, const Range&): the length of the result
would *not* be determinable at compile time. If you want that, you'll
have to use a blitz::Vector (no `Tiny').
-Frank
PS: To whom it may concern: note the new email address.