Menu
▾
▴
oorexx-devel — Open Object Rexx Developer Mailing List
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
|
Mar
(2) |
Apr
(4) |
May
(35) |
Jun
(6) |
Jul
(23) |
Aug
(25) |
Sep
|
Oct
(72) |
Nov
(25) |
Dec
(13) |
| 2006 |
Jan
(104) |
Feb
(19) |
Mar
(43) |
Apr
(19) |
May
(62) |
Jun
(133) |
Jul
(44) |
Aug
(46) |
Sep
(68) |
Oct
(45) |
Nov
(97) |
Dec
(19) |
| 2007 |
Jan
(75) |
Feb
(232) |
Mar
(116) |
Apr
(368) |
May
(111) |
Jun
(134) |
Jul
(97) |
Aug
(107) |
Sep
(173) |
Oct
(579) |
Nov
(256) |
Dec
(213) |
| 2008 |
Jan
(242) |
Feb
(73) |
Mar
(26) |
Apr
(13) |
May
(10) |
Jun
(201) |
Jul
(367) |
Aug
(341) |
Sep
(246) |
Oct
(304) |
Nov
(104) |
Dec
(103) |
| 2009 |
Jan
(80) |
Feb
(183) |
Mar
(165) |
Apr
(302) |
May
(255) |
Jun
(136) |
Jul
(189) |
Aug
(107) |
Sep
(179) |
Oct
(94) |
Nov
(47) |
Dec
(86) |
| 2010 |
Jan
(102) |
Feb
(142) |
Mar
(86) |
Apr
(182) |
May
(77) |
Jun
(56) |
Jul
(14) |
Aug
(182) |
Sep
(117) |
Oct
(87) |
Nov
(76) |
Dec
(76) |
| 2011 |
Jan
(27) |
Feb
(196) |
Mar
(69) |
Apr
(26) |
May
(9) |
Jun
(54) |
Jul
(60) |
Aug
(49) |
Sep
(11) |
Oct
(38) |
Nov
(49) |
Dec
(32) |
| 2012 |
Jan
(61) |
Feb
(166) |
Mar
(72) |
Apr
(66) |
May
(33) |
Jun
(138) |
Jul
(89) |
Aug
(354) |
Sep
(61) |
Oct
(69) |
Nov
(60) |
Dec
(45) |
| 2013 |
Jan
(14) |
Feb
(13) |
Mar
(29) |
Apr
(52) |
May
(63) |
Jun
(68) |
Jul
(32) |
Aug
(13) |
Sep
(34) |
Oct
(49) |
Nov
(86) |
Dec
(219) |
| 2014 |
Jan
(101) |
Feb
(72) |
Mar
(50) |
Apr
(32) |
May
(99) |
Jun
(141) |
Jul
(89) |
Aug
(14) |
Sep
(137) |
Oct
(221) |
Nov
(18) |
Dec
(10) |
| 2015 |
Jan
(50) |
Feb
(12) |
Mar
(33) |
Apr
(86) |
May
(72) |
Jun
(90) |
Jul
(33) |
Aug
(9) |
Sep
(9) |
Oct
(27) |
Nov
(25) |
Dec
(9) |
| 2016 |
Jan
(16) |
Feb
(27) |
Mar
(16) |
Apr
(12) |
May
(23) |
Jun
(80) |
Jul
(127) |
Aug
(39) |
Sep
(12) |
Oct
(32) |
Nov
(20) |
Dec
(29) |
| 2017 |
Jan
(46) |
Feb
(77) |
Mar
(19) |
Apr
(36) |
May
(99) |
Jun
(45) |
Jul
(75) |
Aug
(53) |
Sep
(26) |
Oct
(57) |
Nov
(22) |
Dec
(4) |
| 2018 |
Jan
(11) |
Feb
(48) |
Mar
(80) |
Apr
(159) |
May
(41) |
Jun
(10) |
Jul
(36) |
Aug
(84) |
Sep
(76) |
Oct
(38) |
Nov
(177) |
Dec
(319) |
| 2019 |
Jan
(213) |
Feb
(244) |
Mar
(95) |
Apr
(48) |
May
(19) |
Jun
(3) |
Jul
(2) |
Aug
(17) |
Sep
(16) |
Oct
(35) |
Nov
(68) |
Dec
(20) |
| 2020 |
Jan
(16) |
Feb
(91) |
Mar
(244) |
Apr
(139) |
May
(13) |
Jun
(42) |
Jul
(29) |
Aug
(60) |
Sep
(53) |
Oct
(19) |
Nov
(63) |
Dec
(3) |
| 2021 |
Jan
(51) |
Feb
(72) |
Mar
(87) |
Apr
(31) |
May
(19) |
Jun
(73) |
Jul
(93) |
Aug
(31) |
Sep
(24) |
Oct
(79) |
Nov
(60) |
Dec
(24) |
| 2022 |
Jan
(49) |
Feb
(33) |
Mar
(13) |
Apr
(29) |
May
(92) |
Jun
(66) |
Jul
(64) |
Aug
(54) |
Sep
(22) |
Oct
(2) |
Nov
(23) |
Dec
(252) |
| 2023 |
Jan
(100) |
Feb
(121) |
Mar
(13) |
Apr
(43) |
May
(46) |
Jun
(24) |
Jul
(19) |
Aug
(8) |
Sep
(17) |
Oct
(15) |
Nov
(25) |
Dec
(24) |
| 2024 |
Jan
(43) |
Feb
(14) |
Mar
(40) |
Apr
(34) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: David A. <dav...@gm...> - 2008-11-10 20:29:35
|
Rick McGuire wrote: > I parallel to this (or maybe even preceding the build machine switch), > shouldn't we see if we can get the docs to to build cleanly on Fedora > 9? > > Rick > > On Mon, Nov 10, 2008 at 3:08 PM, Mark Miesfeld <mie...@gm...> wrote: > >> On Mon, Nov 10, 2008 at 11:14 AM, David Ashley >> <dav...@gm...> wrote: >> >> >>> ... >>> >>> So, I am going to propose a plan. This plan will mean the Build Machine >>> will be offline for possibly a week, maybe more if I run into real >>> trouble. But here it is. >>> >>> 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. >>> 2. If I can not get the above to work fall back and install Red Hat 5.2 >>> and VMware Server 2.0 on the Build Machine. >>> 3. Upgrade the VM guests and possibly install new guests (or upgrade old >>> guests) to newer versions. >>> >>> Please let me know if this is a problem for anyone. Also let me know if >>> you have preferred versions of VM guests that you would like to see >>> installed. >>> >> Kind of late getting back to the thread. But, I don't have any >> problem with your plan. Do whatever you think is right. >> >> -- >> Mark Miesfeld >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > I will work on that first. David Ashley |
|
From: Rick M. <obj...@gm...> - 2008-11-10 20:27:36
|
I parallel to this (or maybe even preceding the build machine switch), shouldn't we see if we can get the docs to to build cleanly on Fedora 9? Rick On Mon, Nov 10, 2008 at 3:08 PM, Mark Miesfeld <mie...@gm...> wrote: > On Mon, Nov 10, 2008 at 11:14 AM, David Ashley > <dav...@gm...> wrote: > >> ... >> >> So, I am going to propose a plan. This plan will mean the Build Machine >> will be offline for possibly a week, maybe more if I run into real >> trouble. But here it is. >> >> 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. >> 2. If I can not get the above to work fall back and install Red Hat 5.2 >> and VMware Server 2.0 on the Build Machine. >> 3. Upgrade the VM guests and possibly install new guests (or upgrade old >> guests) to newer versions. >> >> Please let me know if this is a problem for anyone. Also let me know if >> you have preferred versions of VM guests that you would like to see >> installed. > > Kind of late getting back to the thread. But, I don't have any > problem with your plan. Do whatever you think is right. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
|
From: Mark M. <mie...@gm...> - 2008-11-10 20:13:00
|
On Mon, Nov 10, 2008 at 9:43 AM, Rick McGuire <obj...@gm...> wrote: > ... > If we're > getting missing imagedata end tag errors now, that might actually be a > good thing, as before, we got errors if the end tags were specified. Actually, I was getting errors no matter what I did. With the tags as they were, I would get missing end tag errors. If I changed the > to /> I get an error about character data not being allowed there. And if I added a </imagedata> then I get an error saying there was no open imagedata tag. That's when I decided I needed help from the expert. <grin> -- Mark Miesfeld |
|
From: Mark M. <mie...@gm...> - 2008-11-10 20:08:52
|
On Mon, Nov 10, 2008 at 11:14 AM, David Ashley <dav...@gm...> wrote: > ... > > So, I am going to propose a plan. This plan will mean the Build Machine > will be offline for possibly a week, maybe more if I run into real > trouble. But here it is. > > 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. > 2. If I can not get the above to work fall back and install Red Hat 5.2 > and VMware Server 2.0 on the Build Machine. > 3. Upgrade the VM guests and possibly install new guests (or upgrade old > guests) to newer versions. > > Please let me know if this is a problem for anyone. Also let me know if > you have preferred versions of VM guests that you would like to see > installed. Kind of late getting back to the thread. But, I don't have any problem with your plan. Do whatever you think is right. -- Mark Miesfeld |
|
From: Rick M. <obj...@gm...> - 2008-11-10 19:48:35
|
I think I also installed it directly from an ISO image mapped to the DVD drive. Rick On Mon, Nov 10, 2008 at 2:46 PM, David Ashley <dav...@gm...> wrote: > Rick McGuire wrote: > > That's what I mean. I have Fedora 9 running as a guest OS on VMWare > Server 1.0. However, VMWare is running on Windows, which might be the > difference. > > Rick > > On Mon, Nov 10, 2008 at 2:25 PM, David Ashley > <dav...@gm...> wrote: > > > Rick McGuire wrote: > > That's interesting, because that's exactly how I run it....Fedora 9 on > VMWare 1.0. > > Rick > > On Mon, Nov 10, 2008 at 2:14 PM, David Ashley > <dav...@gm...> wrote: > > > All - > > New problem, actually, an old problem I had forgotten about. > > Fedora 9 will not install on a VMware Server 1.0 system as a guest OS. :-( > > This is the reason I was investigating VMware Server 2.0. The old VMware > Server has problems with all the new Linux distributions. It has to do > with the Linux kernel being used in the latest distributions. There is > some kind of problem with that kernel and the old VMware Server. > > I have experimented with the latest VMware Server running on Red Hat 5.2 > and Fedora 9. I can get either of those two kinds of systems running > without problems. There are some other advantages I will not go into > here for upgrading to the new VMware. > > However there is one small problem. Fedora 9 has a problem on my > hardware with the network card. Currently I have only tried this on my > older server so I don't know if the problem will exist on the Build > machine or not. The problem has to do with the static IP address data > not being saved properly and on reboot the info is essentially lost. > This happens on Fedora 9 but not on Red Hat 5.2. > > So, I am going to propose a plan. This plan will mean the Build Machine > will be offline for possibly a week, maybe more if I run into real > trouble. But here it is. > > 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. > 2. If I can not get the above to work fall back and install Red Hat 5.2 > and VMware Server 2.0 on the Build Machine. > 3. Upgrade the VM guests and possibly install new guests (or upgrade old > guests) to newer versions. > > Please let me know if this is a problem for anyone. Also let me know if > you have preferred versions of VM guests that you would like to see > installed. > > David Ashley > ooRexx Team > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > N, the other way. You can not install Fedora 9 as a guest OS. > > David Ashley > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > That might be the problem. All I know is the the DVD for Fedora 9 will not > boot as a guest VM. I have tried several guest OS settings and none appear > to allow the DVD to boot. > > Bummer. > > David Ashley > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
|
From: David A. <dav...@gm...> - 2008-11-10 19:46:54
|
Rick McGuire wrote: > That's what I mean. I have Fedora 9 running as a guest OS on VMWare > Server 1.0. However, VMWare is running on Windows, which might be the > difference. > > Rick > > On Mon, Nov 10, 2008 at 2:25 PM, David Ashley > <dav...@gm...> wrote: > >> Rick McGuire wrote: >> >> That's interesting, because that's exactly how I run it....Fedora 9 on >> VMWare 1.0. >> >> Rick >> >> On Mon, Nov 10, 2008 at 2:14 PM, David Ashley >> <dav...@gm...> wrote: >> >> >> All - >> >> New problem, actually, an old problem I had forgotten about. >> >> Fedora 9 will not install on a VMware Server 1.0 system as a guest OS. :-( >> >> This is the reason I was investigating VMware Server 2.0. The old VMware >> Server has problems with all the new Linux distributions. It has to do >> with the Linux kernel being used in the latest distributions. There is >> some kind of problem with that kernel and the old VMware Server. >> >> I have experimented with the latest VMware Server running on Red Hat 5.2 >> and Fedora 9. I can get either of those two kinds of systems running >> without problems. There are some other advantages I will not go into >> here for upgrading to the new VMware. >> >> However there is one small problem. Fedora 9 has a problem on my >> hardware with the network card. Currently I have only tried this on my >> older server so I don't know if the problem will exist on the Build >> machine or not. The problem has to do with the static IP address data >> not being saved properly and on reboot the info is essentially lost. >> This happens on Fedora 9 but not on Red Hat 5.2. >> >> So, I am going to propose a plan. This plan will mean the Build Machine >> will be offline for possibly a week, maybe more if I run into real >> trouble. But here it is. >> >> 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. >> 2. If I can not get the above to work fall back and install Red Hat 5.2 >> and VMware Server 2.0 on the Build Machine. >> 3. Upgrade the VM guests and possibly install new guests (or upgrade old >> guests) to newer versions. >> >> Please let me know if this is a problem for anyone. Also let me know if >> you have preferred versions of VM guests that you would like to see >> installed. >> >> David Ashley >> ooRexx Team >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >> >> N, the other way. You can not install Fedora 9 as a guest OS. >> >> David Ashley >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > That might be the problem. All I know is the the DVD for Fedora 9 will not boot as a guest VM. I have tried several guest OS settings and none appear to allow the DVD to boot. Bummer. David Ashley |
|
From: Rick M. <obj...@gm...> - 2008-11-10 19:28:07
|
That's what I mean. I have Fedora 9 running as a guest OS on VMWare Server 1.0. However, VMWare is running on Windows, which might be the difference. Rick On Mon, Nov 10, 2008 at 2:25 PM, David Ashley <dav...@gm...> wrote: > Rick McGuire wrote: > > That's interesting, because that's exactly how I run it....Fedora 9 on > VMWare 1.0. > > Rick > > On Mon, Nov 10, 2008 at 2:14 PM, David Ashley > <dav...@gm...> wrote: > > > All - > > New problem, actually, an old problem I had forgotten about. > > Fedora 9 will not install on a VMware Server 1.0 system as a guest OS. :-( > > This is the reason I was investigating VMware Server 2.0. The old VMware > Server has problems with all the new Linux distributions. It has to do > with the Linux kernel being used in the latest distributions. There is > some kind of problem with that kernel and the old VMware Server. > > I have experimented with the latest VMware Server running on Red Hat 5.2 > and Fedora 9. I can get either of those two kinds of systems running > without problems. There are some other advantages I will not go into > here for upgrading to the new VMware. > > However there is one small problem. Fedora 9 has a problem on my > hardware with the network card. Currently I have only tried this on my > older server so I don't know if the problem will exist on the Build > machine or not. The problem has to do with the static IP address data > not being saved properly and on reboot the info is essentially lost. > This happens on Fedora 9 but not on Red Hat 5.2. > > So, I am going to propose a plan. This plan will mean the Build Machine > will be offline for possibly a week, maybe more if I run into real > trouble. But here it is. > > 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. > 2. If I can not get the above to work fall back and install Red Hat 5.2 > and VMware Server 2.0 on the Build Machine. > 3. Upgrade the VM guests and possibly install new guests (or upgrade old > guests) to newer versions. > > Please let me know if this is a problem for anyone. Also let me know if > you have preferred versions of VM guests that you would like to see > installed. > > David Ashley > ooRexx Team > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > N, the other way. You can not install Fedora 9 as a guest OS. > > David Ashley > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
|
From: David A. <dav...@gm...> - 2008-11-10 19:25:57
|
Rick McGuire wrote: > That's interesting, because that's exactly how I run it....Fedora 9 on > VMWare 1.0. > > Rick > > On Mon, Nov 10, 2008 at 2:14 PM, David Ashley > <dav...@gm...> wrote: > >> All - >> >> New problem, actually, an old problem I had forgotten about. >> >> Fedora 9 will not install on a VMware Server 1.0 system as a guest OS. :-( >> >> This is the reason I was investigating VMware Server 2.0. The old VMware >> Server has problems with all the new Linux distributions. It has to do >> with the Linux kernel being used in the latest distributions. There is >> some kind of problem with that kernel and the old VMware Server. >> >> I have experimented with the latest VMware Server running on Red Hat 5.2 >> and Fedora 9. I can get either of those two kinds of systems running >> without problems. There are some other advantages I will not go into >> here for upgrading to the new VMware. >> >> However there is one small problem. Fedora 9 has a problem on my >> hardware with the network card. Currently I have only tried this on my >> older server so I don't know if the problem will exist on the Build >> machine or not. The problem has to do with the static IP address data >> not being saved properly and on reboot the info is essentially lost. >> This happens on Fedora 9 but not on Red Hat 5.2. >> >> So, I am going to propose a plan. This plan will mean the Build Machine >> will be offline for possibly a week, maybe more if I run into real >> trouble. But here it is. >> >> 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. >> 2. If I can not get the above to work fall back and install Red Hat 5.2 >> and VMware Server 2.0 on the Build Machine. >> 3. Upgrade the VM guests and possibly install new guests (or upgrade old >> guests) to newer versions. >> >> Please let me know if this is a problem for anyone. Also let me know if >> you have preferred versions of VM guests that you would like to see >> installed. >> >> David Ashley >> ooRexx Team >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > N, the other way. You can not install Fedora 9 as a guest OS. David Ashley |
|
From: Rick M. <obj...@gm...> - 2008-11-10 19:19:05
|
That's interesting, because that's exactly how I run it....Fedora 9 on VMWare 1.0. Rick On Mon, Nov 10, 2008 at 2:14 PM, David Ashley <dav...@gm...> wrote: > All - > > New problem, actually, an old problem I had forgotten about. > > Fedora 9 will not install on a VMware Server 1.0 system as a guest OS. :-( > > This is the reason I was investigating VMware Server 2.0. The old VMware > Server has problems with all the new Linux distributions. It has to do > with the Linux kernel being used in the latest distributions. There is > some kind of problem with that kernel and the old VMware Server. > > I have experimented with the latest VMware Server running on Red Hat 5.2 > and Fedora 9. I can get either of those two kinds of systems running > without problems. There are some other advantages I will not go into > here for upgrading to the new VMware. > > However there is one small problem. Fedora 9 has a problem on my > hardware with the network card. Currently I have only tried this on my > older server so I don't know if the problem will exist on the Build > machine or not. The problem has to do with the static IP address data > not being saved properly and on reboot the info is essentially lost. > This happens on Fedora 9 but not on Red Hat 5.2. > > So, I am going to propose a plan. This plan will mean the Build Machine > will be offline for possibly a week, maybe more if I run into real > trouble. But here it is. > > 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. > 2. If I can not get the above to work fall back and install Red Hat 5.2 > and VMware Server 2.0 on the Build Machine. > 3. Upgrade the VM guests and possibly install new guests (or upgrade old > guests) to newer versions. > > Please let me know if this is a problem for anyone. Also let me know if > you have preferred versions of VM guests that you would like to see > installed. > > David Ashley > ooRexx Team > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
|
From: David A. <dav...@gm...> - 2008-11-10 19:15:04
|
All - New problem, actually, an old problem I had forgotten about. Fedora 9 will not install on a VMware Server 1.0 system as a guest OS. :-( This is the reason I was investigating VMware Server 2.0. The old VMware Server has problems with all the new Linux distributions. It has to do with the Linux kernel being used in the latest distributions. There is some kind of problem with that kernel and the old VMware Server. I have experimented with the latest VMware Server running on Red Hat 5.2 and Fedora 9. I can get either of those two kinds of systems running without problems. There are some other advantages I will not go into here for upgrading to the new VMware. However there is one small problem. Fedora 9 has a problem on my hardware with the network card. Currently I have only tried this on my older server so I don't know if the problem will exist on the Build machine or not. The problem has to do with the static IP address data not being saved properly and on reboot the info is essentially lost. This happens on Fedora 9 but not on Red Hat 5.2. So, I am going to propose a plan. This plan will mean the Build Machine will be offline for possibly a week, maybe more if I run into real trouble. But here it is. 1. Install Fedora 9 and VMware Server 2.0 on the Build Machine. 2. If I can not get the above to work fall back and install Red Hat 5.2 and VMware Server 2.0 on the Build Machine. 3. Upgrade the VM guests and possibly install new guests (or upgrade old guests) to newer versions. Please let me know if this is a problem for anyone. Also let me know if you have preferred versions of VM guests that you would like to see installed. David Ashley ooRexx Team |
|
From: Rick M. <obj...@gm...> - 2008-11-10 18:13:07
|
I'm +10000000 for the Fedora 9 upgrade, since this means tools like XMLMind have a chance of being used to update/manage the docs. My build system is already at that level, so I'm been without the capability of doing a local build for some time. Rick On Mon, Nov 10, 2008 at 1:09 PM, David Ashley <dav...@gm...> wrote: > Rick McGuire wrote: > > This looks like the type of errors I was getting when I tried to build > the docs on my Fedora 9 system. David took the todo to figure out the > problem then, but I'm not sure he ever got around to it. If we're > getting missing imagedata end tag errors now, that might actually be a > good thing, as before, we got errors if the end tags were specified. > Unfortunately, it also means many tools for working with XML files > would gag on the doc files because they were malformed. A few weeks > ago, I was attempting to use the XMLMind wysiwyg editor as a review > tool, and gave up once I hit the imagedata gotcha. > > Rick > > On Mon, Nov 10, 2008 at 11:57 AM, Mark Miesfeld <mie...@gm...> wrote: > > > David, > > When you have some time can you take a look at the rexxref doc sgml files. > > rexxref doesn't build on the build machine, nor on my local machine. > There were a lot of syntax errors, many of which I fixed. But there > are still a lot of errors that say: end tag for "imagedata" omitted, > but OMITTAG NO was specified. I can't figure out: why they started > showing up, how to fix them. > > There are also a couple for colspec which seem like the same thing. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > Ok, we need to make a decision here. On Fedora 9 the bug is now fixed > concerning the bad image end tag. This means that if we leave the docs as is > they will not compile on a Fedora 9 system. If we fix them they will not > format on anything before Fedora 9. > > IMHO we should upgrade the docs so they compile correctly on Fedora 9. This > means I will need to upgrade the build machine with a Fedora 9 VM and move > the docs build to that VM. > > Any objections? > > David Ashley > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
|
From: David A. <dav...@gm...> - 2008-11-10 18:09:47
|
Rick McGuire wrote: > This looks like the type of errors I was getting when I tried to build > the docs on my Fedora 9 system. David took the todo to figure out the > problem then, but I'm not sure he ever got around to it. If we're > getting missing imagedata end tag errors now, that might actually be a > good thing, as before, we got errors if the end tags were specified. > Unfortunately, it also means many tools for working with XML files > would gag on the doc files because they were malformed. A few weeks > ago, I was attempting to use the XMLMind wysiwyg editor as a review > tool, and gave up once I hit the imagedata gotcha. > > Rick > > On Mon, Nov 10, 2008 at 11:57 AM, Mark Miesfeld <mie...@gm...> wrote: > >> David, >> >> When you have some time can you take a look at the rexxref doc sgml files. >> >> rexxref doesn't build on the build machine, nor on my local machine. >> There were a lot of syntax errors, many of which I fixed. But there >> are still a lot of errors that say: end tag for "imagedata" omitted, >> but OMITTAG NO was specified. I can't figure out: why they started >> showing up, how to fix them. >> >> There are also a couple for colspec which seem like the same thing. >> >> -- >> Mark Miesfeld >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > Ok, we need to make a decision here. On Fedora 9 the bug is now fixed concerning the bad image end tag. This means that if we leave the docs as is they will not compile on a Fedora 9 system. If we fix them they will not format on anything before Fedora 9. IMHO we should upgrade the docs so they compile correctly on Fedora 9. This means I will need to upgrade the build machine with a Fedora 9 VM and move the docs build to that VM. Any objections? David Ashley |
|
From: Rick M. <obj...@gm...> - 2008-11-10 18:09:19
|
Yes, but note that every single occurrence of the imagedata tags comes complete with a comment warning you that actually closing those tags will give an error. Perhaps this has been corrected now with the newer processor releases, but we need to have the expert look at it. Rick On Mon, Nov 10, 2008 at 1:06 PM, Brandon Cherry <br...@sa...> wrote: > Just to point it out, there should be a "/" before the ">". > -- > Brandon Cherry > > Brandon Cherry wrote: >> Looks like self closing tags are wrong. >> >> References: >> http://www.docbook.org/tdg/en/html/imagedata.html#d0e92395 >> http://help.unc.edu/?id=4765#d0e677 > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
|
From: Brandon C. <br...@sa...> - 2008-11-10 18:06:35
|
Just to point it out, there should be a "/" before the ">". -- Brandon Cherry Brandon Cherry wrote: > Looks like self closing tags are wrong. > > References: > http://www.docbook.org/tdg/en/html/imagedata.html#d0e92395 > http://help.unc.edu/?id=4765#d0e677 |
|
From: Brandon C. <br...@sa...> - 2008-11-10 18:05:25
|
Looks like self closing tags are wrong. References: http://www.docbook.org/tdg/en/html/imagedata.html#d0e92395 http://help.unc.edu/?id=4765#d0e677 -- Brandon Cherry Mark Miesfeld wrote: > David, > > When you have some time can you take a look at the rexxref doc sgml files. > > rexxref doesn't build on the build machine, nor on my local machine. > There were a lot of syntax errors, many of which I fixed. But there > are still a lot of errors that say: end tag for "imagedata" omitted, > but OMITTAG NO was specified. I can't figure out: why they started > showing up, how to fix them. > > There are also a couple for colspec which seem like the same thing. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
|
From: Rick M. <obj...@gm...> - 2008-11-10 17:43:38
|
This looks like the type of errors I was getting when I tried to build the docs on my Fedora 9 system. David took the todo to figure out the problem then, but I'm not sure he ever got around to it. If we're getting missing imagedata end tag errors now, that might actually be a good thing, as before, we got errors if the end tags were specified. Unfortunately, it also means many tools for working with XML files would gag on the doc files because they were malformed. A few weeks ago, I was attempting to use the XMLMind wysiwyg editor as a review tool, and gave up once I hit the imagedata gotcha. Rick On Mon, Nov 10, 2008 at 11:57 AM, Mark Miesfeld <mie...@gm...> wrote: > David, > > When you have some time can you take a look at the rexxref doc sgml files. > > rexxref doesn't build on the build machine, nor on my local machine. > There were a lot of syntax errors, many of which I fixed. But there > are still a lot of errors that say: end tag for "imagedata" omitted, > but OMITTAG NO was specified. I can't figure out: why they started > showing up, how to fix them. > > There are also a couple for colspec which seem like the same thing. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
|
From: Mark M. <mie...@gm...> - 2008-11-10 16:57:45
|
David, When you have some time can you take a look at the rexxref doc sgml files. rexxref doesn't build on the build machine, nor on my local machine. There were a lot of syntax errors, many of which I fixed. But there are still a lot of errors that say: end tag for "imagedata" omitted, but OMITTAG NO was specified. I can't figure out: why they started showing up, how to fix them. There are also a couple for colspec which seem like the same thing. -- Mark Miesfeld |
|
From: Mark M. <mie...@gm...> - 2008-11-09 22:27:52
|
On Sun, Nov 9, 2008 at 12:58 PM, Rick McGuire <obj...@gm...> wrote: > I think the first would be most useful, and also head off the "I'm > getting error code nnnnn back from an ole operation. Where is this > documented?" questions. How many of the errors are describable? I think the first is most useful also, it's what I would want. The errors are only describable if they come from system components, of if the application designer picked existing HRESULT values. In other words all the HRESULT values in WinError.h would have a description. However, there is a range of values that applications can use for their own reasons. That's what Excel is doing for the VT_ERROR returns that prompted the bug to begin with. Those don't have any description. If you were working with Excel you could map the hexadecimal string to a certain error through trial and error. I don't see anywhere that Excel has them documented. The Excel spreadsheet that was attached to the bug would give the poster a good start. For instance, 0x800a07d7 is returned for a cell that has #DIV/0!, 0x800a07ed is returned for #NAME?, 0x800a07e7 is returned for #REF!, etc. It is possible that other applications with an OLE interface document their error messages. I'll go with that form, it is certainly more useful than the current behavior. -- Mark Miesfeld |
|
From: Rick M. <obj...@gm...> - 2008-11-09 21:09:24
|
I think the first would be most useful, and also head off the "I'm
getting error code nnnnn back from an ole operation. Where is this
documented?" questions. How many of the errors are describable?
Rick
On Sun, Nov 9, 2008 at 3:19 PM, Mark Miesfeld <mie...@gm...> wrote:
> Date: Sun, Nov 9, 2008 at 10:15 AM
> Subject: [Oorexx-bugs] [ oorexx-Bugs-2248663 ] Error reading Excel
> sheet with #! type error
>
> There is the above bug which was recently opened. It has to do with
> OLEObject raising an exception in VariantToRexx() for a VT_ERROR
> variant.
>
> The exception looks like:
>
> 23 *-* Say '('iCol','iRow'):' myWorkSheet~Cells(iRow,iCol)~Value
> Error 92 running
> E:\work.ooRexx\other\bugs.new\Ole.VT_ERROR.2248663\bug-lct.rex line
> 23: OLE er
> ror
> Error 92.902: Cannot convert OLE VARIANT to REXX object: The
> conversion of the VARIANT type VT_ERROR into a REXX object failed.
>
> Now, VT_ERROR is simply a HRESULT, which in turn is just a long. So
> there is no reason why it can not be converted.
>
> The exception is raised because because the original orexxole.c code
> lumped VT_ERROR in with a number of types that actually can not be
> converted. Like:
>
> case VT_STORAGE:
> case VT_STREAMED_OBJECT:
>
> I think this should be fixed to return a value, not raise an
> exception. But the question becomes what value to convert it to.
> (Maybe this is the question the original developers had and they
> decided to just punt.)
>
> My preference is to converted to a string describing it, but it could
> just be converted to its numerical value.
>
> These are the possibilities that I see, with the ordering as I would
> prefer. What do others think?
>
> VT_ERROR (0x80010126) <Unable to obtain user info from an access token>
> VT_ERROR (0x8001012a) <The system function, AccessCheck, returned false>
> VT_ERROR (0x8001011f) <This operation returned because the timeout
> period expired.>
> VT_ERROR (0x800a07d0) <no description>
>
> VT_ERROR (0x80010126)
> VT_ERROR (0x8001012a)
> VT_ERROR (0x8001011f)
> VT_ERROR (0x800a07d0)
>
> 0x80010126
> 0x8001012a
> 0x8001011f
> 0x800a07d0
>
> -2147417814
> -2147417818
> -2147417825
> -2146826288
>
> --
> Mark Miesfeld
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Oorexx-devel mailing list
> Oor...@li...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
|
|
From: Mark M. <mie...@gm...> - 2008-11-09 20:19:09
|
Date: Sun, Nov 9, 2008 at 10:15 AM
Subject: [Oorexx-bugs] [ oorexx-Bugs-2248663 ] Error reading Excel
sheet with #! type error
There is the above bug which was recently opened. It has to do with
OLEObject raising an exception in VariantToRexx() for a VT_ERROR
variant.
The exception looks like:
23 *-* Say '('iCol','iRow'):' myWorkSheet~Cells(iRow,iCol)~Value
Error 92 running
E:\work.ooRexx\other\bugs.new\Ole.VT_ERROR.2248663\bug-lct.rex line
23: OLE er
ror
Error 92.902: Cannot convert OLE VARIANT to REXX object: The
conversion of the VARIANT type VT_ERROR into a REXX object failed.
Now, VT_ERROR is simply a HRESULT, which in turn is just a long. So
there is no reason why it can not be converted.
The exception is raised because because the original orexxole.c code
lumped VT_ERROR in with a number of types that actually can not be
converted. Like:
case VT_STORAGE:
case VT_STREAMED_OBJECT:
I think this should be fixed to return a value, not raise an
exception. But the question becomes what value to convert it to.
(Maybe this is the question the original developers had and they
decided to just punt.)
My preference is to converted to a string describing it, but it could
just be converted to its numerical value.
These are the possibilities that I see, with the ordering as I would
prefer. What do others think?
VT_ERROR (0x80010126) <Unable to obtain user info from an access token>
VT_ERROR (0x8001012a) <The system function, AccessCheck, returned false>
VT_ERROR (0x8001011f) <This operation returned because the timeout
period expired.>
VT_ERROR (0x800a07d0) <no description>
VT_ERROR (0x80010126)
VT_ERROR (0x8001012a)
VT_ERROR (0x8001011f)
VT_ERROR (0x800a07d0)
0x80010126
0x8001012a
0x8001011f
0x800a07d0
-2147417814
-2147417818
-2147417825
-2146826288
--
Mark Miesfeld
|
|
From: Rick M. <obj...@gm...> - 2008-11-09 16:54:29
|
I'm still not seeing the problem. If you's doing that, then you'd just separate the target entry point by name and be explicit about what you're mapping to. You're going to have to give me a real example, I think. Rick On Sun, Nov 9, 2008 at 11:49 AM, David Ashley <dav...@gm...> wrote: > Rick McGuire wrote: > > There's no name collision problem that I'm aware of. The names > involved here are the internal names defined in the package table. If > two classes use the same libraries and reuse the same backing native > methods, that will work just fine. Perhaps I'm missing something in > your point. Can you give a concrete example? > > Rick > > On Sun, Nov 9, 2008 at 11:38 AM, David Ashley > <dav...@gm...> wrote: > > > Mark Miesfeld wrote: > > On Sun, Nov 9, 2008 at 7:33 AM, Rick McGuire <obj...@gm...> wrote: > > > > I think there's one other change I need to consider. This is likely > to lead so some interesting problems with > case. For example, > > ::attribute foo EXTERNAL 'LIBRARY yada" > > will require "GETFOO" and "SETFOO", but this version > > ::attribute "Foo" EXTERNAL 'LIBRARY yada' > > will require "GETFoo" and "SetFoo". I think I'd like to make the > resolution rules for resolving the procedures > case insensitive. Since this resolution step is performed using a > generated table, there are no platform implications > to doing this, and I seriously double many people will want to define > different methods using case to distinguish them. > > > Good point. For this form, I think I would have expected the > resolution to be case insensitive and would have only learned it > wasn't through trial and error. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > I can see one potential problem with the this method definition. If two > classes use the same external library then you will have a name collision > using the this method for methods of the same name. This probably ok in 90% > of the cases but there will always be that instance where one method needs > to perform something special and then you have a problem. > > I think the potential confusion factor is kind of high for this kind of > definition. I prefer an explicit definition of the external procedure. > > David Ashley > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > The point I was trying to make concernes the "special case" where a method > in one of the classes need to perform special processing that the method of > the same name in the other class neither needs or wants (for instance, > additional argument checking). In that case you have an unresolvable > collision in terms of functionality. > > I just think the potential confusion factor is too high. > > David Ashley > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
|
From: David A. <dav...@gm...> - 2008-11-09 16:50:01
|
Rick McGuire wrote: > There's no name collision problem that I'm aware of. The names > involved here are the internal names defined in the package table. If > two classes use the same libraries and reuse the same backing native > methods, that will work just fine. Perhaps I'm missing something in > your point. Can you give a concrete example? > > Rick > > On Sun, Nov 9, 2008 at 11:38 AM, David Ashley > <dav...@gm...> wrote: > >> Mark Miesfeld wrote: >> >> On Sun, Nov 9, 2008 at 7:33 AM, Rick McGuire <obj...@gm...> wrote: >> >> >> >> I think there's one other change I need to consider. This is likely >> to lead so some interesting problems with >> case. For example, >> >> ::attribute foo EXTERNAL 'LIBRARY yada" >> >> will require "GETFOO" and "SETFOO", but this version >> >> ::attribute "Foo" EXTERNAL 'LIBRARY yada' >> >> will require "GETFoo" and "SetFoo". I think I'd like to make the >> resolution rules for resolving the procedures >> case insensitive. Since this resolution step is performed using a >> generated table, there are no platform implications >> to doing this, and I seriously double many people will want to define >> different methods using case to distinguish them. >> >> >> Good point. For this form, I think I would have expected the >> resolution to be case insensitive and would have only learned it >> wasn't through trial and error. >> >> -- >> Mark Miesfeld >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >> >> I can see one potential problem with the this method definition. If two >> classes use the same external library then you will have a name collision >> using the this method for methods of the same name. This probably ok in 90% >> of the cases but there will always be that instance where one method needs >> to perform something special and then you have a problem. >> >> I think the potential confusion factor is kind of high for this kind of >> definition. I prefer an explicit definition of the external procedure. >> >> David Ashley >> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >> > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > The point I was trying to make concernes the "special case" where a method in one of the classes need to perform special processing that the method of the same name in the other class neither needs or wants (for instance, additional argument checking). In that case you have an unresolvable collision in terms of functionality. I just think the potential confusion factor is too high. David Ashley |
|
From: Rick M. <obj...@gm...> - 2008-11-09 16:42:05
|
There's no name collision problem that I'm aware of. The names involved here are the internal names defined in the package table. If two classes use the same libraries and reuse the same backing native methods, that will work just fine. Perhaps I'm missing something in your point. Can you give a concrete example? Rick On Sun, Nov 9, 2008 at 11:38 AM, David Ashley <dav...@gm...> wrote: > Mark Miesfeld wrote: > > On Sun, Nov 9, 2008 at 7:33 AM, Rick McGuire <obj...@gm...> wrote: > > > > I think there's one other change I need to consider. This is likely > to lead so some interesting problems with > case. For example, > > ::attribute foo EXTERNAL 'LIBRARY yada" > > will require "GETFOO" and "SETFOO", but this version > > ::attribute "Foo" EXTERNAL 'LIBRARY yada' > > will require "GETFoo" and "SetFoo". I think I'd like to make the > resolution rules for resolving the procedures > case insensitive. Since this resolution step is performed using a > generated table, there are no platform implications > to doing this, and I seriously double many people will want to define > different methods using case to distinguish them. > > > Good point. For this form, I think I would have expected the > resolution to be case insensitive and would have only learned it > wasn't through trial and error. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > I can see one potential problem with the this method definition. If two > classes use the same external library then you will have a name collision > using the this method for methods of the same name. This probably ok in 90% > of the cases but there will always be that instance where one method needs > to perform something special and then you have a problem. > > I think the potential confusion factor is kind of high for this kind of > definition. I prefer an explicit definition of the external procedure. > > David Ashley > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
|
From: David A. <dav...@gm...> - 2008-11-09 16:38:33
|
Mark Miesfeld wrote: > On Sun, Nov 9, 2008 at 7:33 AM, Rick McGuire <obj...@gm...> wrote: > > >> I think there's one other change I need to consider. This is likely >> to lead so some interesting problems with >> case. For example, >> >> ::attribute foo EXTERNAL 'LIBRARY yada" >> >> will require "GETFOO" and "SETFOO", but this version >> >> ::attribute "Foo" EXTERNAL 'LIBRARY yada' >> >> will require "GETFoo" and "SetFoo". I think I'd like to make the >> resolution rules for resolving the procedures >> case insensitive. Since this resolution step is performed using a >> generated table, there are no platform implications >> to doing this, and I seriously double many people will want to define >> different methods using case to distinguish them. >> > > Good point. For this form, I think I would have expected the > resolution to be case insensitive and would have only learned it > wasn't through trial and error. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > I can see one potential problem with the this method definition. If two classes use the same external library then you will have a name collision using the this method for methods of the same name. This probably ok in 90% of the cases but there will always be that instance where one method needs to perform something special and then you have a problem. I think the potential confusion factor is kind of high for this kind of definition. I prefer an explicit definition of the external procedure. David Ashley |
|
From: Mark M. <mie...@gm...> - 2008-11-09 15:45:40
|
On Sun, Nov 9, 2008 at 7:33 AM, Rick McGuire <obj...@gm...> wrote: > I think there's one other change I need to consider. This is likely > to lead so some interesting problems with > case. For example, > > ::attribute foo EXTERNAL 'LIBRARY yada" > > will require "GETFOO" and "SETFOO", but this version > > ::attribute "Foo" EXTERNAL 'LIBRARY yada' > > will require "GETFoo" and "SetFoo". I think I'd like to make the > resolution rules for resolving the procedures > case insensitive. Since this resolution step is performed using a > generated table, there are no platform implications > to doing this, and I seriously double many people will want to define > different methods using case to distinguish them. Good point. For this form, I think I would have expected the resolution to be case insensitive and would have only learned it wasn't through trial and error. -- Mark Miesfeld |
263 messages has been excluded from this view by a project administrator.