From: Lee P. <le...@sa...> - 2007-10-31 16:54:02
|
Since many of the planned features of 4.0 are being made to the 3.3 release, will the 3.3 release be 64 bit? Lee |
From: Rick M. <obj...@gm...> - 2007-10-31 17:01:46
|
Not likely, but it will be closer. One of the biggest issues with making a full 64-bit version was the portability of the APIs. I'm not sure we'll be able to get all of that in place for a 3.3 release without stretching the release out longer than we should. I'd like to keep with a release early and often philosophy, so in about 6 months we should have another major release. That release is going to be heavy on internal changes and light on new function, but it will set the stage for a full 64-bit capable release. Rick On 10/31/07, Lee Peedin <le...@sa...> wrote: > > Since many of the planned features of 4.0 are being made to the 3.3release, will the > 3.3 release be > 64 bit? > > Lee > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Lee P. <le...@sa...> - 2007-10-31 17:05:42
|
OK, That what the "tasks" appeared to be doing - paving the way. Just wasn't sure if this was the intent of the 3.3 release. Trying to plan ahead such that the ooRexx Development Team has access via the RexxLA to a 64 bit machine when the time comes. :-) Lee Rick McGuire wrote: > Not likely, but it will be closer. One of the biggest issues with > making a full 64-bit version was the portability of the APIs. I'm not > sure we'll be able to get all of that in place for a 3.3 release without > stretching the release out longer than we should. I'd like to keep with > a release early and often philosophy, so in about 6 months we should > have another major release. That release is going to be heavy on > internal changes and light on new function, but it will set the stage > for a full 64-bit capable release. > > Rick > > On 10/31/07, *Lee Peedin* <le...@sa... > <mailto:le...@sa...>> wrote: > > Since many of the planned features of 4.0 are being made to the 3.3 > release, will the 3.3 release be > 64 bit? > > Lee > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > <http://get.splunk.com/> > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > <mailto:Oor...@li...> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel |
From: Rick M. <obj...@gm...> - 2007-10-31 17:09:42
|
I actually have a 64-bit laptop available to me here (bought it almost 3 years ago....haven't gotten nearly the use out of it I'd intended), but right now, I only have Linux on that. Access to a 64-bit Windows machine will be useful at some point. One of the tasks on the list is to make sure the code compiles cleanly as 64-bit code, which can be done with the current MS compilers on a 32-bit system. I already had the 4.0 prototype compiling cleanly with the 64-bit warnings enabled...and I am SO looking forward to doing that again :-) Rick On 10/31/07, Lee Peedin <le...@sa...> wrote: > > OK, > That what the "tasks" appeared to be doing - paving the way. Just wasn't > sure if this was the > intent of the 3.3 release. Trying to plan ahead such that the ooRexx > Development Team has access > via the RexxLA to a 64 bit machine when the time comes. :-) > > Lee > > Rick McGuire wrote: > > Not likely, but it will be closer. One of the biggest issues with > > making a full 64-bit version was the portability of the APIs. I'm not > > sure we'll be able to get all of that in place for a 3.3 release without > > stretching the release out longer than we should. I'd like to keep with > > a release early and often philosophy, so in about 6 months we should > > have another major release. That release is going to be heavy on > > internal changes and light on new function, but it will set the stage > > for a full 64-bit capable release. > > > > Rick > > > > On 10/31/07, *Lee Peedin* <le...@sa... > > <mailto:le...@sa...>> wrote: > > > > Since many of the planned features of 4.0 are being made to the 3.3 > > release, will the 3.3 release be > > 64 bit? > > > > Lee > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a > browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > <http://get.splunk.com/> > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > <mailto:Oor...@li...> > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Mark M. <mie...@gm...> - 2007-10-31 17:18:54
|
On 10/31/07, Rick McGuire <obj...@gm...> wrote: > I actually have a 64-bit laptop available to me here (bought it almost 3 > years ago....haven't gotten nearly the use out of it I'd intended), but > right now, I only have Linux on that. Access to a 64-bit Windows machine > will be useful at some point. One of the tasks on the list is to make sure > the code compiles cleanly as 64-bit code, which can be done with the current > MS compilers on a 32-bit system. I already had the 4.0 prototype compiling > cleanly with the 64-bit warnings enabled...and I am SO looking forward to > doing that again :-) I have several Intel 64-bit systems and versions of 64-bit XP (and Vista). My intent was to install a 64-bit Windows on at least one system, probably dual-boot. I just haven't got to it yet. It's just a matter of taking the time to reconfigure a system and do the install. -- Mark Miesfeld |
From: Lee P. <le...@sa...> - 2007-10-31 17:27:41
|
So it appears that we are "set" as far as "test systems" go. While the RexxLA doesn't have a lot of money, I'm sure (like the Build machine) that money could be raised for such a system if necessary. Lee Mark Miesfeld wrote: > On 10/31/07, Rick McGuire <obj...@gm...> wrote: > >> I actually have a 64-bit laptop available to me here (bought it almost 3 >> years ago....haven't gotten nearly the use out of it I'd intended), but >> right now, I only have Linux on that. Access to a 64-bit Windows machine >> will be useful at some point. One of the tasks on the list is to make sure >> the code compiles cleanly as 64-bit code, which can be done with the current >> MS compilers on a 32-bit system. I already had the 4.0 prototype compiling >> cleanly with the 64-bit warnings enabled...and I am SO looking forward to >> doing that again :-) > > I have several Intel 64-bit systems and versions of 64-bit XP (and > Vista). My intent was to install a 64-bit Windows on at least one > system, probably dual-boot. I just haven't got to it yet. > > It's just a matter of taking the time to reconfigure a system and do > the install. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Rick M. <obj...@gm...> - 2007-10-31 17:30:06
|
In addition to those systems, I suspect we have access to 64-bit capable AIX and OSX systems as well. Rick On 10/31/07, Lee Peedin <le...@sa...> wrote: > > So it appears that we are "set" as far as "test systems" go. While the > RexxLA doesn't have a lot of > money, I'm sure (like the Build machine) that money could be raised for > such a system if necessary. > > Lee > > Mark Miesfeld wrote: > > On 10/31/07, Rick McGuire <obj...@gm...> wrote: > > > >> I actually have a 64-bit laptop available to me here (bought it almost > 3 > >> years ago....haven't gotten nearly the use out of it I'd intended), but > >> right now, I only have Linux on that. Access to a 64-bit Windows > machine > >> will be useful at some point. One of the tasks on the list is to make > sure > >> the code compiles cleanly as 64-bit code, which can be done with the > current > >> MS compilers on a 32-bit system. I already had the 4.0 prototype > compiling > >> cleanly with the 64-bit warnings enabled...and I am SO looking forward > to > >> doing that again :-) > > > > I have several Intel 64-bit systems and versions of 64-bit XP (and > > Vista). My intent was to install a 64-bit Windows on at least one > > system, probably dual-boot. I just haven't got to it yet. > > > > It's just a matter of taking the time to reconfigure a system and do > > the install. > > > > -- > > Mark Miesfeld > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Lee P. <le...@sa...> - 2007-10-31 17:33:16
|
Rick McGuire wrote: > In addition to those systems, I suspect we have access to 64-bit capable > AIX and OSX systems as well. > > Rick > Sounding better all the time. Lee |
From: Rainer T. <ta...@ta...> - 2007-10-31 18:58:36
|
Hello, Rick McGuire wrote: > In addition to those systems, I suspect we have access to 64-bit > capable AIX Yes, I have access to 64-bit AIX 5.2 and 5.3 systems. I also have access to Visual Age C/C++ 6.0, XL C/C++ 8.0 and 9.0 on AIX. I hope that I will get my new 64-bit AIX development system in the next 4 - 6 weeks. I intend to install a AIX 6 beta on this system so I can check ooRexx on AIX 6. > and OSX systems as well. > > Rick > Bye Rainer > On 10/31/07, *Lee Peedin* < le...@sa... > <mailto:le...@sa...>> wrote: > > So it appears that we are "set" as far as "test systems" > go. While the RexxLA doesn't have a lot of > money, I'm sure (like the Build machine) that money could be > raised for such a system if necessary. > > Lee > > Mark Miesfeld wrote: > > On 10/31/07, Rick McGuire < obj...@gm... > <mailto:obj...@gm...>> wrote: > > > >> I actually have a 64-bit laptop available to me here (bought it > almost 3 > >> years ago....haven't gotten nearly the use out of it I'd > intended), but > >> right now, I only have Linux on that. Access to a 64-bit > Windows machine > >> will be useful at some point. One of the tasks on the list is > to make sure > >> the code compiles cleanly as 64-bit code, which can be done > with the current > >> MS compilers on a 32-bit system. I already had the 4.0 > prototype compiling > >> cleanly with the 64-bit warnings enabled...and I am SO looking > forward to > >> doing that again :-) > > > > I have several Intel 64-bit systems and versions of 64-bit XP (and > > Vista). My intent was to install a 64-bit Windows on at least one > > system, probably dual-boot. I just haven't got to it yet. > > > > It's just a matter of taking the time to reconfigure a system > and do > > the install. > > > > -- > > Mark Miesfeld > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a > browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > <mailto:Oor...@li...> > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > <mailto:Oor...@li...> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Rick M. <obj...@gm...> - 2007-10-31 17:26:38
|
Yeah, I've had similar thoughts....my only reservation about calling this 4.0 is we've always referred to the 4.0 release as being the "big one" that was 64-bit capable and had all of the new APIs. This next release is not going to live up to that expectation, so I'd be leery about calling it that if the delivered 4.0 didn't have all of that promised stuff. Rick On 10/31/07, Gil Barmwater <gi...@be...> wrote: > > It occurs to me that if release 3.3 is going to have significant > structural differences, at least internally, so that a script that has > been tokenized with 3.2 will not be executable, we should think about > calling the release 4.0. This would highlight to our user base that > they need to be sure that installing the new release does not > significantly impact their current operations. To me, a release name > like 3.3 indicates minor fixes and enhancements and would surprise me if > an existing working script that happened to be tokenized should fail to > execute. I might be more inclined to do some investigation before > dropping in the new release if it had a name like 4.0. Just my two > cents... > > Lee Peedin wrote: > > OK, > > That what the "tasks" appeared to be doing - paving the way. Just > wasn't sure if this was the > > intent of the 3.3 release. Trying to plan ahead such that the ooRexx > Development Team has access > > via the RexxLA to a 64 bit machine when the time comes. :-) > > > > Lee > > > > Rick McGuire wrote: > > > >>Not likely, but it will be closer. One of the biggest issues with > >>making a full 64-bit version was the portability of the APIs. I'm not > >>sure we'll be able to get all of that in place for a 3.3 release without > >>stretching the release out longer than we should. I'd like to keep with > >>a release early and often philosophy, so in about 6 months we should > >>have another major release. That release is going to be heavy on > >>internal changes and light on new function, but it will set the stage > >>for a full 64-bit capable release. > >> > >>Rick > >> > >>On 10/31/07, *Lee Peedin* <le...@sa... > >><mailto:le...@sa...>> wrote: > >> > >> Since many of the planned features of 4.0 are being made to the 3.3 > >> release, will the 3.3 release be > >> 64 bit? > >> > >> Lee > >> > > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Splunk Inc. > >> Still grepping through log files to find problems? Stop. > >> Now Search log events and configuration files using AJAX and a > browser. > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >> <http://get.splunk.com/> > >> _______________________________________________ > >> Oorexx-devel mailing list > >> Oor...@li... > >> <mailto:Oor...@li...> > >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > >> > >> > >> > >>------------------------------------------------------------------------ > >> > > >>------------------------------------------------------------------------- > >>This SF.net email is sponsored by: Splunk Inc. > >>Still grepping through log files to find problems? Stop. > >>Now Search log events and configuration files using AJAX and a browser. > >>Download your FREE copy of Splunk now >> http://get.splunk.com/ > >> > >> > >>------------------------------------------------------------------------ > >> > >>_______________________________________________ > >>Oorexx-devel mailing list > >>Oor...@li... > >>https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > -- > Gil Barmwater > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Lee P. <le...@sa...> - 2007-10-31 17:30:33
|
Rick, Gil mentioned this to me earlier this morning and we were wondering if there was any precedence for "skipping" a couple of sub-numbers. Example: 3.2 -> 3.5 Maybe that would at least prompt the "installer" to question/research before installing. Lee Rick McGuire wrote: > Yeah, I've had similar thoughts....my only reservation about calling > this 4.0 is we've always referred to the 4.0 release as being the "big > one" that was 64-bit capable and had all of the new APIs. This next > release is not going to live up to that expectation, so I'd be leery > about calling it that if the delivered 4.0 didn't have all of that > promised stuff. > > Rick > > On 10/31/07, *Gil Barmwater* <gi...@be... > <mailto:gi...@be...> > wrote: > > It occurs to me that if release 3.3 is going to have significant > structural differences, at least internally, so that a script that has > been tokenized with 3.2 will not be executable, we should think about > calling the release 4.0. This would highlight to our user base that > they need to be sure that installing the new release does not > significantly impact their current operations. To me, a release name > like 3.3 indicates minor fixes and enhancements and would surprise me if > an existing working script that happened to be tokenized should fail to > execute. I might be more inclined to do some investigation before > dropping in the new release if it had a name like 4.0. Just my two > cents... > > Lee Peedin wrote: > > OK, > > That what the "tasks" appeared to be doing - paving the > way. Just wasn't sure if this was the > > intent of the 3.3 release. Trying to plan ahead such that the > ooRexx Development Team has access > > via the RexxLA to a 64 bit machine when the time comes. :-) > > > > Lee > > > > Rick McGuire wrote: > > > >>Not likely, but it will be closer. One of the biggest issues with > >>making a full 64-bit version was the portability of the > APIs. I'm not > >>sure we'll be able to get all of that in place for a 3.3 release > without > >>stretching the release out longer than we should. I'd like to > keep with > >>a release early and often philosophy, so in about 6 months we should > >>have another major release. That release is going to be heavy on > >>internal changes and light on new function, but it will set the stage > >>for a full 64-bit capable release. > >> > >>Rick > >> > >>On 10/31/07, *Lee Peedin* < le...@sa... > <mailto:le...@sa...> > >><mailto:le...@sa... <mailto:le...@sa...>>> wrote: > >> > >> Since many of the planned features of 4.0 are being made to > the 3.3 > >> release, will the 3.3 release be > >> 64 bit? > >> > >> Lee > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Splunk Inc. > >> Still grepping through log files to find problems? Stop. > >> Now Search log events and configuration files using AJAX and > a browser. > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >> <http://get.splunk.com/> > >> _______________________________________________ > >> Oorexx-devel mailing list > >> Oor...@li... > <mailto:Oor...@li...> > >> <mailto:Oor...@li... > <mailto:Oor...@li...> > > >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > >> > >> > >> > >>------------------------------------------------------------------------ > > >> > >>------------------------------------------------------------------------- > >>This SF.net email is sponsored by: Splunk Inc. > >>Still grepping through log files to find problems? Stop. > >>Now Search log events and configuration files using AJAX and a > browser. > >>Download your FREE copy of Splunk now >> http://get.splunk.com/ > >> > >> > >>------------------------------------------------------------------------ > >> > >>_______________________________________________ > >>Oorexx-devel mailing list > >> Oor...@li... > <mailto:Oor...@li...> > >>https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a > browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > <mailto:Oor...@li...> > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > -- > Gil Barmwater > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > <mailto:Oor...@li...> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel |
From: Gil B. <gi...@be...> - 2007-10-31 17:15:50
|
It occurs to me that if release 3.3 is going to have significant structural differences, at least internally, so that a script that has been tokenized with 3.2 will not be executable, we should think about calling the release 4.0. This would highlight to our user base that they need to be sure that installing the new release does not significantly impact their current operations. To me, a release name like 3.3 indicates minor fixes and enhancements and would surprise me if an existing working script that happened to be tokenized should fail to execute. I might be more inclined to do some investigation before dropping in the new release if it had a name like 4.0. Just my two cents... Lee Peedin wrote: > OK, > That what the "tasks" appeared to be doing - paving the way. Just wasn't sure if this was the > intent of the 3.3 release. Trying to plan ahead such that the ooRexx Development Team has access > via the RexxLA to a 64 bit machine when the time comes. :-) > > Lee > > Rick McGuire wrote: > >>Not likely, but it will be closer. One of the biggest issues with >>making a full 64-bit version was the portability of the APIs. I'm not >>sure we'll be able to get all of that in place for a 3.3 release without >>stretching the release out longer than we should. I'd like to keep with >>a release early and often philosophy, so in about 6 months we should >>have another major release. That release is going to be heavy on >>internal changes and light on new function, but it will set the stage >>for a full 64-bit capable release. >> >>Rick >> >>On 10/31/07, *Lee Peedin* <le...@sa... >><mailto:le...@sa...>> wrote: >> >> Since many of the planned features of 4.0 are being made to the 3.3 >> release, will the 3.3 release be >> 64 bit? >> >> Lee >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> <http://get.splunk.com/> >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> <mailto:Oor...@li...> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >> >>------------------------------------------------------------------------ >> >>------------------------------------------------------------------------- >>This SF.net email is sponsored by: Splunk Inc. >>Still grepping through log files to find problems? Stop. >>Now Search log events and configuration files using AJAX and a browser. >>Download your FREE copy of Splunk now >> http://get.splunk.com/ >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>Oorexx-devel mailing list >>Oor...@li... >>https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Gil Barmwater |