Well you could say in the license something about maintaining QBASIC compatibility

by qbguy (no login)

For example, you could say something like, "if a modification breaks QBASIC compatiblity, then the new package with modification shall not be called QB64"

Or you could disallow all modification or distribution for a fee but make the source available "for reference only".

I think that would mean that it would not allow QB64 code to be mixed with GPLed code, though.

Posted on May 16, 2008, 6:02 PM
from IP address 75.16.123.88

Respond to this message   

Return to Index


Response TitleAuthor and Date
Re: Well you could say in the license something about maintaining QBASIC compatibility on May 22
 You don't need no freaking Liscense! on May 23
  Lawsuits are strickly follow the money but open source makes it volnuerable to abuse. on May 23
   Making it open source has the exact advantage that you stated - contributions by othersrpgfan3233 on May 23
    Look at what happened to FB on May 23
   i address that (common) myth in something i posted recentlymennonite on May 23
    What trademark? There is no trademark... on May 23
     at least offer a serious reply so i know what one looks likemennonite on May 23
      My view on IP and open sourceroy on May 24
     Cost of filing a trademarkqbguy on May 24
  * Ah, but you forget - FB borrows things from QB _AND_ VB, and it is open source! ;-)rpgfan3233 on May 23
   RPG is one of my favorite people to discuss topics with... on May 23
    * Hmm... You raise some good points that I can't possibly argue against. Great reasoning!rpgfan3233 on May 23
    you're wrong about who can help galleonmennonite on May 24