JADE Environment Development Ideas

Smart Compiler

When compiling a method we use F8 and if there are any compile errors they are identified. What would be beneficial (especially for anyone learning Jade) would be a "smarter" compile which would warn on potential problems in the code. Here are some ideas on what it could do: Warn of transients created but not deleted, unused local variables, variable names with same name as a class variable, method calls that have a return which are not assigned to anything

This was originally discussed in the Jade Forums https://forums.jadeworld.com/viewtopic.php?t=1746
  • Guest
  • May 1 2019
  • Future consideration (Long term)
HistoricalComments
Sam Stokell 26/09/2018 2:34:34 PM
Another one I just thought of, a spell check would be great for literals in code

Paul Daigneault 18/11/2017 4:23:51 AM
It would also be great to see features, like unused variables or inaccessible code being grayed out.

John Richards 7/11/2017 2:25:59 PM
This is being considered as part of a larger review of the language and compiler.

Sam Stokell 3/11/2017 10:07:49 AM
Could also include Casting that is not required for example "thisIsAString.String" "customer.Customer"

FileVision UK Ltd 26/09/2017 4:09:15 AM
I think I better name for this could be "compiler warnings"

John Beaufoy 21/09/2017 2:11:33 PM
Note in the more recent versions of Jade, static analysis is available:
https://www.jadeworld.com/docs/jade-71/content/resources/userguide/ch4methodfeaturedef/displunusedlocalvarsandparams.htm

That said, doing it real time has a greater potential to improve the quality of our code and speed up development.

Some options to consider alongside the basic idea:
- Preferences dictate whether it?s available or not, as this may not be for everyone. Some specific warnings might be ?noise? depending on what you?re trying to do.

- Fix/FixAll hotkey options alongside the warnings - oh the pleasure!

- User hooks are made available, so there would be opportunity for us to write our own warnings. These could then be shared amongst the community, or simply used inhouse to help with internal coding standards / best practice.
  • Attach files
  • Sam Stokell commented
    16 Aug, 2020 07:25am

    'Compiler warnings' would be useful to implement the change on JEDI 145 - That is to flag something as being deprecated 'Compiler warnings' can warn you on this rather than it be a compile error.

    https://jedi.ideas.jadeworld.com/ideas/JAD-I-145

    Would be nice if this gets implemented to be able to select what warnings you want be shown in preferences.

  • +12