Menu
▾
▴
Re: [Oorexx-devel] I/O again
|
From: Mark M. <mie...@gm...> - 2009-04-27 14:51:47
|
I'm just about to try that. I was seeing how reliable it was that I saw RXIT. Seems to be ever time when I paste the text into the window. I think another key is that Rony says he sees it when: > immediately issuing a say statement (typing while rexxtry.rex starts up). So here, the keyboard buffer has data in it (probably, depending on fast he is typing) when the interpreter starts. I'll post as soon as I try it with the patched version. -- Mark Miesfeld. On Mon, Apr 27, 2009 at 7:47 AM, Rick McGuire <obj...@gm...> wrote: > Have you tried reproducing using the patched version? I tried this > technique this morning both the unpatched and official beta version > and didn't get any failures. > > Rick > > On Mon, Apr 27, 2009 at 10:42 AM, Mark Miesfeld <mie...@gm...> wrote: >> Well, okay. By pasting lines into a console window, I got RXIT: >> >> D:\Interpreters\Rexx>rexx -v >> Open Object Rexx Version 4.0.0 >> Build date: Apr 20 2009 >> Addressing Mode: 32 >> >> Copyright (c) IBM Corporation 1995, 2004. >> Copyright (c) RexxLA 2005-2009. >> All Rights Reserved. >> This program and the accompanying materials >> are made available under the terms of the Common Public License v1.0 >> which accompanies this distribution. >> http://www.oorexx.org/license.html >> D:\Interpreters\Rexx>rexxtry say hallo >> HALLO >> ........................................... rexxtry.rex on WindowsNT >> >> D:\Interpreters\Rexx>rexxtry >> REXX-ooRexx_4.0.0(MT) 6.03 20 Apr 2009 >> rexxtry.rex lets you interactively try REXX statements. >> Each string is executed when you hit Enter. >> Enter 'call tell' for a description of the features. >> Go on - try a few... Enter 'exit' to end. >> say sa >> SA >> ........................................... rexxtry.rex on WindowsNT >> >> rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. >> exit >> 'RXIT' is not recognized as an internal or external command, >> operable program or batch file. >> rc = 1 .................................... rexxtry.rex on WindowsNT >> >> >> Prior to that I tried typing the lines in the console window and had >> no luck. When I pasted the lines it was the same console window I had >> been using before. >> >> In the pasting case, the keyboard buffer would have data in it when >> the second interpreter started. >> >> -- >> Mark Miesfeld >> >> >> On Mon, Apr 27, 2009 at 6:17 AM, Rony G. Flatscher >> <Ron...@wu...> wrote: >>> Pretty regularly I can get that problem too when opening a command line >>> window, and first thing I would do is using rexxtry and immediately issuing >>> a say statement (typing while rexxtry.rex starts up). Here's an example that >>> works *quite reliably* for me: >>> >>> Microsoft Windows XP [Version 5.1.2600] >>> (C) Copyright 1985-2001 Microsoft Corp. >>> D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo >>> HALLO >>> ........................................... rexxtry.rex on WindowsNT >>> D:\Dokumente und Einstellungen\Administrator>rexxtry >>> REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 >>> rexxtry.rex lets you interactively try REXX statements. >>> Each string is executed when you hit Enter. >>> Enter 'call tell' for a description of the features. >>> Go on - try a few... Enter 'exit' to end. >>> say sa >>> Der Befehl "RAY" ist entweder falsch geschrieben oder >>> konnte nicht gefunden werden. >>> rc = 1 .................................... rexxtry.rex on WindowsNT >>> >>> >>> Here is what maybe work for you: >>> >>> First copy the following lines into the clipboard (note there is a trailing >>> blank line): >>> >>> rexxtry say hallo >>> rexxtry >>> say sa >>> >>> exit >>> >>> Make sure no Rexx program runs, and no command line window is open in which >>> a Rexx program ran (not sure whether that is really necessary, but who >>> knows) >>> Open a new command line window >>> Just paste the above lines into the window; if necessary repeat steps 2 >>> through 4 >>> >>> Eventually (within ten attempts) the error comes up again (although I might >>> have waited in between invocations, after having all command line windows >>> closed). >>> >>> >>> Here is another run, where this error occurs for the "exit" statement! >>> >>> Microsoft Windows XP [Version 5.1.2600] >>> (C) Copyright 1985-2001 Microsoft Corp. >>> D:\Dokumente und Einstellungen\Administrator>rexxtry say hallo >>> HALLO >>> ........................................... rexxtry.rex on WindowsNT >>> D:\Dokumente und Einstellungen\Administrator>rexxtry >>> REXX-ooRexx_4.0.0(MT) 6.03 24 Apr 2009 >>> rexxtry.rex lets you interactively try REXX statements. >>> Each string is executed when you hit Enter. >>> Enter 'call tell' for a description of the features. >>> Go on - try a few... Enter 'exit' to end. >>> say sa >>> SA >>> ........................................... rexxtry.rex on WindowsNT >>> rexxtry.rex: Enter 'exit' to end. Or '?' for online REXX help. >>> exit >>> Der Befehl "RXIT" ist entweder falsch geschrieben oder >>> konnte nicht gefunden werden. >>> rc = 1 .................................... rexxtry.rex on WindowsNT >>> >>> >>> HTH, >>> >>> ---rony >>> >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensign option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oor...@li... >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensign option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |