#SAS C Disappointing!
20 messages in this thread
Well, I got the new SAS C 5.11 for the Amiga and boy is it a
disappointment. I haven't really tried the compiler per se or any of the
utilities 'cause I've spent the last 5 ours trying to figure out the editor
and running into Guru's left and right.
1. If you use the LSE from it icon and try the "fork command processor" key
or the NEW CLI menu item you get a guru.
2. If you use the SASCSETUP to get a project directory, and try to invoke
the LSE from the icon placed in the directory it says the msg file is not
found. If you copy the DAT, MSG and HLP files into the directory and try
again the LSE runs OK until you try to compile and link. even though it
builds a .lnk file in the right place it claims it can't find it and never
produces the executable.
3. If you have a directory made with SASCSETUP and invoke the editor in the
LSE home directory, then invoke the file for editting it can't compile and
link because again it looses the .lnk file and cant get to an executable.
4. The method they use to invoke the CLI when you start the LSE from a CLI
int the LC: assigned directory (any other way and it will GURU) bypasses
cli-startup. It appears there is no attempt to use a handler here.
So basically it is only good if you keep all the object, link, source and
executable files in the same directory as the lse and compiler. Then you
have to move the files to the project drawer manually. If you want to work
on them again later, manually copy them back to the LC: assigned directory
again. Very ugly. You would think, since they have no options aside from
the o option on the lc command to put outputs of various functions
executabel from the LSE to user defined directories, that they would at
least allow you to cd to a directory and work in that directory without
having to duplicate many files (lc and LSE alonw with all its attendent
files) in the working directory. Very poor thought on user interface.
Is there another editor that the compiler can be called from, that might
[ MORE ]
Wayne,
I don't personally know anyone who uses LSE. I'm sure there are some
lost souls out there who do, but then, they must not get much code written
either. Get yourself a good editor, like CEDPro, uEdit, TxEd, DME, etc.
All LSE does is waste disk space.
-sja
Steve:
I guess I must be that one lost soul who does use LSE, so I thought I
would speak up now (Grin). I'm not a heavy duty programmer, but before LSE
I used ED. Then I tried Emacs or whatever it is from the Extras disk. I
certainly think LSE is more comfortable for me than either of those. After
working with LSE for a while, I sort of like it. I do wish it had a file
requestor though…
I have 5.04 and have noticed several of the problems Wayne had while
trying to invoke the compiler (regarding pathways and necessary files). I
look at LSE much like AmigaBasic (it came with the system for free, and
serves my minimal needs).
Now that I have saved your message, I may try one of the editors you
mentioned to see the difference, thanks for the list.
Bill,
Well, I must say that if my choices were limited to Ed, uEmacs, and LSE,
I'd be using LSE too! Do take a look at a couple of shareware editors —
uEdit and DME, both over in AmigaUser in the Text Utilities Lib. If you
want to go with a commercial product, my favorite is CEDPro from ASDG.
Steve,
Thanks for the advice – I was beginning to think it was just me. I hav
downloaded Uedit to try out. I need tolook further into the compile form
editor operation as I've been spoiled by Turbo environments on the PC and
M2Sprint environment on the Amiga.
Of those you listed, which editor is the "ax" of your choice?
wmc
Wayne, I use UEdit exclusively, and we've made some changes to the standard
'config' to make it more useful for program editing (without hitting the
normal text stuff _too_ hard). If you have any questions about it, feel
free to ask.
Victor A. Wagner, Jr.
Vic,
I've just played with the shareware version of Uedit for about 5 days and
then only sparsely. But it do seem interesting. Do you have it set up to
compile form the editor? can you get error messages back into the editor
somehow?
wmc
Why don't you give DME a try, It has an ARexx interface and there are
programs on here that can interface to Aztec 5.0. DME is a PD editor, you
can find it on CIS.
Wayne,
Well, no, and yes. We don't have it set up to compile from the editor
(although building something to do that shouldn't be _too_ difficult).
When I do compiles, it's almost always through LMK anyway. Whenever you
'run an AmigaDOS command' from UE, the reply is sent to buffer-39, so
getting the error messages back is a cinch. One of these days, I guess
I'll take the time to put it all on a function key.
Victor A. Wagner, Jr.
Wayne,
Editors are very subjective. I personally don't want someone else's
idea of an "integrated environment". This is a multitasking machine. I
can set up an environment that suits me just fine given editors like
CEDPro, uEdit, TxEd, or others that support ARexx.
-sja
Steve,
The features of "environments" that are important to me that I don't have a
ready idea of how to set up are: being popped back into the source at the
error line; being able to cycle through the erroroneous lines; auto indents
at { for c and auto keyword cap for Modula2; intuition based setting of
compiler/linker options and auto make file build operations.
I'm a baby and I want all the hand-holding I can get – what can I say…
wmc
I asked the question on USENET whether anybody does use LSE and there
actually is one person out there who does. Can't remember his name, in fact
he might have used an alias. As for myself, I finally pulled out of 'vi'
and switched to CEDPro and I love it! Changing editors is living h*ll, and
arguing about them is the quickest route to heavy duty flames. As you said
it really is a subjective subject.
—Mike,
Wayne,
5.11??? really, I just 5.10 (didn't know they'd updted it so soon). At
any rate, I don't use LSE and I don't invoke the compiler from my editor
(yet). But I suspect that something is not set up correctly (your path
perhaps). I've seen those guys systems before, and I know they don't do
everything in one directory.
Last time I saw their setup they had more projects 'on the fire' than an
army batallion cook has eggs for breakfast.
Victor A. Wagner, Jr.
Vic,
I got part of the problem fixed when I 'relearned' the lesson that path
adds done after workbench is loaded last only as long as and apply only to
the cli session that the path add command is issued from. By adding LC: as
a path in the startup-sequence I can now invoke the compiler from the
project directory set up by SASCSETUP, but I can't link cause I get a
message that reads: unable to write file '"dh1(40mb):lc/c/hello/hello.lnk
after the requester to load volume '"dh1(40mb): comes up. The name of the
partition that the compiler is on is dh1(40mb) (per the GVP setup
convention). It looks suspiciously like the start of a Unix script string
with variable substitiution and expansion notation with out balancing ' or
".
wmc
Wayne,
Try changing the partition name with the WB rename command. I had an
application that didn't like GVP's names, either. My two partitions are now
called Workbench: and Applications:
David
David,
I've been thinking about doing away with the (40MB) portion of the names
for a while – Just might do it this week.
wmc
You must have LC: added to your AMIGADOS path, not to any WSHell path, or
anything like that. Once I made surethat LC: was added to my path before I
started PopCLI, (to make it the global path for all shells, etc.) then
everything worked fine.
Joe,
Of course I have LC: in my path. The install procedure suggests that
strongly.
Victor A. Wagner, Jr.
So did I and I couldn't get it to work. Trouble was, it was in my WSHell
path, and not the realio-trulio path. It took me awhile to
remember there was a difference, and correct it.