AVR-Chat

This is where I totally agree.  ASM has its place.  Instances of that
place are far fewer than most perceive.

I have written complete embedded programs which are coded in C++ and run
on an IBM compatible computer.  Once the program is tested and verified,
it's recompiled using a different software "port" for another processor.

The only ASM that is involved is the port for the RTOS.  In this way you
have a great deal of portability.

Like I said, ASM does have its place in some applications.

I find that anyone who doesn't understand this concept of portability
lives in the stone ages and therefore I'll take note of who replies with
alternate opinions.




-----Original Message-----
From: Dave Hylands [mailto:dhylands@broadcom.com] 
Sent: Tuesday, March 16, 2004 6:55 PM
Subject: RE: [AVR-Chat] Re: AVR Compiler: which is the best

Yeah, but can you take your modular ASM code and use it on an ARM
processor, or an Intel, etc?

This is one of the reasons why I like C, because I don't have to care
which processor I'm running on. This is certainly not to say that all C
code is portable, because it isn't, but I can write large portions of my
code which I move from one platform to another with little or no
changes.

--
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/

> -----Original Message-----
> From: Kathy Quinlan [mailto:kat-yahoo@kaqelectronics.dyndns.org] 
> Sent: Tuesday, March 16, 2004 4:13 PM
> To: AVR-Chat@yahoogroups.com
> Subject: RE: [AVR-Chat] Re: AVR Compiler: which is the best
> 
> 
> OK 
> 
> I think we need to split this discussion into 2 sections, 
> those who are using an language for hobby and those who are 
> using a language for work.
> 
> The reason I say this is like a PCB layout program, hobbyists 
> go for the package with all the included symbols and foot 
> prints, where as professionals tend to generate their own. 
> 
> With C, most pre defined routines have set IO pins etc, but 
> you may not want to have the LCD hanging of Port A etc.
> 
> The debate so far has revolved around re using code, who says 
> ASM is not reusable ? I find that I can go to an old project, 
> and pull out modules as is needed, and re use them, I have a 
> description block for each module which says what it is 
> called by, what it does, what it expects as an input, what it 
> outputs and what it destroys.
> 
> There are LARGE amounts of ASM code available on the 
> internet, and it only takes a few minutes to modularise it, 
> so it can be reused later.
> 
> Regards,
> 
> Kat.
>