|
From: beRt b. <beR...@al...> - 2005-01-13 07:50:45
|
I had a look on the assertEquals you implemented, and I have some
objections:
1. my existing code doesn't compile anymore
2. I expect assertEquals(new String ("test"), new String("test")) to
succeed, while I expect assertSame( new String ("test"), new
String("test")) to fail. Right now, I can't even use the assertEquals on
Strings...
Kind regards,
Bert.
Luke Bayes wrote:
> OK -
>
> I don't really feel too strongly either way. I just released the
> latest build of AsUnit (2.5) over the weekend with the requested
> change to call the "equals" method.
>
> If you don't want to enforce Comparable, or if you want to make the
> call to equals() optional, we might have to make some minor changes...
>
> There might be some problems in Flex and ultimately MTASC
> compatibility if we start calling optional methods... (not sure
> though)
>
> I definitely don't think it's too much to ask for someone to implement
> an Interface if they want to use a more advanced portion of the
> framework.
>
> Let me know what you folks want to do for the next release.
>
>
> Thanks,
>
>
> Luke Bayes
> www.asunit.com
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
|