EXPORT command inconsistancies?
|
03-28-2017, 05:52 AM
Post: #6
|
|||
|
|||
RE: EXPORT command inconsistancies?
Hello,
EXPORT is a keyword that let the system know that a given symbol in a program (function or global variable) need to be directly accessible by the user. An app that has a program which global do not need to be accessible by the user does not need to use EXPORT. Since function designed to respond to app key events (symb, plot...) are not accessed directly by the user, but by the system, they do not need to be exported. in a non-app program, you need to have at least one exported function that the user can call/run... Note that as soon as the user fully qualifies a symbol, then there is no access restriction anymore and he can use anything, even not exported (from memory). cyrille Although I work for the HP calculator group, the views and opinions I post here are my own. I do not speak for HP. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
EXPORT command inconsistancies? - Bob Frazee - 03-26-2017, 10:13 PM
RE: EXPORT command inconsistancies? - Han - 03-27-2017, 06:56 AM
RE: EXPORT command inconsistancies? - retoa - 03-27-2017, 06:56 AM
RE: EXPORT command inconsistancies? - Han - 03-27-2017, 07:03 AM
RE: EXPORT command inconsistancies? - Bob Frazee - 03-28-2017, 12:49 AM
RE: EXPORT command inconsistancies? - cyrille de brébisson - 03-28-2017 05:52 AM
|
User(s) browsing this thread: 1 Guest(s)