Wishlist for PureBasic v4.0

[A.I]

I would like to see register variables like in C++

Register variables are much faster than normal variables because they use one processor memory slot and lack the need to transfer between main memory. Using register variables as loop counter can speed the execution up to 15%.

Also, as mentioned before, boolean variables would be good, too.

[DriakTravo]

there is no collision between zoomed 3d sprites... or is there

[ricardo]

Yeah! but we must demand Fred to do PureBasic to make things for us

he he

Then must add:

DoMyGame()

and

DoItsFast()

commands.

I hope he also add something similar for applications:

Code: Select all

DoSomeAwesomeAppForMe(#true)
DoItNow(#true)
ImLazyToday(#true)

I have some flags in mind for this ones :roll:

[Psychophanta]

5 more things to add (fixes and addings i requested), hope not forget
Strongly needed this:
Operands' priorities
Triple screen buffer, and ...
Discovered a bug in compiler
For-To small bug...

[Lebostein]

And don't forget the coupled initialisation and allocation of variables:

Code: Select all

Global test.f = 1.23456
Static check.l = 1000, test.l = 20
Deftype.b x=1, y=2, z=3

[blueznl]

well, i almost forgot about it, but the 'when is something an int and when not' issue is still giving me a headache!

viewtopic.php?t=14269

[Dare2]

Absolutely tops on my wishlist for version 4 is, for windows at least:

• To attempt to find and flush all the reported bugs.
  To stress and crash-test PB extensively.
  To get some high powered users attempt to do the same.

If windows gets fixed the majority of users get a stable release. And many linux/macos bugs will get fixed (or die unbirthed) at the same time.


Second and extremely high is for PB to support some "modern" (1980 onwards) data types.


Last on my wishlist is for a new OS version or a new Editor or OOP or anything else that detracts from or dilutes the effort available for fixing and improving the core product.

[Psychophanta]

Don't know if it is in this thread. But if so i remember it:

- Optional parameters for functions
- Allow more than one dimension for fields in structures
- Scientific notation for values (for example 1.624e-7)

[Rescator]

Len() extended to support optional max lenght argument,
and if not allready so, make Len() internaly limit to max
PB string length if no max length is given by the programmer.

And a matching LenS() for length checking similar in the way of PeekS()
(seeing as Win32 api lstrlen() is "unsafe" and Len() can't be used on non PB strings)

[Brice Manuel]

Is there any official word on what will definitely be in 4.0?

[okasvi]

Is there any official word on what will definitely be in 4.0?

i guess Fred isnt stupid enough to make such list... it would kill the chance to use "i didnt promise it" after v4 release

[GeoTrail]

Well, there have been a few hints around the forum

[Shannara]

i guess Fred isnt stupid enough to make such list... it would kill the chance to use "i didnt promise it" after v4 release

Well, since good, smart programmers make lists ... At least internally.

Fred (and/or) PB team did mention a few things that are going to be in 4.0. Such as (finally) the exact same featureset across all OSes (I dont know how they will do it for Amiga version).

[Nik]

Anotehr thing taht would be cool is direktX 9 and a faster Point and Plot
bye

[freak]

Fred (and/or) PB team did mention a few things that are going to be in 4.0. Such as (finally) the exact same featureset across all OSes (I dont know how they will do it for Amiga version).

Who said that ?