Categories
- 3.4K All Categories
- 12 Introductions
- 2.7K Typeface Design
- 475 Font Technology
- 850 Technique and Theory
- 366 Type Business
- 337 Type Design Critiques
- 440 Type Design Software
- 29 Punchcutting
- 75 Lettering and Calligraphy
- 45 Technique and Theory
- 30 Lettering Critiques
- 288 Typography
- 200 History of Typography
- 81 Education
- 7 Resources
- 372 Announcements
- 60 Events
- 78 Job Postings
- 111 Type Releases
- 122 Miscellaneous News
- 195 About TypeDrawers
- 44 TypeDrawers Announcements
- 82 Suggestions and Bug Reports
VTT assembly code
Jens Kutilek
Posts: 248
Looking at the sample font included with VTT, I come across some code that is not immediately obvious to me, and I couldn't find documentation for it anywhere.
I know you can turn pre-push optimization on/off with
What does this similar begin/end command pair do that is used in all the template function definitions?
Then there seems to be something like variable jump markers, but the syntax is not entirely clear to me.
I know you can turn pre-push optimization on/off with
#PUSHOFF /* ... */ #PUSHON
What does this similar begin/end command pair do that is used in all the template function definitions?
FDEF[], 153 #BEGIN /* ... */ #END ENDF[]
Then there seems to be something like variable jump markers, but the syntax is not entirely clear to me.
FDEF[], 153 #BEGIN #PUSHOFF DUP[] #PUSH, 2 RS[] EQ[] #PUSH, 1 SWAP[] #PUSH, BEcln SWAP[] JROT[], (BEcln=#LEndClear) POP[] /* ... */ #LEndClear: SWAP[] POP[] #LEndFn: #END #PUSHON ENDF[]As I understand it, the JROT instruction should jump to the calculated instruction stream position of #LEndClear if the first stack element is True. But why is the "BEcln" value pushed _and_ used as an argument to JROT? Why the extra "variable" BEcln? Couldn't be #LEndClear be used for both?
Tagged:
0