CompuServe Thread

Forum unknown · Off the Cuff

#What goes where?

3 messages in this thread
#109562From: John DraperFeb 17, 1988 1:39 AM
Yes, it is showing. My point was merely that C is a lot less easily read than M2 or Pascal. No hidden meanings, no traps, just that one point. As for terseness, yes, many have stuck up for terseness. "M2 is too verbose" — Steve Ahlstrom, Don Curtis, Ben Blish, to name 3. There have been more, many more, here and elsewhere. I tried to look up array bounds checking without success. I do know that there are compiler switches in virtually all M2 compilers that will allow you to generate extra code to check things like ranges, array bounds, etc., but since i don't know details on it, I won't dwell on it. Perhaps someone who knows M2 and uses the switches will jump in with the answer. Regards, Larry.
#109580From: Nick Sullivan/TransactorFeb 17, 1988 3:07 AM
Larry, the M2 array-bounds checking is only for arrays that you declare as such to the compiler. John is correct that with run-time-allocated arrays the compiler has no way of knowing what the bounds are going to be, hence can't check to see that you remain within them.
#109580From: Nick Sullivan/TransactorFeb 17, 1988 3:07 AM
Larry, the M2 array-bounds checking is only for arrays that you declare as such to the compiler. John is correct that with run-time-allocated arrays the compiler has no way of knowing what the bounds are going to be, hence can't check to see that you remain within them.