This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
general [2014/11/05 11:03] – [General Introduction] gawrilow | general [2014/11/05 11:15] – [Custom variables] gawrilow |
---|
===== Most Important Commands ===== | ===== Most Important Commands ===== |
| |
Precisely speaking, polymake commands are quite normal perl functions, either built-in like ''print'' or ''exit'', or specially written for polymake. As long as you are not concerned about implementation details, you won't feel any difference. All commands taking arguments may be written in two fashions: with argument list enclosed in parentheses or separated by a blank from the command keyword. For example: | Precisely speaking, polymake commands are quite normal perl functions, either built-in ones like ''print'' or ''exit'', or specially written for polymake. As long as you are not concerned about implementation details, you won't feel any difference. All commands taking arguments may be written in two fashions: with argument list enclosed in parentheses or separated by a blank from the command keyword. For example: |
| |
<code> | <code> |
? ''%%reset_custom $name{key};%%'' | ? ''%%reset_custom $name{key};%%'' |
:: restore the default value | :: restore the default value |
.. Both commands come into effect immediately, but also mark the variable as changed, so that the new value will also appear in your personal customization file after the session end. You can also change the custom variables for the rest of current session only, without updating the file -- by a plain assignment. If you want to change some value temporarily, just to influence the evaluation of the next expression, write a ''local'' keyword in front of the assignment. (It's not polymake's black magic, just normal perl operator.) | .. Both commands come into effect immediately, but also mark the variable as changed, so that the new value will also appear in your personal customization file after the session end. You can also change the custom variables for the rest of current session only, without updating the file -- by a plain assignment. If you want to change some value temporarily, just to influence the evaluation of the next expression, write the ''local'' keyword instead of ''set_custom''. (It's not polymake's black magic, just normal perl operator.) |
| |
==== Preferences ==== | ==== Preferences ==== |