Francois Laagel

Side note: block numbers always start at 0 and they are unsigned. However, you are not allowed to LOAD block 0 because in standard compliant implementations, because that would mean...

Thanks Travis. /MOD (on the F411) and .S now look good to me. I haven't run extensive tests but as far as I can tell, they are good to go....

BLOCK and BUFFER are not straight equivalent beasts, despite what some implementations would make you believe. BLOCK will force a read from mass storage, whereas BUFFER will not.

Hi Steve, I do apologize for having poorly stated my position. I totally agree with your 4 point statement (points of agreements) and reference to the ANSI specification for BLOCK...

Hi Steve/Gerry, Blocks are not from a bygone age for folks like me doing retro-computing. As a matter of fact, the ANSI standard specifies the file access word set as...

Hi Steve, I tried Avenue A (implementation change) but that causes : TUF-D T{ RND-TEST-BLOCK \ blk 0 OVER PREPARE-RND-BLOCK \ blk hash UPDATE FLUSH \ blk hash OVER 0...

Hi Steve, When you initialize a block acquired via BUFFER directly, you can write it to mass storage but, from the point of view of the Forth system, that block...

A side note while I'm at it: if you want authoritative third party confirmation, I recommend (like Gerry said) you do not waste your time on comp.lang.forth. Better go to...

Hi Steve, I really appreciate your thoroughness with respect to this matter. However, even if you _think_ the block is in memory, the Forth block subsystem does not, since (I...

OK, you have been factual and I ought to be as well. Wrt the ANSI standard: "not being already in memory" is where I think you just cannot maintain that...