Steve Murphy wrote:
>>> Why can't MPASM deal with "unix" type files (no CR just LF
>>> seperators)?
>>
>> Um, because it runs on Windows and there is therefore no need for it?
>
> It may run on windows, but that doesn't mean the disk file is
> kept on windows. My experience shows that Unix file systems are
> more robust and reliable than windows, including NTFS (albeit I have
> little experience with the new W2K and XP versions of NTFS) I keep the
> source for my projects on my Unix machine. And use unix tools and
> utilities to process them. When I start a new project, it is a pain
> to temporarily send it over to the windows machine to Edit (add a
> comment line) and then back to the Unix box so MPASM won't error. I
> really wish Microchip would make this modification. It is the only
> program I know of that exhibits this behavior
>
> Steve


Sorry to respond so late, but I've been away for a few days.  Now I have
>500 messages to peruse.  :-(

I agree Steve, if MPASM was written correctly (called the correct
function to read a line) there would be no issue.  After all it's a
cross assembler and IMO should behave like one.  It's just plain sloppy
work.  ;-)  I use various environments, and this is just one more
headache that isn't really necessary.  Plus the error message indicates
something is there that shouldn't be, instead of something missing.

Just because MS thinks that there is only one way to seperate text
records, doesn't make it the right way.  In fact they seemed to have
chosen their method solely to be different, as usual.  In fact, nobody
seems to use the proper character (0x1E) for an ascii record separator.
I wonder why that is?  :-?

michael brown

"In the land of the blind, he who has one eye is king"

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads