Sometimes I get aware of some kinks in PB which irritate me when I loose overview or when I have to add some code to a program I have not edited for a long time.
The purpose of function declarations is also to give the programmer an overview about what functions are defined in a project.
When many functions are defined the length of code exceeds 2000 lines or so, then I declared for instance standard functions and exported ones.
I'd be interested in having a look at the declarations and see which functions are exported. Shure, this can be done with a comment; but as You know, comments are sometimes not changed as they should be when an exported status was changed to standard or vice versa.
But if You could see from the declaration which function is exported this would really make sense.
Currently, it is only possible to have a look at a function declaration and then search in the code for the function to become informed if it is exported or not. The alias in the declaration does not help much as soon as the "export" statement is not attached to the function itself.
So, why can't we add the "exported" statement directly to the function declarations?
The purpose of function declarations is also to give the programmer an overview about what functions are defined in a project.
When many functions are defined the length of code exceeds 2000 lines or so, then I declared for instance standard functions and exported ones.
I'd be interested in having a look at the declarations and see which functions are exported. Shure, this can be done with a comment; but as You know, comments are sometimes not changed as they should be when an exported status was changed to standard or vice versa.
But if You could see from the declaration which function is exported this would really make sense.
Currently, it is only possible to have a look at a function declaration and then search in the code for the function to become informed if it is exported or not. The alias in the declaration does not help much as soon as the "export" statement is not attached to the function itself.
So, why can't we add the "exported" statement directly to the function declarations?
Comment