[Oorexx-devel] CMake build; MutableBuffer missing caselessPos
With a CMake build, the MutableBuffer class is missing caselessPos:
C:\work.ooRexx\wc\ooTest\4.x>qtest.rex
3 *-* say .mutablebuffer~new('Saturday')~caselessPos('da')
Error 97 running C:\work.ooRexx\wc\ooTest\4.x\qtest.rex line 3: Object
method not found
Error 97.1: Object "a MutableBuffer" does not understand message
"CASELESSPOS"
--
Mark Miesfeld
--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Suspect executables not getting built correctly ...
Well, both the release and debug flags need it. I don't know about any top level version. It did fix the crashes I was seeing. In the debug version at list, CMake has a -RTC1 flag that enables run time error checking. We weren't using that flag. This seems like a good flag to use, maybe. It has brought out 2 run time asserts, at least. The first one in rxmath.cpp, I fixed. (I think.) There is another in winsystm.cls I haven't got to yet. In rxmath.cpp it was using an uninitialized variable: result. I think the variable was supposed to be angle. You might want to check that fix. -- Mark Miesfeld On Sun, Jun 15, 2014 at 6:07 PM, Rick McGuire wrote: > I see you figured this out already. Was it really necessary to set the > _DEBUG and _RELEASE flags? I suspect the top level version would be > sufficient. > > Rick > > > On Sun, Jun 15, 2014 at 9:04 PM, Rick McGuire > wrote: > >> Ok, should be pretty easy to fix this. A few questions: >> >> 1) Does this apply to both .exes and .dlls? >> 2) Does it apply to all of the applicable types? >> 3) Is the option the same for both release and debug versions? >> >> Rick >> >> >> On Sun, Jun 15, 2014 at 6:36 PM, Mark Miesfeld >> wrote: >> >>> There is also a file in the make files directory, for example under >>> rexx.dir, flags.make. >>> >>> It shows: >>> >>> CXX_FLAGS = /DWIN32 /D_WINDOWS /W3 /GR /EHsc /D_DEBUG */MDd* /Zi /Ob0 >>> /Od /RTC1 -IC:\work.ooRexx\wc\main\api\platform\windows >>> -IC:\work.ooRexx\wc\main\api - >>> ... >>> >>> So, the DLLs are getting linked to the dynamic CRT library. ooRexx has >>> always linked to the static CRT library. While there are plenty of >>> arguments for linking one way or the other, I think switching now will >>> cause problems. Other than that, I believe that static linking is the >>> right choice to begin with. >>> >>> I think this one difference is causing the compiler to crash in the >>> current build. >>> >>> There are other differences in the flags, but I'm not sure if they are >>> important or not. >>> >>> I'll see if I can figure out how to change to /MTd from the current /MDd. >>> >>> -- >>> Mark Miesfeld >>> >>> >>> >>> On Sun, Jun 15, 2014 at 2:26 PM, Rick McGuire >>> wrote: >>> >>>> I don't have time to do the link, but adding an echo did work. Here is >>>> the value of the CXX_FLAGS for compiling the files in rexx.dll. I don't >>>> have time to compare these to the old build right now: >>>> >>>> CXX_FLAGS=/DWIN32 >>>> /D_WINDOWS >>>> /W3 >>>> /GR >>>> /EHsc >>>> /D_DEBUG >>>> /MDd >>>> /Zi >>>> /Ob0 >>>> /Od >>>> /RTC1 >>>> -Ic:\ORexxDev\oorexx\api\platform\windows >>>> -Ic:\ORexxDev\oorexx\api >>>> -IC:\ORexxDev\builds\install >>>> -Ic:\ORexxDev\oorexx\lib >>>> -Ic:\ORexxDev\oorexx\common >>>> -Ic:\ORexxDev\oorexx\common\platform\windows >>>> -Ic:\ORexxDev\oorexx\interpreter >>>> -Ic:\ORexxDev\oorexx\interpreter\behaviour >>>> -Ic:\ORexxDev\oorexx\interpreter\execution >>>> -Ic:\ORexxDev\oorexx\interpreter\memory >>>> -Ic:\ORexxDev\oorexx\interpreter\package >>>> -Ic:\ORexxDev\oorexx\interpreter\concurrency >>>> -Ic:\ORexxDev\oorexx\interpreter\expression >>>> -Ic:\ORexxDev\oorexx\interpreter\instructions >>>> -Ic:\ORexxDev\oorexx\interpreter\classes >>>> -Ic:\ORexxDev\oorexx\interpreter\classes\support >>>> -Ic:\ORexxDev\oorexx\interpreter\runtime >>>> -Ic:\ORexxDev\oorexx\interpreter\parser >>>> -Ic:\ORexxDev\oorexx\interpreter\messages >>>> -Ic:\ORexxDev\oorexx\interpreter\streamLibrary >>>> -Ic:\ORexxDev\oorexx\interpreter\platform\common >>>> -Ic:\ORexxDev\oorexx\interpreter\platform\windows >>>> -Ic:\ORexxDev\oorexx\rexxapi\client >>>> -Ic:\ORexxDev\oorexx\rexxapi\client\platform\windows >>>> -Ic:\ORexxDev\oorexx\rexxapi\common >>>> -Ic:\ORexxDev\oorexx\rexxapi\common\platform\windows >>>> >>>> Rick >>>> >>>> >>>> On Sun, Jun 15, 2014 at 5:21 PM, Rick McGuire >>>> wrote: >>>> >>>>> Shoot, I stand corrected. It appears nmake writes all of the options >>>>> to
Re: [Oorexx-devel] Suspect executables not getting built correctly ...
There is also a file in the make files directory, for example under rexx.dir, flags.make. It shows: CXX_FLAGS = /DWIN32 /D_WINDOWS /W3 /GR /EHsc /D_DEBUG */MDd* /Zi /Ob0 /Od /RTC1 -IC:\work.ooRexx\wc\main\api\platform\windows -IC:\work.ooRexx\wc\main\api - ... So, the DLLs are getting linked to the dynamic CRT library. ooRexx has always linked to the static CRT library. While there are plenty of arguments for linking one way or the other, I think switching now will cause problems. Other than that, I believe that static linking is the right choice to begin with. I think this one difference is causing the compiler to crash in the current build. There are other differences in the flags, but I'm not sure if they are important or not. I'll see if I can figure out how to change to /MTd from the current /MDd. -- Mark Miesfeld On Sun, Jun 15, 2014 at 2:26 PM, Rick McGuire wrote: > I don't have time to do the link, but adding an echo did work. Here is > the value of the CXX_FLAGS for compiling the files in rexx.dll. I don't > have time to compare these to the old build right now: > > CXX_FLAGS=/DWIN32 > /D_WINDOWS > /W3 > /GR > /EHsc > /D_DEBUG > /MDd > /Zi > /Ob0 > /Od > /RTC1 > -Ic:\ORexxDev\oorexx\api\platform\windows > -Ic:\ORexxDev\oorexx\api > -IC:\ORexxDev\builds\install > -Ic:\ORexxDev\oorexx\lib > -Ic:\ORexxDev\oorexx\common > -Ic:\ORexxDev\oorexx\common\platform\windows > -Ic:\ORexxDev\oorexx\interpreter > -Ic:\ORexxDev\oorexx\interpreter\behaviour > -Ic:\ORexxDev\oorexx\interpreter\execution > -Ic:\ORexxDev\oorexx\interpreter\memory > -Ic:\ORexxDev\oorexx\interpreter\package > -Ic:\ORexxDev\oorexx\interpreter\concurrency > -Ic:\ORexxDev\oorexx\interpreter\expression > -Ic:\ORexxDev\oorexx\interpreter\instructions > -Ic:\ORexxDev\oorexx\interpreter\classes > -Ic:\ORexxDev\oorexx\interpreter\classes\support > -Ic:\ORexxDev\oorexx\interpreter\runtime > -Ic:\ORexxDev\oorexx\interpreter\parser > -Ic:\ORexxDev\oorexx\interpreter\messages > -Ic:\ORexxDev\oorexx\interpreter\streamLibrary > -Ic:\ORexxDev\oorexx\interpreter\platform\common > -Ic:\ORexxDev\oorexx\interpreter\platform\windows > -Ic:\ORexxDev\oorexx\rexxapi\client > -Ic:\ORexxDev\oorexx\rexxapi\client\platform\windows > -Ic:\ORexxDev\oorexx\rexxapi\common > -Ic:\ORexxDev\oorexx\rexxapi\common\platform\windows > > Rick > > > On Sun, Jun 15, 2014 at 5:21 PM, Rick McGuire > wrote: > >> Shoot, I stand corrected. It appears nmake writes all of the options to >> a temp file and uses >> >> C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\cl.exe >> @C:\Users\RICKMC~1\AppData\L >> ocal\Temp\nm4144.tmp >> >> to invoke the compler and linker. The options are not showing up in >> verbose mode. This will probably require some digging in the make file. I >> need to leave fairly shortly and will be gone for the rest of the evening, >> however, each executable has a build.make file in a target dir. So, for >> example, rexx.dll is in CMakeFiles\rexx.dir. You might be able to add an >> echo instruction to the make file to display the current value of CXX_FLAGS >> to see what is getting used. We're pretty much using the defaults for the >> different profiles now, but they are easy to customize. >> >> Rick >> >> >> On Sun, Jun 15, 2014 at 5:10 PM, Mark Miesfeld >> wrote: >> >>> Thanks Rick. >>> >>> -- >>> Mark Miesfeld >>> >>> >>> On Sun, Jun 15, 2014 at 2:06 PM, Rick McGuire >>> wrote: >>> >>>> If you want to see what are getting used for the compile and links, you >>>> can specify "nmake VERBOSE=1", and it will display all of the commands that >>>> nmake is issuing. This allows you to see the exact commands getting issued >>>> for the build steps. >>>> >>>> Rick >>>> >>>> >>>> On Sun, Jun 15, 2014 at 4:37 PM, Mark Miesfeld >>>> wrote: >>>> >>>>> With the same code base, when I run the test suite against 4.3.0 built >>>>> with CMake, the interpreter crashes every time. Not always in the same >>>>> spot, but every time. >>>>> >>>>> Running the test suite against 4.3.0 built using the old .bat process, >>>>> the interpreter never crashes. It does have a lot of test failures, but >>>>> it >>>>> never crashes. (Maybe I shouldn't say never, but it is 0 out of 10.) >>>>> >>>>> I think maybe the CMake build is not using the correct compile/link >>>>> flags for ooRe
Re: [Oorexx-devel] Suspect executables not getting built correctly ...
Okay, yeah I discovered the temp files. Unfortunately during the build the files get deleted to fast to look at them. -- Mark Miesfeld On Sun, Jun 15, 2014 at 2:21 PM, Rick McGuire wrote: > Shoot, I stand corrected. It appears nmake writes all of the options to a > temp file and uses > > C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\cl.exe > @C:\Users\RICKMC~1\AppData\L > ocal\Temp\nm4144.tmp > > to invoke the compler and linker. The options are not showing up in > verbose mode. This will probably require some digging in the make file. I > need to leave fairly shortly and will be gone for the rest of the evening, > however, each executable has a build.make file in a target dir. So, for > example, rexx.dll is in CMakeFiles\rexx.dir. You might be able to add an > echo instruction to the make file to display the current value of CXX_FLAGS > to see what is getting used. We're pretty much using the defaults for the > different profiles now, but they are easy to customize. > > Rick > > > On Sun, Jun 15, 2014 at 5:10 PM, Mark Miesfeld wrote: > >> Thanks Rick. >> >> -- >> Mark Miesfeld >> >> >> On Sun, Jun 15, 2014 at 2:06 PM, Rick McGuire >> wrote: >> >>> If you want to see what are getting used for the compile and links, you >>> can specify "nmake VERBOSE=1", and it will display all of the commands that >>> nmake is issuing. This allows you to see the exact commands getting issued >>> for the build steps. >>> >>> Rick >>> >>> >>> On Sun, Jun 15, 2014 at 4:37 PM, Mark Miesfeld >>> wrote: >>> >>>> With the same code base, when I run the test suite against 4.3.0 built >>>> with CMake, the interpreter crashes every time. Not always in the same >>>> spot, but every time. >>>> >>>> Running the test suite against 4.3.0 built using the old .bat process, >>>> the interpreter never crashes. It does have a lot of test failures, but it >>>> never crashes. (Maybe I shouldn't say never, but it is 0 out of 10.) >>>> >>>> I think maybe the CMake build is not using the correct compile/link >>>> flags for ooRexx. Is there a way to display the command line during the >>>> comple/link phases? >>>> >>>> In particular, I believe, we will have problems if CMake is dynamically >>>> linking to the CRT. >>>> >>>> You can see that the executables are getting build different by just >>>> comparing the sizes of the files: >>>> >>>> CMake debug build: >>>> >>>> C:\Rexx>dir ooRexx\*.dll >>>> Volume in drive C is Win7 >>>> Volume Serial Number is D25E-50D5 >>>> >>>> Directory of C:\Rexx\ooRexx >>>> >>>> 06/15/2014 12:11 PM52,224 hostemu.dll >>>> 06/15/2014 12:12 PM 1,527,296 oodialog.dll >>>> 06/15/2014 12:12 PM 158,208 orexxole.dll >>>> 06/15/2014 12:11 PM 2,123,264 rexx.dll >>>> 06/15/2014 12:08 PM 215,040 rexxapi.dll >>>> 06/15/2014 12:12 PM 156,672 rexxutil.dll >>>> 06/15/2014 12:12 PM52,224 rxmath.dll >>>> 06/15/2014 12:12 PM58,368 rxregexp.dll >>>> 06/15/2014 12:12 PM81,920 rxsock.dll >>>> 06/15/2014 12:12 PM 154,112 rxwinsys.dll >>>> 10 File(s) 4,579,328 bytes >>>>0 Dir(s) 1,773,953,024 bytes free >>>> >>>> .bat file style build: >>>> >>>> C:\Rexx>dir ooRexx.4.3.0.debug-oldStyle\*.dll >>>> Volume in drive C is Win7 >>>> Volume Serial Number is D25E-50D5 >>>> >>>> Directory of C:\Rexx\ooRexx.4.3.0.debug-oldStyle >>>> >>>> 06/15/2014 09:54 AM 236,032 hostemu.dll >>>> 06/15/2014 09:55 AM 1,241,600 oodialog.dll >>>> 06/15/2014 09:54 AM 313,344 orexxole.dll >>>> 06/15/2014 09:54 AM 1,717,248 rexx.dll >>>> 06/15/2014 09:50 AM 372,736 rexxapi.dll >>>> 06/15/2014 09:54 AM 395,776 rexxutil.dll >>>> 06/15/2014 09:54 AM 289,792 rxmath.dll >>>> 06/15/2014 09:54 AM 195,584 rxregexp.dll >>>> 06/15/2014 09:54 AM 238,080 rxsock.dll >>>> 06/15/2014 09:54 AM 311,808 rxwinsys.dll >>>> 10 File(s) 5,312,000 bytes >>>>
Re: [Oorexx-devel] Suspect executables not getting built correctly ...
Thanks Rick. -- Mark Miesfeld On Sun, Jun 15, 2014 at 2:06 PM, Rick McGuire wrote: > If you want to see what are getting used for the compile and links, you > can specify "nmake VERBOSE=1", and it will display all of the commands that > nmake is issuing. This allows you to see the exact commands getting issued > for the build steps. > > Rick > > > On Sun, Jun 15, 2014 at 4:37 PM, Mark Miesfeld wrote: > >> With the same code base, when I run the test suite against 4.3.0 built >> with CMake, the interpreter crashes every time. Not always in the same >> spot, but every time. >> >> Running the test suite against 4.3.0 built using the old .bat process, >> the interpreter never crashes. It does have a lot of test failures, but it >> never crashes. (Maybe I shouldn't say never, but it is 0 out of 10.) >> >> I think maybe the CMake build is not using the correct compile/link flags >> for ooRexx. Is there a way to display the command line during the >> comple/link phases? >> >> In particular, I believe, we will have problems if CMake is dynamically >> linking to the CRT. >> >> You can see that the executables are getting build different by just >> comparing the sizes of the files: >> >> CMake debug build: >> >> C:\Rexx>dir ooRexx\*.dll >> Volume in drive C is Win7 >> Volume Serial Number is D25E-50D5 >> >> Directory of C:\Rexx\ooRexx >> >> 06/15/2014 12:11 PM52,224 hostemu.dll >> 06/15/2014 12:12 PM 1,527,296 oodialog.dll >> 06/15/2014 12:12 PM 158,208 orexxole.dll >> 06/15/2014 12:11 PM 2,123,264 rexx.dll >> 06/15/2014 12:08 PM 215,040 rexxapi.dll >> 06/15/2014 12:12 PM 156,672 rexxutil.dll >> 06/15/2014 12:12 PM52,224 rxmath.dll >> 06/15/2014 12:12 PM58,368 rxregexp.dll >> 06/15/2014 12:12 PM81,920 rxsock.dll >> 06/15/2014 12:12 PM 154,112 rxwinsys.dll >> 10 File(s) 4,579,328 bytes >>0 Dir(s) 1,773,953,024 bytes free >> >> .bat file style build: >> >> C:\Rexx>dir ooRexx.4.3.0.debug-oldStyle\*.dll >> Volume in drive C is Win7 >> Volume Serial Number is D25E-50D5 >> >> Directory of C:\Rexx\ooRexx.4.3.0.debug-oldStyle >> >> 06/15/2014 09:54 AM 236,032 hostemu.dll >> 06/15/2014 09:55 AM 1,241,600 oodialog.dll >> 06/15/2014 09:54 AM 313,344 orexxole.dll >> 06/15/2014 09:54 AM 1,717,248 rexx.dll >> 06/15/2014 09:50 AM 372,736 rexxapi.dll >> 06/15/2014 09:54 AM 395,776 rexxutil.dll >> 06/15/2014 09:54 AM 289,792 rxmath.dll >> 06/15/2014 09:54 AM 195,584 rxregexp.dll >> 06/15/2014 09:54 AM 238,080 rxsock.dll >> 06/15/2014 09:54 AM 311,808 rxwinsys.dll >> 10 File(s) 5,312,000 bytes >>0 Dir(s) 1,773,953,024 bytes free >> >> Looking at the CMake files, it looks to me like none of the extension >> DLLs are built as debug files. But, rexx.dll and oodialog.dll are much >> larger than the old style build, indicating the compile and/or link flags >> are different. >> >> makeorx works with the current head. It just leaves out some of the >> newer samples that Rick added. >> >> I used testOORexx.rex -B as the command line for the test suite. >> >> The CMake build will work with the test suite as long as you build an >> install package and install it. >> >> Otherwise, if you don't want to install the package, you can set >> REXX_HOME to point to the out-of-source build directory like this: >> >> set REXX_HOME=C:\work.ooRexx\wc\build.debug\NSIS\files\DevLib >> >> but, you have to at least build the NSIS installer for that to work. If >> things aren't right, when the external API libraries are built, the header >> files won't be found. >> >> -- >> Mark Miesfeld >> >> >> -- >> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions >> Find What Matters Most in Your Big Data with HPCC Systems >> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >> http://p.sf.net/sfu/hpccsystems >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sour
[Oorexx-devel] Suspect executables not getting built correctly ...
With the same code base, when I run the test suite against 4.3.0 built with CMake, the interpreter crashes every time. Not always in the same spot, but every time. Running the test suite against 4.3.0 built using the old .bat process, the interpreter never crashes. It does have a lot of test failures, but it never crashes. (Maybe I shouldn't say never, but it is 0 out of 10.) I think maybe the CMake build is not using the correct compile/link flags for ooRexx. Is there a way to display the command line during the comple/link phases? In particular, I believe, we will have problems if CMake is dynamically linking to the CRT. You can see that the executables are getting build different by just comparing the sizes of the files: CMake debug build: C:\Rexx>dir ooRexx\*.dll Volume in drive C is Win7 Volume Serial Number is D25E-50D5 Directory of C:\Rexx\ooRexx 06/15/2014 12:11 PM52,224 hostemu.dll 06/15/2014 12:12 PM 1,527,296 oodialog.dll 06/15/2014 12:12 PM 158,208 orexxole.dll 06/15/2014 12:11 PM 2,123,264 rexx.dll 06/15/2014 12:08 PM 215,040 rexxapi.dll 06/15/2014 12:12 PM 156,672 rexxutil.dll 06/15/2014 12:12 PM52,224 rxmath.dll 06/15/2014 12:12 PM58,368 rxregexp.dll 06/15/2014 12:12 PM81,920 rxsock.dll 06/15/2014 12:12 PM 154,112 rxwinsys.dll 10 File(s) 4,579,328 bytes 0 Dir(s) 1,773,953,024 bytes free .bat file style build: C:\Rexx>dir ooRexx.4.3.0.debug-oldStyle\*.dll Volume in drive C is Win7 Volume Serial Number is D25E-50D5 Directory of C:\Rexx\ooRexx.4.3.0.debug-oldStyle 06/15/2014 09:54 AM 236,032 hostemu.dll 06/15/2014 09:55 AM 1,241,600 oodialog.dll 06/15/2014 09:54 AM 313,344 orexxole.dll 06/15/2014 09:54 AM 1,717,248 rexx.dll 06/15/2014 09:50 AM 372,736 rexxapi.dll 06/15/2014 09:54 AM 395,776 rexxutil.dll 06/15/2014 09:54 AM 289,792 rxmath.dll 06/15/2014 09:54 AM 195,584 rxregexp.dll 06/15/2014 09:54 AM 238,080 rxsock.dll 06/15/2014 09:54 AM 311,808 rxwinsys.dll 10 File(s) 5,312,000 bytes 0 Dir(s) 1,773,953,024 bytes free Looking at the CMake files, it looks to me like none of the extension DLLs are built as debug files. But, rexx.dll and oodialog.dll are much larger than the old style build, indicating the compile and/or link flags are different. makeorx works with the current head. It just leaves out some of the newer samples that Rick added. I used testOORexx.rex -B as the command line for the test suite. The CMake build will work with the test suite as long as you build an install package and install it. Otherwise, if you don't want to install the package, you can set REXX_HOME to point to the out-of-source build directory like this: set REXX_HOME=C:\work.ooRexx\wc\build.debug\NSIS\files\DevLib but, you have to at least build the NSIS installer for that to work. If things aren't right, when the external API libraries are built, the header files won't be found. -- Mark Miesfeld -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Discuss: Embedding data into an ooRexx program.
This sounds pretty good. I confess it is not something that I have desired, but I can think of uses for it if it was available. -- Mark Miesfeld On Sat, Jun 14, 2014 at 6:42 AM, Rick McGuire wrote: > This is something I've been thinking about for some time, and we even have > a couple of RFEs open for something like this (though in fairness, I opened > one of these). On occasion, I find I'd like to write a program that needs > some associated data. Coding the data as a series of assignment statements > is a pain, and if you off-load the data into an external file, you run the > risk of the program and the data getting separated. It would be nice to be > able to include the data directly in the program. > > This can be kludged up a bit, in fact one of the samples I just created > uses this technique (see the timezone example, which embeds a timezone > table directly in the file. This works, but it has its drawbacks. For > example, the data in there is still subject to Rexx comment parsing rules, > so there are limits to what you can embed with this technique. It also > fails if you compile the code with rexxc, since it requires the use of > sourceline. > > What I'm thinking of is a new directive (Something like ::DATA, ::ASSET, > or ::RESOURCE...we can debate the spelling of the directive name later). > When encountered, it will consume all file lines without parsing until it > encounters a terminating delimiter. This is somewhat equivalent to the > CDATA directive in XML. We would need to define the rules for what that > delimiter is. As a first pass, I'd suggest something like ::ENDDATA (or > END, this depends on what we end up naming the directive. The > terminator must appear at the beginning of a line to be recognized. It > might be nice to support adding a name for matching up and also allowing > comments on the line, so I don't think we want to say something like "the > terminator must be the only thing on the line". > > Ideally, we should be to embed any text data inside the directive and the > terminator, including Rexx code. To facilitate that, we might want to be > able to specify the terminator name on the opening directive. > > For accessing this, right now I envision accessing these a methods of the > .Package class. I'm not particularly in favor of doing this via .local or > special variables. This mechanism is horribly overused and we run into > name conflicts every time we add something to it. > > One big question is how this data is returned. I can think of at least 3 > options that I'd want: 1) an array of lines, 2) a single string with > linends inserted or 3) a single string with the data all concatenated > together. The last would be handy for storing base64-encoded binary data. > An option on the directive specifying how this should be handled would be > nice...we'd need to decide on a default. I'd probably vote array of lines > currently. > > Since this would frequently be treated as an embedded file, I think a > class that acts as an in-memory input stream would be a nice addition here. > There are some prototypes of this in the incubator currently, the work > just needs to be completed. > > Like I said, I've been thinking about this for some time and I'm > constantly running into situations where I want this feature, so it might > be time to start discussing this for real. > > Rick > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Confused at where we are with CMake
On Thu, Jun 12, 2014 at 12:47 PM, Rick McGuire wrote: > I think it is ready to go, although it probably needs a round or two of > testing to make sure everything works. Right now, can build either of two > ways, the non-template based version you did (although this version is > probably out of date with respect to the samples) and the template-based > build I was working on. As far as I know, the template version is > complete. To build, first build via nmake, then issue "nmake > nsis_template_installer" to build it. > Okay, that's the piece I missed. I thought it was going to work by issuing CPack after issuing nmake to build the binaries. -- Mark Miesfeld -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Confused at where we are with CMake
I've gotten confused on the status of packaging on Windows. To create the NSIS package are we using CPack, going to use CPack but it isn't ready yet, or ... ? Thanks. -- Mark Miesfeld -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Are test suite adjustments needed for the cmake build?
Okay, thanks Rick. -- Mark Miesfeld On Thu, Jun 12, 2014 at 12:11 PM, Rick McGuire wrote: > Ok, I think rxregexp should be fixed now. There was a typo in the target > dependencies that prevented it using the .rc and .def file on the link. > The .def file was the kiss of death that prevented it from loading. > > Rick > > > On Thu, Jun 12, 2014 at 3:01 PM, Mark Miesfeld wrote: > >> I was taking a look a the test suit to fix this up if needed. Looking at >> the code, it seems setting REXX_API to point to: >> >> build\_CPack_Packages\win64\NSIS\ooRexx-4.3.0-win64\DevLib\api >> >> should work. >> >> But, I discovered that rxregexp.dll is not getting built correctly. so >> the test suite won't run. >> >> 48 *-* ::METHOD INIT EXTERNAL "LIBRARY rxregexp RegExp_Init" >> 4 *-* ::requires "rxregexp.cls" >> Error 98 running C:\Rexx\ooRexx\rxregexp.cls line 48: Execution error >> Error 98.903: Unable to load library "rxregexp" >> >> I'm not sure exactly what the problem is ... >> >> You can see something is wrong by right clicking on rxregexp.dll and >> selecting properties. Some of the properties are not filled in, like they >> are for some of the other DLLs, like rxsock.dll for instance. >> >> -- >> Mark Miesfeld >> >> >> >> On Thu, Jun 12, 2014 at 6:29 AM, Rick McGuire >> wrote: >> >>> I'm guessing there might need to be some adjustments made in the build >>> suite for locating information in out-of-source builds. For example, I'm >>> sure the process of locating the headers required for building the native >>> api tests will require adjustment. The readme doesn't give any hints about >>> environment variable requirements, so I'm not sure where to start. >>> >>> Rick >>> >>> >>> -- >>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions >>> Find What Matters Most in Your Big Data with HPCC Systems >>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >>> http://p.sf.net/sfu/hpccsystems >>> ___ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> >> >> >> -- >> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions >> Find What Matters Most in Your Big Data with HPCC Systems >> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >> http://p.sf.net/sfu/hpccsystems >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Are test suite adjustments needed for the cmake build?
I was taking a look a the test suit to fix this up if needed. Looking at the code, it seems setting REXX_API to point to: build\_CPack_Packages\win64\NSIS\ooRexx-4.3.0-win64\DevLib\api should work. But, I discovered that rxregexp.dll is not getting built correctly. so the test suite won't run. 48 *-* ::METHOD INIT EXTERNAL "LIBRARY rxregexp RegExp_Init" 4 *-* ::requires "rxregexp.cls" Error 98 running C:\Rexx\ooRexx\rxregexp.cls line 48: Execution error Error 98.903: Unable to load library "rxregexp" I'm not sure exactly what the problem is ... You can see something is wrong by right clicking on rxregexp.dll and selecting properties. Some of the properties are not filled in, like they are for some of the other DLLs, like rxsock.dll for instance. -- Mark Miesfeld On Thu, Jun 12, 2014 at 6:29 AM, Rick McGuire wrote: > I'm guessing there might need to be some adjustments made in the build > suite for locating information in out-of-source builds. For example, I'm > sure the process of locating the headers required for building the native > api tests will require adjustment. The readme doesn't give any hints about > environment variable requirements, so I'm not sure where to start. > > Rick > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Are test suite adjustments needed for the cmake build?
To locate the header files, the test suite uses the REXX_HOME variable, if I remember correctly. It also tries to locate the buildDir. So, you could set REXX_HOME to point to where the header, lib files are. I've got to go right now, the code is in ::routine locateAPIDir in building.frm. I'll look up how it works later. -- Mark Miesfeld On Thu, Jun 12, 2014 at 6:29 AM, Rick McGuire wrote: > I'm guessing there might need to be some adjustments made in the build > suite for locating information in out-of-source builds. For example, I'm > sure the process of locating the headers required for building the native > api tests will require adjustment. The readme doesn't give any hints about > environment variable requirements, so I'm not sure where to start. > > Rick > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The factor.rex sample program
Jon, I'm okay with adding the sample. Note that the rest of Rick's advice is pertinent. -- Mark Miesfeld On Wed, Jun 11, 2014 at 10:31 AM, Rick McGuire wrote: > Jon, > > You'll need to get Rony's permission, but I'm ok with that. Note that we > generally don't include author information in the code, so you'll need to > clean that sort of stuff up, although I would not be adverse to adding a > "originally contributed by" notice. > > Rick > > > On Wed, Jun 11, 2014 at 1:26 PM, Sahananda (Jon) Wolfers < > sahana...@windhorse.biz> wrote: > >> Hi Rick, >> >> glad to see this one. I always wondered who created classes on the fly. >> I say get rid of it. >> >> I'd like to add Rony's singleton meta-class and use_singleton script to >> the samples. Is that OK? >> >> Jon >> >> >> On 11 June 2014 18:05, Mark Miesfeld wrote: >> >>> I say go for it. Whatever you think is useful, go ahead and do it. >>> >>> -- >>> Mark Miesfeld >>> >>> >>> On Wed, Jun 11, 2014 at 10:00 AM, Rick McGuire >>> wrote: >>> >>>> I've been going through the samples and modernizing some of these >>>> samples. One of the samples, factor.rex, demonstrates some features that >>>> are really features I would hope that no programmer would ever use because >>>> the language directives are really the way to go. I'd like to delete this >>>> one...any objections? >>>> >>>> btw, I'm also going to add a few of the programs I wrote for Rosetta >>>> Code to the samples, the ones that illustrate some interesting ooRexx >>>> features. Other than the oodialog samples, the set of samples we have are >>>> really pretty stale. There are very few in there that I would refer >>>> someone too for an example of how to do something, so they really fail >>>> pretty badly in their usefulness. >>>> >>>> Rick >>>> >>>> >>>> -- >>>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk >>>> Solutions >>>> Find What Matters Most in Your Big Data with HPCC Systems >>>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >>>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >>>> http://p.sf.net/sfu/hpccsystems >>>> ___ >>>> Oorexx-devel mailing list >>>> Oorexx-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>> >>>> >>> >>> >>> -- >>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions >>> Find What Matters Most in Your Big Data with HPCC Systems >>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >>> http://p.sf.net/sfu/hpccsystems >>> ___ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> >> >> >> -- >> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions >> Find What Matters Most in Your Big Data with HPCC Systems >> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >> http://p.sf.net/sfu/hpccsystems >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] The factor.rex sample program
I say go for it. Whatever you think is useful, go ahead and do it. -- Mark Miesfeld On Wed, Jun 11, 2014 at 10:00 AM, Rick McGuire wrote: > I've been going through the samples and modernizing some of these samples. > One of the samples, factor.rex, demonstrates some features that are really > features I would hope that no programmer would ever use because the > language directives are really the way to go. I'd like to delete this > one...any objections? > > btw, I'm also going to add a few of the programs I wrote for Rosetta Code > to the samples, the ones that illustrate some interesting ooRexx features. > Other than the oodialog samples, the set of samples we have are really > pretty stale. There are very few in there that I would refer someone too > for an example of how to do something, so they really fail pretty badly in > their usefulness. > > Rick > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] A couple of questions about the NSIS script.
On Mon, Jun 9, 2014 at 1:45 PM, Rick McGuire wrote:
>
> On Mon, Jun 9, 2014 at 4:37 PM, Mark Miesfeld wrote:
>
>> On Mon, Jun 9, 2014 at 1:24 PM, Rick McGuire
>> wrote:
>>
>>> Spotted a couple of things about the how the NSIS script is currently
>>> set up:
>>>
>>> 1) We're setting the variable NODOTVER on the makensis command line,
>>> but I don't see any references to this in the script. Is this still needed?
>>>
>>
>> It was used for the exe name, i.e. ooRexx430-x86_64. I switched to using
>> 4.3.0.10145 instead. So, it's not needed anymore.
>>
> It's still being used in the .EXE file:
>
> OutFile "${SHORTNAME}.${VERSION}-${CPU}.exe"
>
>
No: makensis /DVERSION=x.x /DNODOTVER=xx ...
${VERSION} is the dotted version
>
> It is also being used to set a bitness value in the registry.
>
>
I think the CPU word is is used to set the bitness ...
>
>
>>
>>
>>> 2) The makensis command line is setting the variable CPU to either "x32"
>>> or "x64", but the script code is testing for the value "x86_64". One of
>>> these probably has to change...which one?
>>>
>>
>> It should be x86_64. A change I didn't notice in the new build process.
>>
>
> What should the 32-bit version be?
>
x86_32
--
Mark Miesfeld
--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] A couple of questions about the NSIS script.
On Mon, Jun 9, 2014 at 1:24 PM, Rick McGuire wrote: > Spotted a couple of things about the how the NSIS script is currently set > up: > > 1) We're setting the variable NODOTVER on the makensis command line, but > I don't see any references to this in the script. Is this still needed? > It was used for the exe name, i.e. ooRexx430-x86_64. I switched to using 4.3.0.10145 instead. So, it's not needed anymore. > 2) The makensis command line is setting the variable CPU to either "x32" > or "x64", but the script code is testing for the value "x86_64". One of > these probably has to change...which one? > It should be x86_64. A change I didn't notice in the new build process. -- Mark Miesfeld -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Future CPU Architecture Decisions
Jon, You don't need to be overly concerned with this, in my opinion. The ooRexx code base builds on both 32-bit and 64-bit Windows and will continue to build that way as long as your current machines are still running. -- Mark Miesfeld On Mon, Jun 9, 2014 at 12:03 PM, Sahananda (Jon) Wolfers < sahana...@windhorse.biz> wrote: > Just speaking for myself here: > > I have upwards of 70 machines I am responsible for running ooRexx on 32Bit > processors (Celeron 430, Pentium 4, Northwood, Celeron M320, Barias, > Coppermine etc..). > They are all running Windows OSs (Mainly the now defunct XP). > Nearly half of them are tills, so expensive to replace and built like > tanks to last forever. > > I think from what David said, the question is only about ending 32Bit > support on some or all linux distros, or is the suggestion to end all > support for 32bit ooRexx? > > thanks, > > Jon > > > > On 9 June 2014 18:50, David Ashley wrote: > >> The bottom line is that any library or application that is 32 bit only >> would not be usable in a 64 bit operating system. Perhaps the most >> obvious library is the IBM DB2 Rexx libraries. These are 32 bit only (no >> 64 bit libraries exist) and would not work on a 64 bit OS, no matter >> what version of ooRexx you would use with it. A replacement library >> would need to be found. >> >> Maybe this is also a good point to address Windows. At this point >> Microsoft has not announced anything about dropping support for 32 bit >> libraries/apps. So I think that we can safely assume Microsoft will >> continue to support 32 bit apps and libraries since the number of 32 bit >> only apps is still very large. Indeed, IMHO Microsoft may never be able >> to give up 32 bit support entirely. They are between their OS rock and >> their user apps hard place. >> >> David Ashley >> >> On Mon, 2014-06-09 at 18:19 +0100, Sahananda (Jon) Wolfers wrote: >> > Hi David >> > >> > >> > Could you just lay out for us what that would mean in terms of users >> > still on 32bit machines and also those reliant on extensions like rexx >> > \sql, rexxCurl etc. >> > >> > >> > thanks, >> > >> > >> > Jon >> >> >> >> >> >> -- >> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions >> Find What Matters Most in Your Big Data with HPCC Systems >> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. >> Leverages Graph Analysis for Fast Processing & Easy Data Exploration >> http://p.sf.net/sfu/hpccsystems >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > > > -- > HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions > Find What Matters Most in Your Big Data with HPCC Systems > Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. > Leverages Graph Analysis for Fast Processing & Easy Data Exploration > http://p.sf.net/sfu/hpccsystems > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] NSIS installer and CPack
On Mon, Jun 9, 2014 at 7:29 AM, Rick McGuire wrote: > > btw, do we still need the isNT tests in the .nsi file? We can eliminate > one include file if those are no longer needed. > We don't really need it. But, if we remove it, the section for setting the path needs to be fixed up, if I recall correctly. -- Mark Miesfeld -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://www.hpccsystems.com___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] NSIS installer and CPack
Rick, Okay. The configure_file() command looks promising. That's what I was trying to do yesterday by using a NSIS.template.in file that was a copy of our old oorexx.nsi file and just have variables for the /D options. But, it didn't work at all. -- Mark Miesfeld On Mon, Jun 9, 2014 at 2:50 AM, Rick McGuire wrote: > Mark, > > One of the difficulties with converting our file to an NSIS template was > getting around which variables in the template are done by directly > substituting variables from the CMake file and which ones are done via the > generator. In particular, the generator was causing me the biggest issues. > Now that I know how things are getting built, I believe it possible to > construct the file list and short cuts in CMake code and then use the > configure_file() command to create the .nsi from a template. This would > also eliminate the need to pass a bunch of -D values to the makensis > command...all of that would be handled by the template substitution. > > At any rate, that is a sandbox project, I think, but I believe it doable. > We should try to keep the install() commands in the CMake file as > up-to-date as possible, even though they are not doing anything for us at > the moment. > > Rick > > > On Sun, Jun 8, 2014 at 6:47 PM, Mark Miesfeld wrote: > >> Hi Rick, >> >> I just made a couple of small changes and your custom target now works. >> >> I don't think I have an objection to using the CPack version. >> >> Earlier today, I was thinking we could drive the installer creation from >> CPack by just using a NSIS.template.in file that was a copy of our >> current script and copying the files from platform/windows/install to the >> directory that NSIS.template.in is copied to. >> >> I'm not sure if that is what you are thinking of, or not. >> >> I'll play around with that and see if I can get it to work. >> >> -- >> Mark Miesfeld >> >> >> On Sun, Jun 8, 2014 at 3:19 PM, Rick McGuire >> wrote: >> >>> Mark, >>> >>> I've been poking around, and it might actually be possible to still >>> drive the install from CMake and still keep the current installer. I've >>> how to get access to the install information and it should be possible to >>> inject that information into a template install file. This is something >>> for the longer term, but this gets by all of your objections to switching >>> to the CPack version. The only thing that would change would be the >>> removal of the manifest and shortcut information from the .nsi file. >>> Everything else would remain the same. >>> >>> Rick >>> >>> Rick >>> >>> >>> On Sun, Jun 8, 2014 at 3:44 PM, Rick McGuire >>> wrote: >>> >>>> Mark, >>>> >>>> I was right, it was pretty easy to add this as a build target (assuming >>>> I got the command syntax right). To build the installer, just issue the >>>> command "nmake nsis_installer" from the build directory command line. This >>>> is setup with dependencies on the doc files being in an indicated directory >>>> and is currently assuming the script is platform\windows\cpack.nsi. >>>> Hopefully the I have the makensis command syntax correct, but that should >>>> be easy to fix. >>>> >>>> Rick >>>> >>>> >>>> On Sun, Jun 8, 2014 at 2:52 PM, Rick McGuire >>>> wrote: >>>> >>>>> Ok, I guess I'm good with that. Since we need to tweak this a bit, I >>>>> suggest we leave oorexx.nsi unchanged and check in a new file to build >>>>> from >>>>> (and I agree, a custom script might not be a bad idea). A batch file is a >>>>> good idea here, although I wonder if we can add a to the cmake script that >>>>> is not part of the ALL category so that this becomes an NMAKE target we >>>>> can >>>>> invoke from the build directory in question. The cmake script already >>>>> knows about the locations for everything, and we can probably build in a >>>>> dependency for the doc files so it will refuse to build without the files >>>>> there. >>>>> >>>>> I just checked in a change to the cmake script to copy those >>>>> additional class files (and rexxtry) to the bin directory. For >>>>> test/development purposes, it makes sense for those to be part of the >>>>> build
Re: [Oorexx-devel] Fwd: [Oorexx-svn] SF.net SVN: oorexx-code-0:[10144] main/trunk/CMakeLists.txt
Okay, I've added the cpack.nsi file.
--
Mark Miesfeld
On Sun, Jun 8, 2014 at 4:09 PM, Mark Miesfeld wrote:
> I screwed that up. Give me a few minutes to fix it up.
>
> --
> Mark Miesfeld
>
>
> On Sun, Jun 8, 2014 at 4:05 PM, Mark Miesfeld wrote:
>
>> Yes, I should have. I'll do that now.
>>
>> --
>> Mark Miesfeld
>>
>>
>> On Sun, Jun 8, 2014 at 3:59 PM, Rick McGuire
>> wrote:
>>
>>> Mark,
>>>
>>> did you need to checkin the cpack.nsi file with this commit?
>>>
>>> Rick
>>>
>>>
>>> -- Forwarded message --
>>> From:
>>> Date: Sun, Jun 8, 2014 at 6:27 PM
>>> Subject: [Oorexx-svn] SF.net SVN: oorexx-code-0:[10144]
>>> main/trunk/CMakeLists.txt
>>> To: oorexx-...@lists.sourceforge.net
>>>
>>>
>>> Revision: 10144
>>> http://sourceforge.net/p/oorexx/code-0/10144
>>> Author: miesfeld
>>> Date: 2014-06-08 22:27:52 + (Sun, 08 Jun 2014)
>>> Log Message:
>>> ---
>>> Fix up the Windows custom nsis_installer target so it works
>>>
>>> Modified Paths:
>>> --
>>> main/trunk/CMakeLists.txt
>>>
>>> Modified: main/trunk/CMakeLists.txt
>>> ===
>>> --- main/trunk/CMakeLists.txt 2014-06-08 22:12:46 UTC (rev 10143)
>>> +++ main/trunk/CMakeLists.txt 2014-06-08 22:27:52 UTC (rev 10144)
>>> @@ -85,6 +85,7 @@
>>> ENDMACRO(Subversion_GET_REVISION)
>>>
>>> Subversion_GET_REVISION(${CMAKE_SOURCE_DIR} ORX_BLD_LVL)
>>> +set (ORX_VERSION_NSIS
>>> ${ORX_MAJOR}.${ORX_MINOR}.${ORX_MOD_LVL}.${ORX_BLD_LVL})
>>> endif ()
>>>
>>> message(STATUS "SVN Revision Number is ${ORX_BLD_LVL}")
>>> @@ -1392,7 +1393,7 @@
>>> # directories in native form first
>>>
>>> file(TO_NATIVE_PATH ${CMAKE_CURRENT_SOURCE_DIR} NATIVE_SOURCE_DIR)
>>> - file(TO_NATIVE_PATH ${CMAKE_CURRENT_BINARY_DIR} NATIVE_BINARY_DIR)
>>> + file(TO_NATIVE_PATH ${CMAKE_CURRENT_BINARY_DIR}/bin
>>> NATIVE_BINARY_DIR)
>>>
>>> add_custom_target(nsis_installer
>>>DEPENDS ${DOC_SOURCE_DIR}/readme.pdf
>>> @@ -1407,7 +1408,7 @@
>>>${DOC_SOURCE_DIR}/winextensions.pdf
>>>${build_platform_dir}/install/cpack.nsi
>>>VERBATIM
>>> - COMMAND ${NSIS_EXECUTABLE} "/DVERSION=${ORX_VERSION}
>>> /DNODOTVER=${ORX_NODOT_VERSION} /DSRCDIR=${NATIVE_SOURCE_DIR}
>>> /DBINDIR=${NATIVE_BINARY_DIR} /DCPU=${CPU} cpack.nsi"
>>> + COMMAND ${NSIS_EXECUTABLE} /DVERSION=${ORX_VERSION_NSIS}
>>> /DNODOTVER=${ORX_NODOT_VERSION} /DSRCDIR=${NATIVE_SOURCE_DIR}
>>> /DBINDIR=${NATIVE_BINARY_DIR} /DCPU=${CPU} cpack.nsi
>>>WORKING_DIRECTORY
>>> ${CMAKE_CURRENT_SOURCE_DIR}/${build_platform_dir}/install
>>>COMMENT "Building NSIS installer")
>>> endif()
>>>
>>>
>>>
>>> --
>>> Learn Graph Databases - Download FREE O'Reilly Book
>>> "Graph Databases" is the definitive new guide to graph databases and
>>> their
>>> applications. Written by three acclaimed leaders in the field,
>>> this first edition is now available. Download your free book today!
>>> http://p.sf.net/sfu/NeoTech
>>> ___
>>> Oorexx-svn mailing list
>>> oorexx-...@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-svn
>>>
>>>
>>>
>>> --
>>> Learn Graph Databases - Download FREE O'Reilly Book
>>> "Graph Databases" is the definitive new guide to graph databases and
>>> their
>>> applications. Written by three acclaimed leaders in the field,
>>> this first edition is now available. Download your free book today!
>>> http://p.sf.net/sfu/NeoTech
>>> ___
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>>>
>>
>
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Fwd: [Oorexx-svn] SF.net SVN: oorexx-code-0:[10144] main/trunk/CMakeLists.txt
I screwed that up. Give me a few minutes to fix it up.
--
Mark Miesfeld
On Sun, Jun 8, 2014 at 4:05 PM, Mark Miesfeld wrote:
> Yes, I should have. I'll do that now.
>
> --
> Mark Miesfeld
>
>
> On Sun, Jun 8, 2014 at 3:59 PM, Rick McGuire
> wrote:
>
>> Mark,
>>
>> did you need to checkin the cpack.nsi file with this commit?
>>
>> Rick
>>
>>
>> -- Forwarded message --
>> From:
>> Date: Sun, Jun 8, 2014 at 6:27 PM
>> Subject: [Oorexx-svn] SF.net SVN: oorexx-code-0:[10144]
>> main/trunk/CMakeLists.txt
>> To: oorexx-...@lists.sourceforge.net
>>
>>
>> Revision: 10144
>> http://sourceforge.net/p/oorexx/code-0/10144
>> Author: miesfeld
>> Date: 2014-06-08 22:27:52 + (Sun, 08 Jun 2014)
>> Log Message:
>> ---
>> Fix up the Windows custom nsis_installer target so it works
>>
>> Modified Paths:
>> --
>> main/trunk/CMakeLists.txt
>>
>> Modified: main/trunk/CMakeLists.txt
>> ===
>> --- main/trunk/CMakeLists.txt 2014-06-08 22:12:46 UTC (rev 10143)
>> +++ main/trunk/CMakeLists.txt 2014-06-08 22:27:52 UTC (rev 10144)
>> @@ -85,6 +85,7 @@
>> ENDMACRO(Subversion_GET_REVISION)
>>
>> Subversion_GET_REVISION(${CMAKE_SOURCE_DIR} ORX_BLD_LVL)
>> +set (ORX_VERSION_NSIS
>> ${ORX_MAJOR}.${ORX_MINOR}.${ORX_MOD_LVL}.${ORX_BLD_LVL})
>> endif ()
>>
>> message(STATUS "SVN Revision Number is ${ORX_BLD_LVL}")
>> @@ -1392,7 +1393,7 @@
>> # directories in native form first
>>
>> file(TO_NATIVE_PATH ${CMAKE_CURRENT_SOURCE_DIR} NATIVE_SOURCE_DIR)
>> - file(TO_NATIVE_PATH ${CMAKE_CURRENT_BINARY_DIR} NATIVE_BINARY_DIR)
>> + file(TO_NATIVE_PATH ${CMAKE_CURRENT_BINARY_DIR}/bin NATIVE_BINARY_DIR)
>>
>> add_custom_target(nsis_installer
>>DEPENDS ${DOC_SOURCE_DIR}/readme.pdf
>> @@ -1407,7 +1408,7 @@
>>${DOC_SOURCE_DIR}/winextensions.pdf
>>${build_platform_dir}/install/cpack.nsi
>>VERBATIM
>> - COMMAND ${NSIS_EXECUTABLE} "/DVERSION=${ORX_VERSION}
>> /DNODOTVER=${ORX_NODOT_VERSION} /DSRCDIR=${NATIVE_SOURCE_DIR}
>> /DBINDIR=${NATIVE_BINARY_DIR} /DCPU=${CPU} cpack.nsi"
>> + COMMAND ${NSIS_EXECUTABLE} /DVERSION=${ORX_VERSION_NSIS}
>> /DNODOTVER=${ORX_NODOT_VERSION} /DSRCDIR=${NATIVE_SOURCE_DIR}
>> /DBINDIR=${NATIVE_BINARY_DIR} /DCPU=${CPU} cpack.nsi
>>WORKING_DIRECTORY
>> ${CMAKE_CURRENT_SOURCE_DIR}/${build_platform_dir}/install
>>COMMENT "Building NSIS installer")
>> endif()
>>
>>
>>
>> --
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> ___
>> Oorexx-svn mailing list
>> oorexx-...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-svn
>>
>>
>>
>> --
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Fwd: [Oorexx-svn] SF.net SVN: oorexx-code-0:[10144] main/trunk/CMakeLists.txt
Yes, I should have. I'll do that now.
--
Mark Miesfeld
On Sun, Jun 8, 2014 at 3:59 PM, Rick McGuire wrote:
> Mark,
>
> did you need to checkin the cpack.nsi file with this commit?
>
> Rick
>
>
> -- Forwarded message --
> From:
> Date: Sun, Jun 8, 2014 at 6:27 PM
> Subject: [Oorexx-svn] SF.net SVN: oorexx-code-0:[10144]
> main/trunk/CMakeLists.txt
> To: oorexx-...@lists.sourceforge.net
>
>
> Revision: 10144
> http://sourceforge.net/p/oorexx/code-0/10144
> Author: miesfeld
> Date: 2014-06-08 22:27:52 + (Sun, 08 Jun 2014)
> Log Message:
> ---
> Fix up the Windows custom nsis_installer target so it works
>
> Modified Paths:
> --
> main/trunk/CMakeLists.txt
>
> Modified: main/trunk/CMakeLists.txt
> ===
> --- main/trunk/CMakeLists.txt 2014-06-08 22:12:46 UTC (rev 10143)
> +++ main/trunk/CMakeLists.txt 2014-06-08 22:27:52 UTC (rev 10144)
> @@ -85,6 +85,7 @@
> ENDMACRO(Subversion_GET_REVISION)
>
> Subversion_GET_REVISION(${CMAKE_SOURCE_DIR} ORX_BLD_LVL)
> +set (ORX_VERSION_NSIS
> ${ORX_MAJOR}.${ORX_MINOR}.${ORX_MOD_LVL}.${ORX_BLD_LVL})
> endif ()
>
> message(STATUS "SVN Revision Number is ${ORX_BLD_LVL}")
> @@ -1392,7 +1393,7 @@
> # directories in native form first
>
> file(TO_NATIVE_PATH ${CMAKE_CURRENT_SOURCE_DIR} NATIVE_SOURCE_DIR)
> - file(TO_NATIVE_PATH ${CMAKE_CURRENT_BINARY_DIR} NATIVE_BINARY_DIR)
> + file(TO_NATIVE_PATH ${CMAKE_CURRENT_BINARY_DIR}/bin NATIVE_BINARY_DIR)
>
> add_custom_target(nsis_installer
>DEPENDS ${DOC_SOURCE_DIR}/readme.pdf
> @@ -1407,7 +1408,7 @@
>${DOC_SOURCE_DIR}/winextensions.pdf
>${build_platform_dir}/install/cpack.nsi
>VERBATIM
> - COMMAND ${NSIS_EXECUTABLE} "/DVERSION=${ORX_VERSION}
> /DNODOTVER=${ORX_NODOT_VERSION} /DSRCDIR=${NATIVE_SOURCE_DIR}
> /DBINDIR=${NATIVE_BINARY_DIR} /DCPU=${CPU} cpack.nsi"
> + COMMAND ${NSIS_EXECUTABLE} /DVERSION=${ORX_VERSION_NSIS}
> /DNODOTVER=${ORX_NODOT_VERSION} /DSRCDIR=${NATIVE_SOURCE_DIR}
> /DBINDIR=${NATIVE_BINARY_DIR} /DCPU=${CPU} cpack.nsi
>WORKING_DIRECTORY
> ${CMAKE_CURRENT_SOURCE_DIR}/${build_platform_dir}/install
>COMMENT "Building NSIS installer")
> endif()
>
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> ___
> Oorexx-svn mailing list
> oorexx-...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-svn
>
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] NSIS installer and CPack
Hi Rick, I just made a couple of small changes and your custom target now works. I don't think I have an objection to using the CPack version. Earlier today, I was thinking we could drive the installer creation from CPack by just using a NSIS.template.in file that was a copy of our current script and copying the files from platform/windows/install to the directory that NSIS.template.in is copied to. I'm not sure if that is what you are thinking of, or not. I'll play around with that and see if I can get it to work. -- Mark Miesfeld On Sun, Jun 8, 2014 at 3:19 PM, Rick McGuire wrote: > Mark, > > I've been poking around, and it might actually be possible to still drive > the install from CMake and still keep the current installer. I've how to > get access to the install information and it should be possible to inject > that information into a template install file. This is something for the > longer term, but this gets by all of your objections to switching to the > CPack version. The only thing that would change would be the removal of > the manifest and shortcut information from the .nsi file. Everything else > would remain the same. > > Rick > > Rick > > > On Sun, Jun 8, 2014 at 3:44 PM, Rick McGuire > wrote: > >> Mark, >> >> I was right, it was pretty easy to add this as a build target (assuming I >> got the command syntax right). To build the installer, just issue the >> command "nmake nsis_installer" from the build directory command line. This >> is setup with dependencies on the doc files being in an indicated directory >> and is currently assuming the script is platform\windows\cpack.nsi. >> Hopefully the I have the makensis command syntax correct, but that should >> be easy to fix. >> >> Rick >> >> >> On Sun, Jun 8, 2014 at 2:52 PM, Rick McGuire >> wrote: >> >>> Ok, I guess I'm good with that. Since we need to tweak this a bit, I >>> suggest we leave oorexx.nsi unchanged and check in a new file to build from >>> (and I agree, a custom script might not be a bad idea). A batch file is a >>> good idea here, although I wonder if we can add a to the cmake script that >>> is not part of the ALL category so that this becomes an NMAKE target we can >>> invoke from the build directory in question. The cmake script already >>> knows about the locations for everything, and we can probably build in a >>> dependency for the doc files so it will refuse to build without the files >>> there. >>> >>> I just checked in a change to the cmake script to copy those additional >>> class files (and rexxtry) to the bin directory. For test/development >>> purposes, it makes sense for those to be part of the build. >>> >>> Rick >>> >>> >>> On Sun, Jun 8, 2014 at 2:19 PM, Mark Miesfeld >>> wrote: >>> >>>> Sorry I wasn't engaged in this topic earlier. But, I don't agree with >>>> the approach we've taken with this. >>>> >>>> We have a perfectly good NSIS script that produces the NSIS installer >>>> on Windows. This script has been refined over the years until it is at the >>>> point it is today. >>>> >>>> I think we should just stick with it. >>>> >>>> It took me about an hour to get it working with the CPack build. It >>>> doesn't make any changes to the way the non-CPack NSIS installer worked. >>>> And most of the time was because the CPack build isn't including some of >>>> the *.cls files yet. socket.cls, csvStream.cls, etc.. Also there was a >>>> change to the API samples directory that was included in the the current >>>> oorexx.nsi script >>>> >>>> It is slightly awkward because you need to cd from the build directory >>>> to the source directory and then run a long command line: >>>> >>>> *C:\work.ooRexx\wc\build>cd >>>> \work.ooRexx\wc\main\platform\windows\install* >>>> >>>> *C:\work.ooRexx\wc\main\platform\windows\install>* >>>> >>>> *C:\work.ooRexx\wc\main\platform\windows\install>makensis >>>> /DVERSION=4.3.0 /DNODOTVER=430 /DSRCDIR=c:\work.ooRexx\wc\m* >>>> *ain /DBINDIR=C:\work.ooRexx\wc\build\bin /DCPU=x64 cpack.nsi* >>>> >>>> That could be fixed with a simple Rexx or .bat script. >>>> >>>> Using a CPack generated NSIS script has, I believe, some problems that >>>>
[Oorexx-devel] NSIS installer and CPack
Sorry I wasn't engaged in this topic earlier. But, I don't agree with the approach we've taken with this. We have a perfectly good NSIS script that produces the NSIS installer on Windows. This script has been refined over the years until it is at the point it is today. I think we should just stick with it. It took me about an hour to get it working with the CPack build. It doesn't make any changes to the way the non-CPack NSIS installer worked. And most of the time was because the CPack build isn't including some of the *.cls files yet. socket.cls, csvStream.cls, etc.. Also there was a change to the API samples directory that was included in the the current oorexx.nsi script It is slightly awkward because you need to cd from the build directory to the source directory and then run a long command line: *C:\work.ooRexx\wc\build>cd \work.ooRexx\wc\main\platform\windows\install* *C:\work.ooRexx\wc\main\platform\windows\install>* *C:\work.ooRexx\wc\main\platform\windows\install>makensis /DVERSION=4.3.0 /DNODOTVER=430 /DSRCDIR=c:\work.ooRexx\wc\m* *ain /DBINDIR=C:\work.ooRexx\wc\build\bin /DCPU=x64 cpack.nsi* That could be fixed with a simple Rexx or .bat script. Using a CPack generated NSIS script has, I believe, some problems that will force the next Windows installer to behave differently. 1.) We have the bin files being placed in a different directory. 2.) The CPack NSIS script writes the uninstall information to a different registry location. This will be a problem with the automatic uninstallation of an existing install. It will also cause problems with the "upgrade" option on Windows. Both of these can probably be fixed by checking both registry locations. But, still, that is a good bit of added work. I know Rick has put in a lot of time on a CPack generated NSIS script. But, I think there is still a lot of time that needs to be spent on it. I'm in favor of just sticking with our current script. -- Mark Miesfeld -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Some more CPack NSIS questions/problems.
On Fri, Jun 6, 2014 at 4:08 PM, Rick McGuire wrote: > I'm getting a deeper understanding of how the NSIS generator works, and I > think I'm going to need to scrap my current working template and start over > using the default NSIS template as a starting point. Rather than trying to > convert our current install into a template, I believe it is necessary to > add in all of our extras to the current template. > I think that probably makes the most sense. > There are aspects of the NSIS generator that we really can't replace, > particularly the parts that generate the lists of installed files. > That's the one part of a NSIS install that is probably the same for any package and so is probably what the CMake people would concentrate on. -- Mark Miesfeld -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] rexx.exe manifest file and cmake.
On Wed, May 21, 2014 at 2:39 PM, Rick McGuire wrote: > Yep, I caught that. I had also added it to rexxc.exe because I didn't > understand what it was for. That one can be removed. > > Btw, I see ooDialog has a .exe file and a .com file. I think I've got > those building correctly, but I'm not sure I understand what the .com file > is for. I'm also adding the manifest to that one. > The .com file is essentially to allow: C:\work.ooRexx>oodialog -v ooDialog 4.2.4.10010 C:\work.ooRexx> The .com file runs first and parses the command line. If the command line indicates a GUI application is needed, it restarts itself as oodialog.exe. oodialog.exe is linked as subsystem:windows, while oodialog.com is linked as subsystem:Console So, I don't think oodialog.com needs the manifest, but I don't remember for sure. It would depend on if oodialog.exe is started as a separate process or created as a child process. Which I don't remember off the top of my head. -- Mark Miesfeld -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] rexx.exe manifest file and cmake.
On Wed, May 21, 2014 at 2:29 PM, Rick McGuire wrote: > Mark, > > Thanks for the answer. I did find a solution for this. It turns out to > possible to replace or merge additional manifest information into the > executables as a post-processing step. I wasn't really sure which .exe > files needed this, so I end up merging it into them all. If only ooDialog > needs this, then that can simplify things in the cmake file considerably > since I had to add a lot of WIN32 conditional stuff to do this. > It is actually all the executables that would run an ooDialog program. So, rexx.exe, rexxhide.exe, rexxpaws.exe and oodialog.exe need the manifest. With the common controls dependency part I posted. -- Mark Miesfeld > > Rick > > > On Wed, May 21, 2014 at 5:17 PM, Mark Miesfeld wrote: > >> Hi Rick, >> >> I'm still traveling and only have good Internet once in awhile. So I've >> put off answering this. But thought I'd better do something about it. >> >> The existing manifest was only needed for ooDialog. The important part >> is the part to load the 6.0 common controls library: >> >> Open Object Rexx Interpreter. >> >> >> > type="win32" >> name="Microsoft.Windows.Common-Controls" >> version="6.0.0.0" >> processorArchitecture="amd64" >> publicKeyToken="6595b64144ccf1df" >> language="*" >> /> >> >> >> >> Since that is needed by any Windows GUI application to use the 6.0, or >> later, version of the library, it seems odd to me that CMake wouldn't have >> a way to do it, if it is generating its own manifest. Without it, the >> pre-verison 6.0 is loaded automatically, which is essentially W2K controls. >> >> It took me quite a bit of work to get it working originally. It needs to >> be the manifest of the executable that loads the ooDialog extension, which >> I didn't understand when I first started with it. I thought it was >> sufficient to use it for ooDialog.dll. >> >> So, if we can't get CMake to add the common controls part to the manifest >> it generates, then I'll have to add the custom step. I won't be back at >> home until after Memorial day. I'll work on it then if you haven't already >> come up with something. >> >> -- >> Mark Miesfeld >> >> >> >> On Mon, May 5, 2014 at 4:17 AM, Rick McGuire wrote: >> >>> This is mostly to get this question recorded for Mark for when he gets >>> back from vacation. >>> >>> I'm currently running into some issues with the manifest file we're >>> embedding in rexx.exe via an include within rexx.rc. Building this via >>> this method causes a duplicate resource error because the cmake build tools >>> generate a default manifest which gets embedded via the /MANIFEST and >>> /MANIFESTFILE linker options. When the .rc file pulls in the second >>> manifest, this creates the error. >>> >>> For now, I've commented out the link in rexx.rc that pulls in the >>> manifest file, so the cmake build is using the one it generates. For the >>> existing build, I've switched to rexx.mak file to use /MANIFEST and >>> /MANIFESTFILE link options. We're going to run into this same issue with >>> the oodialog executables when we get that portion working in cmake as well. >>> I really don't understand the manifests and what information needs to be >>> in there. The cmake-generated manifests and the ones we are using are >>> quite different. Here is our version: >>> >>> >>> >>> >> version="1.0.0.0" >>> processorArchitecture="amd64" >>> name="RexxLA.ooRexx.rexx" >>> type="win32" >>> /> >>> Open Object Rexx Interpreter. >>> >>> >>> >> type="win32" >>> name="Microsoft.Windows.Common-Controls" >>> version="6.0.0.0" >>> processorArchitecture="amd64" >>> publicKeyToken="6595b64144ccf1df" >>> language="*" >>> /> >>> >>> >>> >>> >>> >>> and here is the cmake version: >>> >>> >>> >>> >>>
Re: [Oorexx-devel] rexx.exe manifest file and cmake.
Hi Rick, I'm still traveling and only have good Internet once in awhile. So I've put off answering this. But thought I'd better do something about it. The existing manifest was only needed for ooDialog. The important part is the part to load the 6.0 common controls library: Open Object Rexx Interpreter. Since that is needed by any Windows GUI application to use the 6.0, or later, version of the library, it seems odd to me that CMake wouldn't have a way to do it, if it is generating its own manifest. Without it, the pre-verison 6.0 is loaded automatically, which is essentially W2K controls. It took me quite a bit of work to get it working originally. It needs to be the manifest of the executable that loads the ooDialog extension, which I didn't understand when I first started with it. I thought it was sufficient to use it for ooDialog.dll. So, if we can't get CMake to add the common controls part to the manifest it generates, then I'll have to add the custom step. I won't be back at home until after Memorial day. I'll work on it then if you haven't already come up with something. -- Mark Miesfeld On Mon, May 5, 2014 at 4:17 AM, Rick McGuire wrote: > This is mostly to get this question recorded for Mark for when he gets > back from vacation. > > I'm currently running into some issues with the manifest file we're > embedding in rexx.exe via an include within rexx.rc. Building this via > this method causes a duplicate resource error because the cmake build tools > generate a default manifest which gets embedded via the /MANIFEST and > /MANIFESTFILE linker options. When the .rc file pulls in the second > manifest, this creates the error. > > For now, I've commented out the link in rexx.rc that pulls in the manifest > file, so the cmake build is using the one it generates. For the existing > build, I've switched to rexx.mak file to use /MANIFEST and /MANIFESTFILE > link options. We're going to run into this same issue with the oodialog > executables when we get that portion working in cmake as well. I really > don't understand the manifests and what information needs to be in there. > The cmake-generated manifests and the ones we are using are quite > different. Here is our version: > > > > version="1.0.0.0" > processorArchitecture="amd64" > name="RexxLA.ooRexx.rexx" > type="win32" > /> > Open Object Rexx Interpreter. > > > type="win32" > name="Microsoft.Windows.Common-Controls" > version="6.0.0.0" > processorArchitecture="amd64" > publicKeyToken="6595b64144ccf1df" > language="*" > /> > > > > > > and here is the cmake version: > > > > > > > > > > > > > > Note that cmake generates one of these for all of the dlls and exes. > > > So, do we need to continue using our manifest version or can just allow the > cmake defaults? Does the cmake version cause any problems with the other > files? I've found information on how to use custom manifests, which involves > disabling the automatic generation and then adding a post-processing step > that uses a tool to add the custom manifest. A bit of a pain, but doable. I > think I'd prefer to let cmake do the heavy lifting if we can. > > > Rick > > > > -- > Is your legacy SCM system holding you back? Join Perforce May 7 to find > out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] CMake deb
Hi David, Well, it looks like being slow works our pretty well. It seems this is fixed. ;-) -- Mark Miesfeld On Mon, May 19, 2014 at 1:55 PM, David Ashley wrote: > Mark - > > If you get some time please look at the CMake for a deb output install > file. Currently, it does not work. > > 1. The files all get installed. > 2. The post install script does NOT get run. > 3. The install fails quietly because the installer is showing it is not > installed. > > The steps are: > 1. Check out the svn trunk > 2. From your build subdir run "cmake -DBUILD_DEB /path/to/oorexx/source > 3. Then run "make ./" > 4. Now run "cpack ./" > > The deb file should be in your current directory (your build dir). > > I am not sure what I am missing. I got the rpm build working in short > order but the deb build has me stumped. > > David Ashley > > > > -- > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] NSIS versions used for ooRexx and CPack
Hi Rick, It must be something CPack is doing. You'll have to use the regular install and then unzip the long string version over the top of it, I guess. On May 17, 2014 3:27 PM, "Rick McGuire" wrote: Mark, Made my first attempt at generating an NSIS install using CMake, and it failed terribly because the NSIS build I'm using is the longstring download that doesn't have an install step. CPack is looking for some NSIS registry entries, which obviously don't exist. Do you know if there is an official NSIS install that has that longstring fix? Rick -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Pondering redoing the Windows build process
Sounds like a reasonable project. I'd say go for the single file to start with. -- Mark Miesfeld On Mon, Apr 21, 2014 at 6:24 AM, Rick McGuire wrote: > I've not liked the lack of dependency management in the makefiles used for > building Windows for quite a while. David spent quite a bit of time trying > to get a Windows build working with autoconf and never really got things > working. I'm sort of thinking we might be able to do this as a manual > process by taking the Makefile generated for Linux and manually converting > it into a Windows makefile. At first glance, this doesn't really look to > be that bad. There are a lot of changes to make, but mostly of the > repetitive variety. Once converted, we'll have a make file with all of the > dependencies created. This will still need to manually updated in the > future, but we'll have a make file that operates better than the one we're > using now (which for all intents, is 25 years old). Hopefully, we'll be > able to keep this skewing too much from the autoconf generated one. It > might even be an interesting exercise to write a tool to sync the > dependencies up again. Left as a exercise to the reader! I'm willing to > take a crack at converting to see if this is workable. > > The autoconf generated make file builds all of the project from the single > makefile, while on Windows, we have separate makefiles for each of the > subprojects (e.g., various extensions like rxsock, rxmath, etc.). I can go > either way on the port, though I suspect as a first step, I'll create a > combined make. Note that this will not cover the Windows-only extensions > because the Linux Makefile does not have anything generated for those > directories. Any opinions on the single file/multiple file question? > > Rick > > > -- > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] condition('CODE') S*O*L*V*E*D
On Sun, Apr 6, 2014 at 1:20 PM, Walter Pachl wrote: > SOLVED: > ... > > Reading helps :-) > That's what I keep telling you. ;-) -- Mark Miesfeld -- ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] rxMath -> rxm.class help sought
Walter,
A good use of your skills. I commend you on your work. But, I can't over
any help.
--
Mark Miesfeld
On Sat, Apr 5, 2014 at 9:53 AM, Walter Pachl
wrote:
> Rxm
>5 March 2014
>
>
>
> The distribution of ooRexx contains a function package called rxMath that
> provides the computation of trigonometric and some other functions.
>
> Based on the underlying c-library the precision of the returned values is
> limited to 16 digits.
>
> Close observation show that sometimes the last one or two digits of the
> returned values are not correct.
>
> Many years ago I experimented with implementing these functions in Rexx
> with its virtually unlimited precision.
>
> The rxm class is intended to provide the same functionality as rxMath with
> no limit on the specified or implied precision.
>
> While I tried to get full compatibility there remain a few (actually very
> few) differences:
>
>
>
> - RxCalcTan(90) raises the Syntax condition
>
> - rxCalcexp(x) limits x to 709. or so.
>
>
>
> Handling of syntactically incorrect arguments is still to be finished!
>
>
>
> The program testexp.rex shows what I have coded so far.
>
> You can see the 3 discrepancies when comparing rxm and rxMath.
>
> The surprise (disappointment) is that *condition('D')* returns nothing
> whatsoever
>
>
>
> Any help / advice / critique would be highly appreciated
>
>
>
> Thanks
>
>
>
> Walter
>
>
>
> PS rxmexp etc. will eventually be changed to rxCalcexp to become
> compatible with rxMath!
>
>
>
>
>
> Find the program at
>
> https://www.dropbox.com/sh/9v939j55ikderfx/SYLv80C-wP?n=132389230
>
>
>
>
> --
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
--
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] orxsock6 - Initial development Complete
I haven't even tried to build it on Windows yet. Two of my systems died in the same week, and I've been constrained for time. I just glanced at it and it looks like it needs a nMake make file. -- Mark Miesfeld On Tue, Mar 18, 2014 at 5:57 AM, Rick McGuire wrote: > Is this buildable on Windows yet? I'd like to try playing around with > this some. > > Rick > > > On Fri, Mar 7, 2014 at 8:07 PM, Mark Miesfeld wrote: > >> Hi Jon, >> >> I was going to try to do a Windows build tomorrow if I have time. If I >> do build the Windows library I'll let you know. Then it will be easy. ;-) >> >> -- >> Mark Miesfeld >> >> >> >> On Fri, Mar 7, 2014 at 12:49 PM, Sahananda (Jon) Wolfers < >> sahana...@windhorse.biz> wrote: >> >>> OK. I just thought there was something easy there I could do to help. >>> >>> Jon >>> >>> >>> On 7 March 2014 19:14, Mark Miesfeld wrote: >>> >>>> Jon, >>>> >>>> It is probably a Linux build of the library. We would need a Windows >>>> build of the library. >>>> >>>> -- >>>> Mark Miesfeld >>>> >>>> >>>> >>>> On Fri, Mar 7, 2014 at 10:40 AM, Sahananda (Jon) Wolfers < >>>> sahana...@windhorse.biz> wrote: >>>> >>>>> Hi David, >>>>> >>>>> Do you need to do any setup to run the tests? >>>>> This is what I get just trying to run test1 from your sandbox folder >>>>> on Windows7 >>>>> >>>>> hth Jon >>>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> *C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orxsock6>rexx >>>>>> -v Open Object Rexx Version 4.2.0Build date: Feb 22 2014Addressing Mode: >>>>>> 32Copyright (c) IBM Corporation 1995, 2004.Copyright (c) RexxLA >>>>>> 2005-2013.All Rights Reserved.This program and the accompanying materials >>>>>> are made available under the terms of the Common Public License v1.0 >>>>>> which >>>>>> accompanies thisdistribution or athttp://www.oorexx.org/license.html >>>>>> <http://www.oorexx.org/license.html>C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orxsock6>rexx >>>>>> test1245 *-* ::method priviate_init private external "LIBRARY >>>>>> orxsock6 >>>>>> orxSocket6"67 *-* ::requires 'orxsock6.cls'Error 98 running >>>>>> C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orx >>>>>> sock6\orxsock6.cls line 245: Execution errorError 98.903: Unable to >>>>>> load >>>>>> library "orxsock6"* >>>>> >>>>> >>>>> >>>>> >>>>> On 7 March 2014 17:37, Mark Miesfeld wrote: >>>>> >>>>>> Hi David, >>>>>> >>>>>> Good work on this. >>>>>> >>>>>> I'm still out of town. I'll try to test on Windows this weekend, but >>>>>> I just might not have enough time. >>>>>> >>>>>> -- >>>>>> Mark Miesfeld >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Mar 7, 2014 at 9:24 AM, David Ashley < >>>>>> w.david.ash...@gmail.com> wrote: >>>>>> >>>>>>> All - >>>>>>> >>>>>>> I think I am done with the initial development for support of IPv6. >>>>>>> The >>>>>>> files are in my sandbox under the orxsock6 subdirectory. It has been >>>>>>> tested under Fedora20 and all the supplied tests work. >>>>>>> >>>>>>> It would be nice if someone would test this under Windows for me. >>>>>>> >>>>>>> Also, you do NOT need an IPv6 network to successfully run the tests. >>>>>>> All >>>>>>> the tests
Re: [Oorexx-devel] Comodo AV/FW does not like ooDialog.com
On Wed, Mar 12, 2014 at 9:52 AM, Michael Lueck wrote: > Greetings Mark, > > Mark Miesfeld wrote: > > You should submit it to Comodo AV/FW as a false positive. > > > After I sent my email I discovered on the right-click menu a way to do > exactly that, and have done so. > Unfortunately there are several anti-virus programs that are reporting false positives on a few of the files in the distribution or the installer. In all of the cases, if anti-virus program A reports fileX as infected, when anti-virus programs B, C, D, and E scan fileX they report it as clean. Also, in all cases when fileX is sent to anti-virus program A as a false positive, the anti-virus program A comes back and says yes, this is a false positive. It is better for the owner / user of anti-virus program A reports it directly. -- Mark Miesfeld -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Comodo AV/FW does not like ooDialog.com
Michael, You should submit it to Comodo AV/FW as a false positive. -- Mark Miesfeld On Wed, Mar 12, 2014 at 3:02 AM, Michael Lueck wrote: > Greetings, > > FYI... > > I updated our Windows machines to v4.2.0 yesterday. This morning I am > seeing that Comodo AV/FW does not appreciate this file: > > TrojWare.Win32.Injector.ALGW@305097843 C:\Program > Files\ooRexx\ooDialog.com > > Google was unable to pull up a hit against that supposed threat name. > > Blessings, > > -- > Michael Lueck > Lueck Data Systems > http://www.lueckdatasystems.com/ > > > -- > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx Web Site Download Page
Hi David, My view, which is not in favor with others, is that we should just point people to the files page on SourceForge. So whatever you want to do is fine with me. I don't see much point in listing all the previous versions. I would suggest just giving this URL: https://sourceforge.net/projects/oorexx/files/oorexx/ and an explanatory paragraph saying: To get previous versions of ooRexx go there. And maybe some brief explanation saying, for example to get ooRexx 4.1.1 go the directory named 4.1.1. Although the whole process seems self-evident to me. And maybe another paragraph saying to see all packages released by the ooRexx project go to: https://sourceforge.net/projects/oorexx/files/ and browse the folders -- Mark Miesfeld On Tue, Mar 11, 2014 at 8:37 AM, David Ashley wrote: > All - > > The download page on the main ooRexx web site is getting a little too > crowded with the old releases. I was about to update it with the new > 4.2.0 release when I changed my mind and decided it was time to do > something else with this page. > > First, I have some observations. > > 1. Listing the individual files for download is error prone at best. A > simple typo can make the link useless. > 2. Listing details for the old releases is not very useful. Usually > people want the latest version. > > So I suggest we only list each version as a link to the SourceForge > repository (there would be a different link for each version). That way > the SF repository becomes the only real place from which to download > files and we do not have to maintain two places that list the files for > download. > > Opinions/suggestions? > > David Ashley > > > > -- > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] orxsock6 - Initial development Complete
Hi Jon, I was going to try to do a Windows build tomorrow if I have time. If I do build the Windows library I'll let you know. Then it will be easy. ;-) -- Mark Miesfeld On Fri, Mar 7, 2014 at 12:49 PM, Sahananda (Jon) Wolfers < sahana...@windhorse.biz> wrote: > OK. I just thought there was something easy there I could do to help. > > Jon > > > On 7 March 2014 19:14, Mark Miesfeld wrote: > >> Jon, >> >> It is probably a Linux build of the library. We would need a Windows >> build of the library. >> >> -- >> Mark Miesfeld >> >> >> >> On Fri, Mar 7, 2014 at 10:40 AM, Sahananda (Jon) Wolfers < >> sahana...@windhorse.biz> wrote: >> >>> Hi David, >>> >>> Do you need to do any setup to run the tests? >>> This is what I get just trying to run test1 from your sandbox folder on >>> Windows7 >>> >>> hth Jon >>> >>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> *C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orxsock6>rexx >>>> -v Open Object Rexx Version 4.2.0Build date: Feb 22 2014Addressing Mode: >>>> 32Copyright (c) IBM Corporation 1995, 2004.Copyright (c) RexxLA >>>> 2005-2013.All Rights Reserved.This program and the accompanying materials >>>> are made available under the terms of the Common Public License v1.0 which >>>> accompanies thisdistribution or athttp://www.oorexx.org/license.html >>>> <http://www.oorexx.org/license.html>C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orxsock6>rexx >>>> test1245 *-* ::method priviate_init private external "LIBRARY orxsock6 >>>> orxSocket6"67 *-* ::requires 'orxsock6.cls'Error 98 running >>>> C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orx >>>> sock6\orxsock6.cls line 245: Execution errorError 98.903: Unable to load >>>> library "orxsock6"* >>> >>> >>> >>> >>> On 7 March 2014 17:37, Mark Miesfeld wrote: >>> >>>> Hi David, >>>> >>>> Good work on this. >>>> >>>> I'm still out of town. I'll try to test on Windows this weekend, but I >>>> just might not have enough time. >>>> >>>> -- >>>> Mark Miesfeld >>>> >>>> >>>> >>>> On Fri, Mar 7, 2014 at 9:24 AM, David Ashley >>>> wrote: >>>> >>>>> All - >>>>> >>>>> I think I am done with the initial development for support of IPv6. The >>>>> files are in my sandbox under the orxsock6 subdirectory. It has been >>>>> tested under Fedora20 and all the supplied tests work. >>>>> >>>>> It would be nice if someone would test this under Windows for me. >>>>> >>>>> Also, you do NOT need an IPv6 network to successfully run the tests. >>>>> All >>>>> the tests use the internal virtual adapter (127.0.0.1 or ::1) so a real >>>>> network is not necessary. >>>>> >>>>> As always, all feedback will be embraced. >>>>> >>>>> Have fun. >>>>> >>>>> David Ashley >>>>> >>>>> >>>>> >>>>> -- >>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to >>>>> Perforce. >>>>> With Perforce, you get hassle-free workflows. Merge that actually >>>>> works. >>>>> Faster operations. Version large binaries. Built-in WAN optimization >>>>> and the >>>>> freedom to use Git, Perforce or both. Make the move to Perforce. >>>>> >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >>>>> ___ >>>>> Oorexx-devel mailing list >>>>> Oorexx-devel@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>>> >>>> >>>> >>>> >>>> --
Re: [Oorexx-devel] orxsock6 - Initial development Complete
Jon, It is probably a Linux build of the library. We would need a Windows build of the library. -- Mark Miesfeld On Fri, Mar 7, 2014 at 10:40 AM, Sahananda (Jon) Wolfers < sahana...@windhorse.biz> wrote: > Hi David, > > Do you need to do any setup to run the tests? > This is what I get just trying to run test1 from your sandbox folder on > Windows7 > > hth Jon > > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orxsock6>rexx >> -v Open Object Rexx Version 4.2.0Build date: Feb 22 2014Addressing Mode: >> 32Copyright (c) IBM Corporation 1995, 2004.Copyright (c) RexxLA >> 2005-2013.All Rights Reserved.This program and the accompanying materials >> are made available under the terms of the Common Public License v1.0 which >> accompanies thisdistribution or athttp://www.oorexx.org/license.html >> <http://www.oorexx.org/license.html>C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orxsock6>rexx >> test1245 *-* ::method priviate_init private external "LIBRARY orxsock6 >> orxSocket6"67 *-* ::requires 'orxsock6.cls'Error 98 running >> C:\Users\sahananda\Documents\oorexxSVN\code-0\sandbox\david\orx >> sock6\orxsock6.cls line 245: Execution errorError 98.903: Unable to load >> library "orxsock6"* > > > > > On 7 March 2014 17:37, Mark Miesfeld wrote: > >> Hi David, >> >> Good work on this. >> >> I'm still out of town. I'll try to test on Windows this weekend, but I >> just might not have enough time. >> >> -- >> Mark Miesfeld >> >> >> >> On Fri, Mar 7, 2014 at 9:24 AM, David Ashley wrote: >> >>> All - >>> >>> I think I am done with the initial development for support of IPv6. The >>> files are in my sandbox under the orxsock6 subdirectory. It has been >>> tested under Fedora20 and all the supplied tests work. >>> >>> It would be nice if someone would test this under Windows for me. >>> >>> Also, you do NOT need an IPv6 network to successfully run the tests. All >>> the tests use the internal virtual adapter (127.0.0.1 or ::1) so a real >>> network is not necessary. >>> >>> As always, all feedback will be embraced. >>> >>> Have fun. >>> >>> David Ashley >>> >>> >>> >>> -- >>> Subversion Kills Productivity. Get off Subversion & Make the Move to >>> Perforce. >>> With Perforce, you get hassle-free workflows. Merge that actually works. >>> Faster operations. Version large binaries. Built-in WAN optimization >>> and the >>> freedom to use Git, Perforce or both. Make the move to Perforce. >>> >>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >>> ___ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >> >> >> >> -- >> Subversion Kills Productivity. Get off Subversion & Make the Move to >> Perforce. >> With Perforce, you get hassle-free workflows. Merge that actually works. >> Faster operations. Version large binaries. Built-in WAN optimization and >> the >> freedom to use Git, Perforce or both. Make the move to Perforce. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > -- > Subversion Kills Productivity. Get off Subversion & Make the Move to > Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and > the > freedom to use Git, Perforce or both. Make the move to Perforce. > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] orxsock6 - Initial development Complete
Hi David, Good work on this. I'm still out of town. I'll try to test on Windows this weekend, but I just might not have enough time. -- Mark Miesfeld On Fri, Mar 7, 2014 at 9:24 AM, David Ashley wrote: > All - > > I think I am done with the initial development for support of IPv6. The > files are in my sandbox under the orxsock6 subdirectory. It has been > tested under Fedora20 and all the supplied tests work. > > It would be nice if someone would test this under Windows for me. > > Also, you do NOT need an IPv6 network to successfully run the tests. All > the tests use the internal virtual adapter (127.0.0.1 or ::1) so a real > network is not necessary. > > As always, all feedback will be embraced. > > Have fun. > > David Ashley > > > > -- > Subversion Kills Productivity. Get off Subversion & Make the Move to > Perforce. > With Perforce, you get hassle-free workflows. Merge that actually works. > Faster operations. Version large binaries. Built-in WAN optimization and > the > freedom to use Git, Perforce or both. Make the move to Perforce. > > http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Announce: The official release of ooRexx 4.2.0
The Open Object Rexx Project is happy to announce the official release of oRexx 4.2.0. The installation packages are now available on SourceForge at: https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0/ ooRexx 4.2.0 is an enhancement and bug fix release. The first new feature release in some time. There are a large number of new feature requests that have been implemented in this release. In addition, many reported bugs have been fixed. Please read the CHANGES document for a list of the bug tracker items fixed and the feature request tracker items that have been implemented. -- The ooRexx Development Team -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.2.0 Files Uploaded
Thanks David, I'll send out an announcement notice this evening and make the folder visible. -- Mark Miesfeld On Sun, Feb 23, 2014 at 1:20 PM, David Ashley wrote: > Mark, Rick - > > I uploaded the following > > - all the *nix install files > - all the docs > > The Build Machine has also been reset to start building everything from > the trunks (code and docs). > > David Ashley > > > > -- > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.2.0 Survey
Okay, I have copied ooRexx 4.2.0 main and docs branch to release in svn. I renamed the 4.2.0 branch to 4.2 branch to be the fixes branch for 4.2. I created the 4.2.0 release directory on SourceForge and put the Windows builds and the misc doc files there. David - I have the 4.2.0 directory as "Staged". If you are logged in as Admin you can see it, if not you don't see it. It looks like you can just click the I (info) icon, uncheck the Staged check box, and save at any time to change the directory from staged to not statge. Otherwise it becomes unstaged on Tuesday. I didn't do anything with the oorexx-docs directory on SourceForge. It still has the 4.2.0 beta docs. I didn't put a 4.2.0 debug build up yet. I'm doing a little research and will probably hold off on that until I'm back in town. Rick and Mike - It looks like the winDbg debugger supports JIT debugging, which means it should automatically break in if a crash happens on a system it is installed on. It is a free download. If we supply the .pdb files with a debug build, we should be able to get good information from a crash on a user's system, if they will go to the trouble of installing the Windows debugging tools along with the ooRexx debug build. -- Mark Miesfeld -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.2.0 Survey
Okay. -- Mark Miesfeld On Fri, Feb 21, 2014 at 7:18 AM, David Ashley wrote: > Mark - > > Go ahead and shoot for Saturday. I will do the Linux builds on Sunday > (my Saturday is busy). > > David Ashley > > On Fri, 2014-02-21 at 06:42 -0800, Mark Miesfeld wrote: > > I think we should release also. At this point, the one crash is not > > likely to be resolved soon unless the reporter can come up with a way > > to reproduce it > > > > > > I'm going to be pressed for time starting Sunday. Not that that is a > > reason to release earlier than we want to. But, I may have a hard > > time doing the Windows builds after this Saturday for 2 weeks. > > > > > > -- > > Mark Miesfeld > > > > > > On Fri, Feb 21, 2014 at 6:07 AM, David Ashley > > wrote: > > All - > > > > How close are we to the release? All the issues I care about > > are > > resolved. Are there any left? > > > > David Ashley > > > > > > > -- > > Managing the Performance of Cloud-Based Applications > > Take advantage of what the Cloud has to offer - Avoid Common > > Pitfalls. > > Read the Whitepaper. > > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > > ___ > > Oorexx-devel mailing list > > Oorexx-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > > -- > > Managing the Performance of Cloud-Based Applications > > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > > Read the Whitepaper. > > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > > ___ > > Oorexx-devel mailing list > > Oorexx-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > -- > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.2.0 Survey
I think we should release also. At this point, the one crash is not likely to be resolved soon unless the reporter can come up with a way to reproduce it I'm going to be pressed for time starting Sunday. Not that that is a reason to release earlier than we want to. But, I may have a hard time doing the Windows builds after this Saturday for 2 weeks. -- Mark Miesfeld On Fri, Feb 21, 2014 at 6:07 AM, David Ashley wrote: > All - > > How close are we to the release? All the issues I care about are > resolved. Are there any left? > > David Ashley > > > > -- > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Debug downloads
On Thu, Feb 20, 2014 at 8:32 AM, Mike Cowlishaw wrote: > I'm curious Mike, do you have a VC++ debugger installed, and if so is it > the "Express" version? > > The debugger I start on boot is started via the command: > > 'windbg -IS' > > which I think is from VC [++?] and yes I think the Express version, but > quite an old one. > > windbg used to be distributed in the device driver kit and is different than the VC++ debugger. It is supposed to be more powerful, but I don't know if it has just in time debugging, if it breaks in automatically when a crash happens on the system. Looking up some details on windbg, reminded me that the debug build may not be helpful without the .pdb files that are produced during the compile? -- Mark Miesfeld -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Debug downloads
Okay, I've put debug builds for Windows ooRexx 4.2.0 on SourceForge. They are in a subdirectory in the Files section for ooRexx 4.2.0. https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28release%20candidate%202%29/debug.version/ to be explicit. I'm curious Mike, do you have a VC++ debugger installed, and if so is it the "Express" version? -- Mark Miesfeld On Wed, Feb 19, 2014 at 7:47 AM, Mike Cowlishaw wrote: > > > I'm not sure what the requirements for the *ix platforms would be, and > I'm pretty sure we really don't want to do this for all of the flavors > anyway, but I'm thinking it might be a useful thing to have a debug version > of the Windows 32- and 64- bit versions available for download. This might > allow users that have access to the Visual Studio (and know how to use the > debugger) to perform some level of crash diagnosis without needing to > provide a working example they can send us. Sometimes problems like this > can be diagnosed with nothing more than the stack traceback. > > Sounds good to me. I am still (about once every 5 weeks) getting a crash > on my webserver which seems to point to rexx.dll but no way of getting > handle on it (and just as likely it's a problem in my code or the TCP/IP > stack). So running with a debug version that could provide more details on > a crash could be a win. > > Mike > > > > -- > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] rxsock select() function
Won't that break backwards compatibility for any one using select() that doesn't read this list? -- Mark Miesfeld On Wed, Feb 19, 2014 at 1:05 PM, David Ashley wrote: > All - > > Is anyone out there actually using the select() function from the rxsock > function package? If so, please drop a short note to this mailing list. > > I am working on an IPv6 version of rxsock and I would like to drop > support the select() function if there are no objections. So only reply > to this note if you depend on the select() function. > > David Ashley > > > > -- > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Debug downloads
On Wed, Feb 19, 2014 at 7:41 AM, Rick McGuire wrote: > I'm not sure what the requirements for the *ix platforms would be, and I'm > pretty sure we really don't want to do this for all of the flavors anyway, > but I'm thinking it might be a useful thing to have a debug version of the > Windows 32- and 64- bit versions available for download. > Yeah, I think so. I was going to suggest to the person that just opened the bug that I could provide a debug version. I don't see any reason why we couldn't make it available on SourceForge. Maybe have a sub-directory named debug to keep the debug version separate from the other downloads. > This might allow users that have access to the Visual Studio (and know how > to use the debugger) to perform some level of crash diagnosis without > needing to provide a working example they can send us. Sometimes problems > like this can be diagnosed with nothing more than the stack traceback. > I'm not sure what level of support the express version has for the debugger. I seem to recall the debugger in the express version does not automatically break in when a program crashes. But, if the user was motivated enough, he could try running the program under the debugger and waiting for the crash. He should be able to copy and paste the stack trace, even if he didn't know how to use the debugger. I'll put debug versions of the 4.2.0 Windows builds on SourceForge as soon as I can get to it. -- Mark Miesfeld -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Object Context
I'm not sure you can David. I think you need to use SendMessage(). If one of the attributes name is myVal, then use something like: RexxObjectPtr attribtueValue = context->SendMessage0(val, "myVal"); The other thing you could do is define a CSelf for the val object and use one of the get CSelf methods to get the C self struct and get the attribute value from that. Sorry I don't have anything here to look up the exact syntax, so the above is just an approximation. You could look at the .Point class definition in ooDialog for an example of a class that only has two attributes. Then in a method, if one of the args is a .Point object, I just get the CSelf struct and get the x an y attribute values directly from that. -- Mark Miesfeld On Tue, Feb 18, 2014 at 9:20 AM, David Ashley wrote: > I am in the middle of writing the new IPv6 sockets API and I have run > into a little problem. I have a C++ method API that looks like this. > > RexxMethod3(int, // Return type > orxSetSoctOpt6,// Object_method name > int, level,// socket level > int, option, // socket option > RexxObjectPtr, val)// socket option value > > The val argument is itself defined as a simple ooRexx class with two > defined attributes. > > What I can not figure out is how to get a context for val so I can use > the GetObjectVariable method to fetch the values for the two attributes. > > Any help would be appreciated. > > David Ashley > > > > -- > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Announce: An updated ooTest-4.2.0-snapshot06 on SourceForge
A quick announcement that the ooTest-4.2.0-snapshot06 package has been updated and is now available for download from SourceForge: https://sourceforge.net/projects/oorexx/files/oorexxunit/4.2.0.Snapshot.06/? This snapshot represents the current state of the test suite used to test ooRexx 4.2.0. Due to user interest, some changes were made to the test suite and the snapshot was redone. The name of the package was not changed, the older snapshot was replaced by the one produced today. There is no real need to replace the older snapshot on your system unless you are interested in the changes listed below. * An -l option has been added to testOOrexx.rex to write the test results to a log file. An -L option was also added that will append the results to the named log file. By default the log file is overwritten. * An -x option has been added to testOORexx.rex. This option will exclude the test group files listed after the option, from execution. For example, the following command line invocation will exclude the RexxContext.testGroup from being executed: C:\rexx\ooTest-4.2.0-snapshot06>testOORexx.rex -x RexxContext * Some test case failures that were avoidable when run in an unexpected environment were fixed. * The ReadMe.first file has been slightly updated to include some information on some tests that are known to fail when the test suite is run in an unexpected environment. It has always been the hope of the ooRexx development team that users would help test ooRexx by running the test suite and participate in improving the test suite by writing test cases. Any and all questions regarding the test suite, or requests for help in writing test case, are welcome and will be addressed by one of the developers. Thank you, The ooRexx Project Team -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] IPv6 rxsock Function Library
On Tue, Feb 11, 2014 at 12:08 PM, David Ashley wrote: > > Here are the requirements for a common library (Windows or Linux) which > handles both IPv4 and IPv6. > > ... > 2. A Windows server socket must use the setsockopt API to set the > IPV6_V6ONLY option to zero before binding the socket to an address. This > option is zero by default on all OSs except Windows and BSD. > My one suggestion is to do this internally, don't make the user do it. Just document that the default is 0, period. Then if a Windows user wants to change the default through setsockopt, she can. -- Mark Miesfeld -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] IPv6 rxsock Function Library
On Tue, Feb 11, 2014 at 8:06 AM, Mike Cowlishaw wrote:
>
> Maybe just add a new library ('rxsock6'?) which is unencumbered by past
> history.
>
>
Well, that is really more of what I meant. A new extension that was
unencumbered by the original rxsock design. But one that supported both
IPv4 and IPv6.
--
Mark Miesfeld
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] IPv6 rxsock Function Library
On Mon, Feb 10, 2014 at 3:00 PM, Rick McGuire wrote: > To me, it sounds like option 4 of using IPV4 mapped to IPV6 is the > cleanest way to implement this. I'm wondering if we might want to take the > approach used with oodialog and separate the rxsock library from the > interpreter release. The Windows installer could then check the prereqs to > ensure it can be installed on that system. I'd hate for somebody to be > unable to install the entire interpreter because their system didn't have > the prereqs for something they might not even need. > > I haven't joined into the discussion much because I simply don't know much about socket programming. But, I think Rick's last point is valid, It would be a shame if some of the old dinosaurs couldn't install a newer version of ooRexx because of a dependency on a version of .Net that is a later version of what comes with the version of Windows they are using. One of the thoughts I had before David posted the beginning of this thread is that maybe we could use this opportunity to update rxsock itself, so that it better uses the newish APIs and is object orientated than rather than procedural. One possibility would be leave rxsock just as it is and take the code base use it to produce a new extension that supports both IPv4 and IPv6. This new extension could be a separate install, like ooDialog can be installed separately. Users that want IPv6 support could install it, users that didn't want IPv6 could just stick with rxsock. I'm in favor of that, but since David is pushing this, I'm perfectly fine with whatever he wants to do. -- Mark Miesfeld -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] IPv6 rxsock Function Library
On Tue, Feb 11, 2014 at 6:55 AM, Michael Lueck wrote: > (sssiiggghh...) That is a most unfortunate situation. > Most people don't call this unfortunate, they call it progress. > > So all of a sudden, to install ooRexx, ooRexx will be dragging along .Net > onto target boxes. Bloat, bloat, bloat... > Most systems will already have .Net on them. So, nothing needs to be added. On the other hand, if you want to continue living in the previous millennium, you have no need of IPv6. There was no working IPv6 in the previous millennium. In addition, Rick is already concerned about people not being able to upgrade ooRexx because of a dependency on .Net that they don't want or need. Although we haven't hashed out the details on how to overcome that, since it is a concern, I'm sure we will arrive at some compromise there. But it will be a compromise that you will need to make. If you want and need IPv6, then you will need to use the software that supplies it. If you don't want it, then you will be able to use ooRexx, but you won't have IPv6. -- Mark Miesfeld -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Announce: ooTest-4.2.0-snapshot06 now available on SourceForge
A quick announcement that an ooTest-4.2.0-snapshot06 package is now available for download from SourcForge: https://sourceforge.net/projects/oorexx/files/oorexxunit/4.2.0.Snapshot.06/ This snapshot represents the current state of the test suite used to test ooRexx 4.2.0. There has been a lot of information written on how to use the test suite and that information is available in the ooTest-4.2.0-snapshot06 package. If, after reading that information, there are any questions regarding the test suite, please post a question on any of the lists where discussions concerning ooRexx take place. It has always been the hope of the ooRexx development team that users would help test ooRexx by running the test suite and participate in improving the test suite by writing test cases. Any and all questions regarding the test suite, or requests for help in writing test case, are welcome and will be addressed by one of the developers. Thank you, The ooRexx Project Team -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] IPv6 Test Environment
On Fri, Feb 7, 2014 at 11:54 AM, David Ashley wrote: > There has been an enhancement proposed that we support IPv6 in the > rxsock function library. I can do the work, but I have no place to test > the new functionality. Does anyone have an IPv6 test environment > available for testing an IPv6 rxsock function library? Preferably one > with both Windows and Linux clients. > > I saw that enhancement and thought it would be nice to implement it. But I don't have hardly any experience in that area, so I'm glad you're interested Unfortunately I don't have any access to a test environment. -- Mark Miesfeld -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Announce: ooRexx 4.2.0 Release Candidate 2 non available on SourceForge
On Fri, Jan 31, 2014 at 9:50 AM, Perry Werneck wrote: > Is the source code available for download? > It is always available through svn check out. A source code tar or zip file is not currently on SourceForge. for release candidate 2. We'll add one in a day or two. -- Mark Miesfeld -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Announce: ooRexx 4.2.0 Release Candidate 2 non available on SourceForge
The Open Object Rexx Project is happy to announce a release candidate for oRexx 4.2.0. The installation packages are available on SourceForge at: https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28release%20candidate%202%29/ A small number of bugs were discovered in the first release candidate. These have been fixed. All the installation packages have been rebuilt to produce a send release candidate. ooRexx 4.2.0 is an enhancement and bug fix release. The first new feature release in some time. There are a large number of new feature requests that have been implemented in this release. In addition, many reported bugs have been fixed. Please read the CHANGES document for a list of the bug tracker items fixed and the feature request tracker items that have been implemented. Testing by the users of ooRexx has definitely contributed to producing a better 4.2.0 release. Continued testing of the release candidate will help ensure that 4.2.0 is a great release. The second release candidate may be your last chance to test that your ooRexx programs work well with the new version of ooRexx. Please test the second release candidate and report any issues uncovered on the SourceForge bug tracker at: https://sourceforge.net/p/oorexx/bugs/ All users of ooRexx are strongly urged to, at a minimum, run the Rexx programs they use under the release candidate code. All testing done by users of ooRexx is highly appreciated and of great help. This testing is one way for ooRexx users to contribute back to the project. Thank you, The ooRexx Project Team -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.2.0 RC2 *nix Files Uploaded
On Fri, Jan 31, 2014 at 6:15 AM, David Ashley wrote: > The ooRexx 4.2.0 RC2 *nix are uploading now. They should be visible in > the next 10 minutes or so. > > Thanks David. The Windows builds are already uploaded. I'll send out an announcement notice as soon as I get a chance. Not later than this evening. -- Mark Miesfeld -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0
On Thu, Jan 30, 2014 at 8:25 AM, David Ashley wrote: > I usually take one of the overnight builds and make them release > candidates. So just say "go" and I can be ready the next day. > Go. After tonight's build. I think Rick is done. -- Mark Miesfeld > -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Test Failures on ooRexx 4.2.0
On Thu, Jan 30, 2014 at 4:16 AM, Rick McGuire wrote: > Ok, that didn't take as long as I expected. I'm now getting a clean run > of the entire suite except for one of the Windows event viewer tests that's > always been a bit flaky. We definitely need to spin new release > candidates. > I have a release candidate 2 folder on SourceForge. We should rebuild all packages and put them there. Then I'll announce RC 2 and delete the older folder. I'm a little busy now, let's shot for getting everything updated over the weekend? -- Mark Miesfeld -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.2.0 Release
On Tue, Jan 28, 2014 at 8:32 AM, Gil Barmwater wrote: > I was looking for documentation on the "update" type of install and all > I found was a statement in the PG that said there wasn't one! Should I > open a documentation bug? > Gil, Technically, the 'update' type of install is not an update. The installed version is completely removed and a complete new version is installed. What the uninstall does is save some metadata about how the old version was installed, such as the position of .rex in the PATHEXT, the old installed location, etc., and then use that data for the new install. Sure you can open a documentation bug and I'll reword that statement. The 'update' type of install is explained in the installer on the page that allows you to select that type of install. I thought I had added an explanation in the readMe.pdf file, but I guess I didn't. It seems to me the explanation in the installer is sufficient. But, you can open a doc bug for that and I'll add it. -- Mark Miesfeld -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.2.0 Release
On Tue, Jan 28, 2014 at 6:27 AM, Rick McGuire wrote: > Shouldn't we do another release candidate first since we had fixes to the > last one? > Technically I suppose we should. I was thinking that the changes were pretty low risk. Making the buffer bigger in SysFileTree was clearly needed, and I didn't think that was possibly a source of a new bug.. The change in the Windows installer is only triggered if the person installing has left Rexx programs running. I don't think that will even get tested in a second release candidate. Still, you're probably right we should. I can put a new Windows builds on SourceForge tonight. I'll create a new folder release candidate 2. We can move the release from this weekend to the next, releasing on 2/10 instead of 2/3. If that fits David's schedule. -- Mark Miesfeld -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx 4.2.0 Release
On Tue, Jan 28, 2014 at 6:16 AM, David Ashley wrote: > I think the major feedback from the release candidate has about stopped > so I want to propose that we release 4.2.0 this coming Monday, Feb 3. > That will give us the weekend to put the release together. > > That sounds good to me. -- Mark Miesfeld -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Fwd: [No Reply] False Positive Submission [3415563]
Here is Symantec's reply to the submission of ooRexx-4.2.0.windows.x86_32.exe, saying yes it was a false positive. -- Mark Miesfeld -- Forwarded message -- From: Symantec FP Incident Response Date: Tue, Jan 21, 2014 at 7:01 PM Subject: [No Reply] False Positive Submission [3415563] To: miesf...@gmail.com In relation to submission [3415563]. Upon further analysis and investigation we have verified your submission and as such this detection will be removed from our products. The updated detection will be distributed in the next set of virus definitions, available via LiveUpdate or from our website at http://securityresponse.symantec.com/avcenter/defs.download.html Decisions made by Symantec are subject to change if alterations to the Software are made over time or as classification criteria and/or the policy employed by Symantec changes over time to address the evolving landscape. If you are a software vendor, why not take part in our whitelisting program? To participate in this program, please complete the following form: https://submit.symantec.com/whitelist Sincerely, Symantec Security Response http://securityresponse.symantec.com This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] oorexx 4.2.0 for 32 bit Windows - Unsafe, says Norton!!!
Here is a link to NSIS's page on false positives. http://nsis.sourceforge.net/NSIS_False_Positives There are some links to online virus scanners. You can try scanning the file with one or more of them. Here is a link to the report of doing a scan from one of them. If you look at the report, it reports 2 out of 23 scanners report malware. However the names of the malware are different, and different from what Norton reported. http://virusscan.jotti.org/en/scanresult/92c7a03d4c30e1c2f398d4f90a30968d2bb935ef Basically, I just think the anti-virus software is not very reliable. -- Mark Miesfeld On Tue, Jan 21, 2014 at 8:35 AM, Mark Miesfeld wrote: > > On Tue, Jan 21, 2014 at 6:49 AM, Oliver Sims < > oliver.s...@simsassociates.co.uk> wrote: > >> Just downloaded oorexx-4.2.0.windows.x86_32.exe to my XP machine. At >> end of download, Norton anti-virus popped up and said it was "unsafe" and >> removed the downloaded file!!! >> > > > This is a false positive by Norton. As you can see Norton is using a > heuristic to detect the virus. Heuristic checks are notorious for > producing false positives. > > I submitted the problem to Norton and they admitted it was a false > positive and said it would be corrected. But, if they did anything, it > seems if is related to the file name only. > > You can turn Norton off and download the file, The go to: > > https://submit.symantec.com/false_positive/ > > and submit the download as a false positive. I believe Norton will come > back and agree it is a false positive. > > Other than that I don't know what to do about it. > > I believe it is actually coming from NSIS. The other thing you can do is > turn Norton off, run the installation, then turn Norton back on and have it > scan the installation directory. I believe it will report the files are > okay. > > -- > Mark Miesfeld > > -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Fwd: [No Reply] False Positive submission (3415563)
I just submitted the release canidate build to Symantec. Here is their submission received report. Usually they reply sooner than 2 days. I'll forward their reply as soon as I get it. The process of submitting it is relatively easy and straight forward. I encourage any one who has qualms about the file to submit it on their own. -- Mark Miesfeld -- Forwarded message -- From: Date: Tue, Jan 21, 2014 at 8:50 AM Subject: [No Reply] False Positive submission (3415563) To: miesf...@gmail.com Thank you for contacting Symantec. Your submission has been received and will be reviewed. We endeavor to respond to all submissions within 2 working days. The tracking number for your submission is: 3415563, please reference this tracking number in any further correspondence on this issue. Your submission: - When did the detection you are reporting occur? = DOWNLOAD Which product were you using when you saw this? = NIS Which of the following types of detection are you reporting? = INSIGHT Name (person to contact) = Mark Miesfeld Email address = miesf...@gmail.com Are you the creator or distributor of the software in question? = yes File being uploaded = ooRexx-4.2.0.windows.x86_32.exe Download (or blocking) URL = http://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28release%20candidate%29/ooRexx-4.2.0.windows.x86_32.exe/download Name of the software being detected = oorexx-4.2.0.windows.x86_32.exe Name of detection given by Symantec product = Suspicious.Cloud.7.EP File hash or clipboard paste from product = I dont have this. Additional notes or steps to reproduce the detection = In addition to uploading the file I also included the URL to publicly download the file. The detection from Norton happens when I download the file. - Sincerely, Symantec Security Response http://securityresponse.symantec.com This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Fwd: [No Reply] False Positive submission (3393192)
Here is the submission report for 3393192. I couldn't find it at first or I would have forwarded if first. As you can see here, the file I submitted had a different file name. Which is why I think their "correction" may have been file name based. -- Mark Miesfeld -- Forwarded message -- From: Date: Sun, Dec 15, 2013 at 4:10 PM Subject: [No Reply] False Positive submission (3393192) To: miesf...@gmail.com Thank you for contacting Symantec. Your submission has been received and will be reviewed. We endeavor to respond to all submissions within 2 working days. The tracking number for your submission is: 3393192, please reference this tracking number in any further correspondence on this issue. Your submission: - When did the detection you are reporting occur? = DOWNLOAD Which product were you using when you saw this? = NIS Which of the following types of detection are you reporting? = AUTO-PROTECT Name (person to contact) = Mark Miesfeld Email address = miesf...@gmail.com Are you the creator or distributor of the software in question? = yes File being uploaded = oorexx420_9716-x86_32.exe Download (or blocking) URL = Name of the software being detected = oorexx420_9716-x86_32.exe Name of detection given by Symantec product = Suspicious.Cloud.9.A File hash or clipboard paste from product = This information has disappeared. Your instructions did no good. I can not locate the event in history. Additional notes or steps to reproduce the detection = The file uploaded is a Windows installation file for ooRexx an open source project. The project is hosted on SourceForge: https://sourceforge.net/projects/oorexx/I am a developer and committer on the project. I built the ooRexx interpreter and the installation package from scratch. I had Norton AntiVirus scan the package. It reports no threats: Scan Statistics: Scan Start: Local: 12/15/2013 2:55 PM UTC: 12/15/2013 10:55 PM Scan Time: 9 seconds Scan Targets: C:\work.ooRexx\wc\main.4.2.0\ooRexx420_9716-x86_32.exe Counts: Total items scanned: 1 - Files & Directories: 1 - Registry Entries: 0 - Processes & Start-up Items: 0 - Network & Browser Items: 0 - Other: 0 - Trusted Files: 0 - Skipped Files: 0 Total security risks detected: 0 Total items resolved: 0 Total items that require attention: 0 Resolved Threats: No risks have been resolved Unresolved Threats: No unresolved risks When I go to upload the file to SoureceForge as soon as the file open dialog appears and I navigate to the correct folder Norton AntiVirus puts up a red alert box saying it is processing a threat. Then it automatically deletes it. It did the same thing when I used the Choose File button on this page. I then used the exclude button on the threat processing page to exclude the file so I could upload it here. Now the event from history has disappeared. And even though I set all exclusions to none and none are listed when I go to upload the file to SourceForge it no longer produces an alert. Ive been fooling with this for 2 days. Yesterday afternoon when I first got the alert. I did a complete computer scan and besides tracking cookies no threats were found. I did a second complete scan overnight again no threats. It then did a complete clean of the build and built the package immediately scanned it and then immediately tried to upload it. Got the threat notice. I know there is no virus in the code base and I dont see how the executable could have got infected in such a short time. I dont understand how using Norton AntiVirus to to scan the file can produce a no threat report and then trying to upload the file produces a threat warning. I dont see how two complete computer scans by Norton AntiVirus can say all threats resolved then doing a clean build of the executable can end up with an executable that Norton says is infected. It seems to me this has to be a false positive. Thanks for your time. - Sincerely, Symantec Security Response http://securityresponse.symantec.com This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments &
[Oorexx-devel] Fwd: [No Reply] False Positive Submission [3393192]
This is the reply I got from Norton when I submitted the first beta file to them. As you can see they affirm it is a false positive and say they corrected it. -- Mark Miesfeld -- Forwarded message -- From: Symantec FP Incident Response Date: Sun, Dec 15, 2013 at 10:50 PM Subject: [No Reply] False Positive Submission [3393192] To: miesf...@gmail.com In relation to submission [3393192]. Upon further analysis and investigation we have verified your submission and as such this detection will be removed from our products. The updated detection will be distributed in the next set of virus definitions, available via LiveUpdate or from our website at http://securityresponse.symantec.com/avcenter/defs.download.html Decisions made by Symantec are subject to change if alterations to the Software are made over time or as classification criteria and/or the policy employed by Symantec changes over time to address the evolving landscape. If you are a software vendor, why not take part in our whitelisting program? To participate in this program, please complete the following form: https://submit.symantec.com/whitelist Sincerely, Symantec Security Response http://securityresponse.symantec.com This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] oorexx 4.2.0 for 32 bit Windows - Unsafe, says Norton!!!
On Tue, Jan 21, 2014 at 6:49 AM, Oliver Sims < oliver.s...@simsassociates.co.uk> wrote: > Just downloaded oorexx-4.2.0.windows.x86_32.exe to my XP machine. At end > of download, Norton anti-virus popped up and said it was "unsafe" and > removed the downloaded file!!! > This is a false positive by Norton. As you can see Norton is using a heuristic to detect the virus. Heuristic checks are notorious for producing false positives. I submitted the problem to Norton and they admitted it was a false positive and said it would be corrected. But, if they did anything, it seems if is related to the file name only. You can turn Norton off and download the file, The go to: https://submit.symantec.com/false_positive/ and submit the download as a false positive. I believe Norton will come back and agree it is a false positive. Other than that I don't know what to do about it. I believe it is actually coming from NSIS. The other thing you can do is turn Norton off, run the installation, then turn Norton back on and have it scan the installation directory. I believe it will report the files are okay. -- Mark Miesfeld -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Kedit utility - where to put it
On Sun, Jan 19, 2014 at 10:21 PM, Sahananda (Jon) Wolfers < sahana...@windhorse.biz> wrote: > > If I get time, I will write a rexx sample script to download all files > from a directory from sourceforge into a subfolder in your download folder. > Not sure how, I could use rexcurl, but perhaps one wouldn't want one of > Mark's utilities as a dependency for an ooRexx sample (although that might > be a good thing). I could do it with ole & IE, but I'm not sure whether > that would work on Linux. Do you have thoughts? > > Jon, I have 2 thoughts 1.) I can't believe that SourceForge intends for the snapshot feature to work that way. So, if we open a bug I think they will fix it. It would be a very cool feature if it did work. https://sourceforge.net/p/forge/site-support/6552/ 2.) If we were to decide to allow / accept user contributions and actually want ooRexx users to be able to get those contributions, it would be more user friendly to have a section on the Files download page for them. Currently the download page has: Name Modified Totals: 10 Items oorexx < 14 hours ago ooDialog2014-01-18 oorexx-docs 2013-12-09 ooSQLite2013-08-27 oorexxunit 2012-07-25 oorexx-buildutils 2010-08-18 RexxGTK 2009-11-01 OldFiles2009-07-17 windows-build-tools 2009-02-12 orxutils2006-09-15 I would suggest adding 1 more section: user-contributions 2014-04-11 And under that section have sections for individual contributions. I see several things in the incubator that would be easier for ooRexx users to access if they could be downloaded from the Files download pages. They could go under user-contributions: decimalFormat keditMacros mod_oorexx ooRexxShell ZabrodskyAAT -- Mark Miesfeld -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Announce: ooRexx 4.2.0 Release Candidate now available on SourceForge
The Open Object Rexx Project is happy to announce a release candidate for ooRexx 4.2.0. The installation packages are available on SourceForge at: https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28release%20candidate%29/ ooRexx 4.2.0 is an enhancement and bug fix release. The first new feature release in some time. There are a large number of new feature requests that have been implemented in this release. In addition, many reported bugs have been fixed. Please read the CHANGES document for a list of the bug tracker items fixed and the feature request tracker items that have been implemented. Unless more bug reports are posted, It is anticipated that the official release of ooRexx 4.2.0 will be done in several weeks. This is your last chance to test that your ooRexx programs work well with the new version. Please test the beta and report any issues uncovered on the SourceForge bug tracker at: https://sourceforge.net/p/oorexx/bugs/ The users of ooRexx are strongly urged to, at a minimum, run the Rexx programs they use under the beta code. All testing done by users of ooRexx is highly appreciated and of great help. This testing is one way for ooRexx users to contribute back to the project. Thank you, The ooRexx Project Team -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Kedit utility - where to put it
On Sun, Jan 19, 2014 at 2:05 PM, Sahananda (Jon) Wolfers < sahana...@windhorse.biz> wrote: > > If you do not sign into sourceforge, but go to the project, select code > SVN repository and navigate to a particular file, so that you see a listing > of it, you can then click on the *download this file* link and the file > is downloaded using your web browser. > > Does that not work for you? > Jon, Yes that does work. But, using decimalFormat as an example. If you navigate through the tree to get to /incubator/decimalFormat, there are 4 files from Lee. There is nothing to indicate to the user that you can download a file. Nothing to indicate that if you click on a file you are then able to download it. Plus, once you do know that, it is a little tedious to download them 1 by 1. However at the top of that page there is: Tree [r9856] <https://sourceforge.net/p/oorexx/code-0/9856/> / incubator<https://sourceforge.net/p/oorexx/code-0/HEAD/tree/incubator/> / decimalFormat<https://sourceforge.net/p/oorexx/code-0/HEAD/tree/incubator/decimalFormat/> / Download Snapshot My assumption was that "Download Snapshot" would download all 4 files as a group. Which would certainly be more convenient then clicking on each file one by one and downloading them individually. But, it doesn't. Instead SourceForge takes 5 or 10 minutes to generate a 256 MB zip file that, if you do download and unzip, doesn't even contain a single decimalFormat file. As the person who argued to Mike that SourceForge was easy for people to use, I can't even think of where to start with an argument that this would be good for ooRexx users. ;-) Anyway, I'm not trying to dissuade you from putting your files in the incubator and giving out directions on hot to get them. I think you should. Maybe we can get SourceForge to fix or enhance the "Download Snapshot" so that it works the way I would intuitively expect it to work. -- Mark Miesfeld -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Moving towards an ooRexx 4.2.0 release?
On Sun, Jan 19, 2014 at 10:58 AM, Rick McGuire wrote: > That sounds good to me. Things have been really quiet on the beta lately, > so I think it's time to spin a release candidate. > > Okay. I think I will create a new folder in the Files download, ooRexx 4.2.0 Release Candidate and put the Windows builds in it. Then when David has time, he can add the Linux builds to it and I'll announce the release candidate is available. -- Mark Miesfeld > Rick > > > On Sun, Jan 19, 2014 at 1:55 PM, Mark Miesfeld wrote: > >> Hi All, >> >> I'm not sure where others think we are in relation to doing the 4.2.0 >> release. I'm finished with everything I feel strongly about being in the >> release. >> >> Unless someone else has something they are still working on, or intend to >> work on, I'm thinking maybe we should update all the packages on >> SourceForge and call them the release candidate. Then give it 10 days or 2 >> weeks and if no bugs are opened, do the release. >> >> Or ... ? >> >> -- >> Mark Miesfeld >> >> >> -- >> CenturyLink Cloud: The Leader in Enterprise Cloud Services. >> Learn Why More Businesses Are Choosing CenturyLink Cloud For >> Critical Workloads, Development Environments & Everything In Between. >> Get a Quote or Start a Free Trial Today. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > -- > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Moving towards an ooRexx 4.2.0 release?
Hi All, I'm not sure where others think we are in relation to doing the 4.2.0 release. I'm finished with everything I feel strongly about being in the release. Unless someone else has something they are still working on, or intend to work on, I'm thinking maybe we should update all the packages on SourceForge and call them the release candidate. Then give it 10 days or 2 weeks and if no bugs are opened, do the release. Or ... ? -- Mark Miesfeld -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Kedit utility - where to put it
On Sun, Jan 19, 2014 at 2:08 AM, Sahananda (Jon) Wolfers < sahana...@windhorse.biz> wrote: > > However, if it is OK to put them on the SVN I feel they would be easier to > find, so if it is possible I would prepend any necessary license and put > them there. > > Jon, I think it is perfectly acceptable for you to put them in the SVN repository. I think the incubator is the best current place. Although, I would also be in favor of starting a new branch for user contributions. I have thought about having a place for user contributions often, but not deeply. By that I mean it has crossed my mind a lot but I've never gone to the effort of proposing it to the team or thinking about how to implement it If we had a branch in the repository for user contributions, and a developer willing to maintain a section in the Files downloads section for the contributions that would be ideal. When you browse the svn tree in the project there is a link called Shapshot, which I had assumed would give you a tar or zip file of just the current directory. But, I just tried it to see how easy it would be for users to get something from the incubator. I tried it with Lee's decimalFormat: Tree [r9855] <https://sourceforge.net/p/oorexx/code-0/9855/> / incubator<https://sourceforge.net/p/oorexx/code-0/HEAD/tree/incubator/> / decimalFormat<https://sourceforge.net/p/oorexx/code-0/HEAD/tree/incubator/decimalFormat/> / unfortunately, it took forever to create and produced a 256,784,919 byte file, which looks to be the entire repository. I'm sure Mike would point out to me that this was hardly user friendly. ;-) So we already have some stuff in the incubator that would make a good start towards a user contributions section. I realize that Lee was a committer, but it's sort of a shame that his decimal formatter is not available to the casual user. Anyhow, I think the idea of accepting user contributions is worth talking about and maybe implementing. But, as a committer, I think you can certainly set up something to make your utilities easily available to ooRexx users, and you should go for it. -- Mark Miesfeld -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Announce: ooDialog version 4.2.3, official release, is now available on SourceForge
Installation packages for ooDialog version 4.2.3 are now available on SourceForge at: https://sourceforge.net/projects/oorexx/files/ooDialog/4.2.3/ This is the official release of ooDialog 4.2.3. ooDialog 4.2.3 is a routine update with bug fixes and a few enhancements. The ReadMe file that displays on the SourceForge download page contains a list of the bug fixes and enhancements in 4.2.3. In addition the ooDialog reference manual, in chapter 1, Brief Overview, section 1.5 Current Release contains a complete discussion of the changes in ooDialog 4.2.3 from ooDialog 4.2.2. 4.2.3 has a few new features. It contains the implementations of Request For Enhancements that were submitted to the project on SourceForge. Users of ooDialog are encouraged to submit requests for features or enhancements they would like to see in ooDialog using the Request for Enhancement tracker at: https://sourceforge.net/p/oorexx/feature-requests/?source=navbar The new features in 4.2.3 include implementations of Vista Open File and Save File dialogs, along with a stand alone ooDialog executable. The executable can be used to display information about ooDialog, to run ooDialog programs with not visible console (similar to rexxhide but with a few enhancements,) as a drag-and-drop target for ooDialog programs, and to configure file associations for ooDialog programs. There are no known bugs in ooDialog at the time of this release. Anyone suspecting they have discovered a bug or other problem in ooDialog is encourage to report this using the ooRexx SourceForge tracker for bugs: https://sourceforge.net/p/oorexx/bugs/?source=navbar Beginning with the release of ooDialog 4.2.0, the installation of ooDialog has been decoupled from the interpreter. ooDialog 4.2.3 installs over the top of any ooRexx installation. It replaces the version of ooDialog in the ooRexx installation with ooDialog 4.2.3. This type of ooDialog installation is called an "independent" ooDialog installation to indicate the ooDialog installation is independent of an ooRexx installation and, to a degree, the version of ooRexx installed. ooDialog 4.2.3 requires a minimum ooRexx version of 4.1.0 to be installed on the target computer. Installation is simple, done through a typical Windows installer. Pick the installation package that matches the bitness of the ooRexx installation. I.e., a 32-bit package for a 32-bit ooRexx and a 64-bit package for a 64-bit ooRexx. Note that the bitness of the operating system is not relevant here. If you have installed a 32-bit ooRexx on a Windows 64-bit system, you must install a 32-bit ooDialog. The installer will detect the installed ooRexx, location, and version. If the ooRexx version is less than 4.1.0, or if there is no installed ooRexx, the installer will abort with a message explaining the problem. Otherwise the installer will replace the current ooDialog with ooDialog 4.2.3. -- Mark Miesfeld for the ooRexx Development Team -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx Web Sites
On Thu, Jan 9, 2014 at 10:42 AM, Sahananda (Jon) Wolfers < sahana...@windhorse.biz> wrote: > I notice on the support page a link to comp.lang.rexx > news:comp.lang.rexx";>comp.lang.rexx > which doesn't work for me. > In fact, I've been unable to get comp.lang.rexx since google retired > google reader. > > Is it still going? If so, does anyone have a url that can go in here? > It is still going, although there are not as many posts as several years ago. This is the bookmark I use: https://groups.google.com/forum/?hl=en#!forum/comp.lang.rexx -- Mark Miesfeld -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooDialog Doc
I looked up the fix I read about before: Q: I get an error Exception in thread "main" java.lang.OutOfMemoryError: Java heap space when trying to build PDF. What is wrong? A: The default memory allocated for Java is not big enough to build your PDF. You need to increase the memory allocated to *FOP*. Before running $ publican build run echo "FOP_OPTS='-Xms50m -Xmx700m'" > ~/.foprc. This sets the initial heap space to 50 MB and allows it to grow to a maximum of 700 MB. Here is a link to the Publican doc that has the above: http://jfearn.fedorapeople.org/en-US/Publican/3.2/html/Users_Guide/chap-Users_Guide-Frequently_Asked_Questions.html#idp10662944 -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooDialog Doc
David, This is what causes the build to fail: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space One suggested fix is a flag to increase the heap space. But as I said, I could never get it to work. And, I don't remember the flag right now. -- Mark Miesfeld On Wed, Jan 8, 2014 at 6:39 AM, Mark Miesfeld wrote: > > On Wed, Jan 8, 2014 at 5:47 AM, David Ashley wrote: > >> Mark, anyone - >> >> Would someone please take a look at the ooDialog document? It has not >> built successfully in almost two weeks on the Build Machine. >> > > > David, > > It is a Java out of memory problem. > > I have that problem on one of my laptops with very little memory. > Supposedly it can be fixed by telling Java it can use more memory. But, I > haven't used Java much for a long time and I could never get the suggested > fixes to work. > > I just build on a system with more physical ram. So, I was thinking maybe > you could up the memory allocation for the virtual machine? I don't know > much about virtual machines either. Can you temporarily up the memory and > then decrease it? > > Supposedly, Publican 3.0 and later eased the problem somewhat, so I was > surprised to see it on the build machine. > > -- > Mark Miesfeld > > >> >> Thanks, >> David Ashley >> >> >> >> -- >> Rapidly troubleshoot problems before they affect your business. Most IT >> organizations don't have a clear picture of how application performance >> affects their revenue. With AppDynamics, you get 100% visibility into your >> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics >> Pro! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooDialog Doc
On Wed, Jan 8, 2014 at 5:47 AM, David Ashley wrote: > Mark, anyone - > > Would someone please take a look at the ooDialog document? It has not > built successfully in almost two weeks on the Build Machine. > David, It is a Java out of memory problem. I have that problem on one of my laptops with very little memory. Supposedly it can be fixed by telling Java it can use more memory. But, I haven't used Java much for a long time and I could never get the suggested fixes to work. I just build on a system with more physical ram. So, I was thinking maybe you could up the memory allocation for the virtual machine? I don't know much about virtual machines either. Can you temporarily up the memory and then decrease it? Supposedly, Publican 3.0 and later eased the problem somewhat, so I was surprised to see it on the build machine. -- Mark Miesfeld > > Thanks, > David Ashley > > > > -- > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Status ooRexx 4.2 branch on AIX
On Fri, Dec 27, 2013 at 7:10 AM, Rainer Tammer wrote: > The current ooRexx 4.2 branch does build under AIX 6.1 (64Bit) without a > problem. All sample programs do work. > Hi Rainer, that's good to hear. > > Which text suite should be used for ooRexx 4.2 branch?? > Trunk. p/oorexx/code-0/test/trunk -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] THE Function registration problem
Rick, Reading your previous post I was going to reply that, on Windows, there is a reference count and MSDN says the library won't be unloaded until the count goes to 0. But, it looks like you've already seen that. ;-) -- Mark Miesfeld On Mon, Dec 23, 2013 at 5:41 AM, Rick McGuire wrote: > Ok, it looks like solution #1 will work. Both dlopen() and Windows > LoadLibrary maintain reference counts, so it is possible to lock library in > place if it needs to maintain a local copy. This could be a fairly simple > fix (which can probably wait until Thursday). > > Rick > > > On Mon, Dec 23, 2013 at 8:23 AM, Rick McGuire wrote: > >> Still waiting for Walter to open a bug report on how to recreate the THE >> problem so I can verify, but I have a theory on what's going on here. >> >> I wrote some test cases and added them to the test suite for function EXE >> registrations, and they are definitely working. However, the information >> from Mark Hessling gave me a hint. There was a bug I fixed that was a >> memory leak with these function registrations. The leak would occur if a >> process did local registrations and then did not deregister them before >> terminating. rxapi would then accumulate these dead resistrations every >> time the application was run. I tried a number of different methods of >> forcing these to get cleaned up at process termination, but it turned out >> to be very difficult to do everything needed at process termination time >> because things were going away. >> >> In the end, I fixed the problem by keeping all *Exe registrations in the >> local process rather than using rxapi. Since these were only callable from >> the process registered them, this took rxapi out of the picture entirely. >> The table got nicely cleaned up when the process went away, and was even a >> bit of a performance boost since an IPC was no longer called to invoke >> these functions. It seemed like a nice clean solution to the problem. >> >> Until THE (or more specifically, RexxWrapper) threw a monkey wrench into >> the whole mess. My thinking here was applications would load rexxapi and >> leave it loaded. I'm betting that RexxWrapper is dynamically loading the >> library, calling the function, then unloading the library afterwards >> (again, I need to be able to recreate Walter's problem to verify). The >> unloading process, of course, nukes the local table, so when rexx.dll is >> loaded, rexxapi is reloaded with a fresh table and the functions cannot be >> located. >> >> So, I'm looking for some way to protect these tables within a process >> that will work across platforms, so I'm going to need some help from the >> platform experts. >> >> The first thing that comes to mind is it possible to lock rexxapi in once >> it is loaded? Do library loadings have a usage count that could prevent >> one from getting unloaded? If rexxapi could issue a load against itself >> when first loaded (or maybe only when the local tables are used), that >> could solve the problem. >> >> Another thought is to move the table to another library that rexxapi >> could load dynamically and leave loaded. This could be something quite >> tiny. Or we could add this to the rexx library and dynamically load that >> to obtain the table. One would assume that these APIs would only be used >> if it is intended that Rexx is going to get used. Again, this would only >> work if loads nest, since I assume RexxWrapper will dynamically load >> rexx.dll as well, and we would not want the table to go away if that is >> unloaded. And if the loads, nest, then solution #1 of locking the library >> into the process would be a better solution. >> >> I'm going to be a bit limited in internet access until Thursday evening, >> but I wanted to get this discussion rolling on how to potentially solve >> this problem. >> >> Rick >> > > > > -- > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo
[Oorexx-devel] Announce: ooDialog 4.2.3 release candidate now available
Installation packages for ooDialog 4.2.3, final release candidate, are now available on SourceForge at: https://sourceforge.net/projects/oorexx/files/ooDialog/4.2.3%20%28release%20canidate%29/ The ooDialog 4.2.3 release is a routine update, providing some incremental improvements and a few bug fixes. ooDialog 4.2.3 can be installed to any ooRexx installation, 4.1.0 or later. 4.2.3 has been in beta now for over 3 weeks with only 1 minor bug reported and fixed. Unless some other bugs are reported in the next few days, it is anticipated that the official release version of ooDialog 4.2.3 will be done on Christmas day 2013. This may be your last chance to ensure your ooDialog applications run correctly before the official release. If problems are discovered please report them immediately using the SourceForge bug tracker at: https://sourceforge.net/p/oorexx/bugs/ -- The ooRexx Development Team -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] What version of publican are you updating to?
Okay thanks Rick. I knew from experimenting a couple of months ago that the then current doc source wouldn't build under newer versions of Publican. That's why I suspected I would have problems unless I upgraded my Publican version. -- Mark Miesfeld On Wed, Dec 18, 2013 at 1:47 PM, Rick McGuire wrote: > Mark, > > I've finally reinstalled vmware on my system and got a Fedora system set > up so I'd have a system where I could do compiles and doc builds. I ended > up with publican version 3.2.1, which did not appear able to build. With > David's updates, this version appears to be working now. > > Rick > > > On Wed, Dec 18, 2013 at 4:16 PM, Mark Miesfeld wrote: > >> HI David, >> >> I see you made some changes to the doc source for a newer version of >> Publican. >> >> I'll need to update my build environment to? What version of Publican >> are you using? >> >> -- >> Mark Miesfeld >> >> >> -- >> Rapidly troubleshoot problems before they affect your business. Most IT >> organizations don't have a clear picture of how application performance >> affects their revenue. With AppDynamics, you get 100% visibility into your >> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics >> Pro! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >> ___ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > -- > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] What version of publican are you updating to?
HI David, I see you made some changes to the doc source for a newer version of Publican. I'll need to update my build environment to? What version of Publican are you using? -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Windows installer: Finish page
On Tue, Dec 17, 2013 at 10:07 AM, Walter Pachl wrote: > But non-newbies would know where to look. > We were talking about the disappointed newbie > Talking about the disappointed newbie is what started this whole thing. But, now we are talking about what the finish page should look like / do. We have more options here. For instance: 2 chkBx Show Open Object Rexx 4.2.0 Releases Notes (or Read Me file.) 3 hypLnk How to Get Started if You are New to Open Object Rexx Where #3 is specifically designed for the newbie -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Windows installer: Finish page
On Tue, Dec 17, 2013 at 8:54 AM, Walter Pachl wrote: > Can we see a draft? > It is displayed at: https://sourceforge.net/projects/oorexx/files/oorexx/4.2.0%20%28beta%29/ below the file list. The readme file is actually a copy of the ReleaseNotes file. SourceForge used to have you mark a file as the release notes and it would display it on the Files page. The new SourceForge displays a file that is named Readme. What I currently do is copy the ReleaseNotes file to a file named ReadMe.txt. Since this is what gets displayed on the File download page, the intent of the text is to help people in picking what to download. > I doubt that readme (showing mosty changes) is useful to a newbie > That may be true. An enterprising contributor could maybe write a specific file to be shown by the installer here. Could maybe find an existing web page to be shown here, or write a new web page designed to be shown here. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Windows installer: Finish page
On Tue, Dec 17, 2013 at 8:44 AM, Mike Cowlishaw wrote: > > Rick's suggestion of readme rather than licence is good (assuming the > readme is useful/up to date -- I haven't looked at it for a while). > Yes, the license was a quick pick, the readme makes more sense. It is updated for this release, whether it is useful is probably a subjective opinion. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Problem Using EXPOSE
On Tue, Dec 17, 2013 at 6:39 AM, Sanford Geiger wrote:
> Ok, but this is NOT how IBM Rexx works. Is there a way to make all
> variables in a program be made available to any routine or method?
>
You could stick the variables in the .local directory. This is similar to
global variables and all the arguments against global variables would apply.
/** ooRexx global variables **/
.local~fld1 = "123456"
.local~fld2 = copies("C",20)
myclass = .tclass~new
myclass~testmethod
myclass~testExposeAndLocal
fld3 = .local~fld1 || .local~fld2
say fld3
return
::class tclass
::method testmethod public
expose fld1 fld2
fld1 = "abcdef"
fld2 = "123456789ZZZ"
::method testExposeAndLocal
expose fld1 fld2
.local~fld1 = fld1
.local~fld2 = fld2
::requires ooDialog.cls
--
Mark Miesfeld
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Hardware support in the readme files.
On Fri, Dec 13, 2013 at 5:22 PM, Rick McGuire wrote: > When reviewing Patch file 189 (let's see if this creates a real link for > the mailing list.[patches:#189]), I noticed we give the hardware > requirements as: > > IBM-compatible, Pentium or AMD processor, or higher. Both 32-bit and 64-bit > processors are supported. > > > It's been a long time since I've heard the term "IBM-Compatible" used, and I > suspect the Pentium brand is also obsolete. I suspect this probably should > be called an "Intel-compatible processor (including AMD). Not sure what the > exact wording should be here. but the existing wording seems wrong to me. > > I needed to add something to the read me for Windows, so I'll fix this up. Really any hardware that runs a supported version of Windows is fine. It is the operating system that is the limiting factor, not a particular processor or other hardware. I suggest this: Any hardware capable of running a supported Windows operating systems is sufficient. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Docs
Definitely a big improvement. There is still the problem that Publican doesn't produce a decent index section. You can't go to the F's without scrolling through all the pages starting at "%" -- Mark Miesfeld On Sun, Dec 15, 2013 at 9:50 AM, David Ashley wrote: > All - > > I fixed the syntax errors that prevented rexxref from building last > night. I then put the latest build of rexxref up on the Build machine. > > I also made a quick scan of the whole document this morning. With the > switch to publican our docs now look really professional. And the > content is not bad either! I am really happy with them at this point and > I think they are pretty much ready for release except for any glitches > we may find. > > David Ashley > > > > -- > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx does nothing visible when installed.
On Sun, Dec 15, 2013 at 8:13 AM, Oliver Sims < oliver.s...@simsassociates.co.uk> wrote: > Any chance of somewhow providing a reference to Chapter 2 of the Rexx > Programmer Guide? > Sure there is a chance. I've been working on this over the weekend. When I get everything working I was going to post to the list and describe things and then people could decide what the actual content should be. Essentially, there can be 2 check boxes on the Finish page, initially unchecked. If the user checks any of them it produces an action when the user pushes the Finish button. The labels can be any text. In addition, there can be an underlined link to a file or URL on the page. Right now I have one check box that says Create Desktop Icon and the icon opens up the Open Object Rexx Start Menu folder. The second check box can do whatever is decided on, or be left out. The underlined link can open whatever is decided on, or be left out. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Bug or Not?
On Sat, Dec 14, 2013 at 2:52 PM, Rick McGuire wrote: > I think a fix for this is pretty simple, > ... ...the big remaining question is whether we should be setting the other flag as well. Assuming umask() is actually doing what I think it is, then I believe the answer is yes. Do other agree? I think I agree if I have followed this correctly. I think you set this flag, but then when the file is actually created, if the user's umask doesn't have the other flag set, then the file is not created with the other bit set. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] How about adding the SQLLite support to the ooRexx distribution?
On Fri, Dec 13, 2013 at 10:35 AM, Perry Werneck wrote: > Well, why not use an DB independent library to add support to other > databases? > The SQLite source code is public domain, so the entire database engine can be directly integrated into our source code base with no licensing issues at all. ooSQLite is a complete package. There is nothing an ooRexx users needs to install, or do, to use ooSQLite. It is what I choose to do. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] How about adding the SQLLite support to the ooRexx distribution?
On Fri, Dec 13, 2013 at 9:57 AM, Erich Steinböck wrote: > > But, the documentation is not finished > Mark, if there's something you can delegate, I'd look into it > Erich, If you'd like to look into it, then great. ooSQLite consists of an object orientated interface (classes and methods of the classes,) and a functional interface (consists entirely of ::routines.) The methods of the classes, mostly, map one to one with SQLite functions. The routines are all one-to-one mappings of the SQLite functions. So most of the doc comes straight from the SQLite documentation. For methods and routines I use a boilerplate format. In the current doc, the boilerplate for all classes / methods / routines is already there. The doc starts out documenting the classes in ooSQLite. The first classes in order are finished: The ooSQLite Class and The ooSQLiteBackup Class sections are done. The ooSQLiteConnection Class is probably 99% done. Some of the individual routines are done. You can get a general idea of how I'm documenting things by reading the finished sections You can tell what is un-filled-in boilerplate by reading the doc and you will typically see: xx Arguments: The arguments are: TERM xx Return value: xx Remarks: Additional comments. Details Anything? Example: This example ... In general I doc each method and routine in the C / C++ code, so if you can read the comment headers in ooSQLite.cpp you will be able to get much of the doc from that. When I didn't doc a method or routine, it is because, usually, it does nothing other than invoke a simple SQLite function and just passes on the result. In these case, it is pretty much, whatever the SQLite says it is. if you need some tips on locating that doc in the C / C++ code just ask. I do not use the IBM railroad tracks, but rather a modified version whose main goal is to stay on one line. By one line I mean not continued. Optional args are always on a second line. In the preface section of ooDialog, I explain how to read the syntax diagrams. If you read that you should understand pretty well how to create it. So - whatever you'd like to do, go for it. If you have questions on how a method or routine works, I'll gladly help. I'd prefer that you ask those questions on the user's list so that others can benefit. I think many users are not comfortable asking questions on the developer's list and I'd like to encourage them to ask questions. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] How about adding the SQLLite support to the ooRexx distribution?
On Fri, Dec 13, 2013 at 7:34 AM, Rony G. Flatscher wrote: > > are there any thoughts about adding the SQLLite support to the ooRexx > 4.2.0 distribution or should > it remain a standalone add-on? > I do want to add it to the distribution. But, the documentation is not finished and I doubt that I will finish it before we want to release 4.2.0. In addition, I'm not sure how to integrate it into the unix-like build. I'm sure I can figure it out, or get David to help me. But, it is one more task that needs to be done. So, for now I was not thinking to add it to 4.2.0. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Bug or Not?
Well good.
Seem counter-intuitive at first glance. I'm glad you read the docs.
--
Mark Miesfeld
On Thu, Dec 12, 2013 at 2:42 PM, Rick McGuire wrote:
> If I'm reading the docs for umask correctly, the right fix is the easy
> fix. If we set the other bits on, the process umask setting will take take
> of turning the inappropriate flags off again.
>
> Rick
>
>
> On Thu, Dec 12, 2013 at 3:46 PM, David Ashley wrote:
>
>> The problem is that the file open call unconditionally set a permission
>> of 0600 which only gives the owner rw permissions. Here is the strace
>> for the call which was caused by a lineout function call which opened a
>> new file.
>>
>> open("/ibm/tci/data/lodb/requests/crackdispo-testlot-1234567-2013-12-12-11.06.00.00-20131212-43362.tmp",
>> O_RDWR|O_CREAT, 0600) =
>> 4
>>
>> You can see where the 0600 is used for to set the file permissions.
>>
>> There are several options to fixing this. The easiest is just setting
>> the read bit for Group and Other. The correct method is to fetch the
>> user's umask and setting the bits based on that. But it does add some
>> complexity because the umask can not be used directly in the open
>> function, it must be XORed with a value of all ones to get the
>> permissions the user wants for new files.
>>
>> David Ashley
>>
>> On Thu, 2013-12-12 at 15:09 -0500, Rick McGuire wrote:
>> > Never even realized we were responsible for applying stuff like that.
>> > Would have thought the system would have been handling that. In any
>> > event, I think I agree we need to fix that, although given nobody has
>> > complained about it before this, I'm not sure I'd agree it needs to be
>> > fixed ASAP. In any event, we should probably try to get it into
>> > 4.2.0.
>> >
>> >
>> > Rick
>> >
>> >
>> > On Thu, Dec 12, 2013 at 3:00 PM, David Ashley
>> > wrote:
>> > All -
>> >
>> > I cannot believe I have been using ooRexx on Linux for about
>> > 10 years
>> > and I just had something pointed to me by a user that I have
>> > never
>> > noticed before.
>> >
>> > When ooRexx creates a file on *nix that file is created with
>> > the
>> > permissions -rw--- which means that only the owner can
>> > read and
>> > write to the file. No other user (except of course root) can
>> > open the
>> > file in any mode. Of course this makes it impossible for the
>> > file to be
>> > shared with other users without modifying the permissions.
>> >
>> > The basic problem here is that ooRexx is ignoring the umask
>> > setting for
>> > the user and always forcing the restricted permissions on a
>> > new file.
>> >
>> > I believe this is a bug and needs to be fixed ASAP. But I
>> > would like
>> > some agreement on this before I open a bug ticket.
>> >
>> > David Ashley
>> >
>> >
>> >
>> --
>> > Rapidly troubleshoot problems before they affect your
>> > business. Most IT
>> > organizations don't have a clear picture of how application
>> > performance
>> > affects their revenue. With AppDynamics, you get 100%
>> > visibility into your
>> > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
>> > AppDynamics Pro!
>> >
>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>> > ___
>> > Oorexx-devel mailing list
>> > Oorexx-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> >
>> >
>> >
>> --
>> > Rapidly troubleshoot problems before they affect your business. Most IT
>> > organizations don't have a clear picture of how application performance
>> > affects their revenue. With AppDynamics, you get 100% visibility into
>> your
>> > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
>> AppDynamics Pro!
>> >
>>
Re: [Oorexx-devel] Bug or Not?
On Thu, Dec 12, 2013 at 1:08 PM, Rick McGuire wrote: > I suspect we need to be doing the right fix rather than the easy fix. > I agree, the easy fix seems worse than the current behavior. What if the user doesn't want others to be able to read the file. Better the user has to manually intervene to share a file with others than manually intervene to not share a file with others. -- Mark Miesfeld -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
