From david@imagine1.com  Tue Nov 21 04:32:50 1995
Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id EAA03585 for <sc22wg5@dkuug.dk>; Tue, 21 Nov 1995 04:32:45 +0100
Received: from ppp34.swcp.com (ppp34.swcp.com [198.59.115.144]) by kitsune.swcp.com (8.6.9/8.6.9) with SMTP id UAA29705 for <sc22wg5@dkuug.dk>; Mon, 20 Nov 1995 20:32:39 -0700
Date: Mon, 20 Nov 1995 20:32:39 -0700
Message-Id: <199511210332.UAA29705@kitsune.swcp.com>
X-Sender: evt@swcp.com
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====================_816921167==_"
To: sc22wg5@dkuug.dk
From: david@imagine1.com (David L. Epstein)
Subject: Invitation for CoCo
X-Mailer: <PC Eudora Version 1.4>
X-Attachments: C:\DE\WG5\COCO\INVITE.TXT;


--=====================_816921167==_
Content-Type: text/plain; charset="us-ascii"




--=====================_816921167==_
Content-Type: text/plain; charset="us-ascii"


"I use not only all the brains I have,
 but all I can borrow."
  -- Woodrow Wilson

You are invited to join the Conditional Compilation (CoCo)
development team.  The challenge before the CoCo development
team is to design/debug/document a CoCo definition before
the next WG5 meeting.  Although time appears short, there
are existing CoCo definitions that can be used as a starting
point.  Also, my experience has been that once the objectives
have been set, 90% of the definition is straightforward.

Here are some objectives for some different CoCo definitions:

 (A) existing practice -- subset cpp or superset cpp
 (B) Fortran-like      -- subset Fortran or superset Fortran
 (C) somehow combine (A) and (B)
 (D) other

The CoCo development body shall focus on defining CoCo languages, 
not on deciding which CoCo language is the best for Fortran.

Recall that in San Diego, paper WG5/N1139 (X3J3/95-257) contains
a definition for 'fcc', which follows the (A) objective.
Also in San Diego, temp papers WG5/S13 and WG5/S48 (X3J3/95-178) 
contain a definition for 'CCF', which follows the (B) objective.

Those interesting in joining the development body are encouraged to
browse these definitions.  My intent, however, is to start from
scratch.

For those with limited time, but a desire to participate, joining
the development body could simply mean reading your email and
jumping in for your specific interest (for example, the "handling
of the Fortran INCLUDE" part of the CoCo definition.)

As CoCo is such a hot topic, you are also invited to be an observer.
Kurt will be setting up an email reflector for CoCo, so observers
could sit in the stands and watch.

Join as a developer or an observer by sending me email.

David Epstein
david@imagine1.com


--=====================_816921167==_--