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


bug #10895: Having Array and Field causes code duplication

Submitted by:  Richard Biener <richi>
Submitted on:  Wed 03 Nov 2004 10:11:09 PM UTC  
Category: Enhancement requestSeverity: 2 - Minor
Status: NoneAssigned to: None
Open/Closed: Open

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


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>
Project Administrator


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

Attach File(s):

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


CC list is empty


Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.


Please enter the title of George Orwell's famous dystopian book (it's a date):



No Changes Have Been Made to This Item

Back to the top

Powered by Savane 3.1-cleanup1