Michael Leuchtenburg wrote:
> The PIC18 compiler claims "ANSI C compliance". Somehow, I doubt it.
If that's Microchip's own compiler for the PIC18s then it's very close.
I used it for a real work project and it's not bad. I had to
occasionally look at the assembly output to check up on what the
c
Spake Martin Ebourne:
> On Sat, 2006-05-20 at 16:16 -0400, Michael Leuchtenburg wrote:
> > I would be more specific in my subject header, but I really hate
> > everything about Basic18. Basic18 is a compiler for Basic for the PIC18.
>
> You could always try the PIC C compiler. It's been a while si
On Sat, 2006-05-20 at 16:16 -0400, Michael Leuchtenburg wrote:
> I would be more specific in my subject header, but I really hate
> everything about Basic18. Basic18 is a compiler for Basic for the PIC18.
You could always try the PIC C compiler. It's been a while since I last
had cause to hate it
On 20 May 2006, at 21:16, Michael Leuchtenburg wrote:
...
Unless, of course, you want to index into arrays. For an array of
bytes,
it's fine - no problem. But if you want to index into an array of
two-byte data, ah, now there is a problem. Because, you see, in
order to
find the pointer to
I would be more specific in my subject header, but I really hate
everything about Basic18. Basic18 is a compiler for Basic for the PIC18.
You can find it here:
http://www.midwest-software.com/Basic18/basic18.htm
If you want to.
There's a lot of hate here, but I'll try to focus on just one part.
