PureBasic Forums - English

thanks.

jbernard13 wrote:Please fred

with when the final version?

just after beta17 !

jbernard13 wrote:Please fred

with when the final version?

Don't be afraid.
Moreover, Do you think final version is bug free? haha! mmmm

may be final version = when the new docs will be ready ?

Thanks also,

any roadmap which changes could be seen in the near future?

Are there any main areas where the most work will be done, like...

... bug fixes (of course)
... integer function enhancements (like abs, mod, div, scale, pred, succ, inc, dec,...)
... other things (do while / loop until, QuickSin, QuickCos, Floor, Ceil,...)
... ide enhancements (more speed, bold names, better autocomplete, autocase for variables, alternative shortcut settings,...)
... directory structure for the PureBasic package (example sources divided in categories, etc.)

Michael

Is it possible that between the v4 beta 1 and the v4 beta 3, the execution speed of programs under Windows GUI increased again?
Because I start to hallucinate...

This would be too risky between betas. It may have been a bugfix.

Hi,

Added GetDatabaseDouble()/Quad(), any tests on these commands are welcome

all runs fine now.

But, in tests I've noted that GetDatabase[Long/Float/Double/Quad]() are equivalent to GetDatabaseString() combined with (followed by) Val/ValF/ValD/ValQ().
Is correct this?.

JOAQUIN

jqn wrote:Hi,

Added GetDatabaseDouble()/Quad(), any tests on these commands are welcome

all runs fine now.

But, in tests I've noted that GetDatabase[Long/Float/Double/Quad]() are equivalent to GetDatabaseString() combined with (followed by) Val/ValF/ValD/ValQ().
Is correct this?.

Yes, it's correct, as you can retrieve anything in string form. Tough, it's advised to use the specialised function for speed and may be for compatibility, as it's not granted than a database stores floating number in exactly the same format than another (dot instead of coma, use of exponent character etc.).

coma wrote:may be final version = when the new docs will be ready ?

That's all I'm waiting for before I start to do more than play.

Hello Fred,

The BETA 3 has a lot of problems with memory accesses.
Often, I get a "invalid memory access"-errormessage if I write two or more allocatememories in next to another.
And the same problem is sometimes, if I call PeekS with a stringpointer more than one times in next to another.
And in other sources, the same codes works perfectly.

Without some code to reproduce the error, there is not much we can do.

I get same memory access problem.

It seems to be random ?! But if you remove the offending line, or comment it, the message appears at the next line above!!!

It's obviously a programming error, further down in the code.... but the IDE/Compiler isn't showing the problem!

If I get it with a small example I'll post the code

Trond got rid of his memory access errors by installing the beta into a newly created directory.

Mine is a fresh install too, just the PBOSL library added.

Is there an example of using Unicode?
It crashes when specifying it with ProjectOptions. Is this normal?