WDL uses KEYMACRO, a macro processor developed by former WDL developer, Alex McGregor.
KEYMACRO is a lightweight macro processor that is easy to use, especially for larger or more complex macros. It is designed to make coding easier and more fun by:
· allowing greater code reuse
· making writing macros easier
· enabling faster development by having a more natural syntax for macro definition
There are four types of KEYMACRO macros:
· Standard
· Triggered Macros
· ECHO Macros
· Routine Macros
If you are working on a project that is too complicated for KEYMACRO, or if you want to write your own macros, the FASTER Project is a resource that you can use to write macros using the standard KEYMACRO syntax.
• File reading/writing wrappers (for low-level I/O)
For win32, we make special effort to make our file reading/writing functions very fast. If you want to enable some of the lower-level features of win32, you can use these WDL utilities:
· SafeRead (to handle reading from filestreams)
· SafeWrite (to handle writing to filestreams)
· fgetter/fgetw (to get at low-level I/O functions)
There are a number of design goals behind these wrappers. In particular, we want to make writing and reading programs much more fun and less confusing. Most of the time, reading and writing from files is actually a fairly complicated process that hides a lot of functionality from the programmer. Writing C++ code is much harder than writing a bytecode like BASIC, and using a higher-level language makes it even harder. We use these functions to make it easier to write code with the same abstractions as what we use to write BASIC. The philosophy is that we are doing win32 programming in C++, and you can only do that if you make it as easy as possible to write good win32 programs.
One more thing: Macros are faster. They are one of the very fastest ways to code. They can do far more than a compiler can do, and it only takes a few hours of practice to get really good at writing them. Some good examples are:
· Compile-time code generation (from a pattern-matching preprocessor)
· Preprocessing (from macros)
· Source-to-source code transformation (e.g a77f14ba26 fabler
https://www.cpowerfitnessltd.com/profil ... er/profile
https://www.terraepassi.com/profile/Sun ... lm/profile
https://yo.kinkymatters.com/profile/man ... ik/profile
https://www.techcargo.com/profile/Solid ... at/profile
https://www.maddierosehills.co.uk/profi ... ka/profile
WDL uses KEYMACRO, a macro processor developed by former WDL developer, Alex McGregor.
KEYMACRO is a lightweight macro processor that is easy to use, especially for larger or more complex macros. It is designed to make coding easier and more fun by:
· allowing greater code reuse
· making writing macros easier
· enabling faster development by having a more natural syntax for macro definition
There are four types of KEYMACRO macros:
· Standard
· Triggered Macros
· ECHO Macros
· Routine Macros
If you are working on a project that is too complicated for KEYMACRO, or if you want to write your own macros, the FASTER Project is a resource that you can use to write macros using the standard KEYMACRO syntax.
• File reading/writing wrappers (for low-level I/O)
For win32, we make special effort to make our file reading/writing functions very fast. If you want to enable some of the lower-level features of win32, you can use these WDL utilities:
· SafeRead (to handle reading from filestreams)
· SafeWrite (to handle writing to filestreams)
· fgetter/fgetw (to get at low-level I/O functions)
There are a number of design goals behind these wrappers. In particular, we want to make writing and reading programs much more fun and less confusing. Most of the time, reading and writing from files is actually a fairly complicated process that hides a lot of functionality from the programmer. Writing C++ code is much harder than writing a bytecode like BASIC, and using a higher-level language makes it even harder. We use these functions to make it easier to write code with the same abstractions as what we use to write BASIC. The philosophy is that we are doing win32 programming in C++, and you can only do that if you make it as easy as possible to write good win32 programs.
One more thing: Macros are faster. They are one of the very fastest ways to code. They can do far more than a compiler can do, and it only takes a few hours of practice to get really good at writing them. Some good examples are:
· Compile-time code generation (from a pattern-matching preprocessor)
· Preprocessing (from macros)
· Source-to-source code transformation (e.g a77f14ba26 fabler
https://www.cpowerfitnessltd.com/profile/kirstanahleanther/profile
https://www.terraepassi.com/profile/Sunny-Korean-Movie-2011-Eng-Sub-Download-Film/profile
https://yo.kinkymatters.com/profile/manfridpavelikpavelik/profile
https://www.techcargo.com/profile/Solid-Edge-V20-Selicensedat/profile
https://www.maddierosehills.co.uk/profile/charleinyannycka/profile