On Mon, Feb 27, 2012 at 12:05 AM, Tor Lillqvist <tml@iki.fi> wrote:
The whole discussion is non-technical. Removing Basic from the product
would not be a technical decision.
Maybe not, but *how* do do it (which is what I ask) is a technical question.
I would find it counter-productive to make the product less useful for
fear that, maybe, Apple would object to it.
Of course anybody is free to submit (once licensing issues have been
resolved, presumably) for App Store review an app based on our code
that *does* include BASIC functionality. It wold be fairly trivial to
replace the current small number of places where $(OS) == "IOS" is
checked with checks for $(DISABLE_INTERPRETERS) == "TRUE" or somesuch
instead.
from a technical point of view that would make more sens: separating
what you are doing (disable interpreter) vs why you are doing it
(ios).
The 'disabling' of interpreter is not technically inherent to IOS, nor
is it necessarily the only platform concerned by it.
(one could imagine someone taking advantage of that to create a 'safe'
version for another platform)
Norbert
Context
Re: Most elegant way to disable all BASIC functionality? · Andrew Douglas Pitonyak
Re: Most elegant way to disable all BASIC functionality? · Josh Heidenreich
Re: Most elegant way to disable all BASIC functionality? · Andrew Douglas Pitonyak
Re: Most elegant way to disable all BASIC functionality? · Eike Rathke
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.