🚀 go-pugleaf

In article <267063fd-6b6comp.sys.amiga.tech@tronsbox.UUCP>, bleys@tronsbox.UUCP (Bill Cavanaugh) writes:
> I attempted to use the Lattice "lc" command to compile a file that was in
> RAM:.  I typed "lc -Lm file.c", and got the message "File RAM:-Lm.c does not
> exist.  Try again."
> 
> What's the deal?  It works with a standard CLI, but not with WShell/ConMan. 
> Is there some path expanding going on?  Is there some way I can turn it off?

The problem is with Lattice (and they've know about it for quite a while now).
What is happening is that WShell includes the path with the command name,
which in this case is "RAM DISK:"; notice the space between RAM and DISK. When
Lattice builds its arg vector it gets the command name from the process or CLI
struct (I forget which), appends the arguments from the command line to it,
then it parses it. Lattice will have this problem with any command that has a
space in the name. For details on how to fix your programs, see below.

If you have the latest WShell (don't know what it is, its at work), there is a
config option that will turn the path off; look at the docs or call Bill Hawes.

To fix your own programs you need to replace the Lattice supplied c.o and
_main.o (in lc.lib). Suitable replacements can be found in the RCS distribution
(rsbx.lib and its source) or on the latest set of developer disks.

						rsbx

>  * Bill Cavanaugh       uunet!tronsbox!bleys                        *


------------------------------------------------------------------------
  Raymond S. Brand			rsbx@cbmvax.commodore.com
  Commodore-Amiga Engineering		...!uunet!cbmvax!rsbx
  1200 Wilson Drive			(215)-431-9100
  West Chester PA 19380			"We're working on it"
------------------------------------------------------------------------