Spike: move auto-load into the LCB (plan B: getenv platform check)#49
Closed
SethMorrowSoftware wants to merge 0 commit into
Closed
Spike: move auto-load into the LCB (plan B: getenv platform check)#49SethMorrowSoftware wants to merge 0 commit into
SethMorrowSoftware wants to merge 0 commit into
Conversation
SethMorrowSoftware
changed the title
SethMorrowSoftware
force-pushed
the
claude/beautiful-cray-lwlsgr
branch
from
187ee7c to
61a52be
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closed — spike complete, answer is "no"
This spike asked whether the auto-load could live in the LCB instead of the Kit. It can't, and we now know definitively why:
try/catchin LiveCode Builder — the parser rejectstry(compile error). So a failed binding can't be caught.c:>empty-library bindings don't resolve on Windows —c:>getenvfailed at runtime with "Unable to bind foreign handler ... _getenv". Same mechanism asdlopen/realpath, so none of the libc probes reach the CRT on Windows.With no way to catch the failure and no way to detect the platform from inside the LCB without throwing, the LCB cannot self-gate. The Kit approach in
main(#48) — gating onthe platformin LiveCodeScript — stands as the correct and final design. Branch reset tomain; nothing to merge here.https://claude.ai/code/session_01EVV5fGeXqtWs8WDrmgWNku