I was tinkering with v4.5 (as I had installed that a few months ago, =20 but never did use it then), but getting v5.x now. One thing I noticed =20 with v4.5 is that the ADC-read function only allowed for use of the =20 internal Vref, not external Vref. I guess you just write your own =20 inline function for things like this? I found some nice C tutorials with ROM/RAM size comparisons by =20 googlium ( http://www.gooligum.com.au/ ), and will repeat the same =20 code for the compilers I'm evaluating (MikroC, SourceBoost). However =20 I would've felt better if the author compared a larger piece of code, =20 say close to the 2K limit, using a wider set of library functions. I did find one worrysome bug with MikroC v4.5, that with 2 EEPROM =20 reads, the second one would not work. If I commented out the first =20 one, the second would work. But they were not sequential, so it's not =20 really a case of the first not completing ... at least I don't think =20 so. They were in a switch statement, and I verified each case =20 statement was being called properly. That really concerns me because when coding, adding compiler bugs to =20 my own bugs, especially when I'm new at C for PIC's, exponentially =20 increases the frustration factor. My highest priority in a compiler =20 would be bug-free-ness and then small code size. Cost is an issue, =20 but I'd pay more to be assured of these. (Though I'm not about to =20 drop $1k+ on C18 right now for just one chip series). Well-covered =20 libraries are nice, but if anything is lacking I at least have the =20 option of rolling my own. Still wish Microchip would be more reasonable about their C compiler =20 prices, as it only helps the chip sales. And I'm not being a =20 freeloader, as I may have been the one in a million who agreed with =20 Microchip partially charging for samples a couple years back (IIRC =20 they charged for the shipping, but later dropped it). Cheers, -Neil. Quoting fred jones : > > I have the MikroC and MikroBasic compilers for several PIC =20 > platforms. I like them. The price is right, free lifetime upgrades =20 > and support, great libraries, huge selection of development tools. > > I started with Microchip Assembly. I switched to Mikro compilers to =20 > speed up software development. When they went to the pro series =20 > compilers, it was free and the code size was greatly improved. You =20 > can download a free copy and try it. > Good Luck, > FJ > > >> Date: Mon, 5 Sep 2011 15:32:03 -0700 >> From: picdude3@narwani.org >> To: piclist@mit.edu >> Subject: [PIC] Anyone here using MikroC? >> >> Would you care to comment on it's stability & "bug-free-ness"? And if >> you have any size comparisons between this and any other compiler (or >> even MPASM), that would be nice. >> >> Cheers, >> -Neil. >> >> >> -- >> 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 > --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .