Bug 51990 - 'parameter' vs 'argument' in compiler errors/settings
Summary: 'parameter' vs 'argument' in compiler errors/settings
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.0 M8   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-13 14:50 EST by Luc Bourlier CLA
Modified: 2004-03-24 09:32 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 Luc Bourlier CLA 2004-02-13 14:50:12 EST 
The compiler option about never-read parameters is called 'parameter is never
read' in the preference page (java/compiler/unused code). But when such an error
is reported in the problems view, it appears as 'The argument XXX is never read'.
It would be better to use the same term.
Comment 1 Martin Aeschlimann CLA 2004-02-16 05:40:06 EST 
I think 'parameter' is the correct term here; the error message should be fixed.
Comment 2 Philipe Mulet CLA 2004-02-16 05:51:50 EST 
Good point. We actually had a few occurrences of messages using 'argument' in 
place of 'parameter'.

Fixed
Comment 3 Philipe Mulet CLA 2004-02-16 08:02:35 EST 
forgot to assign
Comment 4 Philipe Mulet CLA 2004-02-16 08:03:02 EST 
Fixed
Comment 5 Jerome Lanneluc CLA 2004-03-24 09:32:43 EST 
Verified in build I200403240010.