moricode wrote: Fri Feb 28, 2025 5:06 am
so , we do not need opening compiler when open IDE .
we only need load syntax color rule and load load library function name , then the IDE is working perfectly , why need to load whole giant compiler ?
compiler only need for compilation , no need for editing.
The compiler is used at startup to communicate with the IDE, passing on information that the IDE does not have, such as the list of functions...
When the IDE is started, it is launched with: pbcompiler.exe /STANDBY /LANGUAGE English
It is possible to do this in cmd:
Code: Select all
pbcompiler.exe /STANDBY /LANGUAGE English
It will answer
STARTING 6.20 PureBasic 6.20 (Windows - x64)
READY
Once ready you can write, for example FUNCTIONLIST and return. It will enumerate the list of functions:
FUNCTIONLIST
1816
AbortFTPFile (#Ftp) - Abort the current asyncrhonous file operation.
AbortHTTP ..........
Crtl+C to close it
#
Otherwise, I've never encountered the “compiler is not ready” message before, but now I get it when I start the IDE, it's pretty annoying to have to restart it.
I don't know if it has anything to do with Pb 6.20 Install but it's about the same time.
I tested in cmd, the time for the compiler to be ready and indeed, it is quite long the first time
Code: Select all
C:\Program Files\PureBasic\Compilers>Echo %Time% Ctrl+C as soon as you see ready for the end time & pbcompiler.exe /STANDBY /LANGUAGE Francais & Call Echo ^%Time^%
16:31:17,82 Ctrl+C as soon as you see ready for the end time
STARTING 6.20 PureBasic 6.20 (Windows - x64)
READY
16:31:18,51
I searched a little, the maximum delay seems to be 15s to WaitForCompilerReady() in CompilerInterface.pb
Code: Select all
Timeout.q = ElapsedMilliseconds() + 15000 ; just for safety
While AvailableProgramOutput(CompilerProgram) = 0 And ElapsedMilliseconds() < Timeout
It would be a good idea to have this delay in the compiler settings, but well, no idea why it takes longer than 15s sometimes here, now.