Contributions do not have to be restricted to programming code There are many ways you can contribute to the development of this project and some do not require Git. PureBasic is an open-source project that welcomes user contributions. With all the options available, PureBasic is an ideal application for beginners and advanced users. Below are the names of those who have contributed to the assets within this repository. The content included in this repository comprises Copyright Fantaisie Software. The principal advantages of PureBasic are portability, the development of very fast and efficiently native 32-bit or 64-bit executables, as well as the most important thing, the straightforward BASIC language syntax. PureBasic is a modern regular programming language. Last but not least, the third thing you should be aware of PureBasic is that it’s not free.
Then, the second thing you must be aware of regarding PureBasic is the fact that it’s speedy reliable, user-friendly, loaded with features that experienced programmers are sure to appreciate, and it’s available across multiple platforms. more to the fact, it’s a programming language built on the established BASIC rules. The primary thing to be aware of regarding PureBasic is that it’s a programming language. Fixed issue with Structure Pointers in Procedure Parameters, transforms to Pointers now.Today, PureBasic has developed this Programming Languages app for PC.Fixed issue with Structured List/Array/Map in Procedure Parameters.Fixed issue where a *pointer would cause further Procedure Parameters to lose their types.Stops when encountering the statement seperator “ :” or comment “ ” operators.įixed issue where array arguments would still have impossible structures.Īdded support for structured List/Array/Map arguments with some conditions.Īdded support for all basic types when used with List/Array/Map arguments.įixed issue where a *pointer.structure had no default parameter.įixed issue with a string as custom parameter, it was not escaped.
Fixed issue with a space in the directory/file path of source file.Improved ProcedureDLL and ProcedureCDLL with appropriate DeclareDLL and DeclareCDLL. Now naming version after PureBasic’s version when possible.Īdded support for Runtime procedure statements.Īdded support for case independent keyword detection. Treats a colon seperator as a new line to allow multiple declarations on a single line.Īdded support for module header generation (requires additional files and include lines in source code). Now supports any amount of spaces in front of a procedure. Improved parsing engine to comply with latest PureBasic syntax. Using compiler directives to remove the need of multiple files for modules.Fixed case where the compiler directives failed when a module is declared above global procedures.
Now ignoring content between Macro / EndMacro statements.Fixed a comment after EndProcedure / EndModule / EndMacro skipping the next procedure declaration.Added SpiderBasic header generation support.Fixed double colon operator inside procedure arguments OnVstMain(*Effect.Vst2::AEffect).Fixed runtime keyword not getting detected properly.Removed the timestamp and version info in generated headers to make them git-friendly.I hope you too will enjoy the new freedom thanks to this little tool! Changes
Purebasic source files generator#
That’s the reason I required an automatic header generator for PureBasic. PureBasic is a great language but I was always annoyed about the fact I could never choose where I would locate my Procedures, if I wished to use a Procedure somewhere I would have to move it above of the Procedure that was going to call it, the Declare statement allows to tell the compiler specific Procedures are going to exist and to find them but writing them over and over, fixing arguments is not only a pain but makes your source look like a mess. This does not apply when using basic types and is a limitation of PureBasic. IncludeFile #PB_Compiler_File + "i" - PBHGENĪt the moment if you wish to have a procedure with structured List/Array/Map arguments, you will have to put that procedure above the code where you call it from. To use automatic header generation also in modules use: Module MyModule
0 kommentar(er)
