PureBasic Forums - English

Cool, that's what I thought. I just made too many mistakes cutting and pasting. I got compiles from 28ms to 78ms on various png files. But, I declared a single @ char for MyString, which resulted in a mono character output. Ill run your explicit code now. Thanks! EDIT: Infratec's enableexplicit code...

Tried to run the topic but ran into some pitfalls.
Where is MyString defined?
No EnableExplicit

What is the goal of the textual output?

There is an argument to insist on consistent syntax. But many prefer "can't" to "cannot" or "can not". "a = a + 1" vs "a + 1" For simplicity, I would force 1 and only 1 way to reference. Shortcuts and undefined behavior should be avoided as complexit...

Yes, semaphores have been very reliable for me. Just be careful with the shared use of Map() data. This is my NOTE TO SELF: ; Current PB Design means a Map()'s current element pointer is NOT "threaded". ; A read in one thread can change the current element within another thread. ; Unlike a...

Before I compile various apps, I have to configure them. So why not force the issue with settable constants? Here is example to force the use of USESQLITE CompilerIf Defined(MY_EXE, #PB_Constant) ; Do nothing. CompilerElse #MY_EXE = 0 CompilerEndIf CompilerIf #MY_EXE #SQLITE_USE_DLL = 0 ; 0=use stat...

Ok, is this the new behavior?
exe$ = UCase(PeekS(@Process\szExeFile, -1, #PB_Ascii)) ;<-- v611b1 syntax error but used to work.
exe$ = UCase(PeekS(@Process\szExeFile[0], -1, #PB_Ascii)) ;<-- v611b1 ok.

Structure Processentry32 field:
szExeFile.c[260]

Nice
My redim bug works.

Read the release notes. It is a necessary improvement compiling with latest C libs. You can reduce the larger files somewhat using VS2022 link.exe.

Compile exe without debugger and report.

As Psychophanta said, accuracy can be subjective. Search the forum for examples of math errors when mixing integers and floats. The results depend on the order of the algebraic expression and can be very hard to find. For floating point calculations, I prefix "0.0+" to force a floating poi...

Not as simple as that obviously.
But, there are cases where algebraic rules vary from ideal. Or when asm and cbe compiles do not match. Or when a bug forces a change in scope.

These slow development and release of your app.
Size of the app exe is so far down the list it could be last.

My priority for EXE => accurate, fast, something I have not thought about yet, something else, size.

Haha, I blame it on an eclipse in my brain.

The workaround works. But, I have to search for these cases within my code. Not so fun.