-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix unbound vars errors in WRITESTRIKEFONTFILE from earlier edit. #2003
base: master
Are you sure you want to change the base?
Conversation
DUMMYINDEX etc should probably be a constant. And in fact it is, in EDITFONT. That declaraton probably should be moved to FONT.
… On Feb 1, 2025, at 11:37 AM, Matt Heffron ***@***.***> wrote:
@MattHeffron <https://github.com/MattHeffron> requested your review on: #2003 <#2003> Fix unbound vars errors in WRITESTRIKEFONTFILE from earlier edit..
—
Reply to this email directly, view it on GitHub <#2003 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJKMVCWPPHIGMLSJGND2NUPA3AVCNFSM6AAAAABWJSX242VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJWGE2TAOBYG44DONQ>.
You are receiving this because your review was requested.
|
…XCHAR from EDITFONT to FONT.
Moved those two constants from EDITFONT to FONT, per @rmkaplan. |
I think the constants BITSPERWORD and BYTESPERWORD should also be removed from EDITFONT. Those are in MODARITH and EXPORTS.ALL |
So, if removed, should EDITFONT add MODARITH to the (DECLARE%: EVAL@COMPILE DONTCOPY
(FILES (LOADCOMP) FONT MODARITH)) At this point, this is no longer part of fixing |
No, EDITFONT should load EXPORTS.ALL for compiling, that brings in the constants from MODARITH.
… On Feb 2, 2025, at 4:07 PM, Matt Heffron ***@***.***> wrote:
I think the constants BITSPERWORD and BYTESPERWORD should also be removed from EDITFONT. Those are in MODARITH and EXPORTS.ALL
So, if removed, should EDITFONT add MODARITH to the LOADCOMP? I.e., do
(DECLARE%: ***@***.*** DONTCOPY
(FILES (LOADCOMP) FONT MODARITH))
At this point, this is no longer part of fixing WRITESTRIKEFONTFILE in file FONT, but is more general clean up.
—
Reply to this email directly, view it on GitHub <#2003 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJN3MHXWVH6AGGZHB4T2N2XMVAVCNFSM6AAAAABWJSX242VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRZGYZTOMJRGY>.
You are receiving this because you were mentioned.
|
See the discussion on PR 2002 that strongly implies not to automatically load EXPORTS.ALL, even under How do we want these kind of dependencies to be "taken care of"? |
No description provided.