PureBasic Forum

Are there any plans for the community to see a version of PB 6.0?

You belive the version number is the cool stuff?

Don't be petty, there is only 0.27 missing

A new major version indicates core changes and functionality in the core language (not just some function in libs) (except if you are chrome developer where version system exist like a calendar to you )

a new major version (6 ?) would indicate, for example, the anticipated linux ARM support, and many more.

Given the opportunity would like to suggest a change i was thinking of and i believe it would the ,still small, PB team.
Combining two more "discussions" taken place.
"PB long term cost" and "PB lack of frequent updates"

I Suggest to change structure of compiler and REMOVE a lot of functions and maybe entire libraries from core distribution transform them to "dll's" or "modules" of "pb dynamic linked libs" etc
The idea behind this is that libraries has expanded too much and need verification and improvement to every release.

AS we all know a dll is loaded and executed no matter the compiler version and or compiler itself (gcc / PB /Visual C, all "execute" stdcall dll's)
so moving "less important" libs to modules it require less work in updates but will KEEP the work already done creating these libs and adding useful functionality to PB, to future version with little or no "cost".

ADDITIONAL some new or more complicated libs maybe have some cost.

to name a few libs that will have practically no impact to change to "dll" are
AudioCD
Cipher
Mail
FTP

A few "future" libs that MAYBE have cost could possible be, for example, "ffmpeg player/decoder" etc

Note that my suggestion is NOT about removing function, i like functions and is one of the main reason PB has the power it has.
Just looking ways to remove overwhelm to Team.

I prefer those libs stay within the current automated testing so they are vetted with each compiler update.
Are you suggesting instead that calls to those libs will be changed to calls to frozen dll's within the automated tests?
That seems like a LOT of extra work.

as long as a "module" / "plugin" method is created will need no check, since a working module will be working ..
if you change the "dll" will need to check dll

this plugins/extension method exist in many languages for that exact reason

it will need some work once to change compiler structure to accept modular/extension system.
After this significant work will reduced, otherwise the working volume will continue to increase forever, while the team is not increased linear to that...

icesoft & saki: don't people have the right to ask to see what is new?

Sure you can ask.
But a look into the crystal ball or asking the oracle of Delphi is not very helpful.

They say : "Never do the bill without asking the cook"

New versions are not discussed publically. So, no.

Ive never seen any road map. Things happen or dont happen. Dev speed did slow down last years. Maybe its going up again. Lets hope and lets also hope fo some long due syntax additions. Lalala ;

A good option for 6.0 was version 5.5, where the Ascii support for Pb was removed. But whatever, there are more important things than the version number.

Well then just follow simple forum rules. If you have nothing contributing or positive to say then just shut up... No need to call me petty.

If the pandemic doesn't wipe us all out!