Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!labrea!rutgers!bellcore!texbell!uhnix1!uhnix2!uace0
From: uace0@uhnix2.uh.edu (Michael B. Vederman)
Newsgroups: comp.sys.atari.st
Subject: Re: Laser C (was Re: Infinite reboots)
Message-ID: <712@uhnix2.uh.edu>
Date: 19 Jan 89 00:52:11 GMT
References: <478@orbit.UUCP> <4029@mtuxo.att.com> <904@laura.UUCP> <2377@nunki.usc.edu>
Reply-To: uace0@uhnix2.UUCP
Organization: University of Houston
Lines: 29

In article <2377@nunki.usc.edu> rjung@sal45.usc.edu (Robert  allen Jung) writes:
>In article <904@laura.UUCP> klute%trillian.irb@unido.UUCP (Rainer Klute) writes:
>>In article <4029@mtuxo.att.com> rcd@mtuxo.att.com (XG1V6-R.DUTT) writes:
>  Just thought I'd also mention that the Laser C GEM shell works quirkly with
>Shadow installed (who's at fault?!?). The usual process of compile-link-run
>(^R) won't always work, which makes it a hassle to get some programming done
>while trying to call bulletin boards.  B-)
>
>  And does anybody know when Laser DB is shipping?
>


Please don't blame SHADOW for this!

LASER C doesn't work with many programs that take over some vectors while
in the shell, or even before you enter the shell.

LASER C does some very funny things to 'watch' vectors so it can trap out
problems on crashes, etc.

I can't use AMONST (memory resident debugger/monitor) with LASER C Shell.

- mike

-- 
for (;;)                              : Use ATARINET, send an interactive
        do_it(c_programmers);         : message such as:
                                      : Tell UH-INFO at UHUPVM1 ATARINET HELP
University Atari Computer Enthusiasts : University of Houston UACE