PureBasic 6.20 is out !

[Fred]

Will portable installs still support userlibs in the existing parent folder?

Sure

[marc_256]

Thanks Fred and team for the upgrade of PB 6.20.B1
Special thanks to Pf Shadoko for the OGRE 3D / 14.3 version upgrade ...

Me to, after a somber period I needed some good news ...

Marc

[le_magn]

Thank you very much Fred and the whole team for this great update

[idle]

Great that we can make libs now and TLS support both are great additions!

[PBJim]

- Added: TLS support for Network library (Thanks Idle for the tips) !

Thank you for the good work, PB team.

Does the provision of TLS support allow a PB client and server to communicate through TLS?

[pf shadoko]

@marc_256

don't thank me for the 3D, it was Fred who did most of it

but you should thank me for the Libs
because I'm the one who's been churning Fred for a very long time to get him to add this feature.

[threedslider]

Awesome !

Thanks a lot to all team !

I was working my project to Vulkan but don't finish xD and my 3d modeling too

Right now I am in my job as internship for dev web in Ruby programming.

Once come back I will resume it

@Fred : What is your experience of upgrading to Ogre 14.x ? Just curious cause you have done a fantastic job

Happy coding to all !

[User_Russian]

- All functions are compiled in the same object, which means the library will always includes all the functions in the final executable.

GCC has options -ffunction-sections and -fdata-sections https://gcc.gnu.org/onlinedocs/gcc/Opti ... n-sections

Place each function or data item into its own section in the output file if the target supports arbitrary sections. The name of the function or the name of the data item determines the section’s name in the output file.

Use these options on systems where the linker can perform optimizations to improve locality of reference in the instruction space. Most systems using the ELF object format have linkers with such optimizations. On AIX, the linker rearranges sections (CSECTs) based on the call graph. The performance impact varies.

Together with a linker garbage collection (linker --gc-sections option) these options may lead to smaller statically-linked executables (after stripping).

On ELF/DWARF systems these options do not degenerate the quality of the debug information. There could be issues with other object files/debug info formats.

Only use these options when there are significant benefits from doing so. When you specify these options, the assembler and linker create larger object and executable files and are also slower. These options affect code generation. They prevent optimizations by the compiler and assembler using relative locations inside a translation unit since the locations are unknown until link time. An example of such an optimization is relaxing calls to short call instructions.

But support from the linker is needed (parameter --gc-sections).

[idle]

- Added: TLS support for Network library (Thanks Idle for the tips) !

Thank you for the good work, PB team.

Does the provision of TLS support allow a PB client and server to communicate through TLS?

Yes it will, I haven't got time to test it today but if Fred followed the code I used in atomic web server it should work transparently to the users and also handle multiple certs

[Fred]

I will post a sample tomorrow for the TLS stuff, I completely forgot !

[jacdelad]

Woohoo! Time to buy a second licence.

[skywalk]

- All functions are compiled in the same object, which means the library will always includes all the functions in the final executable.

GCC has options -ffunction-sections and -fdata-sections

Given the slow downs and complexity, I would prefer an own PB tool code to strip functions prior to compile.

[J. Baker]

Very nice, Fred! Thanks!

[Denis]

Pas mal...

[Bisonte]

...native PureLibrary creation directly using PureBasic !...

The hobby developer's wet dream

It was really time to buy a new license