My OSWORD 14,0 (return date & time as string) certainly doesn't return century 19, it returns the correct century between 00 and 99 (assuming you set it right). And yes, it does tick over correctly despite not having hardware support. I even correct the three times per four centuries leap year bug.OSWORD 14,8+n use an 8-byte date/time block with the century specified. I don't think the broken functionality of always returning "19" in the string return functions should be replicated. I would argue that that functionality expected to return "19xx" from 1980 to 1999, not for year numbers 00-79, being "in the past" from the point of view then. So if the year number is 00-79 it is out of specification, so it is allowable to tighten the specification to correctly return "20xx" for that range. As recommended in Acorn documents I remember reading in the 1980s anyway, and has been implemented in loads of MOS patches and third-party RTC programs.
I think the "BCD block" results are intended for further processing, so including a century in the block isn't really important. If you need it, you can look it up. After all, does an alarm time need a century? The only exception is OSWORD 14,2: convert BCD block to string. I consider this call useless precisely because there is no way to pass a century to it, and include it only for compatibility. I might implement your OSWORD 14,10, because that seems useful, but the rest don't really seem worth it to me.
Statistics: Posted by Barneyntd — Wed Jan 22, 2025 9:20 pm