[Oorexx-devel] The build machine
On Windows, trunk builds and the interpreter is relatively stable. I am building the installer package on my system without any problems. On the build machine, the Windows build fails and there is no log output or e-mail generated. I fixed the build yesterday so it builds fine using Visual C++ 6.0. So that is not the problem. Can we get that fixed? Or, is it just not working because David is migrating to the new site he posted yesterday? -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The build machine
All - I will try to debug this today. Thanks, W. David Ashley IBM Systems and Technology Group Lab Services Open Object Rexx Team Mobile Phone: 512-289-7506 Mark Miesfeld [EMAIL PROTECTED] omTo Sent by: ooRexx Dev List oorexx-devel-boun oorexx-devel@lists.sourceforge.net [EMAIL PROTECTED] orge.net cc Subject 07/18/2008 07:00 [Oorexx-devel] The build machine AM Please respond to Open Object Rexx Developer Mailing List [EMAIL PROTECTED] ts.sourceforge.ne t On Windows, trunk builds and the interpreter is relatively stable. I am building the installer package on my system without any problems. On the build machine, the Windows build fails and there is no log output or e-mail generated. I fixed the build yesterday so it builds fine using Visual C++ 6.0. So that is not the problem. Can we get that fixed? Or, is it just not working because David is migrating to the new site he posted yesterday? -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel inline: graycol.gifinline: pic05736.gifinline: ecblank.gif- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The build machine
On Fri, Jul 18, 2008 at 6:13 AM, David Ashley [EMAIL PROTECTED] wrote: I will try to debug this today. Thanks David. I'm not in a big rush about it, whenever you get a chance. I just wanted someone smarter than me to take a look at it sometime. grin The Fedora and Docs build works perfectly. The Ubuntu build always produces this message (since late last night): Downloads Build ooRexx RexxLA Valid HTML 4.01! Valid CSS! Build ooRexx Interpreter 3.x The background process is currently busy performing a build. The current time at the server is 18 Jul 2008 08:41:38 . So I suspect that the Ubuntu VM may just be hung. -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The build machine
Ok, there are two problems with the Windows build. 1. The build cannot locate some of the docs so it aborts the build. 2. There is a email problem (which I will fix). The Ubuntu build is fixed. Thanks, W. David Ashley IBM Systems and Technology Group Lab Services Open Object Rexx Team Mobile Phone: 512-289-7506 Mark Miesfeld [EMAIL PROTECTED] omTo Sent by: ooRexx Dev List oorexx-devel-boun oorexx-devel@lists.sourceforge.net [EMAIL PROTECTED] orge.net cc Subject 07/18/2008 07:00 [Oorexx-devel] The build machine AM Please respond to Open Object Rexx Developer Mailing List [EMAIL PROTECTED] ts.sourceforge.ne t On Windows, trunk builds and the interpreter is relatively stable. I am building the installer package on my system without any problems. On the build machine, the Windows build fails and there is no log output or e-mail generated. I fixed the build yesterday so it builds fine using Visual C++ 6.0. So that is not the problem. Can we get that fixed? Or, is it just not working because David is migrating to the new site he posted yesterday? -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel inline: graycol.gifinline: pic14478.gifinline: ecblank.gif- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The build machine
On Fri, Jul 18, 2008 at 7:19 AM, David Ashley [EMAIL PROTECTED] wrote: Ok, there are two problems with the Windows build. 1. The build cannot locate some of the docs so it aborts the build. makeorx for Windows has the option of specifying a static location to copy the docs from, into the build root. set DOC_LOCATION=C:\myDocs makeorx NODEBUG PACKAGE and makeorx NODEBUG PACKAGE C:\myDocs are equivalent commands. You can specify DOC_LOCATION either as an environment variable or on the command line. If you created a static location in the Windows VM and put a set of docs there, set DOC_LOCATION to point to that static location then the build would never fail. If you wanted to get really fancy, you could add a step to the Docs build to always copy the finished files to that static location. Then anytime the Docs were built, the static location would be updated with the latest docs. -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The build machine
On Fri, Jul 18, 2008 at 8:20 AM, Mark Miesfeld [EMAIL PROTECTED] wrote: On Fri, Jul 18, 2008 at 7:19 AM, David Ashley [EMAIL PROTECTED] wrote: Ok, there are two problems with the Windows build. 1. The build cannot locate some of the docs so it aborts the build. makeorx for Windows has the option of specifying a static location to copy the docs from, into the build root. set DOC_LOCATION=C:\myDocs makeorx NODEBUG PACKAGE and makeorx NODEBUG PACKAGE C:\myDocs are equivalent commands. You can specify DOC_LOCATION either as an environment variable or on the command line. Sorry, that was poorly worded. It should read: You can either put the DOC_LOCATION variable into the environment and point it at the static doc directory, or you can specify the doc directory as the third option on the command line to makeorx. -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The build machine
Mark - I don't think that is the problem. This all worked just fine for the 3.2 build. I think there is something wrong or some modification was made to the PACKAGE option. I run makeorx.bat BOTH PACKAGE AFTER I set the DOC_LOCATION environment variable. Thanks, W. David Ashley IBM Systems and Technology Group Lab Services Open Object Rexx Team Mobile Phone: 512-289-7506 Mark Miesfeld [EMAIL PROTECTED] omTo Sent by: Open Object Rexx Developer Mailing oorexx-devel-boun List [EMAIL PROTECTED] oorexx-devel@lists.sourceforge.net orge.net cc 07/18/2008 10:23 Subject AMRe: [Oorexx-devel] The build machine Please respond to Open Object Rexx Developer Mailing List [EMAIL PROTECTED] ts.sourceforge.ne t On Fri, Jul 18, 2008 at 8:20 AM, Mark Miesfeld [EMAIL PROTECTED] wrote: On Fri, Jul 18, 2008 at 7:19 AM, David Ashley [EMAIL PROTECTED] wrote: Ok, there are two problems with the Windows build. 1. The build cannot locate some of the docs so it aborts the build. makeorx for Windows has the option of specifying a static location to copy the docs from, into the build root. set DOC_LOCATION=C:\myDocs makeorx NODEBUG PACKAGE and makeorx NODEBUG PACKAGE C:\myDocs are equivalent commands. You can specify DOC_LOCATION either as an environment variable or on the command line. Sorry, that was poorly worded. It should read: You can either put the DOC_LOCATION variable into the environment and point it at the static doc directory, or you can specify the doc directory as the third option on the command line to makeorx. -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel inline: graycol.gifinline: pic28853.gifinline: ecblank.gif- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The build machine
On Fri, Jul 18, 2008 at 8:52 AM, David Ashley [EMAIL PROTECTED] wrote: I don't think that is the problem. This all worked just fine for the 3.2 build. I think there is something wrong or some modification was made to the PACKAGE option. I run makeorx.bat BOTH PACKAGE AFTER I set the DOC_LOCATION environment variable. Okay, I'll look at it. It seems to work fine in my local working copy. I'll try to see what the problem is. -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] The context class
We had a discussion a while back about the adding an implementation of a class that will retrieve the current execution context via the environment variable .CONTEXT. This now implemented in trunk, and here's the initial set of things I allow you to access via .CONTEXT: - package This is the package object that contains the currently executing thing (method or routine). The package object has a lot of capability within it for resolving packages, classes, routines, etc, as well as things like access to the source code for the package. - executable The .Routine or .Method object that's currently executing. I'm welcome discussion about the spelling of this method, as I'm not completely sure I like EXECUTABLE. We need something that can capture that this can be either a method or a routine. - digits The current context digits setting - form The current numeric form - fuzz The current numeric fuzz - args Retrieves the arguments used to invoke this context, as an array - condition Retrieves the current condition object for this context. Returns .nil if nothing has been trapped. - variables Returns a supplier that allows iteration through all of the current variables. This only returns top-level variables (i.e., simple variables and stems). Compound variables, of course, can be accessed by using stem object values associated with a stem variable. Some notes. 1) Currently, these are read-only values. I'm not sure I'm prepared to start down the slipperly slope of allowing this object to be used to changes settings/variables. I'm not totally opposed to it, but I'm erring on the side of caution for now. This class makes it fairly easy to add those capabilities in the future if we decide this would be a good thing. 2) The object returned by .CONTEXT is only valid as long as the context it was retrieved from is active. Invoking any of the RexxContext methods will raise an error if that context has been terminated. 3) Similarly, RexxContext objects cannot be copied. The copy() method will also raise an error. 4) Adding new stuff to this is fairly easy. If you see a need for something, speak up (particularly something that's basically read-onlysee note 1). Rick - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The context class
On Fri, Jul 18, 2008 at 1:39 PM, Mark Miesfeld [EMAIL PROTECTED] wrote: On Fri, Jul 18, 2008 at 9:41 AM, Rick McGuire [EMAIL PROTECTED] wrote: We had a discussion a while back about the adding an implementation of a class that will retrieve the current execution context via the environment variable .CONTEXT. This now implemented in trunk, and here's the initial set of things I allow you to access via .CONTEXT: Looks good Rick. ... - variables Returns a supplier that allows iteration through all of the current variables. This only returns top-level variables (i.e., simple variables and stems). Compound variables, of course, can be accessed by using stem object values associated with a stem variable. By top-level variables, you just mean not compound variables, right? In other words arrays, directories, etc.. are all top-level? arrays, directories, etc. are not VARIABLES, those are VALUES. For example, a = .array~new d = .directory~new s = Fred stem.1 = Rick stem.2 = Mark The variables that will be returned are A, D, S, and STEM.. The value of STEM. is a .stem object. The values of the simple variables will be whatever object they're assigned to. Some notes. 1) Currently, these are read-only values. I'm not sure I'm prepared to start down the slipperly slope of allowing this object to be used to changes settings/variables. I'm not totally opposed to it, but I'm erring on the side of caution for now. This class makes it fairly easy to add those capabilities in the future if we decide this would be a good thing. I think that is a good plan. Let's not start down the slippery slope until after 4.0.0. Maybe later we can create a sandbox area where you implement the function of allowing the settings / variables to be changed. Then Moritz, myself, and maybe some others that are interested could build from that sandbox to play around with it. To see if we shoot ourselves in the foot or not. grin 2) The object returned by .CONTEXT is only valid as long as the context it was retrieved from is active. Invoking any of the RexxContext methods will raise an error if that context has been terminated. Basically, this would mean within the scope of a method or routine? Or is the context a whole program? Say you had something like contextObj = .Context t = .Talker~new t~passObj(contextObj) context = t~passBackObj ? context good? ::class 'Talker' ::method passObj use strict arg myContext ? myContext good? ::method passBackObj context = .Context return context Is the .Context in a method just good withing that local scope of the method? Is the .Context at the top-level scope of the program, not good within the method? You can pass a context object FORWARD, but never BACKWARD. Thus call foo .context will pass my context object to an entity I call, and it can retrieve information from it. For example, the variable dumper that Les demoed at the Symposium that required interpret to execute can be done much easier by doing call variableDumper .context The variableDumper routine can access the object via USE ARG just like any other object and retrieve the variables. However, you cannot do this: return .context As soon as the return executes, this context will go stale, so any attempt on the part of the caller to use this will result in an error. Also, you had talked about this .Context object being available to external functions written using the native API. (I think you did, maybe I don't remember correctly.) How would you access it? It is not the context object that is passed automatically to the REXX_METHOD methods is it? (Or is it?) A lot of the methods implemented in the RexxCallContext API have directly analogs to what's available via .context. For example GetAllContextVariables() and GetContextDigits(). There were certain things that you could do from native code that you couldn't do from Rexx code. Of course, SetContextVariable() is still one place where there's a capability mismatch. There's one other slippery slope I've sidestepped, and that's the ability to request access to your caller's context. There are a number of nasties that can occur if you try to do that, including opening some potential security holes. I see there's a big difference between deciding to give a called routine access to all of my variables vs. having it just decide to grab it. -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] I'm going to be off the net the next couple of days.
On Fri, Jul 18, 2008 at 11:13 AM, Rick McGuire [EMAIL PROTECTED] wrote: Starting about 45 minutes from now, I'm going to be off the net until Sunday evening. Try not to stack up too many things for me to work on while I'm going :-) I think we still have some work to do on the Linux interpreter. I'll try to not find too many things until you are back. grin Have fun. -- Mark Miesfeld - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
