ped test group] [20080910 16:46:22.114000]
File: E:\work.ooRexx\ooRexxUnit\4.0\ooRexx\API\oo\FUNCTION.testGroup
The test container has no executable tests
This is a native API test and not included in the test types to execute.
[Skipped test group] [20080910 16:46:22.13]
File: E:\work.ooRexx\
On Wed, Sep 10, 2008 at 4:22 PM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> I'd like to experiment with the API tests. How do I get them to build and
> run on Windows?
Rick,
I'd check out my sandbox version, it is working well and is the entire
test suite. I'll merge back to the main branch sho
Mark,
I'd like to experiment with the API tests. How do I get them to build and
run on Windows?
Rick
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications w
/ooRexxUnit/4.0/bin/LINUX:
> SysLibrary::load() liborxfunction.so
> LD_LIBRARY_PATH=/work/tools/work.ooRexx/ooRexxUnit/4.0/bin/LINUX:
> ..
> Executing automated test suite..
> ...
>
> [Framework exception] [20080910 13:21:56.817778]
> File: /work/tools/work.ooRexx/oo
exxUnit/4.0/bin/LINUX:
..
Executing automated test suite..
...
[Framework exception] [20080910 13:21:56.817778]
File: /work/tools/work.ooRexx/ooRexxUnit/4.0/ooRexx/API/oo/METHOD.testGroup
Line: 74
Type: Trap Severity: Fatal
Unable to load library "orxmethod"
74 *-* package~loadP
On Wed, Sep 10, 2008 at 9:24 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> H, if the code that defines the external functions/methods needed are
> placed in a separate file, then the testGroup setup routine could use
>
> .context~package~loadPackage('commonApis.cls")
Rick, this is exactly
In poking around, I discovered that the RexxGTK code makes pretty extensive
use of float because the underlying toolkit use float. That's certainly a
good reason to keep that support there.
Rick
On Wed, Sep 10, 2008 at 7:38 AM, Mark Miesfeld <[EMAIL PROTECTED]> wrote:
> Rick,
>
> I'll take some
H, if the code that defines the external functions/methods needed are
placed in a separate file, then the testGroup setup routine could use
.context~package~loadPackage('commonApis.cls")
Which has the effect of being a ::REQUIRES load that's deferred until run
time. That should allow the
All -
First, I think I have figured out why we cannot set the LD_LIBRARY_PATH and
get it to work under Linux. This has to do with the way ooRexx 4.0 parses a
script on startup. If the interpreter finds the EXTERNAL subkeyword it
actually tries to load the library and check for the entry point. Th
Nothing that I'm aware of.
Rick
On Wed, Sep 10, 2008 at 9:15 AM, David Ruggles <[EMAIL PROTECTED]> wrote:
> I just want to confirm that ooRexx doesn't use the temp directory for
> anything by default, that is correct isn't it?
>
> Thanks,
>
> David Ruggles
> CCNA MCSE (NT) CNA A+
> Network Engine
I just want to confirm that ooRexx doesn't use the temp directory for
anything by default, that is correct isn't it?
Thanks,
David Ruggles
CCNA MCSE (NT) CNA A+
Network EngineerSafe Data, Inc.
(910) 285-7200 [EMAIL PROTECTED]
---
Well, if ObjectToNumber becomes ObjectToWholeNumber, then the obvious
choice for the unsigned one is ObjectToStringSize().
Rick
On Wed, Sep 10, 2008 at 7:38 AM, Mark Miesfeld <[EMAIL PROTECTED]> wrote:
> Rick,
>
> I'll take some time to digest this and probably come back later. But,
> since you
That's what started me down the path of thinking the name had a
problem. David had similar problems with it as well.
Rick
On Wed, Sep 10, 2008 at 8:00 AM, Mark Miesfeld <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 10, 2008 at 4:53 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
>
>> Well, if ObjectToNum
On Wed, Sep 10, 2008 at 4:53 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> Well, if ObjectToNumber becomes ObjectToWholeNumber, then the obvious
> choice for the unsigned one is ObjectToStringSize().
Yeah, that's good. I think those name changes are a good idea. As I
recall, ObjectToNumber() is
Rick,
I'll take some time to digest this and probably come back later. But,
since you did such a nice job of summarizing the open questions, there
are a few that I have a first reaction to.
> 1) Is it complete? I can't think of any others that might need to be added.
undecided.
> 2) Should
David and Rick,
Starting with David's foundation, I want to propose a few possible
changes and discuss some things related to the API tests.
I have a sandbox copy of the test framework / suite so I can implement
the possible changes and you can examine them without effecting the
actual test suite
>From my standpoint, not really a big issue. When running from .libs I
usually have to set LB_LIBRARY_PATH anyway. Whether I add one
directory or two is not a big deal.
Rick
On Wed, Sep 10, 2008 at 6:46 AM, Mark Miesfeld <[EMAIL PROTECTED]> wrote:
> David, Rick,
>
> I wanted to start a new thre
Since we're starting to get API tests written, I thought I'd do an
audit of the various integer types we expose in the APIs and make sure
they were still matching the original intent. I believe they are
still correct, but we might want to consider renaming a couple and
potentially adding some addi
David, Rick,
I wanted to start a new thread so, hopefully, things don't get to
convuleted. I actually have 2 related things I want to discuss, but
I'm going to do it in 2 separate e-mails, again so I don't get things
to complicated.
This is just about the LD_LIBRARY_PATH on Linux. It looks like
19 matches
Mail list logo
