Statistically speaking, it is rarely the compiler distribution, it is usually the antivirus. File complaints with them.

I'm no preproc expert, but maybe the preproc handling of #include once is odd, so try crafting the whole path in a #define with ## and then include the resulting variable.

Note that after I wrote the above text I realized there might be a fundamental difference between FB and FPC. This relates to the module system and the fact that FPC loads module-interfaces from binary, not textual (header) representations. This binary representation is dialect independent. So if FB...

That sounds quite recognizable, a bit like a problem my brother had. He lived in Africa where there were regular power outages. What happened sometimes is that there was an outage during startup or shutdown and then the bios for some stupid reason would consider that a failed boot, and switched the ...

How do you cripple a Windows 10? The Windows 10 install I run, started life as an OEM Windows 8.0, though relatively late (just a few months before 8.1 came out) Slowly I'm thinking a reinstall would be good (and a new SSD, since this one is from 2013), but that is more precaution than necessary. An...

If i interpret Jeff´s post right (correct me, if i´m wrong), his goal is to make the global namespace initially empty, that is, to put all existing statements in a namespace, which must be activated (using ..., or explicit prefix "fbc." or the like). Where (I think) you are wrong is that ...

No. A lot of typing is compiler internal, and gone when the final result runs. While the information might have been there in the compiler, it is not in the EXE

Jeff, for some types of programs, the many symbols (keywords) defined by fbc by default just get in the way. For example, writing a Win API/SDK program, a framework, or a graphics/gui tool kit. i don´t want to be contra-productive, but coming from PB, where we don´t have namespaces but (i didn´t co...

I can remember two problems with our implementation. One is summoned up by this comment: { The handles that are to be passed to the child process must be inheritable. On the other hand, only non-inheritable handles allow the sending of EOF when the write-end is closed. This function is used to dupli...

I have no problems with command lines longer than 260 chars. But saving or renaming a file with a path longer than 260 chars fails with Explorer (manually) and using CreateFileW programmatically. Below 260, the prepending is not required. Above that, it doesn't help. Pretty confusing. And if you do...

Huh?

source seems to be encoded in some way, won't open with notepad. (despite having an .asc extension) Wordpad will do, but that won't help you because the fun stuff is under the hood. Fact is you don't have to prepend the \\?\ stuff, CreateProcessW works fine with a plain UTF-16 path. Wordpad doesn't...

- use CreateProcess W , but read the docs carefully (my highlighting): The TL;DR: - expand paths (make them absolute and resolve all "..\", since NT paths can't handle that) - prepend \\?\ - calll the -W function The Unicode version of this function, CreateProcessW, can modify the content...

How would your using differ from include ?

p.s. Personally I hate classpath and its ilk. It is good to have some minimal hierarchy options, but it is better to use it as little as possible.

In this case I would go the TLS way. The RND() state is per thread.

Still there is a penalty to that too.