API reference - Class MacroInterpreterNotation used in Ruby API documentation Description: A custom interpreter for a DSL (domain specific language)
DSL interpreters are a way to provide macros written in a language specific for the application. One example are DRC scripts which are written in some special language optimized for DRC ruledecks. Interpreters for such languages can be built using scripts itself by providing the interpreter implementation through this object. An interpreter implementation involves at least these steps:
Template macros provide a way for the macro editor to present macros for the new interpreter in the list of templates. Template macros can provide menu bindings, shortcuts and some initial text for example The simple implementation can be enhanced by providing more information, i.e. syntax highlighter information, the debugger to use etc. This involves reimplementing further methods, i.e. "syntax_scheme". This is a simple example for an interpreter in Ruby. Is is registered under the name 'simple-dsl' and just evaluates the script text:
class SimpleInterpreter < RBA::MacroInterpreter
# Constructor
def initialize
# Registers the new interpreter
register("simple-dsl")
# create a template for the macro editor:
# Name is "new_simple", the description will be "Simple interpreter macro"
# in the "Special" group.
mt = create_template("new_simple")
mt.description = "Special;;Simple interpreter macro"
end
# Implements the execute method
def execute(macro)
eval(macro.text, nil, macro.path)
end
end
# Register the new interpreter
SimpleInterpreter::new
Please note that such an implementation is dangerous because the evaluation of the script happens in the context of the interpreter object. In this implementation the script could redefine the execute method for example. This implementation is provided as an example only. A real implementation should add execution of prolog and epilog code inside the execute method and proper error handling. In order to make the above code effective, store the code in an macro, set "early auto-run" and restart KLayout. This class has been introduced in version 0.23. Public constructors
Public methods
Public static methods and constants
Deprecated methods (protected, public, static, non-static and constructors)
Detailed description[static] int MacroFormatDescription: Indicates macro (XML) format for storage_scheme [static] int NoDebuggerDescription: Indicates no debugging for debugger_scheme [static] int PlainTextFormatDescription: Indicates plain text format for storage_scheme [static] int PlainTextWithHashAnnotationsFormatDescription: Indicates plain text format for storage_scheme This format is identical to PlainTextFormat but indicates that it is possible to insert annotations (properties) into the text in a hash-commented header. [static] int RubyDebuggerDescription: Indicates Ruby debugger for debugger_scheme void _createDescription: Ensures the C++ object is created Use this method to ensure the C++ object is created, for example to ensure that resources are allocated. Usually C++ objects are created on demand and not necessarily when the script object is created. void _destroyDescription: Explicitly destroys the object Explicitly destroys the object on C++ side if it was owned by the script interpreter. Subsequent access to this object will throw an exception. If the object is not owned by the script, this method will do nothing. [const] bool _destroyed?Description: Returns a value indicating whether the object was already destroyed This method returns true, if the object was destroyed, either explicitly or by the C++ side. The latter may happen, if the object is owned by a C++ object which got destroyed itself. [const] bool _is_const_object?Description: Returns a value indicating whether the reference is a const reference This method returns true, if self is a const reference. In that case, only const methods may be called on self. void _manageDescription: Marks the object as managed by the script side. After calling this method on an object, the script side will be responsible for the management of the object. This method may be called if an object is returned from a C++ function and the object is known not to be owned by any C++ instance. If necessary, the script side may delete the object if the script's reference is no longer required. Usually it's not required to call this method. It has been introduced in version 0.24. void _unmanageDescription: Marks the object as no longer owned by the script side. Calling this method will make this object no longer owned by the script's memory management. Instead, the object must be managed in some other way. Usually this method may be called if it is known that some C++ object holds and manages this object. Technically speaking, this method will turn the script's reference into a weak reference. After the script engine decides to delete the reference, the object itself will still exist. If the object is not managed otherwise, memory leaks will occur. Usually it's not required to call this method. It has been introduced in version 0.24. void assign(const MacroInterpreter other)Description: Assigns another object to self void createDescription: Ensures the C++ object is created Use of this method is deprecated. Use _create instead Macro ptr create_template(string name)Description: Creates a new macro template
This method will create a register a new macro template. It returns a Macro object which can be modified in order to adjust the template (for example to set description, add a content, menu binding, autorun flags etc.) This method must be called after register has called. [virtual,const] int debugger_schemeDescription: Returns the debugger scheme (which debugger to use for the DSL macro) The returned value can be one of the constants RubyDebugger or NoDebugger. [virtual,const] string descriptionDescription: Returns a description string This string is used for showing the type of DSL macro in the file selection box together with the suffix for example. The default implementation returns an empty string. void destroyDescription: Explicitly destroys the object Use of this method is deprecated. Use _destroy instead [const] bool destroyed?Description: Returns a value indicating whether the object was already destroyed Use of this method is deprecated. Use _destroyed? instead [const] new MacroInterpreter ptr dupDescription: Creates a copy of self [virtual,const] void execute(const Macro ptr macro)Description: Gets called to execute a macro
This method must be reimplemented to execute the macro. The system will call this script when a macro with interpreter type 'dsl' and the name of this interpreter is run. [const] bool is_const_object?Description: Returns a value indicating whether the reference is a const reference Use of this method is deprecated. Use _is_const_object? instead [static] new MacroInterpreter ptr newDescription: Creates a new object of this class Python specific notes:This method is the default initializer of the object void register(string name)Description: Registers the macro interpreter
Registration of the interpreter makes the object known to the system. After registration, macros whose interpreter is set to 'dsl' can use this object to run the script. For executing a script, the system will call the interpreter's execute method. [virtual,const] int storage_schemeDescription: Returns the storage scheme (the format as which the macro is stored) This return value indicates how files for this DSL macro type shall be stored. The returned value can be one of the constants PlainTextFormat, PlainTextWithHashAnnotationsFormat and MacroFormat. [virtual,const] string suffixDescription: Returns the file suffix This string defines which file suffix to associate with the DSL macro. If an empty string is returned no particular suffix is assciated with that macro type and "lym" is assumed. The default implementation returns an empty string. [virtual,const] string syntax_schemeDescription: Returns a string indicating the syntax highlighter scheme The returned string can be empty (indicating no syntax highlighting), "ruby" for the Ruby syntax highlighter or another string. In that case, the highlighter will look for a syntax definition under the resource path ":/syntax/<scheme>.xml". The default implementation returns an empty string (no syntax highlighting). |