AVR-Chat

BASCOM is great for getting results in a hurry. One of my reservations 
with it is it's strange behavior when you mix a keyword into a variable 
name. Off the top of my head:

support = &h12

Might get misinterpreted because support contains the word port. Again, 
that's just an example off the top of my head. Another reservation is 
it's inability to handle complex arithmetic in an expression, for 
example:

day = whatser / 12 * questo + 2

Again, just an example off the top of my head. I think both problems 
stem from the fact that it is a code generator (for lack of a better 
term), rather than a compiler.

I generally use WinAVR. When in doubt about whether there is a problem 
with my C or my hardware, I sometimes use BASCOM to verify the hardware.

WinAVR supports devices without RAM using assembly code. Not sure about 
BASCOM.

There are a lot of good resources and opinions at the avrfreaks web 
site.

Regards,
   JJ

On Sunday, Mar 14, 2004, at 12:24 US/Eastern, VA3TO wrote:

> I never took to C and I usually prefer assembler but when it comes to
> the AVR,
> I am partial to Bascom.  Todays Basic compilers are much more 
> structured
> & efficient and have come a long way since the days of GOTO 100.
> "This is not your father's Basic" :)
> Bascom has a lot of built-in functions, it's quick and easy to get
> something
> up and running and there are lots of samples and support for it. You 
> can
> also
> do inline assembler code anywhere you need it. It's inexpensive yet
> powerful.
> You can get it for US$59 from Rhombus (www.rhombus-tek.com) in the US
> or directly from the author (www.mselec.com) in Europe.
>
> (No commercial interest, just my biased opinion :)
>
> Hugh
>
>
> markevans_1 wrote:
>
>> Ok, I hope this message isnt the start of a huge thread, but I would
>> like biased/unbiased opinions on what you guys recon is the best
>> compiler for the AVR microcontroller.
>>
>> Basically I want something that is cheap, ideally comes with a
>> fuctional IDE and is quick to code with ( has built in libraries,
>> language maps easily to AVR, and is as high level as possible) and
>> at the same time has the abilty to do low level stuff when speed is
>> required ie: inline assembly. It needs to compile fast and generate
>> small code and needs to support AVRs which have no RAM.
>>
>> Not too fussed about language as long as it meets all my above
>> criteria, but I suppose I have some preference to C.
>>
>> Hope you can help
>> Mark.
>>
>>
>>
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>