Segmentation fault protection: Difference between revisions

Content added Content deleted
Line 23: Line 23:
=={{header|Phix}}==
=={{header|Phix}}==
Phix has extensive compilation and runtime error handling, including bounds checking, unassigned variables, invalid assignments, and more, as well as exception handling, and strives to always deliver clear human-readable and actually useful error messages along with the file name and line number where they occurred - of course within reason, as the following example shows messages triggered by inline assembly are inherently always going to be a bit more cryptic than the norm.
Phix has extensive compilation and runtime error handling, including bounds checking, unassigned variables, invalid assignments, and more, as well as exception handling, and strives to always deliver clear human-readable and actually useful error messages along with the file name and line number where they occurred - of course within reason, as the following example shows messages triggered by inline assembly are inherently always going to be a bit more cryptic than the norm.
<!--<lang Phix>(phixonline)-->
<!--<lang Phix>(notonline)-->
<span style="color: #008080;">try</span>
<span style="color: #008080;">try</span>
#ilASM{ xor eax,eax
#ilASM{ xor eax,eax