4 Understanding Macros and Packages

Macros and packages in plasT_eX live a dual life. On one hand, macros can be defined in L^aT_eX files and expanded by plasT_eX itself. On the other hand, macros can also be implemented as Python classes. Packages are the same way. plasT_eX can handle some L^aT_eX packages natively. Others may have to be implemented in Python. In most cases, both implementations work transparently together. If you don’t define that many macros, and the ones that you do define are simple or even of intermediate complexity, it’s probably better to just let plasT_eX handle them natively. However, there are some reasons that you may want to implement Python versions of your macros:

• Python versions of macros are generally faster

• You have more control over what gets inserted into the output document

• You can store information in the document’s userdata dictionary for use later

• You can prevent a macro from being expanded into primitive L^aT_eX commands, so that a custom renderer can be used on that node

• Some macros just don’t make sense in a plasT_eX document

• Some macros are just too complicated for plasT_eX

If any of these reasons appeal to you, read the following sections on how to implement macros and packages in plasT_eX.