4.9 Customization

Page 35 of 800

Search internet

When the Logiweb compiler (lgc) loads a page, it does a number of fixed operations but also invokes four functions which are under author control:

• Verification is done by a 'claim engine'. If you reference the base page as your first reference and if you do not define your own claim engine, the claim engine defined by the base page will run. The claim engine of the base page verifies all test cases on your page. If you reference the check page as first reference, you get another claim engine. The claim engine of the check page does the same as that of the base page but also verifies all proofs on your page. You can define your own claim engine if your like. If you do so, you have the full Logiweb programming language at your disposal, so you can check whatever a computer is able to check.
• Macro expansion is done by a 'macro expansion engine'. If you reference the base page as your first reference and if you do not define your own macro expansion engine, the macro expansion engine defined by the base page will run. That engine is so general that you will probably not need to replace it, but you have the option if you want. If you reference the check page as first reference, you get the same macro expansion engine.
• Rendering is done by a 'rendering engine'. The default rendering engine of the lgc compiler is so general that you will probably not need to define one yourself, but you have the option if you want.
• Unpacking is done by an 'unpacking engine'. When lgc reads a page expressed in the binary 'vector' format, unpacking is governed by the unpacking engine. If you write open source Logiweb pages you will probably not need to define your own unpacking engine. But if you want to compress and/or encrypt your pages, you will need to define an unpacker.

Page 35 of 800

Search logiweb.eu