grip wrote:
Note: I have to type double quotes twice always and I
get two double quotes. I use backspace to remove one every time. A single
double quotes produces no output on the screen
This behaviour is coherent with the hypothesis that you're in fact using
the diaeresis key, and it
On Tue, 24 Feb 2009, Tim McDaniel wrote:
On Tue, 24 Feb 2009, grip wrote:
and so forth.
I just realized I've been forgetting this list's custom of ripping out
e-mail addresses, so I've sent out a bunch of unobfuscated ones
lately. My apologies.
--
Tim McDaniel, t...@panix.com
--
Unsubscrib
On Tue, 24 Feb 2009, Eric Blake wrote:
grip gmail.com> writes:
1. From the command prompt from windows, I tried this
- od -tx1
- " (Note: I have to type double quotes twice always
and I get two double quotes. I use backspace
to remove one e
grip gmail.com> writes:
> 1. From the command prompt from windows, I tried this
> - od -tx1
> - " (Note: I have to type double quotes twice always and I
> get two double quotes. I
> use backspace to remove one every time. A single
> double quotes produces n
Tim McDaniel panix.com> writes:
> On Tue, 24 Feb 2009, grip gmail.com> wrote:
> > 2. Output from od- tx1 -a test.c
> >
> > -BEGIN---
> > 000 23 69 6e 63 6c 75 64 65 20 3c 73 74 64 69 6f 2e
> > # i n c l u d e sp < s t d i
On Tue, 24 Feb 2009, grip wrote:
2. Output from od- tx1 -a test.c
-BEGIN---
000 23 69 6e 63 6c 75 64 65 20 3c 73 74 64 69 6f 2e
# i n c l u d e sp < s t d i o .
020 68 3e 0a 0a 69 6e 74 20 6d 61 69 6e 28 29 0a 20
Ok here are more clues and I think this should help you:
1. From the command prompt from windows, I tried this
- od -tx1
- " (Note: I have to type double quotes twice always and I
get two double quotes. I
use backspace to remove one every time. A single
do
Hi Dave and Tim
1. Output from od -tx1 test.c
-BEGIN---
000 23 69 6e 63 6c 75 64 65 20 3c 73 74 64 69 6f 2e
020 68 3e 0a 0a 69 6e 74 20 6d 61 69 6e 28 29 0a 20
040 7b 0a 70 72 69 6e 74 66 28 a8 54 65 73 74 20 74
060 68 69 73 a8 29
On Mon, 23 Feb 2009, Dave Korn wrote:
Nor do I, but let's see what's in that file: can you show us the
output you get from running "od -tx1 test.c" on your testcase
please, and tell us exactly what editor you used.
I personally prefer "od -tx1 -a test.c": it should add ASCII versions
of each
grip wrote:
> Hi
>
>> Don't use Microsoft Word to write C source files? The real question is,
>> how
>
> :) No, not using Word !!
:) I didn't think it was very likely really!
>> did the file get to be that way in the first place? Do you have an
>> unusual keyboard layout/mapping?
>
>
Hi
>
> Don't use Microsoft Word to write C source files? The real question is,
> how
:) No, not using Word !!
> did the file get to be that way in the first place? Do you have an
> unusual
> keyboard layout/mapping?
I have a Sun Keyboard.
And I did not do any keyboard mapping.
Some l
Hi
>
> Don't use Microsoft Word to write C source files? The real question is,
> how
:) No, not using Word !!
> did the file get to be that way in the first place? Do you have an
> unusual
> keyboard layout/mapping?
I have a Sun Keyboard.
And I did not do any keyboard mapping.
So
On Sun, 22 Feb 2009, Dave Korn wrote:
> grip wrote:
>
> > gcc test.c -o test.
> >
> > I get some strange errors which goes like:
> >
> > test.c: In function `main':
> > test.c:5: error: stray '\168' in program
> > test.c:5: error: `Test' undeclared (first use in this function)
> > test.c:5: err
grip wrote:
> gcc test.c -o test.
>
> I get some strange errors which goes like:
>
> test.c: In function `main':
> test.c:5: error: stray '\168' in program
> test.c:5: error: `Test' undeclared (first use in this function)
> test.c:5: error: (Each undeclared identifier is reported only once
>
Hi all
I am having trouble with gcc and the simplest of programs in C.
To test my gcc installation, I tried this program:
Code:
#include
int main()
{
printf("Test this") ;
return(0);
}
followed by
gcc test.c -o test.
I get some strange errors which goes lik
15 matches
Mail list logo
