2,951
edits
LIMIT ERROR: Difference between revisions
Jump to navigation
Jump to search
m
Errors category
Miraheze>Marshall (Created page with "A '''LIMIT ERROR''' is an error message indicating that some imposed limit of the interpreter (one that is due to resource or design rather than theoretical limitations) h...") |
m (Errors category) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
</source> | </source> | ||
{{Works in|[[Dyalog APL]]}} | {{Works in|[[Dyalog APL]]}} | ||
In a 64-bit interpreter, it is rare to run into an array length limit, since the maximum allowed length is usually on the order of <source lang=apl inline>2*64</source>, and attempting to create an array this large may run into a [[DOMAIN ERROR]] or [[ | In a 64-bit interpreter, it is rare to run into an array length limit, since the maximum allowed length is usually on the order of <source lang=apl inline>2*64</source>, and attempting to create an array this large may run into a [[DOMAIN ERROR]] or [[WS FULL]], as most machines do not have enough addressable memory to store it. [[Empty]] arrays do not need storage space, so working with arrays with one length-0 axis and one long axis can sometimes reveal a LIMIT ERROR: | ||
<source lang=apl> | <source lang=apl> | ||
((0,2*63)⍴2) , ((0,2*63)⍴3) | ((0,2*63)⍴2) , ((0,2*63)⍴3) | ||
| Line 17: | Line 17: | ||
LIMIT ERRORs may appear when working with components outside of APL such as files. Operating system limitations are usually reported as LIMIT ERRORs, since they are caused by constraints outside of the APL interpreter's control. | LIMIT ERRORs may appear when working with components outside of APL such as files. Operating system limitations are usually reported as LIMIT ERRORs, since they are caused by constraints outside of the APL interpreter's control. | ||
{{APL | {{APL features}}[[Category:Errors]] | ||