| Type | Bug | Status | complete | Date | 22-Oct-2010 13:49 |
|---|---|---|---|---|---|
| Version | alpha 109 | Category | Error Handling | Submitted by | Ladislav |
| Platform | All | Severity | minor | Priority | normal |
| Summary | LOAD/NEXT causes "impossible to debug" errors |
|---|---|
| Description | I know that LOAD/NEXT is not supported anymore, but the test below should not fail anyway. (otherwise it will generate "impossible to debug" errors) |
| Example code |
try/except [block? load/next "1"] [true] |
| Assigned to | n/a | Fixed in | alpha 110 | Last Update | 17-Sep-2013 10:55 |
|---|
| Comments | |
|---|---|
|
(0002654)
BrianH 24-Oct-2010 20:46 |
Not exactly the whole story. You forgot to include the print statement:
>> try/except [block? load/next "1"] [true] LOAD/next removed. Use TRANSCODE. == false And here is why the test fails: >> type? load/next "1" LOAD/next removed. Use TRANSCODE. == unset! >> try/except [block? ()] [true] == false Nevertheless, you are right that LOAD/next should fail more spectacularly, by triggering an error. If you aren't paying attention to the output to the console then you might miss that LOAD/next now returns an unset! value, which will only trigger an error in normal usage (assigning the return value to a word, passing it to a non-anytype function, etc.), rather than in test code (passing to a type tester). This deprecation notice should be removed soon, along with the refinement itself. But until then, after the print statement LOAD/next should explicitly trigger the 'script 'no-refine error. |
|
(0002705)
Ladislav 30-Oct-2010 22:06 |
in the core-tests suite |
|
(0003976)
BrianH 17-Sep-2013 00:51 |
The deprecation message has been removed now. See #2041 for details. |
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 17-Sep-2013 10:55 | Ladislav | Description | Modified | - |
| 17-Sep-2013 00:51 | BrianH | Comment : 0003976 | Added | - |
| 3-Nov-2010 16:22 | Ladislav | Status | Modified | tested => complete |
| 2-Nov-2010 06:50 | BrianH | Status | Modified | built => tested |
| 1-Nov-2010 19:43 | BrianH | Status | Modified | pending => built |
| 1-Nov-2010 19:43 | BrianH | Fixedin | Modified | => alpha 110 |
| 30-Oct-2010 22:10 | Ladislav | Comment : 0002705 | Modified | - |
| 30-Oct-2010 22:06 | Ladislav | Comment : 0002705 | Added | - |
| 28-Oct-2010 12:05 | BrianH | Status | Modified | reviewed => pending |
| 24-Oct-2010 21:15 | BrianH | Comment : 0002654 | Modified | - |
| 24-Oct-2010 21:13 | BrianH | Comment : 0002654 | Modified | - |
| 24-Oct-2010 20:47 | BrianH | Comment : 0002654 | Modified | - |
| 24-Oct-2010 20:46 | BrianH | Status | Modified | submitted => reviewed |
| 24-Oct-2010 20:46 | BrianH | Category | Modified | Unspecified => Error Handling |
| 24-Oct-2010 20:46 | BrianH | Comment : 0002654 | Added | - |
| 22-Oct-2010 13:56 | Ladislav | Summary | Modified | LOAD/NEXT test fails => LOAD/NEXT causes "impossible to debug" errors |
| 22-Oct-2010 13:55 | Ladislav | Description | Modified | - |
| 22-Oct-2010 13:53 | Ladislav | Code | Modified | - |
| 22-Oct-2010 13:49 | Ladislav | Ticket | Added | - |