Ryuichi Hayashida wrote:
> I think assertion message is very important reported when it fails. Should
> message be customizable as many assertions in other languages?
>
> assertEqual({exp}, {act} [, {msg}])
> assertFalse({actual} [, {msg}])
> assertTrue({actual} [, {msg}])
>
> This is used as below.
>
> assertTrue(check_something(label), 'something failed with ' . label)
Yes, I was planning on adding the optional message. It's just not that
easy to implement, so I left it for later. I had actually already set
the maximum argument count for that.
I assume that the position would still be prepended to the optional
message.
--
hundred-and-one symptoms of being an internet addict:
162. You go outside and look for a brightness knob to turn down the sun.
/// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
