Bug fix plus a few TCLib support items
https://sourceforge.net/projects/bc9basic/files/bc9Basic/bc9_9271.zip/download

I discovered you no longer get a command prompt using shift/right click from File Explorer with the Windows 10 1703 update. You get a PowerShell item instead.
Looks like a real PIA registry hack to get it back!!!
Of course cmd.exe is still there just not accessible from File Explorer.

James

> Anyone know where files can be forun to use GLEW and GUT in Powerbasic?

I don't think that nobody has translated the GLEW headers.

Regarding GLUT, I translated the headers for freeGlut several years ago.

See: https://forum.powerbasic.com/forum/jose-s-corner/downloads/51414-freeglut-2-8-0-headers

Quotethat shows all the functions in the code tab presently open

UltraEdit 

Hi,

Thank you very much for all your hard work!

Ron

Hi,

The answer is that the declarations can be found in Jose's new WINAPI_III_107 headers in the file "GLEXT.INC.

In case anyone needs to know.

Thanks,

Ron

So the route to take in my opinion is to not worry too much about which IDE or build system you use.  Learning C++ is tough, and I'd concentrate on that, which can be done with any compiler/IDE.  After you get a little confidence, experiment with various compilers and IDEs. 

Notepad++ is a decent lightweight code editor.  I use that a lot with my TCLib (alteernate to C Runtime).  The big trouble I have with every code editor except Visual Studio is that none of them are 100% perfect in providing a 'function management pane/window' that shows all the functions in the code tab presently open.  I become furious over that.  Furious to the point of being on the verge of writing my own editor!  I don't know why they can't write good enough code to do that.   

For just getting started I'd recommend a package with the compiler and IDE together.  Code::Blocks can be setup to build with any compiler, but you've got to struggle through a lot of setup screens to get it all working.  That's why I'd recommend getting the download with the build system (compiler) and IDE integrated.  That way, it ought to work right 'out of the box', so to speak. 

I'm not a fan of Visual Studio but Microsoft's compiler is my main compiler right now (for a good many years GCC from MinGW was my main C++ build system, but it is too bloated to suit me what with all the stuff necessary for compliance with the changes they've made to C++ over the course of the past five years or so).

When I do use an IDE I use the IDE from my Visual Studio 2008 edition.  My main compiler is VC15 from the Visual Studio 2008 edition.  Most C++ work I do now is with my own build libraries which are alternates to the ones supplied by Microsoft.  In that way I can produce binaries as small or smaller than those produced by PowerBASIC and in 64 bit. 

It seems the trend in C++ for a good many years now is to somehow or other morph it into C#.  So you'll have to decide which direction you want to go in with your learning.  For myself I seem to use the high level features of the language sparingly, as I suppose I'm still greatly affected by my early C roots. 

A new standalone 64-bit version, and extra transcriptions are available here:

http://www.objreader.com/index.php?topic=95.0

Visual Studio, has a built-in debugger, intellisense, and all extra goodies you can expect from a modern compiler.

Chris,
  Use any editor you want and compile with my batch files from one of the bc9Basic packages.
There are batch files for VC, TDM (http://tdm-gcc.tdragon.net/), NUWEN distro (https://nuwen.net/mingw.html)

James