

Has a very friendly and powerful debbuger Has as many as possible libraries (functions and peripheral chips) Gives the fastest (in execution time) possible code

Gives the smallest (in size) possible code It is easily to say that the good compiler is that who

I think the most experienced members here after a discussion, to post a sticky for this: how to test a compiler. I see from time to time posts in various forums, personal opinions about what compiler is the best. I install xc8 and I see in installation folder known parts from both hitech and mplabc18 compilers. Second I know that these compilers are going to at its end as soon they are substituted with xc ones, so my post concerns the collectors. The first thing is a clean(or official) method to install without fake.exe or other tricks.
