home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.arch:11842 comp.sys.dec:6580 comp.sys.sgi:18256 comp.sys.hp:14295
- Newsgroups: comp.arch,comp.sys.dec,comp.sys.sgi,comp.sys.hp
- Path: sparky!uunet!psinntp!ficc!peter
- From: peter@ferranti.com (peter da silva)
- Subject: Re: Comparison of Alpha, MIPS and PA-RISC-II wanted
- Message-ID: <id.7P0W.47G@ferranti.com>
- Organization: Xenix Support, FICC
- References: <BzGn32.37C@dscomsa.desy.de> <1gt111INNt3b@hpscit.sc.hp.com> <1992Dec19.012355.26665@ll.mit.edu>
- Date: Tue, 22 Dec 1992 00:01:16 GMT
- Lines: 23
-
- In article <1992Dec19.012355.26665@ll.mit.edu> ejon@ll.mit.edu (Eric Jones) writes:
- > But isn't that exactly his point? Sure you can write an ISAM file
- > structure using fseek (and if you're REALLY smart, you might even
- > write an efficient one), but then how's anyone else going to use
- > your files?
-
- Well, you have two choices:
-
- 1. You bind the ISAM interface into your application and
- ship binaries. You don't document it, and hope that you
- sell enough packages that you have a cpative market for
- the next 10 years.
-
- 2. You document the ISAM interface, ship libraries or source
- to the library, and provide shell commands to hook your
- package into the rest of UNIX.
-
- When Oracle does all three parts of (2) I'll quit badmouthing them.
- --
- Peter da Silva `-_-'
- Ferranti International Controls Corporation 'U`
- Sugar Land, TX 77487-5012 USA
- +1 713 274 5180 "Zure otsoa besarkatu al duzu gaur?"
-