Modify ↓
Opened 15 years ago
Closed 14 years ago
#1995 closed Bug (Wont Fix)
Different results on x86 and x64
| Reported by: | UEZ | Owned by: | |
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | 3.3.6.1 | Severity: | None |
| Keywords: | Cc: |
Description
When I run these lines
#AutoIt3Wrapper_UseX64=n
MsgBox(0,"", StringMid(StringFormat("%-20.*s", "AutoIT.de"),1 , 20))
the result is different to this
#AutoIt3Wrapper_UseX64=y
MsgBox(0,"", StringMid(StringFormat("%-20.*s", "AutoIT.de"),1 , 20))
Should the result not the same?
Br,
UEZ
Attachments (0)
Change History (3)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Nothing need fixed. This is not a bug.
The user has invalid syntax of a conversion specification therefore triggering undefined behavior.
All we should do is document that bad syntax causes undefined behavior. When that's done this ticked can be closed.
Version 0, edited 14 years ago by (next)
comment:3 by , 14 years ago
| Resolution: | → Wont Fix |
|---|---|
| Status: | new → closed |
Addressed by revision [7088].
Note:
See TracTickets
for help on using tickets.

In fact AutoIt does really support .* precision.
Your example is wrong as an extra parameter defining the precision will be needed before the string to defined the precision
MsgBox(0,"", StringMid(StringFormat("%-20.*s", 10, "AutoIT.de"),1 , 20))but as I say Autoit will not support this format
So fix must be done to accept or reject such precision definition