Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!uwmcsd1!marque!gryphon!crash!pnet01!haitex
From: haitex@pnet01.cts.com (Wade Bickel)
Newsgroups: comp.sys.amiga
Subject: Re: Anyone seen a good Amiga Pascal lately ?  Why not Modula-2?
Message-ID: <2665@crash.cts.com>
Date: 12 Mar 88 17:36:14 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 38

papa@pollux.usc.edu (Marco Papa) writes:
>In article <2652@crash.cts.com> haitex@pnet01.cts.com (Wade Bickel) writes:
>>		I noticed you left out my references to Modula-2's seperate
>>	compilation facilities.  This is feature C clearly cannot match.
>>	Seperate compiliation in C requires programmer attention to a
>>	tremendously higher degree than in Modula-2.  ALL my programs use
>        ^^^^^^^^^^^^
>>	seperate compilation.  It's almost as easy as useing #include.
>
>I would definitely have to disagree on this one.  Separate compilation in
>C does NOT require a "tremendously high degree" of programmer attention.
>
>It just requires MAKE and LINT.  MAKE is available in both public domain
>on the Fish Disks, and it is provided with both MANX and LATTICE.  Amiga
>Lint has been available for over 2 years I believe, and MANX, for example,
>provides header files so that all of the Amiga and MANX libraries can be
>type-checked.
        ...
>I just set it up the way I knew it from UNIX.  While not everybody
>has a UNIX background, rules for Makefiles don't seem to be such a
>"tremendous" problem to me.
>

        None-the-less that is tremendously more difficult than doing so in
M2.  All you do in M2 is cut the headers of the procedures you wish to have
be public from your .mod modules into their corresponding .def modules,
refrence them, and thats it.  Same for data or types.

        When I first utilized this facility I had no documentation at all
describing how to do it (I had no books on M2), only examples.  It takes only
a minute or two to figure out{{_xj6'C|fV$ut, with no background at all!

                                                               Wade.


UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!haitex
ARPA: crash!pnet01!haitex@nosc.mil
INET: haitex@pnet01.CTS.COM