bugFreePOOMA - Bugs: bug #10895, Having Array and Field causes code...


bug #10895: Having Array and Field causes code duplication

Submitter:  Richard Biener <richi>
Submitted:  Wed 03 Nov 2004 10:11:09 PM UTC
Category:  Enhancement request Severity:  2 - Minor
Status:  None Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Wed 03 Nov 2004 10:11:09 PM UTC, original submission:  

The way we have the Array and Field abstractions causes needless code duplication.  This is because:
 - Array<int, class, class> and Field<class, class, class>
   don't allow common specializations with template template
 - Expression engines (and others) deal with Array and
   Field, not the other way around.

Possible solutions:
 - template Array on Mesh, T, EngineTag, like Field, but in
   practice use not instantiated NoMesh<Dim>.  Allows to
   merge certain traits classes.
   This may allow use of real Mesh with Arrays in the
 - strip Array/Field information off the ExpressionEngine
   leafs and only combine Array/Field information for the
   Array/Field encapsulating the ExpressionEngine.
   Maybe hard to do, may clash with certain ways the
   FieldEngine works currently (which sucks bad way, too)

This is of course all r3 material.

Richard Biener <richi>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


CC list is empty


There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.


No changes have been made to this item

Back to the top

Powered by Savane 3.13-b921.
Corresponding source code