Bug 23492 - [DOM/AST] lazy init should not count as a modification
Summary: [DOM/AST] lazy init should not count as a modification
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 2.1 M1   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 22560
  Show dependency tree
 
Reported: 2002-09-12 12:00 EDT by Jim des Rivieres CLA
Modified: 2002-09-19 09:53 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jim des Rivieres CLA 2002-09-12 12:00:06 EDT 
There are various places in the DOM/AST implementation that
lazily create nodes for the default child values. This is done
when the child value is read. However, when it creates the
node and sets the field the modification count is increased.
This results, for example, in all bindings being thrown away!

Lazy creation of children is an internal implementation detail.
The client is really just reading the value of a property, not
modifying anything. Consequently, these node creations and
modifications should not count.
Comment 1 Olivier Thomann CLA 2002-09-12 12:59:24 EDT 
Fixed and released in 2.1 stream.
Comment 2 David Audel CLA 2002-09-19 09:53:19 EDT 
Verified.