Bug 335898 - Method signature on autocomplete in subclass do not match that of superclass.
Summary: Method signature on autocomplete in subclass do not match that of superclass.
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: PDT (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PHP Core CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-31 15:33 EST by Toni Uebernickel CLA
Modified: 2020-05-14 10:17 EDT (History)
1 user (show)

See Also:


Attachments
A sample PHP Script, which triggers a fatal error. (188 bytes, text/php)
2011-01-31 15:37 EST, Toni Uebernickel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Toni Uebernickel CLA 2011-01-31 15:33:09 EST
Build Identifier: Build id: 20100917-0705

The method signature which code assist is writing to the editor does not match the actual signature of the superclass.

The default values are not generated.

Reproducible: Always

Steps to Reproduce:
1. Create a class with a method that has a parameter which has a default value.
2. Create a subclass of this class.
3. Start the signature of a method like "protected function exe" for a method "execute" in the subclass.
4. Catch Code Assist (wait or hit shortcut, doesn't matter)
5. The generated code does not contain the default value of the signature of the superclass.
Comment 1 Toni Uebernickel CLA 2011-01-31 15:37:56 EST
Created attachment 188003 [details]
A sample PHP Script, which triggers a fatal error.

PHP Fatal error:  Declaration of bar::execute() must be compatible with that of foo::execute() in different_signatures.php on line 14

Fatal error: Declaration of bar::execute() must be compatible with that of foo::execute() in different_signatures.php on line 14

Errors parsing different_signatures.php