🚀 go-pugleaf

In article <183e09fb.ARN03933@swindj.UUCP>,
    didierj@swindj.UUCP (Alain Didierjean) writes:
>In article <15983@cbmvax.commodore.com>, Ken Farinsky - CATS writes:
>-> Have you considered sending bug reports (along with sample code) to SAS?
>-> Or are you just going to complain that it is broken?  Developers can
>-> only fix problems that:  1) they know about, and 2) they can reproduce.
>-> --
>Considering that the only practical and not too expensive way to get in
>touch with SAS people from here is this very net, could we possibly get
>an E-Mail address for SAS Institute Amiga C debugging crew... Or any
>organisation that agree to be used as a relay of some sort...
>This could possibly be useful to some american users too.
>If not, I'm going to join the "SAS bug of the month club". Not very
>efficient, but excellent for mental hygien..

I can only agree with Alain. Here's my bug of the month:

Try compiling this:
-----------------------------------
typedef int test;

void test(int x) {}
-----------------------------------

LC1 catches a GURU on this one.

Anybody who doesn't have to call long distance overseas international
terribly expensive is welcome to send a formal report on this.

---
 \_/   Mikael Karlsson, Lovsattersvagen 10, S-585 98  LINKOPING, SWEDEN
  V                           | micke@slaka.sirius.se
  |      Absolut Software     | micke@slaka.UUCP
 ~~~                          | {mcvax,seismo}!sunic!liuida!slaka!micke