Jan-Erik Soderholm wrote:
> > Even if this PIC18 -> PIC24/30/33 converter might be a
> nice technical project, isn't the problem that the overall
> application architecture will probably be quite wrong
> for the "other" plattform ? Or at least, could have been
> written much more efficiently ?
>   
.
Oh, yes, absolutely  that is so! 
.
> > It's no different then porting PIC16 code to PIC18, b.t.w.
> You can port it one instruction at-a-time, or you can look
> over it and write it "better" on the PIC18 architecture. It
> can even be more work to "fix" the machine-ported app
> later then to think about it a bit more in the first place.
>   
.
Yup.  No disagreement there, either.  You are stating the obvious, 
Jan-Erik!  :-)
.
> > Still, it's an interesting programming project, and I'm sure
> you'll learn a lot about the instruction set... :-)
>   
.
That is true (already have), but also I needed to refresh myself with 
Perl programming, and this is an excellent text-manipulation project.  
Pattern-matching and "regular expressions" have always been a weak area 
in Perl for me -- probably because there is nothing intuitive about 
looking at a statement such as "/^\$([A-Za-z]).*/" and making sense out 
of it.  :-) 

That said, I still think the translator would be useful for someone 
wanting to convert code from one family to another family.  But only in 
the sense of producing a starting point to work with.

John
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist