Author |
Topic: Compiling LB source code (Read 643 times) |
|
net2014
New Member
member is offline
Posts: 37
|
 |
Compiling LB source code
« Thread started on: Mar 20th, 2015, 2:16pm » |
|
Just a few thoughts, useless as they may be!
Apologies if this is mentioned in the LBB docs somewhere, but I have failed to find an answer.
I read that LBB will not open & run TKNs unless the original username/password is known. Meaning that the file must have been generated by a licensed copy of LB. Thereby lies a problem in that source code written in a trial copy of LB can be compiled to an exe with LBB.
I'm just thinking, would it be possible to require a LB registered username/password before LBB would compile? That would ensure that LBB would only be of use to LBs registered customers, such that trial versions of LB4 operate in the same way in both LB4 and LBB IDEs. That would eliminate 'loss of business' claims, even expanding LB sales, as so many people seem to ask for single exe generation. Also maybe redesign LBB to just be a compiler, i.e. eliminate its IDE and just input the LB source code file.
If that were possible I would be prepared to buy LBB (I'd buy it anyway) instead of it being free. (I already have registered copy of LB4).
|
|
 Logged
|
|
|
|
Mystic
Junior Member
member is offline
Gender: 
Posts: 53
|
|
Re: Compiling LB source code
« Reply #1 on: Mar 20th, 2015, 3:41pm » |
|
I brought up something similar to this behind the curtain.
If the features of LBB that are seemingly a threat to LB's registered community can be made to only work on registered copies of LB, that would help some of the issues.
The overlying issue of "promoting" LBB on the LB board though would remain.
The stance on the LB forums, and it's sort of justified, is that their forums are for LB issues, not a place to discuss other programs.
It's a precarious balance...
|
|
Logged
|
- Rick
|
|
|
Richard Russell
Administrator
member is offline
Posts: 1348
|
|
Re: Compiling LB source code
« Reply #2 on: Mar 21st, 2015, 10:34am » |
|
on Mar 20th, 2015, 2:16pm, net2014 wrote:| I'm just thinking, would it be possible to require a LB registered username/password before LBB would compile? That would ensure that LBB would only be of use to LBs registered customers |
|
That would be exactly like saying you cannot use GCC (free) to compile your C programs without first purchasing Microsoft's Visual C. Or that you cannot run a BBC BASIC program using Brandy (free) without first purchasing a copy of BBC BASIC for Windows! A non-starter as far as I'm concerned.
For LBB users it should be a matter of conscience whether to purchase LB 4.04, not compulsion. For the record I didn't pay for my copy: Carl and I agreed a swap whereby he gave me LB free and I gave him BB4W free. 
Quote:| Also maybe redesign LBB to just be a compiler, i.e. eliminate its IDE and just input the LB source code file. |
|
Which would imply there being no LBB debugger, and indeed not having even the most basic ability to highlight the problem statement if an error occurs during compilation. That would make debugging any program which incorporated LBB-specific code (extensions or bug-fixes) difficult and time consuming.
If Carl is concerned about the 'competition' from LBB then the solution is for him to improve LB4 (and/or release LB5) so that he has a more attractive product offering. That's how it works with every other programming language. But to be fair I'm not aware of Carl ever having expressed such a concern himself; at the very start he said "LBB is a legitimate artifact. Feel free to use it if it suits your needs".
Some LB users have had no previous experience of there being multiple implementations of a programming language, even though that is the norm for many other languages (I think in the case of BBC BASIC there have been something like six independent implementations to date!). They understandably may have difficulty getting their heads around the concept, but that is not my problem!
Richard.
|
|
|
|
|
