PureBasic Forums - English

It would be handy if there was a way of capturing the debug information as a string - that way end users could let us know that information if needed.

Bump, Bump!

I mean if you include /COMMENTED then the compile works and the executable is generated, without that parameter and the executable does not get generated and the compiler outputs loads of odd errors.

(I've edited "comment" in the code to make it clearer what I meant, sorry)

@Barry6 : I have similar issues, so I tried to track it down.

; build.pb
param$=#DQUOTE$+"ReportComplete.pb"+#DQUOTE$
param$+" /OUTPUT "+#DQUOTE$+"ReportComplete.exe"+#DQUOTE$
param$+" /ICON "+#DQUOTE$+"images\liveicon.ico"+#DQUOTE$
param$+" /OPTIMIZER"
param$+" /XP"
param$+" /USER"
param ...

I would do, but i I don't know how to get it moved to feature requests? Maybe an admin can do this?

Shame it hasn't been made native yet, coded it almost 15 years ago...

For Universal, I think they only need to be appended together. So two would need to be included and the universal generated from those two at compile time.

imho it should be added, I wouldn't use it that much - but I don't seen any harm as it' would be optional - it may even be trivial to add?

THEN could simply mean that the next CR is actually an ENDIF CR combo.

Well spotted, that works now - so not a bug (32/64 bit thing).

The debugger quit unexpectedly (both C and asm compilers).

The code that crashed the debugger was the verifyfile procedure in this, it works on previous versions:
(previously I'd tried it on the 32 bit version of PB - so maybe it's a 32/64 bit thing?)


; wintrust.pbi

;!Author: Gustavo J ...

The print library needs improving, hopefully that will happen sometime in pb6.xx...

This looks good. Now that PureBasic will soon be compiled in C, it may be easier to interface to?

That's a shame, maybe gcc could be modded to send back progress?

re alpha 3: My >60,000 line program compiles and works on both the asm and c compilers! :)

@Fred, it would be good if the 'compilation in progress' window let the programmer know what was going on after the initial 'Creating executable file' - as it can take some time, especially if optimisation ...

This is already reported in bugs, I'm sure @fred has sorted it for alpha 3.

The eventual output will be assembler, but via the C compiler. The C compiler may have had more time invested in optimising the output than regular PureBasic - so it could be faster.