With Screen 19 (two consecutive passes) ...
0.166
0.0991
0.163
0.0361
0.144
0.247
0.174
0.102
Search found 48 matches
- Sep 04, 2020 5:56
- Forum: Beginners
- Topic: Slow printing to console screen
- Replies: 14
- Views: 597
- Sep 04, 2020 3:32
- Forum: Beginners
- Topic: Slow printing to console screen
- Replies: 14
- Views: 597
Re: Slow printing to console screen
If I redirect the output to a file, at the command line, my results become ... 0.143... 0.111... 0.00751... 0.00367... Doesn't this confirm that the problem is with Windows? Is it possible that every Print statement results in a total screen rewrite, even when there is no scrolling? Could this expla...
- Sep 04, 2020 0:40
- Forum: Beginners
- Topic: Slow printing to console screen
- Replies: 14
- Views: 597
Re: Slow printing to console screen
I switched to the "legacy console" and was initially surprised at the 2x performance increase. Then I realised that the execution speed was dependent on the size of the CMD window. Smaller windows result in higher speeds. Legacy console, small window, two consecutive runs 5.68 4.77 1.32 1....
- Sep 03, 2020 23:37
- Forum: Beginners
- Topic: Slow printing to console screen
- Replies: 14
- Views: 597
Re: Slow printing to console screen
@fzabkar what vesion of FB are you using and what command options if any are you using? also, is your computer a laptop? FB 1.07.1 for Win32 I'm using an IDE (FBIde 0.4) with a compiler command of ... "<$fbc>" "<$file>" .. so I guess that means there are no compiler options. Com...
- Sep 03, 2020 23:24
- Forum: Beginners
- Topic: Slow printing to console screen
- Replies: 14
- Views: 597
Re: Slow printing to console screen
Thanks @srvaldez, I had already modified my code with timers, but here are my results using your mods (Windows 10 CMD on 2.4GHz Core 2 Duo):
7.90...
7.66...
0.616...
0.651...
7.90...
7.66...
0.616...
0.651...
- Sep 03, 2020 20:46
- Forum: Beginners
- Topic: Slow printing to console screen
- Replies: 14
- Views: 597
Slow printing to console screen
I'm running Windows 10 on a 2.4GHz Core 2 Duo. I'm finding that printing to the console screen is noticeably slow. The following code illustrates this behaviour, at least on my old machine: http://www.users.on.net/~fzabkar/temp/consprnt.bas http://www.users.on.net/~fzabkar/temp/consprnt.exe Is this ...
- Sep 03, 2020 7:44
- Forum: General
- Topic: Commandline parsing problem
- Replies: 25
- Views: 2336
Re: Commandline parsing problem
fxm wrote:In order to update the COMMAND documentation page:
Is this behavior specific to Windows or general (same behavior with Linux)?
I don't have a Linux box to test this. Sorry.
- Sep 02, 2020 19:56
- Forum: Beginners
- Topic: Strange command line parsing behaviour
- Replies: 20
- Views: 928
Re: Strange command line parsing behaviour
Thanks to all for your help.
Should I report the \" command line parsing behaviour as a bug?
Should I report the \" command line parsing behaviour as a bug?
- Sep 01, 2020 20:40
- Forum: Beginners
- Topic: Strange command line parsing behaviour
- Replies: 20
- Views: 928
Re: Strange command line parsing behaviour
I must have had a badly messed up installation. It appears that there was something wrong with INTRIN.BI. After searching the old install directory ... ---------- C:\FREEBASIC_BAD\FREEBASIC-1.07.1-WIN32\INC\WIN\WINNT.BI #define InterlockedCompareExchange64 _InterlockedCompareExchange64 ---------- C:...
- Sep 01, 2020 19:25
- Forum: Beginners
- Topic: Strange command line parsing behaviour
- Replies: 20
- Views: 928
Re: Strange command line parsing behaviour
This is mysterious. FC: cannot open C:\FREEBASIC\FREEBASIC-1.07.1-WIN64\INC\dislin.BI - No such file or folder Is there any dislin.bi in your C:\FREEBASIC\* folder, including subfolders? I have plenty of them, some 50kB, others 77kB... I edited my earlier reply before seeing your post.
- Sep 01, 2020 18:41
- Forum: Beginners
- Topic: Strange command line parsing behaviour
- Replies: 20
- Views: 928
Re: Strange command line parsing behaviour
As I said earlier, I did do a clean install. Same problem.
Edit: I uninstalled and reinstalled one more time. This time it compiled OK. I think the problem may have been that the path in my IDE was still set to the earlier installation. Sorry for the screw-up.
Edit: I uninstalled and reinstalled one more time. This time it compiled OK. I think the problem may have been that the path in my IDE was still set to the earlier installation. Sorry for the screw-up.
- Aug 31, 2020 19:02
- Forum: Beginners
- Topic: Strange command line parsing behaviour
- Replies: 20
- Views: 928
Re: Strange command line parsing behaviour
Yes, still same error. If a reinstall fixes the problem, I'll let you know. Edit: Still the same error. Comparing the *.bi files in the 32-bit and 64-bit INC directories finds differences in ffi.bi, jit.bi, mpg123.bi, and zip.bi. Some BI files are present in 32-bit but not in 64-bit. FC: cannot open...
- Aug 31, 2020 0:30
- Forum: Beginners
- Topic: Strange command line parsing behaviour
- Replies: 20
- Views: 928
Re: Strange command line parsing behaviour
I've moved the FreeBasic directory under the Root. Can you tell me what problems I could have encountered if I had left it where it was?
- Aug 30, 2020 19:18
- Forum: General
- Topic: Commandline parsing problem
- Replies: 25
- Views: 2336
Re: Commandline parsing problem
I'm running under 32-bit Windows and generating 32-bit apps.
This behaviour is an annoyance. ISTM that anything on the command line should be interpreted as is, otherwise what is the point of the Command keyword?
This behaviour is an annoyance. ISTM that anything on the command line should be interpreted as is, otherwise what is the point of the Command keyword?
- Aug 30, 2020 17:38
- Forum: Beginners
- Topic: Strange command line parsing behaviour
- Replies: 20
- Views: 928
Re: Strange command line parsing behaviour
#include "windows.bi" ' do nothing End Command executed: "C:\Program Files\FreeBASIC\FreeBASIC-1.07.1-win32\fbc.exe" "C:\FZWork\FreeBASIC\test\windows_bi.bas" Compiler output: C:\Program Files\FreeBASIC\FreeBASIC-1.07.1-win32\inc\win\winbase.bi(2364) error 42: Variable...