Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index


On 06/28/2017 12:12 PM, Pierre Lepage wrote:
The solution brings a lot of hassle for customers of the LibreOffice suite whose work relies on the performance of StarBasic macros written by third parties. Macros containing code in error by the absence of a closing parenthesis suddenly cease to function. For this reason, the patch has not been released. Here I want to explore a transitional solution by getting your feedback first. This is to include in StarBasic options dialog accessible to the client a "StarBasic Pragma Strict" option (checkbox) by which the client consciously activates the solution (the patch that has not been published!). This check box would be available for a few years with a warning to prompt programmers and customers to require their programmer to correct their default code on the closing parenthesis.

Another option might be to have some form of such a pragma in individual BASIC source files, instead of as an IDE option. (And have the pragma enabled in the "REM ***** BASIC ****** Sub Main ... End Sub" boilerplate that is automatically present in a fresh source file.) That way, users could enable it for their own, new code, while (implicitly) keeping it off for non-conforming old, 3rd-party code.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.