NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/os/mswindo/apps/7568

Internet Message Format | 1993-01-27 | 1.7 KB

Xref: sparky comp.os.ms-windows.apps:7568 comp.os.ms-windows.misc:6594
Newsgroups: comp.windows.ms.programmer,comp.os.ms-windows.apps,comp.os.ms-windows.misc
Path: sparky!uunet!math.fu-berlin.de!ira.uka.de!scsing.switch.ch!news.univie.ac.at!paladin.american.edu!howland.reston.ans.net!usc!cs.utexas.edu!milano!cactus.org!wixer!reaper
From: [e-mail] (Keath Milligan)
Subject: Legal issues and DLLs
Message-ID: <[e-mail]>
Organization: Real/Time Communications
Date: Tue, 26 Jan 1993 17:35:19 GMT
Lines: 19

If you're writing code using Borland C++ 3.1 that uses custom controls, you
know you have to include BWCC.DLL with your programs distribution.  If you
choose to link your run time libraries dynamically, you'll have to include
other .DLLs, such as BC30RTL.DLL or OWL31.DLL as well.

I have spoken briefly with Borland Tech Support about 6 months ago regarding
the legalities of it and I was told that "Borland isn't out to 'get'
anybody" and that it's OK to redistribute these DLLs.  That's nice to know,
but I can't find that anywhere in writing in my Borland package.

I guess my question is:  Did the tech support guy really know what he was
talking about?  What are the terms of redistributing these libs?  I mean,
what if I want to put these in an embedded system product I'm selling to
lower-Slibovian sod farmers?
--
oooooo ooo o o  o            Keath Milligan            o  o  ooooo oooo oooooo
oooo oo ooo  o   o   Prometheus Light and Sound, Inc.   o   o  o ooooooooooooo
oooooooo o oo  o         Real/Time Communications        o    o o ooo oooooooo
oooooo oooo ooo  o  internet: [e-mail]  o   o  o ooo oo ooooooo