|
WIDTH
Mar 23, 2020 4:54:08 GMT
Post by Admin on Mar 23, 2020 4:54:08 GMT
There's still something funny going on with WIDTH, though I suspect it is not a fault with the language itself. I have a program, already compiled, which uses WIDTH. It is the program where I reported problems earlier.
OSCLI("FONT Ariel,48,B") a$="56 o galorĂ¯au" b$="56 o galoriau" PRINTa$WIDTH(a$) PRINTb$WIDTH(b$) OSCLI("FONT")
Using the new 6.12x I can run the program and get the right results. If I compile the program, however, the version with a$ only gives the length for the "56" and ignores the rest of the phrase. The b$ comes out correctly at all times.
When I recompile, of course, I'm compiling "on top" of the previous compilation so as to preserve the inclusions and the icon. What I'm wondering is whether somehow the recompiled program is using or preserving the BASIC of the previous version?
Does that seem likely or even possible?
|
|
|
WIDTH
Mar 23, 2020 17:52:41 GMT
Post by Zaphod on Mar 23, 2020 17:52:41 GMT
Not using 6.13a why is that??? 6.13a works compiled exactly as you would expect for me. Windows 10.
|
|
ken
New Member
Posts: 4
|
WIDTH
Mar 24, 2020 3:45:30 GMT
Post by ken on Mar 24, 2020 3:45:30 GMT
Interesting - and my bad. I was under the impression that 6.12x was the same as 6.13, just a provisional version. However I have now upgraded to 6.13a and recompiled the program using WIDTH and the initial test seems to indicate that it works.
|
|