- Ability to set fuses via compiler directives rather than Edit Project
- Support for inline functions.
- Improved/corrected documentation
And one not on the list -- one that is a bane for me every time I "create a new Project version":
When a Project is "Save As"ed to a new name [such as to create a new version of the Project], the Search Path(s) are not preserved! So, I have to go in and reconnect these path(s), which is a pain! This, and the fact that one CAN'T set fuse directives, in the code, are the two biggest problems I have with your product. It makes it difficult to preserve the integrity of a project that might need to be moved/copied to a different station [e.g. collaboration], or even, ported to a different platform! The fact that the fuse directives are missing from the code, means the code integrity is vulnerable. One means for improving said integrity, might be including the intended fuse settings in a comment, but what a royal pain that is!
The lack of the ability to inline functions is a close second. The way I work around that, currently, is to define a macro version [below the function definition] of a function that needs to be inlined. Another total pain!!
The function definition form, preserves the full intent of the function's structure, which can be made arcane by a conversion to MACRO form -- plus, I think better in the function definition format, and find a function easier to debug, and edit, than is a MACRO. Thus the reason for having, and preserving, a function definition form [that is echoed by the MACRO form]. Also, a MACRO lacks features of the function, like type checking.