callable

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
callable [2019/01/25 16:01] – ↷ Links adapted because of a move operation oroehrigcallable [2019/02/05 12:16] – removed remark about release 2.1 oroehrig
Line 1: Line 1:
 ===== Callable Library ===== ===== Callable Library =====
  
-Starting with release 2.11, polymake offers an alternative interface for integration with other software, a C++ callable library.+polymake offers an alternative interface for integration with other software, a C++ callable library.
  
 This page describes only those parts of the interface which are specific to the callable library.  Software collaborating with polymake may (and in most cases even have to) use the Object and Function interfaces too; they are described on the [[user_guide:extend:clients|Client Development page]]. This page describes only those parts of the interface which are specific to the callable library.  Software collaborating with polymake may (and in most cases even have to) use the Object and Function interfaces too; they are described on the [[user_guide:extend:clients|Client Development page]].
Line 14: Line 14:
  
 ''polymake::Main'' has one constructor: ''polymake::Main'' has one constructor:
-  * ''%%Main(user-settings = "user")%%'' \\ where //user-settings// is a string encoding whether and where the user settings like custom variables or results of rule auto-configuration are retrieved from.  The default value is ''%%"user"%%'', which causes the standard settings for the interactive mode to come into effect (usually stored under ''~/.polymake'').  Other possible values are ''%%"none"%%'' for "no configuration at all" or a [[howto:configure|configuration path]] allowing to combine several configuration sources with user's individual settings.+  * ''%%Main(user-settings = "user")%%'' \\ where //user-settings// is a string encoding whether and where the user settings like custom variables or results of rule auto-configuration are retrieved from.  The default value is ''%%"user"%%'', which causes the standard settings for the interactive mode to come into effect (usually stored under ''~/.polymake'').  Other possible values are ''%%"none"%%'' for "no configuration at all" or a [[install:configure|configuration path]] allowing to combine several configuration sources with user's individual settings.
  
 Further methods: Further methods:
  • callable.txt
  • Last modified: 2021/01/12 15:38
  • by 127.0.0.1