Formally speaking, C99 (ISO/IEC 9899:1999) still refers to ANSI C
which does not tolerate the C++ style comment operator. If you don't
believe me, just pass whatever your compiler's strict ANSI compliance
flag is and see if it doesn't croak on them. Back in 1989, ANSI had not
yet conceded the
and
that includes no C++ style comments, but truly, I haven't tested that
assertion since I'd get crucified if I did. Maybe I'll try it before
checking something in.
Russ
Yakov Lerner wrote:
On 6/20/06, Russell Bateman [EMAIL PROTECTED] wrote:
Formally speaking, C99 (ISO/IEC 9899:1999) still
to mask out your comments and
avoid all the confusion? (that was a joke, I think)
Max
-Original Message-
From: Russell Bateman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 20, 2006 9:22 AM
To: Yakov Lerner
Cc: Vim List
Subject: Re: how to detect c99 vs c89 (//-comments vs /*-comments
I was unable to figure out how to do that. As the last line of my
Makefile.am I always put:
# vim: set tabstop=4 shiftwidth=4 noexpandtab:
since, by default, these guys around me (I'm the new guy) like expandtab
which, as you know, is problematic for makefiles.
Best,
Russ
John Orr wrote:
There is help for this as others have told you by now, but I'm sure you
just want to get going, so here's what I do. I only write in C/C++,
make, bash, HTML and Perl, etc. and not in other, assorted high-level
languages so I don't know its effect on them, but this setting, which I
have in my
http://www.satokar.com/viplugin/index.php?MMN_position=7:7
Not sure of the main page for this tool as I'm at work (where I don't
use Java), but I have it at home. This will get you there, though.
I am using this and it work fine. It's worth the paltry sum I paid for
it. It's not Vim, but
I systematically place a comment at the bottom of files that establishes
tabular format:
/* vim: set tabstop=2 shiftwidth=2: */
and even in scripts and other files:
# This enforces this script's tab settings...
# /* vim: set tabstop=2 shiftwidth=2: */
That way, the problem is solved for
Actually, a spell checker would not catch this mistake which, from a
spell checker's point of view, is one of mere usage, not spelling,
peak being a word for the top of a mountain. Any spell checker would
have let it pass without commentary. And since both words are nouns,
even Microsoft Word
Yakov,
I know how to do this, but the only example I have of it is at work and
I won't be there until tomorrow.
It involves putting something like this at the top or bottom of the file:
/*
* vim set tabstop 4:shiftwidth 3:autoindent */
Anything you can specify using set in ex will get
401 - 409 of 409 matches
Mail list logo
