Re: support for pre-C99 compilers

Bruno Haible <[email protected]>
Newsgroups gmane.lisp.clisp.devel
Message-ID <8442901.PxkMLb7zDp@omega>
Sam wrote:
> > removing 'varbrace' does not have a significant benefit.
> 
> The huge benefit is that C files will look like normal C.

This would not be a benefit. It would be a drawback.

During development, it is important to see all local variable declarations,
in an easy way.

With plain C syntax, neither Emacs nor kate can do this. Most probably, because
the C syntax is a bit ambiguous.

Whereas with 'var' syntax, editors can do this (see attached screenshot).

For this reason, plain C syntax without 'var' is inferior. Even if many people
use it.

> Removing varbrace and comment5 (what does "5" stand for, btw?) is just
> as important for CLISP as making cua-mode the default for Emacs. ;-)

You can remove comment5, if you or someone else converts the comments in the
remeining files (mostly lisparit.d and its include files) in a sensible way -
not in a cheap automated way.

I now prefer to write
  #if 0
   #define foo bar
  #endif
over
  # define foo bar
And comments are well highlighted in today's editors (because the C commment
syntax is unambiguous).

Bruno

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel
highlight.png (image/png, 120.1 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.