[Mono-vb] Few more test cases
Anony Mous
Anon21h@yahoo.co.uk
Sun, 25 Jan 2004 11:15:07 +0000
Hi All,
Its been a while since I looked at mbas but its great to see work is
still progressing. I just wanted to suggest that we develop two sets of
test cases for each behaviour we are trying to test. One set is for
"Option Strict On" and the other should be for "Option Strict Off".
This is for scenarios like with the character literals test (see below)
where it would compile with "Option Strict Off" but not with "Option
Strict On".
Cheers,
Eric.
----------------------------------------------------------------
A Rafael D Teixeira wrote:
> On Fri, 2004-01-23 at 13:57, B Anirban wrote:
>
>>Hi Rafael,
>
>
> Hi Anirban,
>
>
>>Today I have added few more test cases under btests.
>
>
> Good,
>
>
>>During check-in I realized that last time The Test.Sources file didn't
>>get checked-in for some reason (my be I missed to add that in cvs).
>>Anyways, I found that you already placed one in place.
>>Today I added my Test.Sources file in place.
>>Please let me know if you have any concern with the file. In that case
>>we can revert back to your file.
>
>
> The Test.Sources is OK; but we have problems with some of the source
> files, for instance:
>
> CharacterLiterals1.vb
> ---------------------
>
> Module CharacterLiterals1
> Sub Main()
> Dim c As Char
> c = "x"
>
> Dim a As String = "X"c
> If a <> c Then
> Throw New System.Exception("a is not same as c")
> End If
> End Sub
> End Module
>
> Won't compile I corrected it to
>
> Module CharacterLiterals1
> Sub Main()
> Dim c As Char
> c = "x"c
> Dim a As String = "X"
> If a <> c Then
> Throw New System.Exception("a is not same as c")
> End If
> End Sub
> End Module
>
> Already in CVS.
>
>
>>Looking forward for your comments.
>
>
>>From looking briefly at the results file, I think other sources contain
> such errors, I recommend you to always compile with MS vbc in Windows,
> before committing sources to cvs. If that is not possible, double-check
> your coding with the syntax documentation in MSDN and try to understand
> what mbas is saying about the files, to figure if it is a mbas problem
> or a source problem.
>
>
>>Regards.
>>Anirban.
>
>
>>From the lookout, we have plenty of work ahead of us...
>
> Thanks Anirban,
>