Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site h-sc1.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!h-sc1!breuel
From: breuel@h-sc1.UUCP (thomas breuel)
Newsgroups: net.micro.amiga
Subject: Amiga questions, gripes, &c. / Manx C
Message-ID: <1061@h-sc1.UUCP>
Date: Thu, 17-Apr-86 22:02:12 EST
Article-I.D.: h-sc1.1061
Posted: Thu Apr 17 22:02:12 1986
Date-Received: Sat, 19-Apr-86 08:30:53 EST
Distribution: net
Organization: Harvard Univ. Science Center
Lines: 66

I have been using an Amiga (512k, one external drive, Manx C) for a few 
weeks now, and I have a few questions, requests, gripes, and comments. Perhaps
people at Commodore can help me with some of these?

USER INTERFACE:

-- a quick-grow/shrink gadget would be nice. Alternatively, there might
   be a way to reduce windows to icons on the desktop?
-- it should be possible to pull down a screen even if a window covers
   the whole screen
-- the send-behind gadget should not activate a window
-- pop-up menus might be nicer than the menu bar, and they could perhaps
   replace the menu bar transparently to the software?
-- the workbench should be able to run in 640x400 mode
-- a 6x8 system font should give many more characters per line
   and should still be readable

OPERATING SYSTEM:

-- arbitrary processes must be killable. The operating system should
   keep track of all resources used by a process and deallocate
   them when the process dies.
-- the disk driver/loader don't handle multiple loads from the same
   disk too well (much too much seeking). Cacheing or more intelligent
   seeks/loads are needed.
-- the relationship between CLI, DOS, and the ROM Kernel are confusing.
   I haven't read the whole documentation yet, but I have little hope
   that it will reveal the whole and ugly truth. I can just add to those
   voices that request source for CLI (which may help at least a little). 
   And I can just hope that the next release of the documentation is 
   clearer and more structured.

QUESTIONS:

-- is there a BCPL compiler *available*? (yes, I'd like to *use* it)
-- when will memory expansions and reasonably priced hard-disks be
   available?

I apologise for the rather sundry collection of items, but your help
and commentary is appreciated.

I have been using Manx C for programming (UN*X style). I find it an
excellent development system, infinitely superior to Lattice C (which
I used only briefly, however). The compiler generates fast and compact
code, and is largely compatible with Lattice (and the rest of the world).
Some things about the system are particularly noteworthy:

-- the compiler generates code either with 16 or 32 bit integers.
   You can also choose between small and large memory models
   for code and/or data. This makes it easy to port code to the
   Manx compiler, without sacrificing efficiency where needed.
-- arithmetic expressions in '#if' directives don't seem to work
-- Lattice allows structure assignment, Manx doesn't
-- Lattice allows argument type declarations according to ANSI,
   Manx doesn't (in both points, I disagree with the philosophy of
   the authors of Lattice C. I do hope that people will not use these
   misfeatures of the Lattice C compiler. Since there are unfortunately
   always programmers who try to use every last obscure feature
   of a compiler, I also hope, however, that Manx C will incorporate
   these features in the next release).
-- Manx 'make' is a true, UN*X like make with all bells and whistles
   like default and user-defined rules.
-- Manx is working on a debugger. The pre-release is a little bit buggy
   but still very usable (if you are into debuggers. I rarely use them).

						Thomas.