PureBasic Forum

Thanks but as per other suggestions mentioned, even re-install is probably not worth the hassle.

Maybe it's an error that jaPBe can pick up and fix when it's creating the .exe.

If PB wouldn't even compile, I would look into it more.

This is the frustrating thing - what is different between compiling and creating the .exe ??

Neil

I did an experiment with the posted source thinking that maybe JapBe was using a file format slightly incompatible with PB but that looks like a red herring, though you might want to ensure the source has nothing strange hidden by saving it with a plain text editor.

It is important to get the compiler settings right when creating an executable - if for example you have Unicode set in JapBe, then it should also be selected in PB.

When you Compile and Run, PB makes a temporary exe file of course, so it is totally weird that you can do that with the original code but not even that with my simplified version.

I also note that you said "Note that jaPBe will create the .exe ok so nothing to do with virus checker.". That seems a reasonable assumption, but the heuristic testing by AV is akin to astrology - i.e. it is completely unpredictable. So, certainly you should turn-off AV and see if it is messing things up for PB. A point there is file content - the larger the files, the more likely the AV will intercept them. Also, the file names come under scrutiny by AV apps. When I was working on a plugin for a CAD-CAM program called VX, my AV app really really didn't like it. It just so happens that as well as being a CAD-CAM program, VX is a dangerous nerve gas! Not sure what the developers of the AV were thinking, but it just goes to show that your AV can mess-up things that are completely innocent.

Edit: I assume you can copy-paste one of the bigger examples from the PB Help and create an exe from that?

...just noticed another common denominator - it only fails to compile on days that end with 'y'

what is the value of #PB_Compiler_EnumerationValue ?

zero

No, not really. Only if used before any enumeration.



Where ? When ? It depends.



In the first source posted in this thread, for example, the value is 2 first and then 18.