#Lattice & Aztec code dif
07-Dec-90 19:26:43
Sb: #4944-#Lattice & Aztec code dif
Fm: Bob Rakosky 75156,336
To: John Toebes 72230,303
John,
I agree totally with the reasoning for putting that switch in, as I used
to swear frequently at "you guys" when the Lattice compiler first included
function prototypes and I had to learn to put in all those casts. Problem
(for me) is that I've gotten used to doing the casting and have maintained
the habit. I never meant to imply that the compiler shouldn't have that
command-line switch. I'm just being resistant to change. <Grin>
As to the CLI vs. WorkBench thing, for me it's mostly the same
resistance to change. However, I still see at least one shortcoming to the
WB approach -at least in relation to the manner in which I'm accustomed to
setting up my projects. I use a lot of pseudo-targets in my makefile, and
also tend to use a lot of macros in my makefile. Consequently, I am
constantly running LMK and specifying specific targets to be "made", and
frequently invoking LMK with macro-value overrides. I don't think there's
a way yet to adapt this easily to the iconic approach. I probably could
set up a bunch of ICONX scripts to do this, but it seems like more bother
than it's worth. Also doesn't give me quite as much flexibility as I'd
need to anticipate every possible combination I may want.
Still, I have no real complaints with the direction you are taking the
compiler product. I'm a believer. 🙂
…BobR