Bug 237676 - Question from translators
Summary: Question from translators
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-18 14:15 EDT by B. Chen CLA
Modified: 2008-06-24 05:47 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description B. Chen CLA 2008-06-18 14:15:28 EDT
Build ID: Build id: M20080221-1800

Steps To Reproduce:


More information:
Hi, we are translating JDT runtime, our translator has some questions, would appreciate if someone could help answer them -

1. please be so kind and explain what/who is super in the segment below:
HEAD\runtimes\plugins\nl\com.ibm.eclipse.jdt.core\org\eclipse\jdt\internal\compiler\problem\messages.properties (659)
The method {0} is overriding a method without making a super invocation

Please explain what is made with this 'super invocation'

2. please explain what is going in the sentence below:
HEAD\runtimes\plugins\nl\com.ibm.eclipse.jdt.debug\jdimodel_jar\org\eclipse\jdi\internal\JDIMessages.properties (190)
Improper instance counts between VM and client.

Is it about counting mechanism of improper instances?
Comment 1 B. Chen CLA 2008-06-18 14:23:14 EDT
Sorry, the plugin name should be org.eclipse.jdt.core and org.eclipse.jdt.debug
Comment 2 Darin Wright CLA 2008-06-18 15:03:24 EDT
> 2. please explain what is going in the sentence below:
> HEAD\runtimes\plugins\nl\com.ibm.eclipse.jdt.debug\jdimodel_jar\org\eclipse\jdi\internal\JDIMessages.properties
> (190)
> Improper instance counts between VM and client.
> Is it about counting mechanism of improper instances?

This is an unexpected internal error. The Java debugger has asked for the number of instances of a list of N specific class names, but the backend (VM) has returned a set X of instances, where X != N.

We should really update the message to something like "Requested {N} instance counts but received {X} instance counts."

Moving to JCORE for comment on first message.
Comment 3 B. Chen CLA 2008-06-18 22:24:37 EDT
Thank you for your quick response!
Comment 4 B. Chen CLA 2008-06-19 09:45:19 EDT
Another one for jdt.core

3. org.eclipse.jdt.core\org\eclipse\jdt\internal\compiler\problem\messages.properties (698)
please confirm that null comparison in the sentence below 

Null comparison always yields false: The variable {0} cannot be null at this location

is actually a compare procedure that check whether a value is null.
Comment 5 Philipe Mulet CLA 2008-06-19 10:02:07 EDT
>1. please be so kind and explain what/who is super in the segment below:
> HEAD\runtimes\plugins\nl\com.ibm.eclipse.jdt.core\org\eclipse\jdt\internal\compiler\problem\messages.properties
> (659)
> The method {0} is overriding a method without making a super invocation
> Please explain what is made with this 'super invocation'

In Java, super invocation refers to invoking a method from a superclass. You can redefine (override) a method in a subtype, and normally a good programming style for the overriding method would be to invoke the method from the super class somehow. 
 3.org.eclipse.jdt.core\org\eclipse\jdt\internal\compiler\problem\messages.properties
>(698)
> please confirm that null comparison in the sentence below 
> Null comparison always yields false: The variable {0} cannot be null at this
location
> is actually a compare procedure that check whether a value is null.

Yes this is correct.
Comment 6 B. Chen CLA 2008-06-19 22:48:27 EDT
Thank you!
Comment 7 B. Chen CLA 2008-06-19 22:49:01 EDT
Close the bug
Comment 8 Jerome Lanneluc CLA 2008-06-24 05:47:15 EDT
Resolving as INVALID because this is rather a question than a bug, and we try
not to use FIXED, WORKSFORME or WONTFIX in such cases - the question is legitimate and please see no offense in the INVALID keyword.