On Mon, 4 Aug 2003, Frank Heckenbach wrote:
Mirsad Todorovac wrote:
- Val 3rd parameter
It's in mir034[cd].pas - I believe they should be in last attachment. I may have forgotten to mention.
They weren't there.
Good Lord! You're right. They're attached now. (rngv0.05.tar.gz)
BTW, some tests do "too much", but I'll leave it at that now. (Hope they'll always catch the right error.)
Well, so do I: but some things I've inherited some of it.
I hope you don't mean TGrayScale enumerated type, because I'm sort of fond of it. (-;
No, I don't mean that. Sometimes do you an additional assignment after the critical statment and in a few cases you do a loop where a single statement at the critical step would suffice.
Well, I was somewhat puzzled if the statement that isn't used by anything might be optimized out at -O3, I guess.
You could have noticed how I try to catch precisely "one off" errors in my last tests, so I hope they're improved by now ...
Yes, in most cases it's quite accurate. (Not always, but that's ok -- testing one off *always* could leave a small chance that the range checks miss "more" out-of-range cases. So I think in this regard the mixture is ok.)
OK.
Not exactly. These declarations would be valid. But a subrange type with a (non-constant) out-of-range initializer.
mir046[ceil][lu].pas
Still missing now:
- Val 3rd parameter
mir034[cd].pas (finally)
- Pack, Unpack more strictly
Still TODO.
- Type initializers
I think that's touched in mir046*.pas
- `asm' target (IA32 specific suffices)
Still TODO.
I should have done more, but I'm sending this immediatelly, for the remaining subjects will require more study.
Mirsad