To everyone that has replied...
Sorry, I was off line moving house for a couple of weeks.
OOP: From what I know and my experience with QBASIC4.5 was that it had basic object constructs. But we don't have to use OOP if we don't desire to.
Most OOP is built upon Imperative Procedural Orientation and OOP is more of a level up (I am not and engineer so forgive me if I have the terminology off by 1). FB Back end is C which is not natively OOP. It can be done in C with a lot of boilerplate coding, but that's why they created C++
Most of what I do, even in Python 3 is from an "Imperative Procedural Orientation" but all orientations can blend a little in practice.
Thank you all for the reply's and suggestions
At present I have ( with some correspondence with ray and sorting out some hick ups) raylib V4.0.0 and raygui V3.1.x combined and compiling as a single dll for windows ( I am yet to do the Linux Shared Objects ). I can also add the current source version of physac but am leaving it to the side for now. Ray has told me that the headers in .\src\extras are dated and deprecated and will be removed from the raylib V4.2.0 release coming up soon. They (easings.h, rmem.h, gui_textbox_extended.h) will need to be updated if someone feels they have a need for them. Don't use the headers in "raylib\src\extras" as they are old versions, this includes .\extras\raygui.h. You will need to get raygui and physac current source (Not release version) and add it to the raylib source to compile all as a single dll. (There is a binary constant in raylib that I recommend changing to a HEX constant for C-99 compliance)
I have converted (Untested atm) raylib.h to raylib.bi including comments and some of the suggested fixes from my questions in the forum. I will do the other headers as time permits. I should end up with Raylib v4.0.0 and raygui V3.1 shared library dll/so as well as the header conversions rlibs.bi.
I have to double check with ray on the licensing for shipping the pre-compiled shared library but I think it will be OK.
I will compile the the shared library in winlibs GCC 9.3.0 (SJLJ exceptions) + MinGW-w64 7.0.0 (release 2) the same as FB if I run into backward compatibility issues with the current GCC version (I'm am uncertain how to roll back to and older GCC dev tools in Linux, so something I'll have to learn if needed.) I am also looking at creating the OpenGL3.3 version as well as the OpenGL_2.1 version as I get my students to use VirtualBox for much of the examples (VirtualBox can only do up to OpenGL v2.1).
I will look at the newer raylib V4.2 but it will depend heavily upon when the Python 3 bindings get done. <- I can't do all of it, Man has to sleep sometime lol.