|
About the Errors category
|
|
0
|
224
|
October 2, 2021
|
|
Should EVALUATE/NEXT bomb on an error?
|
|
3
|
463
|
August 23, 2024
|
|
Avoid Raised Errors in PACK! (But Feel The Power!)
|
|
1
|
63
|
September 18, 2024
|
|
Making FAIL Stand Out With Antiform TAG!
|
|
0
|
25
|
September 16, 2024
|
|
Pointing the Blame In FAIL
|
|
4
|
613
|
September 2, 2024
|
|
Recovering Values From A Raised Definitional Error
|
|
1
|
261
|
September 11, 2024
|
|
FAIL vs. RETURN RAISE: The New Age of Definitional Errors!
|
|
0
|
469
|
June 28, 2022
|
|
The VOID-in-NULL-out Protocol
|
|
1
|
450
|
July 14, 2022
|
|
WORD!, PATH!, and URL!s as ERROR! ids
|
|
7
|
575
|
January 22, 2019
|
|
Discouraging The Interception of Abrupt Failures
|
|
3
|
382
|
August 29, 2024
|
|
Making CALL Raise a (definitional) Error For Bad Exit Codes
|
|
2
|
215
|
August 24, 2024
|
|
Should SET-WORD!s Have "Raised Error Interception"?
|
|
0
|
187
|
February 7, 2023
|
|
The Need To Rethink ERROR!
|
|
2
|
648
|
June 9, 2022
|
|
The FAIL That Wins Big: Combinator Definitional Errors
|
|
0
|
207
|
August 19, 2022
|
|
Safety Concept: Error on discarded plain BLOCK! ?
|
|
3
|
426
|
November 29, 2021
|
|
Embracing Host Language Exception Model in the API
|
|
0
|
549
|
March 4, 2018
|
|
Hooking FAIL and PANIC...should DO of an ERROR! be "unhookable"?
|
|
0
|
436
|
January 21, 2018
|
|
More Comprehensible Errors With per-Cell Labeling!
|
|
1
|
556
|
October 6, 2020
|