Wednesday, March 08, 2006
EclipseZone - Clean Up Warnings with the 'restriction' Suppression Flag
Eclipse 3.2 M5 brings the addition of a new supported SuppressWarnings annotation parameter: 'restriction'. This new annotation allows you to tell the Eclipse JDT compiler to stop nagging you about something naughty you are doing in your code, such as referencing an 'internal' package in your Eclipse plug-in, or perhaps your project has access rules defined, as I described previously here . These access rules and definitions exist for a reason; to warn you if you are breaking rules. That being said, sometimes breaking rules is neccessary; and in those cases it's nice to be able to tell Eclipse to keep it's mouth shut
Subscribe to:
Post Comments (Atom)
Popular Posts
- Using QCLRDTAQ to clear data queues in CL and RPG
- 80 Column Punched Cards and the History of RPG on the AS400
- List Job (QUSLJOB) API
- What is QZHQSSRV job?
- Make a Home made, open source mp3 Player
- AS400 APIs
- Encrypt Data on as400 (QC3ENCDT, Qc3EncryptData)
- AS400 Job Scheduler
- API Example - Deleting Old Spooled Files
- UDATE and *DATE in AS400 RPG
No comments:
Post a Comment