Bug 50433 - Rationalize signatures of AST.parse* methods
Summary: Rationalize signatures of AST.parse* methods
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.0 M8   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-22 16:59 EST by Jim des Rivieres CLA
Modified: 2004-03-25 10:18 EST (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 2004-01-22 16:59:48 EST 
To bring some consistency to the AST.parse* method signatures:

- all parse* methods that may consult the java model or resolve bindings 
should accept a progress monitor
- all parse* methods that take progress monitors should allow null to be 
passed as well
- all parse* methods that take working copy owners should allow null to be 
passed as well (this has well-defined semantics)
- all parse* methods that have been replaced by ones that take progress 
monitor should be deprecated
Comment 1 Jim des Rivieres CLA 2004-01-22 17:04:49 EST 
I've made the rest of the changes required to bring things in line.

A handful of the API methods were added in 3.0 are now marked @deprecated.
These should be deleted after M7 (marked with TODOs).

This PR should be resolved as FIXED once these extra methods have been deleted.
Comment 2 Jerome Lanneluc CLA 2004-01-29 14:02:24 EST 
Since deprecated methods will be deleted after M7, changing target milestone to 
M8.
Comment 3 Jerome Lanneluc CLA 2004-03-04 07:20:39 EST 
Deprecated methods have been removed.
Comment 4 Frederic Fusier CLA 2004-03-25 10:18:22 EST 
Verified for 3.0 using build I200403250010.