Re: [Oorexx-devel] rxsocket example

[tango foxtrot]

I'll buy that, thanks Rick

On 2021-07-13 14:55, Rick McGuire wrote:



On Tue, Jul 13, 2021 at 5:37 PM Terry Fuller > wrote:


Hi René & all,

To be clear, I am instantiating an object but I haven't gotten an
error doing so... I was just reading the doc to understand how to
do this and I found the sample case to be odd.

For example if I were to write a line like:

-1~errno

I would expect something like -1 does not understand the message
errno.  The if statement in the doc seemed to be identical to that
case (if s=-1 then ... s~errno...).

So, the socket is instantiated even if it's value is set to -1?


On 2021-07-12 12:45, René Jansen wrote:

Hi Terry,

just for my understanding of what you mean: you instantiated an
object, which’ particular purpose was to open a tcp socket. The
fact that this did go wrong, does not mean you cannot send the
object a message of ‘let me know the error code of what happened
when you tried to open the socket’. You are not sending anything
over the socket (it is most prpbably not there) - you are
communicating with your object.

Or seems something else wrong?

best regards,

René.


On 12 Jul 2021, at 21:34, Terry Fuller mailto:t...@pgmguild.com>> wrote:

Hello all,

I'm working my way thru a project that makes use of rxsockets.   in

*ooRexx Documentation 5.0.0 **
**Open Object Rexx RxSock TCP/IP Socket Functions
Reference**
**Edition 1 *

i found:

-- get a new socket s = .socket~new() if s = -1 then do say
'Error' s~errno() 'creating server socket' return end

but... if s is -1, sending a message to it to extract an error
message number seems wrong; at least to me.  Am I missing something?

I suspect this was a bad conversion of the docs from the OS/2 function 
based version into the object based version. This probably should be 
"if s~error = -1 then do"


Rick

-- 
taf

___
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  



-- 
taf


___
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
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] rxsocket example

[Rick McGuire]

On Tue, Jul 13, 2021 at 5:37 PM Terry Fuller  wrote:

> Hi René & all,
>
> To be clear, I am instantiating an object but I haven't gotten an error
> doing so... I was just reading the doc to understand how to do this and I
> found the sample case to be odd.
>
> For example if I were to write a line like:
>
> -1~errno
>
> I would expect something like -1 does not understand the message errno.
> The if statement in the doc seemed to be identical to that case (if s=-1
> then ... s~errno...).
>
> So, the socket is instantiated even if it's value is set to -1?
>
>
> On 2021-07-12 12:45, René Jansen wrote:
>
> Hi Terry,
>
> just for my understanding of what you mean: you instantiated an object,
> which’ particular purpose was to open a tcp socket. The fact that this did
> go wrong, does not mean you cannot send the object a message of ‘let me
> know the error code of what happened when you tried to open the socket’.
> You are not sending anything over the socket (it is most prpbably not
> there) - you are communicating with your object.
>
> Or seems something else wrong?
>
> best regards,
>
> René.
>
> On 12 Jul 2021, at 21:34, Terry Fuller  wrote:
>
> Hello all,
>
> I'm working my way thru a project that makes use of rxsockets.   in
>
> *ooRexx Documentation 5.0.0 *
> *Open Object Rexx RxSock TCP/IP Socket Functions Reference*
> * Edition 1 *
>
> i found:
>
>  -- get a new socket
>  s = .socket~new()
>  if s = -1 then do
>  say 'Error' s~errno() 'creating server socket'
>  return
>  end
>
>
> but... if s is -1, sending a message to it to extract an error message
> number seems wrong; at least to me.  Am I missing something?
>
> I suspect this was a bad conversion of the docs from the OS/2 function
based version into the object based version. This probably should be "if
s~error = -1 then do"

Rick


> --
> taf
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
>
>
> ___
> Oorexx-devel mailing 
> listOorexx-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
> --
> taf
>
> ___
> 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] rxsocket example

[Terry Fuller]

Hi René & all,

To be clear, I am instantiating an object but I haven't gotten an error 
doing so... I was just reading the doc to understand how to do this and 
I found the sample case to be odd.


For example if I were to write a line like:

-1~errno

I would expect something like -1 does not understand the message errno.  
The if statement in the doc seemed to be identical to that case (if s=-1 
then ... s~errno...).


So, the socket is instantiated even if it's value is set to -1?


On 2021-07-12 12:45, René Jansen wrote:

Hi Terry,

just for my understanding of what you mean: you instantiated an 
object, which’ particular purpose was to open a tcp socket. The fact 
that this did go wrong, does not mean you cannot send the object a 
message of ‘let me know the error code of what happened when you tried 
to open the socket’. You are not sending anything over the socket (it 
is most prpbably not there) - you are communicating with your object.


Or seems something else wrong?

best regards,

René.

On 12 Jul 2021, at 21:34, Terry Fuller > wrote:


Hello all,

I'm working my way thru a project that makes use of rxsockets.   in

*ooRexx Documentation 5.0.0 **
**Open Object Rexx RxSock TCP/IP Socket Functions Reference**
**Edition 1 *

i found:

-- get a new socket s = .socket~new() if s = -1 then do say 'Error' 
s~errno() 'creating server socket' return end


but... if s is -1, sending a message to it to extract an error 
message number seems wrong; at least to me.  Am I missing something?


--
taf
___
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


--
taf

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx on Windows 8

[P.O. Jonsson]

Hi Jeremy,

It is 8.1. Professional, and I do not think anyone in his right mind is 
actually using Windows 8 or 8.1 for that matter ;-) It is almost as extinct as 
Microsoft BOB 

The whole point in installing Windows 7 and Windows 8 is to see if they behave 
differently in the build and test of ooRexx.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 13.07.2021 um 22:39 schrieb Jeremy Nicoll :
> 
> On Tue, 13 Jul 2021, at 09:17, P.O. Jonsson wrote:
>> I have successfully added 64 bit Windows 8 to the Jenkins Zoo...
> 
> Do you really mean the base Windows 8, or 8.1 ?  
> 
> I would have thought that nearly everyone running Win 8 or 8.1
> would be using the latter. 
> 
> -- 
> Jeremy Nicoll - my opinions are my own.
> 
> 
> ___
> 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] ooRexx on Windows 8

[Jeremy Nicoll]

On Tue, 13 Jul 2021, at 09:17, P.O. Jonsson wrote:
> I have successfully added 64 bit Windows 8 to the Jenkins Zoo...

Do you really mean the base Windows 8, or 8.1 ?  

I would have thought that nearly everyone running Win 8 or 8.1
would be using the latter. 

-- 
Jeremy Nicoll - my opinions are my own.


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] ooRexx on Windows 8

[P.O. Jonsson]

I am moving this to the bug section, there is more to it.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 13.07.2021 um 10:17 schrieb P.O. Jonsson :
> 
> I have successfully added 64 bit Windows 8 to the Jenkins Zoo and can build 
> 64 bit ooRexx with „success“.
> 
> However, in the testing I get stuck early, on "Executing 
> ...\ooRexx\API\oo\FUNCTION.testGroup“, the 3rd testgroup to run.
> 
> I have copied the Windows 10 build steps and running the same on Windows 10 
> quickly passes this testGroup. Any ideas what can be wrong here? Please look 
> at the running job in Jenkins for details.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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

[Oorexx-devel] ooRexx on Windows 8

[P.O. Jonsson]

I have successfully added 64 bit Windows 8 to the Jenkins Zoo and can build 64 
bit ooRexx with „success“.

However, in the testing I get stuck early, on "Executing 
...\ooRexx\API\oo\FUNCTION.testGroup“, the 3rd testgroup to run.

I have copied the Windows 10 build steps and running the same on Windows 10 
quickly passes this testGroup. Any ideas what can be wrong here? Please look at 
the running job in Jenkins for details.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel