Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uflorida!uakari.primate.wisc.edu!sdd.hp.com!decwrl!ucbvax!MATHEMATIK.UNI-ULM.DE!borchert
From: borchert@MATHEMATIK.UNI-ULM.DE (Andreas Borchert)
Newsgroups: comp.lang.modula2
Subject: Re: Topspeed
Message-ID: <9006271111.AA00160@mathematik.uni-ulm.de>
Date: 27 Jun 90 11:11:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Modula2 List <INFO-M2%UCF1VM.BITNET@PSUVM.PSU.EDU>
Organization: The Internet
Lines: 30

Scott Canion writes:

> On 18-Jun-90, sources inform us that Ola Garstad @ 2:502/100.0 said:
>
>  PM>> and specify that a
>  PM>> given procedure can have a variable number of parameters (lets you
>  PM>> create your own printf-like procedure).
>
>  OG> Oh - No!
>  OG>
>  OG> THAT will make a lot of non-portable code!
>  OG>
>  OG> Looks like JPI is doing it's best to destroy M-2.
>
> Isn't the term "Portable Modula-2 Code" an oxymoron?  I mean, since Wirth
> purposely decided -not- to offer any standardized library routines, I think
> that really shot portability right out the door....

I don't agree. You don't need standardized libraries for portability.
If you have the sources of a complete library then it is sufficient
to port your library.
An example: I've ported 30,000 lines Modula-2 within 15 hours without
any preparation from our UNIX system to JPI Modula-2. I haven't known
JPI Modula-2 before. Most of the time was spent on language problems
(forward declarations, bugs of JPI-Modula-2, type conversions etc.).

Andreas Borchert
--
borchert@mathematik.uni-ulm.de
borchert@dulruu51.bitnet