Re: Cases in AS400

No doubt, CASE generated code does make you dizzy.  However I too 
suggested that you not look at the CASE generated code.  That you stay in 
the action diagram.  At one time I thought of changing the application 
sets to only generate the source code into QTEMP, and compile the objects 
only into the more permanent library.

Are we on the same track?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Kaynor@xxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/28/2005 11:03 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Re: Cases in AS400






 
With apologies for jumping in late... I'd just like to take umbrage with 
the 
disparaging statements about generated code.
 
I used Synon/2e (now Advantage:2e) for eight years before I learned  RPG. 
That was reality for me.  I still use it without viewing the  generated 
code, 
and in fact interact with vendor code generated in  COBOL (which I also 
don't 
look at).  The "code" I care  about is in the Action Diagram.  The biggest 

benefit of a  CASE tool is the ability to work at a higher level of 
abstraction 
than the 3GL  provides.
 
Just as I don't look at the machine code generated by the compiler, I 
should 
not look at the HLL code generated by the CASE tool.  When I do, it  is 
because of my ignorance of the CASE tool or a bug in its generater, and 
neither 
should be tolerated.
 
The programmers whom I see looking at generated code are usually looking 
for 
warm-fuzzies about what they just created, or don't understand how the 
CASE 
tool works, and are using the generated code to understand what it  does.  

Neither is an efficient use of their time.   They  should learn how to 
program 
IN THE TOOL, not use it to "manipulate code." 
 
I have lots of respect for your posts, Rob, and David, and I missed 
Peter's 
original post, so this may not be germane to his original  point.   But, I 

contend that all of you miss the point  of using a CASE tool when you 
disparage 
its generated  code. 
 
--Chapin Kaynor
  Vermont
 
 

date:  Fri, 22 Apr 2005 14:54:19 -0500
from: rob@xxxxxxxxx
subject: Re: Cases  in AS400

I agree David.  I used to use AS/SET and that code was,  and still is, 
ugly.  In fact they still convert 10 character field  names down to 6 
characters.

Sometimes I wonder if they do this  stuff just to discourage you from 
looking at the generated code, stay the  he!! out, and only use the case 
tool to manipulate code.

Rob  Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box  2000
Dock 108
6928N 400E
Kendallville, IN  46755
http://www.dekko.com





David Gibbs  <david@xxxxxxxxxxxx> 
Sent by:  midrange-l-bounces@xxxxxxxxxxxx
04/22/2005 01:47 PM
Please respond  to
Midrange Systems Technical Discussion  <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Re:  Cases in AS400






Peter Vidal wrote:
> SYNON?  Ugly code....

I think all case tools generate ugly code ... but the  theory is, you use
the case tool to manage generate the code, so who cares  how ugly it is.

That is, of course, a theory only.

Reality,  obviously, is another story.

david

-- 
David  Gibbs
david@xxxxxxxxxxxx




-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.