#Purebasic xml code#
#Purebasic xml license#
#Purebasic xml windows#

For some libraries, there are code hacks to get the version by querying the library itself. Unfortunately, PureBASIC documentation doesn’t mention which version of the libraries is in use. Here is an incomplete list of the third libraries used by PureLibraries ( PB 5.50). Here is an incomplete list of PureLibraries ( PB 5.50) along with the third components used by them.

#Purebasic xml license#

The presence of these third party components/libraries is the resason why you have to include a license file with your compiled applications. PureBASIC’s Database library uses SQLite and PostgreSQL libraries PB’s Scintilla library and gadget use Scintilla library PureBASIC’s XML library uses the expat XML parser and so on. For example, the Regular Expression PureLibrary relies on the PCRE (Perl-Compatible Regular Expressions) library – a famous open source library for regular expressions, employed in many softwares. PureBASIC uses third party open source libraries to implement its PureLibraries. By exploring each entry you can learn which commands and functionalities are offered by these PureLibraries. Which means that Joystick, Keyboard and Mouse are the actual names of PureLibraries. For example, you’ll find under “2D Games & Multimedia Libraries”: The single entries under these sections correspond to PureBASIC’s PureLibraries. PureBASIC’s documentation groups PureLibraries under three main “libraries” sections: The same applies to PureBASIC’s documentation. Usually, unless the context demands disambiguation, “PureLibraries” are simply referred to as “PureBASIC libraries,” “PureLibs” or just “libraries” – when you read on the forums a discussion about the Scintilla library, it is usually implied to refer to the Scintilla PureLibrary. Scintilla PureLibrary vs original Scintilla C++ library).

It also avoids confusion with the original third party libraries they are built on top of (eg. FileSystem PureLibrary vs native OS FileSystem libraries). The term “PureLibraries” is a convenience to avoid confusion and conflicts with system libraries (eg. The users doesn’t need to place any C-style “include” directives: the compiler will automatically detect the required components based on the commands found in the source code. Inclusion (linking) of PureLibraries in the final compiled binary file is handled transparently by PureBASIC.

#Purebasic xml windows#

if your program uses regular expressions, the compiler will include the RegularExpression PureLibrary into the output binary file by statically linking it – with a few exceptions, like Scintilla for Windows which uses a dynamic libary (a DLL) instead of a static one. The required PureLibraries are included (linked) in the final compiled application – eg. For each PureLibrary mentioned in the documentation there is a correspondingly named file in the PureLibraries folder. PureLibraries are stored in the PureLibraries subfolder of PureBASIC installation path. RegularExpression PureLibrary handles regular expressions, List handles linked-lists, FileSystem handles file system operation, and so on. The term “PureLibraries” refers to PureBASIC’s built-in libraries that provide commands and functionalities in specific areas – eg.