changes for Visual D 1.4.1-beta3

CHANGES

@@ -1421,3 +1421,16 @@ Version history
   * mago: improved stability when displaying arrays from invalid memory address
   * dmdserver: fixed a couple of assertions causing the server to restart
   * dmdserver: replaced new location storage to avoid leaking memory
+
+2025-05-04 version 1.4.1-beta3
+  * mago:
+    - the option "Expand strings to show array of characters" had no effect
+    - the call stack now displays D expression if "Parameter values" is enabled
+    - issue #253: mago: with option "Shorten type names and function names in call stack"
+      module names are removed when displayed
+    - issue #305: mago: with option "Call property methods implicitly in expression evaluation"
+      methods annotated with @property and without arguments are evaluated without parentheses
+    - format options could be erratic when execution function for expression evaluation
+    - fixed selecting the zero-argument method in case multiple overloads
+    - added format specifiers 'd' (decimmal), 'x' (hex), '@' (evaluate function automatically)
+    - added a couple of caches for better responsiveness

VERSION

@@ -2,4 +2,4 @@
 #define VERSION_MINOR      4
 #define VERSION_REVISION   1
 #define VERSION_BETA       -beta
-#define VERSION_BUILD      2
+#define VERSION_BUILD      3

doc/CompileCommands.dd

@@ -78,7 +78,7 @@ $(H3 DMD/Win32)
 
 $(PRE obj2asm -x "$(DOLLAR)(InputFile)" >"$(DOLLAR)(TargetPath)")
 
-This assumes obj2asm can be found in through PATH. If this is not the case, please add
+This assumes obj2asm can be found through PATH. If this is not the case, please add
 the full path to it. The same replacement macros can be used as in the project 
 configurations.
 
@@ -110,7 +110,7 @@ use LLVM tools for other architectures, you'll have to change the default settin
 
 $(PRE llvm-objdump -disassemble -x86-asm-syntax=intel -no-show-raw-insn "$(DOLLAR)(InputPath)" >"$(DOLLAR)(TargetPath)" )
 
-You'll have to add the path the LLVM tools to the "Executable Paths" or to the
+You'll have to add the path to the LLVM tools to the "Executable Paths" or to the
 llvm-objdump command.
 
 $(H3 GDC)