Problem solved..
The LCD.C and LCD.H files I've been using are NOT part of the WinAVR
distribution!
This is my work PC, used by others, and someone switched out the fine coffee
normally served in this restaurant with Folger's Crystals.. Let's watch.
:-P
Sorry for the confusion..
I got suspiciou
Bob Paddock wrote:
On Mon, Mar 30, 2009 at 2:48 PM, David VanHorn wrote:
I thought I must be doing something fairly trivial wrong, this IS
only my second project in C...
Dave, I have two recommendations for a beginner at C.
1) Buy yourself a copy of Gimpel Lint, even if you have to pay
for i
I learned to code C/C++ with the dummies book, it gave pretty clear
examples.
C doesn't have to be hard, just take the time to grock it and not
rush it.
Also, this is a great read for understanding social dynamics on how to
ask people questions and get an answer.
http://www.catb.org/~es
On Mon, Mar 30, 2009 at 2:48 PM, David VanHorn wrote:
> I thought I must be doing something fairly trivial wrong, this IS
> only my second project in C...
Dave, I have two recommendations for a beginner at C.
1) Buy yourself a copy of Gimpel Lint, even if you have to pay
for it out of your own p
Hi,
I'm assuming you meant to post this on the mailing list rather than just
to me. It's easy to press the "Reply" button on your mail program
rather than the "Reply All" - it's a mistake we've all made on occasion.
There was some good reason for the mailing list being configured the
way it
Correction: The routine in question is lcd_putc not lcd_puts.
___
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
From: i...@hotmail.com
>That would work. Another way is to have get_key return int.
Oops. I mean, of course, make "key" an int. Having get_key return an int that
is then stored into a char would accomplish... nothing.
Regards,
-=Dave
Express your personality in color! Prev
From: j...@uriah.heep.sax.de
> Dave Hansen wrote:
>
> > In this code=2C the handle_input function falls into an infinite loop if pl=
> > ain char is signed. This is because key gets promoted (to signed int) befo=
> > re the comparison with EXIT_KEY (which is already signed int). If plain c=
>
Dave Hansen wrote:
From: david.br...@hesbynett.no
[...char vs. signed cahr vs. unsigned char...]
>
> Don't look it up - if you learn the compiler's default behaviour, you
> risk writing incorrect code. If it is in any way relevant whether a
> char is signed or not, write "signed char" or "un
David VanHorn wrote:
I know what *I* am missing - the source code! How is anyone
supposed to help you with your problem until you post the actual
compilable code snippet? We need a compilable code sample which
demonstrates the problem, along with the compiler fla
>
> I know what *I* am missing - the source code! How is anyone supposed to
>> help you with your problem until you post the actual compilable code
>> snippet? We need a compilable code sample which demonstrates the problem,
>> along with the compiler flags you used and also the compiler version
David VanHorn wrote:
I was originally declaring my variable passed to lcd_puts as
signed char LCD_String[LCD_Line_Len + 1]
This, after discovering to my surprise that lcd_puts wants signed chars.
Recently, I've converted to the portable typedefs as
unit8_t and int8_t
Now, whichever of
From: avr-gcc-list-bounces+larry=barello@nongnu.org
[mailto:avr-gcc-list-bounces+larry=barello@nongnu.org] On Behalf Of
David VanHorn
Sent: Monday, March 30, 2009 10:15 AM
To: avr-gcc-list@nongnu.org
Subject: Re: [avr-gcc-list] Re: Passing a string variable to lcd_puts
I am still ver
I am still very puzzled over why the compiler balks wether I use signed or
unsigned chars to feed lcd_puts.
When I used "unsigned char" it balked. When I used "char", it didn't.
Now when I use int8_t or uint8_t, it balks.
___
AVR-GCC-list mailing list
A
Dave Hansen wrote:
> In this code=2C the handle_input function falls into an infinite loop if pl=
> ain char is signed. This is because key gets promoted (to signed int) befo=
> re the comparison with EXIT_KEY (which is already signed int). If plain c=
> har is signed=2C and key is 0xF1=2C the
From: david.br...@hesbynett.no
[...char vs. signed cahr vs. unsigned char...]
>
> Don't look it up - if you learn the compiler's default behaviour, you
> risk writing incorrect code. If it is in any way relevant whether a
> char is signed or not, write "signed char" or "unsigned char" explici
David Brown wrote:
> That's true in C, but C++ considers all three as separate types (C++
> is a little bit fussier about mixing types).
C99 does as well, but it doesn't enforce it in a strict way. An
application making assumptions about the signedness of the type "char"
is simply no longer ful
Preston Wilson wrote:
Sorry David for the second reply to you. I intended to reply to everyone.
"David VanHorn" wrote:
In C there are 3 char types. "char" "signed char" "unsigned char" so
maybe "char" isn't signed?
Ok, so that leaves me VERY confused..
Correct me if I'm wrong, but "sign
18 matches
Mail list logo
