Ben Fritz wrote:
> I like the v:variable idea combined with enum. Then tests will be
> easier to read, calls easier to understand, and it will be hard to
> accidentally use the same id twice.
Keep in mind that there are hundreds of allocations, we would have to
come up with a nice name for each of them and make a table with all
those names as strings.
I like to run tests on an actual build, not a special "test build".
Thus the overhead would be in every Vim executable.
Well, it would be possible to put the enum in a .h file and add a Vim
script function to lookup the number in there.
That doesn't add more overhead for the executable, since enums are just
numbers. And we only need to define the name once.
--
NEIL INNES PLAYED: THE FIRST SELF-DESTRUCTIVE MONK, ROBIN'S LEAST FAVORITE
MINSTREL, THE PAGE CRUSHED BY A RABBIT, THE OWNER OF A DUCK
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
