As a discussion starter, I'd like to throw out a few wish list items that would be helpful in our environment and, I assume, might be helpful to others:
1. Block comments
There are times when it would be very helpful to have the capability to use block comments. In BASIC programs, using a 'IFDEF()' sort of works but this capability should be available in all source code environments, e.g., BASIC programs, procs, paragraphs, etc. This would allow using markdown for documentation and would simplify program maintenance and management.
2. Default text file type
Files using Type 1 and Type 19 are intended for storing text data. Type 1 is a throwback (way back) to old Pick capabilities and, on current systems (Linux or other) is just another piece of tedium to deal with. I would like to suggest a configuration item that would indicate the type of file to use for standard text files. So, if a new account is created, those system files (like &SAVEDLISTS&) would be created as Type 19, rather than Type 1. It might also be handy to add the capability in the 'CREATE-FILE' verb to have the option of 'TEXT' for file type. That would retrieve the config parameter and would create a new file with either Type 1 or Type 19, based on the config option.
3. Add a keyword "INCLUDE" for line 1
When compiling a library, the files that contain equated variables or blocks of code that are not intended to be run on their own could include the word "INCLUDE" on line 1. We currently use "PROGRAM", "SUBROUTINE", "FUNCTION", "PA", "PROC". If the "INCLUDE" keyword was added, the compiler could know that item should not be compiled but contains components used by one or more programs, subroutines or functions.
Are there other good ideas out there? Are any of these helpful to other developers? I can't comment on the ease or difficulty of implementing any of these but we won't get them if they are not discussed...
Thanks!
------------------------------
Jeff Teter
Woodforest National Bank
The Woodlands, TX
------------------------------
