Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!ucsd!usc!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.unix.programmer Subject: Re: Why use U* over VMS Message-ID: Date: 30 Oct 90 23:42:18 GMT References: <1990Oct25.160937.28144@edm.uucp> <1809.272c3135@dcs.simpact.com> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 25 In article <1809.272c3135@dcs.simpact.com> kquick@dcs.simpact.com (Kevin Quick, Simpact Assoc., Inc.) writes: > 4. Overall, the C RTL is very similar between Unix and VMS, with the effort > for VMS C being to adhere to the C "standard" (chuckle, chuckle :-) and > make non-destructive language enhancements where needed. Well, they made some arbitrary language "enhancements" as well, that didn't need to be done. For example, "#include stdio" instead of "#include ". Now you can keep on #including instead of stdio, but it's quicker the other way... even though they're semantically identical. Arbitrary. > As far as the system RTL availability, the VMS has a large and very > convenient RTL, which is implemented with a general callable interface The number of features in the standard VMS library are nice. The interface to them from C has an un-necessary amount of suckiness, but the features themselves are handy. It also comes with a number of VM features that are very useful, equivalent to mmap() on SunOS. > 5. VMS supports a very large number of third-party terminal devices, so > it is not probable that you are going to have problems here. It's virtually certain that you will not be able to use non DEC-compatible terminals. It comes with a terminfo clone, but none of the editors support it. Dumb. -- Peter da Silva. `-_-' +1 713 274 5180. 'U` peter@ferranti.com