From 39619b629d3614f6b284865f5c254ebda5272f2b Mon Sep 17 00:00:00 2001 From: mrdudz Date: Sat, 19 Aug 2023 15:39:16 +0200 Subject: [PATCH] fix docs on .version (forgot to update it when __CC65__ was fixed) --- doc/ca65.sgml | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/doc/ca65.sgml b/doc/ca65.sgml index b4ef3e188..982c68949 100644 --- a/doc/ca65.sgml +++ b/doc/ca65.sgml @@ -1367,17 +1367,22 @@ writable. Reading this pseudo variable will give the assembler version according to the following formula: - VER_MAJOR*$100 + VER_MINOR*$10 + (VER_MAJOR * 0x100) + VER_MINOR - It may be used to encode the assembler version or check the assembler for - special features not available with older versions. + The upper 8 bits are the major-, the lower 8 bits are the minor version. Example: - Version 2.14 of the assembler will return $2E0 as numerical constant when - reading the pseudo variable (VER_MAJOR * 0x100) + VER_MINOR * 0x10 - + which resulted in broken values starting at version 2.16 of the assembler. For + this reason the value of this pseudo variable is considered purely informal - you should + not use it to check for a specific assembler version and use different code + according to the detected version - please update your code to work with the + recent version of the assembler instead (There is very little reason to not use + the most recent version - and even less to support older versions in your code). Pseudo functions