Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!princeton!phoenix!rjchen
From: rjchen@phoenix.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: DeSmet C -> Microsoft C
Message-ID: <164@phoenix.PRINCETON.EDU>
Date: Mon, 30-Mar-87 12:59:39 EST
Article-I.D.: phoenix.164
Posted: Mon Mar 30 12:59:39 1987
Date-Received: Wed, 1-Apr-87 01:02:47 EST
References: <3380@osu-eddie.UUCP> <366@hscfvax.UUCP>
Reply-To: rjchen@phoenix.UUCP (Raymond Juimong Chen)
Distribution: na
Organization: Princeton Univ. Computing and Information Technology
Lines: 20
Keywords: DeSmet C, syntax, translate
Summary: sounds like an artifact of being tossed from machine to machine

In article <3380@osu-eddie.UUCP>, holly@osu-eddie.UUCP (Joe Hollingsworth) writes:
> Lately, I've come across some public domain C programs written in
> DeSmet C.  However, I don't have a DeSmet C compiler and I haven't
> found any switches in my Microsoft C compiler that will enable it
> to recognize the DeSmet C Syntax.  (If you're not familiar with this
> syntax, it seems to like to do away with { and }.  Using a $ for {
> and either indentation or blank lines to signal a }.  Also appears
> to use :: for ||.  What else I don't know.)

I had a similar problem with Pascal programs;  braces came out as : and
assorted punctuation got mangled.  I think that some locations can't
handle those special characters and substitute (or just plain delete)
them.  For example, I have seen ^ become ~ and { become :.

So, unless you like to decipher the code, I'd say it's going to be a
difficult task trying to return the file to its original state.
-- 
-- Raymond Chen, BITNET: (preferably) 6101695@pucc, rjchen@pucc
                 ARPA: rjchen@phoenix.PRINCETON.EDU
                 UUCP: {allegra}!princeton!phoenix!rjchen