home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.arch:11787 comp.sys.dec:6556 comp.sys.sgi:18218 comp.sys.hp:14258
- Newsgroups: comp.arch,comp.sys.dec,comp.sys.sgi,comp.sys.hp
- Path: sparky!uunet!usc!sdd.hp.com!ux1.cso.uiuc.edu!news.cso.uiuc.edu!crux.scs.uiuc.edu!mcdonald
- From: mcdonald@aries.scs.uiuc.edu (J. D. McDonald)
- Subject: Re: Comparison of Alpha, MIPS and PA-RISC-II wanted
- References: <BzGn32.37C@dscomsa.desy.de> <1gt111INNt3b@hpscit.sc.hp.com> <1992Dec19.012355.26665@ll.mit.edu>
- Message-ID: <mcdonald.624@aries.scs.uiuc.edu>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: UIUC SCS
- Date: Sat, 19 Dec 1992 16:55:40 GMT
- Lines: 33
-
- 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?
-
- By RTFM of course!!
-
- Consider the converse:
-
- You write a file using the oddball formats of VMS.
-
- You send it to someone else.
-
- He can't read it because it's oddball.
-
- How does he read it??
- The only way is to RTFM and here the FM refers to the 1600 pounds
- of VMS stuff or Disk 47 of the 677 volume CD manuals.
-
- The Unix way has proven to be the best way; its one of the biggest
- reasons VMS is a current sales disaster.
-
- The doc for your own ISAM is maybe 2 pages long.
-
- Also consider this: if you write that file on VMS using the VMS
- proprietary method, you can't read it on any other machine using
- the same code. If you did it the C/Unix way, you code will run as-is
- on any machine using standard C. Even VMS.
-
- Doug McDonald
-