Bugzilla – Full Text Bug Listing
| Summary: | Passing null as first vararg makes parameter null (3.1M4) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Joe Thurbon <joe_thurbon> | ||||
| Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eric | ||||
| Version: | 3.1 | ||||||
| Target Milestone: | 3.1 M6 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 18440 [details]
Pass null when its the only argument
This checks the number of arguments passed to the vararg portion of the call to
determine if it should be null or an array of elements which contain null.
Fixed and released in HEAD. Thanks for the patch. I prefer to rewrite a big the arguments generation. To make it easier to read. *** Bug 88581 has been marked as a duplicate of this bug. *** Verified in 20050330-0500 |
The following method boolean f(Object ... args) { return args == null; } should return false for a call f(null, null) but it does not. In general, passing null as the first vararg makes the argument array within a vararg method null, rather than an array whose first element is null.