Home > Articles > Programming > Java

📄 Contents

  1. FAQ 319: What is eScript?
  2. FAQ 320: Language integration phase 1: How do I compile and build programs?
  3. FAQ 321: How do I load source files edited outside Eclipse?
  4. FAQ 322: How do I run an external builder on my source files?
  5. FAQ 323: How do I implement a compiler that runs inside Eclipse?
  6. FAQ 324: How do I react to changes in source files?
  7. FAQ 325: How do I implement an Eclipse builder?
  8. FAQ 326: Where are project build specifications stored?
  9. FAQ 327: How do I add a builder to a given project?
  10. FAQ 328: How do I implement an incremental project builder?
  11. FAQ 329: How do I handle setup problems for a given builder?
  12. FAQ 330: How do I make my compiler incremental?
  13. FAQ 331: Language integration phase 2: How do I implement a DOM?
  14. FAQ 332: How do I implement a DOM for my language?
  15. FAQ 333: How can I ensure that my model is scalable?
  16. FAQ 334: Language integration phase 3: How do I edit programs?
  17. FAQ 335: How do I write an editor for my own language?
  18. FAQ 336: How do I add Content Assist to my language editor?
  19. FAQ 337: How do I add hover support to my text editor?
  20. FAQ 338: How do I create problem markers for my compiler?
  21. FAQ 339: How do I implement Quick Fixes for my own language?
  22. FAQ 340: How do I support refactoring for my own language?
  23. FAQ 341: How do I create an Outline view for my own language editor?
  24. FAQ 342: Language integration phase 4: What are the finishing touches?
  25. FAQ 343: What wizards do I define for my own language?
  26. FAQ 344: When does my language need its own nature?
  27. FAQ 345: When does my language need its own perspective?
  28. FAQ 346: How do I add documentation and help for my own language?
  29. FAQ 347: How do I support source-level debugging for my own language?
  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

FAQ 338: How do I create problem markers for my compiler?

Adding problem markers for eScript compilation happens in two simple steps.

  1. Right before we compile the resource, we remove all problem markers from the resource:

    void compileResource(IResource resource) {
       resource.deleteMarkers(IMarker.PROBLEM,
          true, IResource.DEPTH_INFINITE);
       doCompileResource(resource);
    }
    
  2. During compilation, errors are attached to the resource as follows:

    void reportError(IResource res, int line, String msg) {
       IMarker m = res.createMarker(IMarker.PROBLEM);
       m.setAttribute(IMarker.LINE_NUMBER, line);
       m.setAttribute(IMarker.MESSAGE, msg);
       m.setAttribute(IMarker.PRIORITY,IMarker.PRIORITY_HIGH);
       m.setAttribute(IMarker.SEVERITY,IMarker.SEVERITY_ERROR);
    }
    

To simplify matters, we use the existing problem-marker type. See the online Eclipse article “Mark My Words” for an explanation on how to declare your own marker types.

Simply by attaching a marker to a resource, the IDE will take care of placing visual indicators at the two indicator bars in the editor. The IDE will also add entries to the Problems view. If we indicated additional information in the marker for IMarker.CHAR_START and IMarker.CHAR_END, the editor will also draw a red squiggly line under the offending problem. Figure 19.4 shows the result of a compilation of a problematic eScript file.

19fig04.jpgFigure 19.4 A problematic eScript file

Note

FAQ 339 How do I implement Quick Fixes for my own language?

  • + Share This
  • 🔖 Save To Your Account