#312 Can't assign IntersectionIterators from different entities
Metadata
| Property | Value |
|---|---|
| Reported by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Reported at | Aug 20, 2007 15:03 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Last edited at | Aug 9, 2010 09:36 |
| Closed by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Closed at | Aug 9, 2010 09:36 |
| Closed in version | Unknown |
| Resolution | Fixed |
| Comment |
Description
Consider the following pseudo-code fragment
IntersectionIterator it1 = entity1.ilevelbegin(); IntersectionIterator it2 = entity2.ilevelbegin();
it1 = it2;
If entity1 is not entity2 then some grids (e.g., SGrid and YaspGrid) abort at the assignment with a runtime error. Some may say that this is a feature rather than a bug, because the intersections of entity1 and entity2 are in different containers. However I find this behaviour rather annoying because it means I cannot hand an Int.Iterator by reference to a function which then overwrites it with a result value.