You mentioned "lines per hour".  I am interested
in how it is measured (design, coding, debugging,
testing?) and what the normal lines per hour are
for the industry.

Thank you,

Bill

----- Original Message -----
From: "Wouter van Ooijen" <wf@XS4ALL.NL>
To: <PICLIST@MITVMA.MIT.EDU>
Sent: Thursday, August 01, 2002 7:19 AM
Subject: Re: [PIC]: Re: PIC development STINKS!


> > I honestly don't know whty people in general
don't like assembly.
>
> 1. It does not eliminate unused (uncalled) code
> 2. It does not optimize (like: inline code that
is called only once)
> 3. It does not warn when I exceed 8 (or 9, or 2,
...) stack levels
> 4. It does not (automatically) hack around the
stack limit
> 5. It does not 'share' file registers used in
different pieces of code
> (pseudo-stack)
> 6. It is slower to write (general rule:
lines/hour is the sam in each
> langauge, HLL typically produces a few
instrutions poer line fo HLL, so
> it codes faster, even considering an asm coder
would have used somewhat
> fewer instructions)
> 7. It is more difficult to read
> 8. It is more difficult get target-independence
(I know, even HLL won't
> be totally target-independent)
> 9. It does not transparently handle
coding/banking (I know: not all
> HLL's do that either)
> 10. It is more difficult to explain to 14-year
old kids
> ....
>
> Wouter van Ooijen
>
> -- ------------------------------------
> http://www.voti.nl
> PICmicro chips, programmers, consulting
>
> --
> http://www.piclist.com hint: The list server can
filter out subtopics
> (like ads or off topics) for you. See
http://www.piclist.com/#topics
>
>

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics