bugFreePOOMA - Bugs: bug #10897, Don't handle up-to-date-ness of...

 
 

bug #10897: Don't handle up-to-date-ness of internal/external guards differently

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

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

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

 

Wed 03 Nov 2004 10:15:43 PM UTC, original submission:

The way external guards are updated (for Fields only!) sucks. Using relations for this is the wrong way. It does not permit optimizing the updates as we can with the internal guards.

Solution:
- Unify dirty handling of internal/external guards. For this
to work we need to move guard dirty handling from the
MultiPatch engine down to the Brick (and similar) engine.
We get handling of external guards for free, then.
- We can still use the relation infrastructure to implement
BCs - just the trigger needs to be elsewhere. We can
use a different mechanism to allow BCs for Array, too.

Richard Guenther <richi>
Project Administrator

 

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

Attach File(s):
   
   
Comment:
   

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-cleanup