View Single Post
Old 01 August 2015, 17:50   #159
Mrs Beanbag
Glastonbridge Software
Mrs Beanbag's Avatar
Join Date: Jan 2012
Location: Edinburgh/Scotland
Posts: 2,202
Originally Posted by Samurai_Crow View Post
Ummm... You do realize you can make up your own macros in Assembly in such a way that there is a debug and release version of the macros, don't you?
How will that help me? I don't want null pointers to crash the entire system in the released version, either.

Also remember that the '020+ has exception vectors specifically for the purpose of range checks and such.

To check the address of an array lookup of type long for range validity, you do something like this on 68020+:
Well of course you can explicitly check for nulls and out-of-ranges in your own code (debug or release) but i don't think you understand my point... the system is still not protected from code not written that way. I'm thinking about a CPU architecture in which these kinds of errors simply can't happen.
Mrs Beanbag is offline  
Page generated in 0.04108 seconds with 10 queries