Olivier Teuliere wrote:
> As Luc said, C tips will often be useful for C++,
> but the reverse may not be true (example:
> http://vim.wikia.com/wiki/Highlighting_of_method_names_in_the_definition)
I didn't notice anyone address my big problem:
By having C and C++ as separate categories, you force
a programmer to search BOTH categories.
If I were looking for tips on C, I just wouldn't trust that the editors had
correctly used category C++, so I'd have to search C and C++ categories.
I should mention that many years of C programming, and a smaller number of
years on C++, have made me rather cautious. I understand that C and C++ are
different, but if I wanted a C++ tip, I would have to search all the C tips
as well, and vice versa.
Olivier gave an example of a C++ only tip above, but it might actually be
quite helpful for a C programmer working with a bunch of typedefs or structs
etc. The reader would have to totally change the tip to make it applicable,
but the fact that you can tweak the syntax rules could be very useful.
OK, the tip could be very useful for someone editing cake recipes as well,
so I'll have to draw the line somewhere.
> it's our responsibility to use the correct categories for each tip.
The correct way to handle this is to have categories:
VimTip
LanguageSpecific
Cfamily
C
C++
C#
Does anyone want that complexity?
John
_______________________________________________
Vim-l mailing list
[email protected]
http://lists.wikia.com/mailman/listinfo/vim-l
