>> I guess if there is further discussion on this it needs to go to the [EE]:
>> thread.

>I respectfully disagree. This is very much about [PIC]:

Well I was figuring that if it continued on about compiler internals (even if it
is about optimising for a PIC) then it should go [EE] before James steps in. I
was not quite clear enough about that in my suggestion above, and I thought that
the real intention of the [PIC] category was to be focused on problems of PIC
code and hardware as such. Compiler internals do not really fit into this. Parts
of the discussion (if there really are any) that relate directly to the PIC
rather than optimisation could certainly stay in [PIC].

we have had threads running in more than one category in the recent past because
of a divergence of discussion line.

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu