Bugzilla – Full Text Bug Listing
| Summary: | Proposal for boolean | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Leopold Welsch <leo_welsch> |
| Component: | Core | Assignee: | David Audel <david_audel> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | 3.1 M7 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
What exactly are you asking for ? what is unclear from the first two lines of the code? What about any other boolean expressions ? That's an idea, but somehow you have to set the boolean to true or false. And I would say it's #1 task you'll do in a code. I know, there are other possibilities of setting it, but focusing on the most use-cases I would say true/false. It's still a proposal, nothing more. BTW: Since I've developed VB as well, that VB6-IDE has this proposal as default and I found it most useful! Simple, easy, effective. Ok, so your original request was actually: true/false should be included on boolean completions (and I agree with best relevance). I was talking about: boolean test = somePredicate(); I wonder how we missed the obvious true/false case To say it that way: #1 priority is this true/false. I wonder as well why this obvious issue nobody thought about ;) the other assignments is an idea, but I guess too much about it. cause you could easily extend it to non-boolean like integer and then it get's complicated. Except somebody has an clear idea about what could be. Fixed and test added CompletionTests#testCompletionKeywordTrue5() CompletionTests#testCompletionKeywordTrue6() true or false were already proposed but relevance computation was not complete. They are not only keywords, they are also boolean expressions. Verified in I20050510-0010 + JDT/Core v_556 |
boolean test; test= (the proposal should be true/false) I don't think the request of the status 'test' makes much sense, i.e. if (test == true) { .... => the first part would be very nice to have it.