> Please use MPLAB to view my code.  That's what I used to create it.

But, the compiler doesn't care WHAT you created it with OR what someone
viewed it with, it just cares about what's in the file.

It's looking strongly, based on various prior posts, and on Alex's last two,
that the file has content which is interpreted by various things in various
ways and, importantly, the compiler appears to see something that MPLab+your
eyes+ your brain can't see.

It sounds like your system has provided you with an immensely valuable
embedded (and other) programming learning experience :-).

Suggestion:

Try typing in the 'identical" code as you see it after cut and pasting and
then delete the cut and pasted code and see if it compiles OK. If so, THEN
go back and hunt it down and kill it. You then can chalk another "mission
flown" symbol on the side of your cockpit.




   Russell


(Lancaster "G for George", which rests in the brightly lit darkness of the
Canberra National War Memorial Museum in Canberra Australia has (AFAIR)
about 100 mission-flown symbols on the side of its cockpit. Each one denotes
a safely survived wartime mission. Statistically, the odd aircraft has to
manage this sort of result - but happy indeed the crew that get to fly in
it. You'll be a few mission symbols short of that so far I suspect. After
you find your bug you can paint on another one and look forward to the day
that you've achieved 120 missions equivalent :-)).

http://upload.wikimedia.org/wikipedia/commons/c/cb/G_for_george_panorama.jpg
Despite the artificial look in the photo it's the real thing.










On 1 March 2010 18:16, Jason Hsu <jhsu802701@gmail.com> wrote:

> Please use MPLAB to view my code.  That's what I used to create it.
>
> On Sun, Feb 28, 2010 at 11:11 PM, Alex Harford <harford@gmail.com> wrote:
> > Jason, the strange thing I see is that the newlines are odd looking.
> > See what it looks like opened on a Linux box in vim:
> >
> > http://imgur.com/qvgwj
> >
> > There are ^Ms shown, but where you pasted the code in, there is a ^M
> > but it didn't cause a newline!?
> >
> > Maybe a dos2unix / unix2dos pass will straighten things out.
> >
>
>
>
>
> --
> Jason Hsu
> http://www.jasonhsu.com/swrwatt.html
> http://www.jasonhsu.com/swrwatt-c.txt
> http://www.jasonhsu.com/swrwatt-asm.txt
>   --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist