home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.ibm.pc.programmer:423 comp.os.msdos.programmer:9361 comp.lang.c++:13660
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!swrinde!network.ucsd.edu!cogsci!crl!hartung
- From: hartung@crl.ucsd.edu (Jeff Hartung)
- Newsgroups: comp.sys.ibm.pc.programmer,comp.os.msdos.programmer,comp.lang.c++
- Subject: Re: Why no source control in Borland
- Message-ID: <1601@cogsci.ucsd.EDU>
- Date: 15 Sep 92 03:14:59 GMT
- References: <1992Sep10.052148.10777@monu6.cc.monash.edu.au>
- Sender: news@cogsci.ucsd.EDU
- Organization: University of California, San Diego
- Lines: 18
-
- In article <1992Sep10.052148.10777@monu6.cc.monash.edu.au> parry@yoyo.cc.monash.edu.au (Tom J Parry) writes:
- >It strikes me as starnge that given the current size of the Borland C++ 3.1
- >compiler package, that there is no source control system.
- >
- >Currently, the full package has every conceivable feature you could want
- >except source control and OS/2 support [oops, wrong winge]. The only
-
- And 32-bit code generation, and a DOS extender (32-bit would be nice, 16-bit
- would be OK, the Phar Lap "Lite" they included with the upgrade was a table
- scrap, and a shameless example of commercial crippleware), and probably a few
- other things I can't think of right now.
-
-
- --
- --Jeff Hartung--
- Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
- InterNet - hartung@crl.ucsd.edu BITNET - hartung@ucsd
- UUCP - ucsd!crl.ucsd.edu!hartung
-