Summary: | Two Translation Clarification Questions | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | John Ryding <trippinbilly25> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | VERIFIED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | camle, kitlo, Olivier_Thomann |
Version: | 3.4 | ||
Target Milestone: | 3.4 M6 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
John Ryding
2008-03-12 16:57:03 EDT
(In reply to comment #0) > SANITY CHECK: Invalid opcode {0} at pc {1} for stackmap table attribute for > method {2} Instead of "pc" we could have use "position". "opcode" this is like a bytecode instruction. > {1} files to index ({0}) > > For example, does it mean "there are {1} files to index? Yes. This is the meaning. > Also, what does {0} stand for? {0} this is the job family. For indexing jobs, this returns where the files to index are coming from. If these answers are enough, I would close as FIXED. Closing as INVALID as no change in the JDT/Core is required. Verified for 3.4M6 |