On 10/25/12 2:21 PM, Roy Stogner wrote: > > On Thu, 25 Oct 2012, Boyce Griffith wrote: > >> Libraries like Eigen and Blitz++ use operator() for accessors rather >> than operator[]. How horrible would it be to go ahead and change to >> operator() when making this change to LibMeshNArray? > > Hmmm... it would mean that we couldn't get away with starting with > just a typedef, we'd actually have to build a basic shim class right > from the start, and it would be much more of a pain in the neck for > user codes to upgrade. > > On the other hand, if we did want to keep operator[] support around > indefinitely and we end up with a target class that doesn't support > it, that would mean we'd have to keep a shim class around > indefinitely... *and* we'd make it much less convenient to use a > different-semantic operator[] from the target class, e.g. the Blitz++ > component accessor. > > More opinions would be welcome; I'm not even sure what I'd prefer yet.
Is it even possible to have the shim class use operator[] for multidimensional indexing ([i][j])? I don't know how you setup an equivalent to "operator[][]". (Such a thing doesn't exist in C++, does it?) -- Boyce ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
