> He told me that he offered the compiler to "PB.inc" to have it sold as Powerbasic x64 but they were nopt intertested.

How are they going to sell a converter that uses an alpha compiler as the backend?

The first link is working. I have modified the 2nd link.

Hello Brian

hows' going?  how's the progress of your PB 64bit compiler?

anything in English ?  as i can't read German

how good is Purebasic?

Some Good NEWS at last .... Brian Alvarez is the savior for PB  as without a real PB 64 bit compiler how could PB inc sell their stuff?

similar to MS which takes over other products to kill it? 

There are rumors that Brian is really far with a x64 Compiler that supports Power Basic like Syntax.
He told me that he offered the compiler to "PB.inc" to have it sold as Powerbasic x64 but they were nopt intertested.
Maybe there will finally be an PB x64 like compiler?

PS: I could not yet test it.

This is a PDF File of a book that can help with Purebasic.

Purebasic Reference Manual 4.5

Download Purebasic here: Purebasic Download

Quote from: José Roca on July 27, 2018, 04:11:32 AM
Examples and templates are available if you install the WinFBE editor.

They are also available separately in my GitHub repository:
https://github.com/JoseRoca/WinFBX

On-line help for the WinFBX framework:
http://www.jose.it-berater.org/WinFBX/WinFBX.html

The WinFBX framework provides almost all the PowerBasic functionality missing in FreeBasic and much more. Everything compiles in both 32 and 64 bit without any changes and everything is unicode aware.

The first Link seems not to work anymore?

Quote
In my experience, not knowing how to control the IDE "starship" is a big part of the problem, so I always prefer to walk through these complications and sort them out. I appreciate the help!

For a long time starting back in the 1980s IDEs were a big help.  But they just kept adding features and becoming more and more complicated.  Visual Studio is the classic example of this.   I believe things have reached the point where they are now an impediment to someone just starting out at programming.  I'm not saying they aren't useful, its just that for folks that started out programming a long time ago and 'grew up' with them, they are more understandable.  Take your situation with character sets.  The particular setting that caused your program to default to wide character builds is fairly well hidden.

Quote from: James C. Fuller on August 09, 2019, 11:49:35 AM
I emailed Fred and here is his response:


For some reason I can't seem to log in to Jose's Forum.  I seem to recall this happening before.  In any case, I finally found the post up in the main section of Jose's board, and it looks to me like the pre-defined symbol by Microsoft is causing the fellow's program to run as a UNICODE build as opposed to an ansi build, and that's why he is confused.  You are certainly aware of that issue, aren't you?  The issue is that when using Visual Studio  all builds are UNICODE unless one goes into the 'General Properties' window of the project, where one finds a dropdown where one can select ansi, wide character etc.  It defaults to wide character.  Since you and I work from batch files or command line, we don't have to deal with that.  Perhaps if you can log in you might mention that to the fellow?  He's worried about it.

That makes sense. I will examine it and I imagine it will fix it.

Thanks so much for the help, and also to Frederick Harris: huge thanks! for that tutorial "ProgEx37" tutorial 'series.' Slowly making progress in that, and it is exactly what I needed to move forward as a developer!

Based on the ~35k views of the thread, I am not alone! 

ADDIT: Whoo hoo! FIXED! 
iLen = 13;
sizeof(szBuffer) = 14
In my experience, not knowing how to control the IDE "starship" is a big part of the problem, so I always prefer to walk through these complications and sort them out. I appreciate the help!