IdeaJam(tm) : List warnings when compiling LotusScript code

Domino Designer / : List warnings when compiling LotusScript code

Thu, 07 Feb 2008 00:40:49 +0000

Author: Scott Leis
Tags: LotusScript
Idea: This is an extension/generalisation of the linked idea.

When compiling LotusScript code, Designer should present a list of warnings - things that compile OK and don't prevent code execution, but look dubious. Some examples (adapted from things I've seen in the Delphi IDE):
- Variable declared but never used.
- Sub/Function never called.
- Possible loss of information on type conversion (e.g. if a Long is converted to an Integer).

re: List warnings when compiling LotusScript code

Thu, 07 Feb 2008 05:23:05 +0000

Author: Rob Goudvis
Comment: You can add to the wishlist:

- variables used but not assinged any value

re: List warnings when compiling LotusScript code

Thu, 07 Feb 2008 15:51:34 +0000

Author: Jan Schulz
Comment: <dream>And then I want quickFix like in eclipse java editor... </>

re: List warnings when compiling LotusScript code

Wed, 13 Feb 2008 23:03:58 +0000

Author: Nick Radov
Comment: Essentially what you're asking for is a static analysis tool. In Domino Designer 8.5 you should be able to write this yourself as an Eclipse plug-in. There are lots of existing similar plug-ins for Java analysis such as PMD and FindBugs. So I think this is an area better left to third parties; it doesn't need to be provided by IBM.

re: List warnings when compiling LotusScript code

Fri, 15 Feb 2008 06:08:22 +0000

Author: Scott Leis
Comment: No, it's not a static analysis tool I'm seeking. I'm after a list of warnings presented in the same way, and at the same time, as Designer currently displays errors. The important difference is that errors prevent code compilation, while warnings should be just suggestions which do *not* prevent compilation.
Delphi has this built into the core compiler/IDE (and has for several years). I expect MS Visual C++ would have something like it too, but I've never used that product.

To me, it seems like Designer falls short of being a solid professional IDE by omitting such a feature. Here's hoping that the Eclipse code editors in Designer 8.5 provide this feature by default, or at least make it much easier to implement.