kiselgra

How bad do you think this would mess up regular code? Think of SBCL's `|List|`. Will such things be affected? They should be if some piece of code macroexpands to...

The rationale here is that stuff that should go after the argument list is specified, fittingly ;), after the c-mera argument list. The case of virtual makes this weird. We...

@lispbub Do you have an opinion on this?

With the exception of `virtual` my intention was to reflect the placement of those specifiers in C++. However, I see that the other point of view is also valid. In...

I'd also like to get rid of the whitespace after the name of a function when it is defined, e.g. ``` (function foo () -> void (return)) ``` gives ```...

When extending this, shoud we add base-classes to structs? This would make code using structs incompatible between cm-c and cm-c++. I think we have to define a c++ version of...

I think issuing a warning would be best thing to do. Changing the mapping of the name would probably lead to chaos :)

One thing, though, users will have to be aware anyhow, will they? E.g. there are functions that overlap via the standard libraries alreads, e.g., `sin` et al. But we can't...

I think you are now hitting the things that would make a README file into a manual :) We are actually working on something like that, but are swamped right...

Weirdly, you have to `set nolisp` for (the correctly working) `indentexpr` to work. If `lisp` (the vim option) is set, then it overrules `indentexpr`. Since an indentexpr is set by...