From: Rick M. <obj...@gm...> - 2013-11-23 20:00:02
|
Mark, I've got a fix for this for stream query exists, but could you take a look at the sysfiletree problem? I'm not convinced this is actually a bug, but a quirk of how FindFirstFile works on Windows with wildcard characters. The stream query exists problem was occurring because FindFirstFile was being used to verify the existence, using an already fully qualified name. Rick |
From: Mike C. <mf...@sp...> - 2013-11-23 20:19:36
|
I've got a fix for this for stream query exists, but could you take a look at the sysfiletree problem? I'm not convinced this is actually a bug, but a quirk of how FindFirstFile works on Windows with wildcard characters. The stream query exists problem was occurring because FindFirstFile was being used to verify the existence, using an already fully qualified name. Definitely a place to tread with care ...my isDir and isFile routines go through some 'hoops' ... suggest we discuss if any changes planned. |
From: Mark M. <mie...@gm...> - 2013-11-23 20:35:54
|
On Sat, Nov 23, 2013 at 12:19 PM, Mike Cowlishaw <mf...@sp...>wrote: > > > I've got a fix for this for stream query exists, but could you take a look > at the sysfiletree problem? I'm not convinced this is actually a bug, but > a quirk of how FindFirstFile works on Windows with wildcard characters. > The stream query exists problem was occurring because FindFirstFile was > being used to verify the existence, using an already fully qualified name. > > Definitely a place to tread with care ...my isDir and isFile routines go > through some 'hoops' ... suggest we discuss if any changes planned. > > > Mike, Okay, I'll list any SysFileTree() changes planned in this thread. Are your routines using SysFileTree() or some other mechanism? -- Mark Miesfeld |
From: Mike C. <mf...@sp...> - 2013-11-24 08:04:27
|
I've got a fix for this for stream query exists, but could you take a look at the sysfiletree problem? I'm not convinced this is actually a bug, but a quirk of how FindFirstFile works on Windows with wildcard characters. The stream query exists problem was occurring because FindFirstFile was being used to verify the existence, using an already fully qualified name. Definitely a place to tread with care ...my isDir and isFile routines go through some 'hoops' ... suggest we discuss if any changes planned. Okay, I'll list any SysFileTree() changes planned in this thread. Are your routines using SysFileTree() or some other mechanism? They used to use stream (query exists) but something was flaky there on some kinds of disks, I think (this was a few years ago). My current 'core routine' uses sysfiletree, with the following comment and code. I don't recall why it cannot be used to test for root directory (the old one could be used for that and was the way I tested whether a disk was present). Mike /* --------------------------------------------------------------- */ /* Return 1 if file or directory exists, 0 otherwise */ /* --------------------------------------------------------------- */ /* */ /* Arg1 is fully qualified file or directory name to test */ /* */ /* A file of size 0 is deemed not to exist. */ /* Note this cannot be used to test for root directory. */ /* --------------------------------------------------------------- */ -- 'query exists' doesn't work for directories exists: parse arg spec call sysfiletree spec, 'LIST', 'BL' if list.0\=1 then return 0 -- does not exist parse var list.1 . . size flags . if size>0 then return 1 -- real file return substr(flags, 2, 1)='D' -- 1 if directory, 0 if zero-size file |
From: Mark M. <mie...@gm...> - 2013-11-24 17:07:32
|
On Sun, Nov 24, 2013 at 12:04 AM, Mike Cowlishaw <mf...@sp...>wrote: > > They used to use stream (query exists) but something was flaky there on > some kinds of disks, I think (this was a few years ago). My current 'core > routine' uses sysfiletree, with the following comment and code. I don't > recall why it cannot be used to test for root directory > > That is also due to FindFirstFile. MSDN says: You cannot use root directories as the *lpFileName* input string for *FindFirstFile*—with or without a trailing backslash. If you want to see files or get the attributes of a root directory, do the following: - To see files in a root directory, you can use "C:\*" and step through the directory by using *FindNextFile*. - To get the attributes of a root directory, use *GetFileAttributes*. -- Mark Miesfeld |
From: Mike C. <mf...@sp...> - 2013-11-24 17:16:57
|
On Sun, Nov 24, 2013 at 12:04 AM, Mike Cowlishaw <mf...@sp...> wrote: They used to use stream (query exists) but something was flaky there on some kinds of disks, I think (this was a few years ago). My current 'core routine' uses sysfiletree, with the following comment and code. I don't recall why it cannot be used to test for root directory That is also due to FindFirstFile. MSDN says: You cannot use root directories as the lpFileName input string for FindFirstFile-with or without a trailing backslash. If you want to see files or get the attributes of a root directory, do the following: * To see files in a root directory, you can use "C:\*" and step through the directory by using FindNextFile. * To get the attributes of a root directory, use GetFileAttributes. OK .. thanks. I wasn't aware of the underlying implementation. Bit of a nuisance in this case. Mike |
From: Walter P. <chr...@ch...> - 2013-11-24 17:28:35
|
I am trying to convince someone (you may know who) to try ooRexx. He asked these questions most of which I cannot reliably answer Would anyone of you be kind enough to take the time to fill in the blanks and replace the question marks? Installing ooRexx: What folders does it create? >> C:\Program files (X86)\oorexx Can I name them myself? >> ?? Can I place them elsewhere than the defaults? >> ?? Does it hijack any of my existing associations? >> I guss so ?? What can the file extension(s) [file type(s)] be? >> user defined ?? Can I name them anything I want, or do I have to use specific FTs? >> I guess any can be used None of this stuff is anywhere that I can find. >> ?? not on top There is no read.me file that I can download without going through THE download. >> There is a readme.pdf under docs which is rather extensive A FAQ for (Microsoft) Windows would be nice. >> Is there ?? Can ooRexx and other REXXes play well together? >> I guess so but I don't know (NOT IBM Object Rexx though - but he wouldn't have THAT) Do I HAVE TO go through an install process or can I just copy a few files somewhere and let it fly. >> I guess not really What (or which) Microsoft Windows versions are supported? >> That's in readme.pdf (and was recently discussed Can I run ooRexx in a stand-alone DOS system (i.e., no windows AT ALL), like I can with Regina, PC/REXX and others? >> I Guess NO As for me I prais the ease of installation on Windows, bu then I am happy with ooRexx only :-) Thank y'aa in advance Walter Pachl |
From: Rick M. <obj...@gm...> - 2013-11-24 17:47:41
|
On Sun, Nov 24, 2013 at 12:28 PM, Walter Pachl <chr...@ch... > wrote: > I am trying to convince someone (you may know who) to try ooRexx. > He asked these questions most of which I cannot reliably answer > Would anyone of you be kind enough to take the time to fill in the blanks > and replace the question marks? > > Installing ooRexx: > > What folders does it create? > >> C:\Program files (X86)\oorexx > Can I name them myself? > Yes > >> ?? > Can I place them elsewhere than the defaults? > >> ?? > Yes > Does it hijack any of my existing associations? > >> I guss so ?? > It depends on what constitutes "hijacked". It does define some file associations and does take over any standard file associations. > What can the file extension(s) [file type(s)] be? > >> user defined ?? > Anything. > Can I name them anything I want, or do I have to use specific FTs? > >> I guess any can be used > Any can be used > None of this stuff is anywhere that I can find. > >> ?? not on top > There is no read.me file that I can download without going through > THE download. > >> There is a readme.pdf under docs which is rather extensive > A FAQ for (Microsoft) Windows would be nice. > >> Is there ?? > Can ooRexx and other REXXes play well together? > >> I guess so but I don't know (NOT IBM Object Rexx though - but he > wouldn't have THAT) > Do I HAVE TO go through an install process or can I just copy a few > files somewhere and let it fly. > >> I guess not really > The only versions available for download are the install versions. It is possible to copy the files and run with it, but frankly, that's harder than just installing it. > What (or which) Microsoft Windows versions are supported? > >> That's in readme.pdf (and was recently discussed > Can I run ooRexx in a stand-alone DOS system (i.e., no windows AT ALL), > like I can with Regina, PC/REXX and others? > >> I Guess NO > No, DOS is not one of the platforms we support. > > As for me I prais the ease of installation on Windows, bu then I am happy > with ooRexx only :-) > > Thank y'aa in advance > > Walter Pachl > > > > ------------------------------------------------------------------------------ > Shape the Mobile Experience: Free Subscription > Software experts and developers: Be at the forefront of tech innovation. > Intel(R) Software Adrenaline delivers strategic insight and game-changing > conversations that shape the rapidly evolving mobile landscape. Sign up > now. > http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Walter P. <chr...@ch...> - 2013-11-24 17:56:47
|
-- Walter Pachl ---- Rick McGuire <obj...@gm...> schrieb: > On Sun, Nov 24, 2013 at 12:28 PM, Walter Pachl <chr...@ch... > > wrote: > > > I am trying to convince someone (you may know who) to try ooRexx. > > He asked these questions most of which I cannot reliably answer > > Would anyone of you be kind enough to take the time to fill in the blanks > > and replace the question marks? > > > > Installing ooRexx: > > > > What folders does it create? > > >> C:\Program files (X86)\oorexx > > Can I name them myself? > > > > Yes > > > >> ?? > > Can I place them elsewhere than the defaults? > > >> ?? > > > > Yes > > > > Does it hijack any of my existing associations? > > >> I guss so ?? > > > It depends on what constitutes "hijacked". It does define some file > associations and does take over any standard file associations. > > > > What can the file extension(s) [file type(s)] be? > > >> user defined ?? > > > > Anything. > > > > Can I name them anything I want, or do I have to use specific FTs? > > >> I guess any can be used > > > > Any can be used > > > > None of this stuff is anywhere that I can find. > > >> ?? not on top > > There is no read.me file that I can download without going through > > THE download. > > >> There is a readme.pdf under docs which is rather extensive > > A FAQ for (Microsoft) Windows would be nice. > > >> Is there ?? > > Can ooRexx and other REXXes play well together? > > >> I guess so but I don't know (NOT IBM Object Rexx though - but he > > wouldn't have THAT) > > Do I HAVE TO go through an install process or can I just copy a few > > files somewhere and let it fly. > > >> I guess not really > > > > The only versions available for download are the install versions. It is > possible to copy the files and run with it, but frankly, that's harder than > just installing it. > > > > What (or which) Microsoft Windows versions are supported? > > >> That's in readme.pdf (and was recently discussed > > Can I run ooRexx in a stand-alone DOS system (i.e., no windows AT ALL), > > like I can with Regina, PC/REXX and others? > > >> I Guess NO > > > > No, DOS is not one of the platforms we support. > > > > > As for me I prais the ease of installation on Windows, bu then I am happy > > with ooRexx only :-) > > > > Thank y'aa in advance > > > > Walter Pachl > > > > > > > > ------------------------------------------------------------------------------ > > Shape the Mobile Experience: Free Subscription > > Software experts and developers: Be at the forefront of tech innovation. > > Intel(R) Software Adrenaline delivers strategic insight and game-changing > > conversations that shape the rapidly evolving mobile landscape. Sign up > > now. > > http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
From: Walter P. <chr...@ch...> - 2013-11-24 18:20:03
|
Thanks for the QUICK reaction and sorry for the premature empty reply :-( -- Walter Pachl - |
From: Mark M. <mie...@gm...> - 2013-11-24 18:04:24
|
On Sun, Nov 24, 2013 at 9:28 AM, Walter Pachl <chr...@ch...>wrote: > I am trying to convince someone (you may know who) to try ooRexx. > He asked these questions most of which I cannot reliably answer > Would anyone of you be kind enough to take the time to fill in the blanks > and replace the question marks? > > Installing ooRexx: > Hi Walter, Since the questions themselves are Windows orientated, my answers are Windows specific: > > What folders does it create? > >> C:\Program files (X86)\oorexx > That is the default installation directory name. You have the option of installing to any directory with any name of your choosing. > Can I name them myself? > >> ?? > You can name the default installation directory to whatever you want. You can not rename the subdirectories during installation > Can I place them elsewhere than the defaults? > >> ?? > I'm not sure what he means by that question. The installation directory can be placed anywhere, the subdirectories are placed under the installation directory. > Does it hijack any of my existing associations? > >> I guss so ?? > Only if you accept the defaults. > What can the file extension(s) [file type(s)] be? > >> user defined ?? > Yes, the file extensions / file types can be anything you want > Can I name them anything I want, or do I have to use specific FTs? > >> I guess any can be used > They can be anything you want. > None of this stuff is anywhere that I can find. > >> ?? not on top > There are several read me files in different formats that can be downloaded separately. The explanatory text on the down load page says this: _Readme.pdf Installation help and other relevant notes that should be read prior to installation. _Readme.html The same text as _Readme.pdf in HTML format. Within those files is this: 2.3.2. Running the Installation Program on Windows I'm not going to copy the text from that section, but it is very detailed, answering the questions asked. You can write explanations in a dozen places in dozens of different ways, but most people simply don't read them. > There is no read.me file that I can download without going through > THE download. > >> There is a readme.pdf under docs which is rather extensive > > A FAQ for (Microsoft) Windows would be nice. > >> Is there ?? > There are the read me files I just listed. > Can ooRexx and other REXXes play well together? > >> I guess so but I don't know (NOT IBM Object Rexx though - but he > wouldn't have THAT) > > Do I HAVE TO go through an install process or can I just copy a few > files somewhere and let it fly. > >> I guess not really > He could build the interpreter himself and copy whatever files he wanted. He could run the installer, copy, to save, what files he wanted, run the un-installer, and then use his copied files to install to any systems he wanted. > What (or which) Microsoft Windows versions are supported? > >> That's in readme.pdf (and was recently discussed > > Can I run ooRexx in a stand-alone DOS system (i.e., no windows AT ALL), > like I can with Regina, PC/REXX and others? > >> I Guess NO > If he means an actual DOS system, then no. However, many people use that type of terminology to mean a console window. If that is what he means, then he can run ooRexx in a console. -- Mark Miesfeld |
From: Walter P. <chr...@ch...> - 2013-11-24 18:27:36
|
Another thank you is in order!!!! Last open Q; Can ooRexx and other REXXes play well together? >> I guess so but I don't know (NOT IBM Object Rexx though - but he wouldn't have THAT) Is this guess of mine correct? Greetings Walter |
From: Mark M. <mie...@gm...> - 2013-11-23 20:33:53
|
Rick, Sure I'll look at SysFileTree(). -- Mark Miesfeld On Sat, Nov 23, 2013 at 11:59 AM, Rick McGuire <obj...@gm...>wrote: > Mark, > > I've got a fix for this for stream query exists, but could you take a look > at the sysfiletree problem? I'm not convinced this is actually a bug, but > a quirk of how FindFirstFile works on Windows with wildcard characters. > The stream query exists problem was occurring because FindFirstFile was > being used to verify the existence, using an already fully qualified name. > > Rick > > > ------------------------------------------------------------------------------ > Shape the Mobile Experience: Free Subscription > Software experts and developers: Be at the forefront of tech innovation. > Intel(R) Software Adrenaline delivers strategic insight and game-changing > conversations that shape the rapidly evolving mobile landscape. Sign up > now. > http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
From: Mark M. <mie...@gm...> - 2013-11-23 21:35:54
|
On Sat, Nov 23, 2013 at 12:35 PM, Mark Miesfeld <mie...@gm...> wrote: > On Sat, Nov 23, 2013 at 12:19 PM, Mike Cowlishaw <mf...@sp...>wrote: > >> >> >> I've got a fix for this for stream query exists, but could you take a >> look at the sysfiletree problem? I'm not convinced this is actually a bug, >> but a quirk of how FindFirstFile works on Windows with wildcard characters. >> The stream query exists problem was occurring because FindFirstFile was >> being used to verify the existence, using an already fully qualified name. >> >> For SysFileTree() this is definitely the result of how FindFirstFile() works. It is documented as a bug, although the Microsoft link seems to have been lost. There is information on it here: http://onsec.ru/onsec.whitepaper-02.eng.pdf The pattern used in the me.rex example sent to SysFileTree is: *.?<>* The white paper referenced above explains that FindFirstFile substitutes * for any < character and ? for any > character. So the pattern used becomes essentially: *.?*?* Me expectation is that SysFileTree returns the same results as dir: C:\temp\test>dir *.?*?* Volume in drive C is Win7 Volume Serial Number is D25E-50D5 Directory of C:\temp\test 11/23/2013 01:06 PM <DIR> . 11/23/2013 01:06 PM <DIR> .. 11/23/2013 01:15 PM 465 me.rex 11/23/2013 12:39 PM 421 me.rexx 2 File(s) 886 bytes 2 Dir(s) 1,848,860,672 bytes free C:\temp\test> So, the results are to be expected when one knows about the FindFirstFile behaviour. > >> Definitely a place to tread with care ...my isDir and isFile routines >> go through some 'hoops' ... suggest we discuss if any changes planned. >> >> >> > The bug itself was opened in relation to SysFileTree on Windows. I don't know how this plays out on Linux, but as I recall Linux file systems do not really have illegal characters except the slash and null. So, I don't think it is much of a problem except on Windows I see 3 possible changes: 1.) Add to the doc that if you use illegal characters in the pattern, your results are undefined. 2.) Check the pattern and if illegal characters are present set stem.0 to 0 and return an error code. 3.) Check the pattern for illegal characters and if present raise a syntax condition. For myself, I prefer 3, because if I'm writing Rexx code I always test the program before real use and prefer a syntax condition so I immediately know I have to fix something before I am finished testing. Mike and Rick probably prefer 1 or 2. -- Mark Miesfeld |
From: Rick M. <obj...@gm...> - 2013-11-23 21:47:56
|
We already have a precedent of option 2 for other illegal characters (e.g. ":"). Rick On Sat, Nov 23, 2013 at 4:35 PM, Mark Miesfeld <mie...@gm...> wrote: > On Sat, Nov 23, 2013 at 12:35 PM, Mark Miesfeld <mie...@gm...>wrote: > >> On Sat, Nov 23, 2013 at 12:19 PM, Mike Cowlishaw <mf...@sp...>wrote: >> >>> >>> >>> I've got a fix for this for stream query exists, but could you take a >>> look at the sysfiletree problem? I'm not convinced this is actually a bug, >>> but a quirk of how FindFirstFile works on Windows with wildcard characters. >>> The stream query exists problem was occurring because FindFirstFile was >>> being used to verify the existence, using an already fully qualified name. >>> >>> > For SysFileTree() this is definitely the result of how FindFirstFile() > works. It is documented as a bug, although the Microsoft link seems to > have been lost. There is information on it here: > > http://onsec.ru/onsec.whitepaper-02.eng.pdf > > The pattern used in the me.rex example sent to SysFileTree is: *.?<>* > > The white paper referenced above explains that FindFirstFile substitutes * > for any < character and ? for any > character. > > So the pattern used becomes essentially: *.?*?* > > Me expectation is that SysFileTree returns the same results as dir: > > C:\temp\test>dir *.?*?* > Volume in drive C is Win7 > Volume Serial Number is D25E-50D5 > > Directory of C:\temp\test > > 11/23/2013 01:06 PM <DIR> . > 11/23/2013 01:06 PM <DIR> .. > 11/23/2013 01:15 PM 465 me.rex > 11/23/2013 12:39 PM 421 me.rexx > 2 File(s) 886 bytes > 2 Dir(s) 1,848,860,672 bytes free > > C:\temp\test> > > So, the results are to be expected when one knows about the FindFirstFile > behaviour. > > >> >>> Definitely a place to tread with care ...my isDir and isFile routines >>> go through some 'hoops' ... suggest we discuss if any changes planned. >>> >>> >>> >> > The bug itself was opened in relation to SysFileTree on Windows. I don't > know how this plays out on Linux, but as I recall Linux file systems do not > really have illegal characters except the slash and null. So, I don't > think it is much of a problem except on Windows > > I see 3 possible changes: > > 1.) Add to the doc that if you use illegal characters in the pattern, > your results are undefined. > > 2.) Check the pattern and if illegal characters are present set stem.0 to > 0 and return an error code. > > 3.) Check the pattern for illegal characters and if present raise a syntax > condition. > > For myself, I prefer 3, because if I'm writing Rexx code I always test the > program before real use and prefer a syntax condition so I immediately know > I have to fix something before I am finished testing. > > Mike and Rick probably prefer 1 or 2. > > -- > Mark Miesfeld > > > > ------------------------------------------------------------------------------ > Shape the Mobile Experience: Free Subscription > Software experts and developers: Be at the forefront of tech innovation. > Intel(R) Software Adrenaline delivers strategic insight and game-changing > conversations that shape the rapidly evolving mobile landscape. Sign up > now. > http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
From: Mark M. <mie...@gm...> - 2013-11-23 21:50:17
|
Okay, I'll implement that tonight. -- Mark Miesfeld On Sat, Nov 23, 2013 at 1:47 PM, Rick McGuire <obj...@gm...> wrote: > We already have a precedent of option 2 for other illegal characters (e.g. > ":"). > > Rick > > > On Sat, Nov 23, 2013 at 4:35 PM, Mark Miesfeld <mie...@gm...> wrote: > >> On Sat, Nov 23, 2013 at 12:35 PM, Mark Miesfeld <mie...@gm...>wrote: >> >>> On Sat, Nov 23, 2013 at 12:19 PM, Mike Cowlishaw <mf...@sp...>wrote: >>> >>>> >>>> >>>> I've got a fix for this for stream query exists, but could you take a >>>> look at the sysfiletree problem? I'm not convinced this is actually a bug, >>>> but a quirk of how FindFirstFile works on Windows with wildcard characters. >>>> The stream query exists problem was occurring because FindFirstFile was >>>> being used to verify the existence, using an already fully qualified name. >>>> >>>> >> For SysFileTree() this is definitely the result of how FindFirstFile() >> works. It is documented as a bug, although the Microsoft link seems to >> have been lost. There is information on it here: >> >> http://onsec.ru/onsec.whitepaper-02.eng.pdf >> >> The pattern used in the me.rex example sent to SysFileTree is: *.?<>* >> >> The white paper referenced above explains that FindFirstFile substitutes >> * for any < character and ? for any > character. >> >> So the pattern used becomes essentially: *.?*?* >> >> Me expectation is that SysFileTree returns the same results as dir: >> >> C:\temp\test>dir *.?*?* >> Volume in drive C is Win7 >> Volume Serial Number is D25E-50D5 >> >> Directory of C:\temp\test >> >> 11/23/2013 01:06 PM <DIR> . >> 11/23/2013 01:06 PM <DIR> .. >> 11/23/2013 01:15 PM 465 me.rex >> 11/23/2013 12:39 PM 421 me.rexx >> 2 File(s) 886 bytes >> 2 Dir(s) 1,848,860,672 bytes free >> >> C:\temp\test> >> >> So, the results are to be expected when one knows about the FindFirstFile >> behaviour. >> >> >>> >>>> Definitely a place to tread with care ...my isDir and isFile routines >>>> go through some 'hoops' ... suggest we discuss if any changes planned. >>>> >>>> >>>> >>> >> The bug itself was opened in relation to SysFileTree on Windows. I don't >> know how this plays out on Linux, but as I recall Linux file systems do not >> really have illegal characters except the slash and null. So, I don't >> think it is much of a problem except on Windows >> >> I see 3 possible changes: >> >> 1.) Add to the doc that if you use illegal characters in the pattern, >> your results are undefined. >> >> 2.) Check the pattern and if illegal characters are present set stem.0 >> to 0 and return an error code. >> >> 3.) Check the pattern for illegal characters and if present raise a >> syntax condition. >> >> For myself, I prefer 3, because if I'm writing Rexx code I always test >> the program before real use and prefer a syntax condition so I immediately >> know I have to fix something before I am finished testing. >> >> Mike and Rick probably prefer 1 or 2. >> >> -- >> Mark Miesfeld >> >> >> >> ------------------------------------------------------------------------------ >> Shape the Mobile Experience: Free Subscription >> Software experts and developers: Be at the forefront of tech innovation. >> Intel(R) Software Adrenaline delivers strategic insight and game-changing >> conversations that shape the rapidly evolving mobile landscape. Sign up >> now. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > ------------------------------------------------------------------------------ > Shape the Mobile Experience: Free Subscription > Software experts and developers: Be at the forefront of tech innovation. > Intel(R) Software Adrenaline delivers strategic insight and game-changing > conversations that shape the rapidly evolving mobile landscape. Sign up > now. > http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |