Re: Gforth BLOCK 0
Bernd Paysan <[email protected]> Sat, 06 Aug 2022 16:48:30 +0200
| Newsgroups | gmane.comp.lang.forth.gforth |
|---|---|
| Message-ID | <12033212.O9o76ZdvQC@liubei> |
Am Samstag, 6. August 2022, 16:39:06 CEST schrieb Josh Grams: > IIRC 0 isn't a valid block number: for instance, > > http://forth.sourceforge.net/standard/dpans/dpans7.htm#7.6.1.1790 LOAD > says "An ambiguous condition exists if u is zero or is not a valid block > number." > > I believe in some systems blocks were actually the raw disk, so the > bootloader would be in block zero and thus it wasn't available for > source code? I could be totally wrong about that. Originally, in Gforth, block 0 did not exist, for that reason. However, other systems had block 0, which you just couldn't load from, so we changed the block numbering scheme to accommodate that. But the code was written around the assumption that block 0 does not exist. Fixed in current git head. -- Bernd Paysan "If you want it done right, you have to do it yourself" net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* https://net2o.de/
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEERJ1NDqPQRwYnwBjr9y2Uk5MtoGcFAmLufz4ACgkQ9y2Uk5Mt oGd20A//Tcl22FvS2eXScNVEHfyLFbDSF/QnlD/+CBxR8SruV/a1qwDl0ZHlXxSb Mq164h7DyZMH6gzeQXVz3eBo3TDV5BVL7q8h7pz3b1KU+UmJKTKfEcxymcE0udAj cHdhRsD26xvmX05fo3go4XZDjcefYsSliO13Ez1V17sH7OW3Oh5/3/seWjxuCFsy 42B4J/qffxMag9+FFBs95+YUS4Gv2caicw3TIkevG6JZep2SEBntM0QtlHFxJLHi EFz69DC0VfvFhtn4ZoMVWFqthp0SbtVtDOIX05fHNIml1PVVlyO1w6i/3lRcjg0a SPJZGCcxo0sll461Jnxboxb0wb0ytgLk5ydoi4WiFP5j0wRZJphyJtiypeezitIO 4Kta7pGgUntVwxsDwcvUfiszx8aFYO42gjOy2uR8BUt79nXtSN4DJzPjg5Nvu0AA b4wmwZA1qVVbDjDnHx9hBAW2Dkh3VJgIjNFYUpVBXNr19ARqpCogtIwexrT6wISx F9DOOvmJG44RYTuncb/x2gMgBWTwHx0Fee/aqupMc4YdrJw3GROWk7Y0orYNCuZm WP/bM6ghhRkbRoJWOhwtZPL/xQw8r24JwTwLJXIjLk55gP2W+AI3qVdJ4yjR/JBZ j1Lwl7fYBfy7CVDSQxnH7zvyBblZELET5JDMUWMIOyvw6xNnIZw= =XOtN -----END PGP SIGNATURE-----