public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: wireless <wireless@tampabay.rr.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] OT: HiTech-C question
Date: Mon, 15 Nov 2010 06:22:20 -0500	[thread overview]
Message-ID: <4CE117EC.5050704@tampabay.rr.com> (raw)
In-Reply-To: <20101114211024.350fb808@osage.osagesoftware.com>

Previously you wrote:
> Greetings,
> 
> I'm using HiTech-C for the first time. 

I agree with both previous responses.

If you insist on closed sources, look here:
http://www.microchipc.com/
==> Pic C Sample Code and PIC FAQ


However, as one who has worked with traditional
development environments for uP, here's my wisdom.

Ditch Hi-tech C immediately. It is garbage and you'll
waist tons of time on things you should not. If you want
to use a commercial compiler, then you have to decide.

Want a really good compiler for Microchip stuff?

==> IAR, as they are THE GOLD STANDARD. www.iar.com

Sure you pay, but, in the long run, you'll be
thankful. Compilers for small micros are only as good
as the folks that develop and support them. IAR
is the best. Nobody else is even close. I know, as I use
to be part of a team, that used everything you can image.


Now, if you're a hack, and CHEAP, which is a compliment,
then get real and start learning how to use the open source
compilers.

I'll dig out a few links of my PIC open source references
and post it, if you like.



hth,
James



  parent reply	other threads:[~2010-11-15 12:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15  2:10 [gentoo-embedded] OT: HiTech-C question David Relson
2010-11-15  3:37 ` Peter Stuge
2010-11-15  7:44   ` Mike Frysinger
2010-11-15 11:22 ` wireless [this message]
2010-11-15 12:25   ` Arkadi Shishlov
2010-11-15 14:45     ` wireless
2010-11-15 16:05       ` Peter Stuge
2010-11-15 18:13         ` wireless
2010-11-15 18:53           ` Peter Stuge
2010-11-15 19:28           ` Arkadi Shishlov
2010-11-15 14:53     ` Peter Stuge
2010-11-15 12:37   ` David Relson
2010-11-15 14:25     ` wireless

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CE117EC.5050704@tampabay.rr.com \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-embedded@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox