Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC830713); site vu44.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!mcvax!vu44!jack From: jack@vu44.UUCP (Jack Jansen) Newsgroups: net.lang.c Subject: Re: $ in identifiers -- poll Message-ID: <553@vu44.UUCP> Date: Thu, 3-Jan-85 14:31:12 EST Article-I.D.: vu44.553 Posted: Thu Jan 3 14:31:12 1985 Date-Received: Sat, 5-Jan-85 02:11:29 EST References: <273@desint.UUCP> <20980036@cmu-cs-k.ARPA> <659@druxp.UUCP> <10496@watmath.UUCP> <526@ncoast.UUCP> Organization: The Retarded Programmers Home, VU, Amsterdam Lines: 23 > How about this construct: > > extern sys_read() : "SYS$READ"; > I think that it should be closer to the identifier. It is the identifier that is modified, after all. If you don't want to use 'entry', the use ':', but keep it next to the identifier, something like extern sys_read:"SYS$READ"(); This is also much more readable in the case of *defining* funny names, which hasn't been discussed yet, but which can be just as useful, for instance when you're writing a library and you want to hide your internal routines. By the way, I'm still in favor of using 'entry' in stead of Yet Another Funny Char. This usage won't even make the entry symbol unusable, since the use of entry for defining entrypoints is presumably somewhere inside the *code*, not the declarations. -- Jack Jansen, {seismo|philabs|decvax}!mcvax!vu44!jack or ...!vu44!htsa!jack If *this* is my opinion, I wasn't sober at the time.