Xref: utzoo comp.lang.c++:13350 gnu.misc.discuss:3045 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!uflorida!screamer!tscs!tct!chip From: chip@tct.com (Chip Salzenberg) Newsgroups: comp.lang.c++,gnu.misc.discuss Subject: Re: 64 bit architectures and C/C++ Message-ID: <28297EA6.69DE@tct.com> Date: 9 May 91 16:53:58 GMT References: <2826D9E7.407F@tct.com> <1991May8.150058.29893@ccad.uiowa.edu> Followup-To: gnu.misc.discuss Organization: Teltronics/TCT, Sarasota, FL Lines: 25 According to cadsi@ccad.uiowa.edu (CADSI): >From article <2826D9E7.407F@tct.com>, by chip@tct.com (Chip Salzenberg): >> G++ 1.39 ... is free, too. > >BUT, you're not supposed to make money on what you compile with G++, >right? I thought I read that before. Wrong. You can make money off a program compiled with G++. In fact, we have our very first C++ project in beta test right now, and it's all compiled with G++. The trick is that you can't distribute a program containing GNU code (like the GNU C++ library "libg++") unless you also distribute source code to the whole program linked therewith. We avoid this problem by avoiding libg++. A new version of the GNU public license may soon make a special case of libraries, by requiring distribution of library source code, but not the source code of the program(s) linked with the library. Stay tuned in gcc.announce and gnu.misc.discuss. -- Brand X Industries Sentient and Semi-Sentient Being Resources Department: Because Sometimes, "Human" Just Isn't Good Enough [tm] Chip Salzenberg ,