Bugzilla – Full Text Bug Listing
| Summary: | [inline] inlined volatile field needs special treatment | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Martin Aeschlimann <martinae> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
3.3 In the following example, public volatile ByteBuffer fMessage; public ByteBuffer getMessage() { return duplicate(fMessage); } private ByteBuffer duplicate(ByteBuffer message) { return (message != null) ? message.duplicate() : null; } Because fMessage is volatile, it shouldn't be used in the inlined code, but first assigned to a local variable. public ByteBuffer getMessage() { ByteBuffer message= fMessage; return (message != null) ? message.duplicate() : null; }