On Tue, Jul 1, 2008 at 11:29 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> I was looking at what you've done for processing syntax errors in the
> CONSTANT directive test group, and I have some suggestions that might
> make these types of tests easier to manage. To start with, you can
> completely eliminate the need to write this to a file by using the new
> package class. For example,
>
> src = .array~new
> src[1] = "return 0"
> src[2] = ""
> src[3] = "::class 'TestClass'"
> src[4] = "::constant PI 3.14195"
> src[5] = "::constant ZERO 0.0"
> src[6] = "::constant PI 3.14195"
Will that looks good. Even though I saw the C++ PackageManager and
PackageClass while stepping through things in the debugger, I didn't
realize a new class had been added to what is available in Rexx code.
Are there any others?
> p = .package~new("test", src)
I like this a little better
::method test_x
<src creation>
self~expectSyntax(99.932)
p = .package~new("test", src)
> Also, it might be nice if this could be incorporated as part of the
> base infrastructure:
>
> self~assertSyntaxError(99.932, src)
Then this, I think
::method test_x
<src creation>
self~assertSyntaxError(99.932, src)
because the second will raise the syntax error within the
ooRexxUnit.cls file. I think, have to look at that code again. If it
does, we would loose some of the info on where the real error was.
--
Mark Miesfeld
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
