[ggt-devel] [ ggt-Bugs-680245 ] op[] doesn't quite behave as expected

[SourceForge.net <no...@so...>]

Bugs item #680245, was opened at 2003-02-04 09:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=437247&aid=680245&group_id=43735

Category: GMTL
Group: HEAD
>Status: Closed
>Resolution: Fixed
Priority: 7
Submitted By: Allen Bierbaum (allenb)
Assigned to: Allen Bierbaum (allenb)
Summary: op[] doesn't quite behave as expected

Initial Comment:
There are some issues with operator[] not behaving as a
user would expect.

if a user has Matrix44f mat;

They may try to access it using multi-array notation like:

mat[3][0]

In the current version, this will not work as expected.
 It doesn't access it in colum or row major order.

The correct way to do this is

mat(3,0)

So I have two ideas to make this more fool proof.

1. Try to make op[] take two params

interesting idea, but not the "normal" notation.

2. Make operator[] return a temporary object that then
has an op[] that calls back into the matrix's op() with
the correct args

This can probably work fairly well and have very little
overhead (just a pointer and an int).

----------------------------------------------------------------------

>Comment By: Ben Scott (nonchocoboy)
Date: 2003-03-21 22:30

Message:
Logged In: YES 
user_id=173947

Allen took care of this for the 0.2.1 release.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=437247&aid=680245&group_id=43735