| Newsgroups |
gmane.comp.lang.e.general |
| Message-ID |
<[email protected]> |
Hi David & all,
On Dec 20, 2007 11:10 PM, David Wagner <[email protected]> wrote:
> We don't try to enforce "good programming practices" in the Joe-E
> verifier.
>
Ok, makes sense. It's all too easy to hoark this one up inadvertently,
though, but you do address this here --
Instead, I've had in my mind that the right way to do this is to build a
> separate "capability lint" tool. The caplint tool would scan your code
> for dangerous programming practices and coding patterns that tend to
> violate "the capability way", and warn you about everything it finds in
> your code.
Right, that sounds just great! The wildcard import thingey is subconscious
when the IDE does it: I hardly ever look at my imports any more; I just hit
Control-Whatever and let the tool take care of it. There is a setting to
control wildcard generation, but I often forget to mess with it. Presumably,
the IDE plugin should include the lint tool, so this would not be an issue.
Thank you and regards,
Ihab
--
Ihab A.B. Awad, Palo Alto, CA
_______________________________________________
e-lang mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/e-lang