Development Errors
Topic | Replies | Views | Activity | |
---|---|---|---|---|
About the Errors category
|
0 | 173 | October 2, 2021 | |
Making CALL Raise a (definitional) Error For Bad Exit Codes
|
0 | 52 | December 8, 2023 | |
Should We Point The Blame in FAIL With "@"?
|
1 | 174 | February 8, 2024 | |
FAIL vs. RETURN RAISE: The New Age of Definitional Errors!
|
0 | 315 | June 28, 2022 | |
The VOID-in-NULL-out Protocol
|
0 | 311 | July 14, 2022 | |
Should SET-WORD!s Have "Raised Error Interception"?
|
0 | 122 | February 7, 2023 | |
The Need To Rethink ERROR!
|
2 | 499 | June 9, 2022 | |
The FAIL That Wins Big: Combinator Definitional Errors
|
0 | 157 | August 19, 2022 | |
Safety Concept: Error on discarded plain BLOCK! ?
|
3 | 345 | November 29, 2021 | |
Embracing Host Language Exception Model in the API
|
0 | 486 | March 4, 2018 | |
Hooking FAIL and PANIC...should DO of an ERROR! be "unhookable"?
|
0 | 372 | January 21, 2018 | |
More Comprehensible Errors With per-Cell Labeling!
|
1 | 454 | October 6, 2020 | |
FAIL-ing with Grace
|
6 | 489 | January 22, 2019 | |
WORD!, PATH!, and URL!s as ERROR! ids
|
2 | 484 | June 8, 2018 |