Permalink
Browse files

add ReadLine wheel

  • Loading branch information...
1 parent 6da529d commit 67477850daef24c43c12c0852b3896f5b3e217b6 @rcaputo committed Feb 22, 2001
Showing with 1,277 additions and 8 deletions.
  1. +6 −3 Changes
  2. +2 −0 MANIFEST
  3. +5 −5 README
  4. +7 −0 lib/POE.pm
  5. +1,186 −0 lib/POE/Wheel/ReadLine.pm
  6. +71 −0 samples/readline.perl
View
@@ -86,9 +86,6 @@ Karsten Sperling found that POSIX::uname wasn't supported back on
use Sys::Hostname, which uses POSIX::uname internally wherever
possible, instead.
-Removed the object layer; files are being restructured as a separate
-component. This is ahead of schedule.
-
Replaced many enum/const statements with constant subs. Fewer of
these mean less regexps to run against the source code, so startup
should be a little peppier.
@@ -101,6 +98,12 @@ like Carp already use it, so it gets loaded no matter what. I'm about
tapped for startup-optimizing ideas that don't involve rewriting
POE::Preprocessor.
+Removed the object layer; files are being restructured as a separate
+component. This is ahead of schedule.
+
+Added POE::Wheel::ReadLine. This is a Term::ReadLine subset that
+cooperates with POE. Now how do I test it non-interactively?
+
0.1205 2001.02.12
-----------------
View
@@ -27,6 +27,7 @@ POE/Session.pm
POE/Wheel.pm
POE/Wheel/FollowTail.pm
POE/Wheel/ListenAccept.pm
+POE/Wheel/ReadLine.pm
POE/Wheel/ReadWrite.pm
POE/Wheel/Run.pm
POE/Wheel/SocketFactory.pm
@@ -51,6 +52,7 @@ samples/packagesessions.perl
samples/preforkedserver.perl
samples/proxy.perl
samples/queue.perl
+samples/readline.perl
samples/ref-type.perl
samples/refsender.perl
samples/refserver.perl
View
10 README
@@ -129,7 +129,7 @@ Test Results
All the tests have been made to run unattended, and testing has been
automated across the systems.
-** POE 0.1205 on OS/2 (home-os2)
+** POE 0.1206 on OS/2 (home-os2)
OS/2 doesn't grok system vs. user time, so the numbers are 0.
@@ -144,7 +144,7 @@ IO::Pty : 0.01
All tests successful, 4 tests and 5 subtests skipped.
Files=24, Tests=429, 159 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00 CPU)
-** POE 0.1205 on FreeBSD (home-bsd)
+** POE 0.1206 on FreeBSD (home-bsd)
Hardware: AMD 486-40; 16MB RAM
System : FreeBSD 4.0-STABLE
@@ -155,9 +155,9 @@ Event : 0.79
IO::Pty : 0.01
All tests successful.
-Files=24, Tests=455, 684 wallclock secs (425.65 cusr + 36.95 csys = 462.60 CPU)
+Files=24, Tests=455, 523 wallclock secs (317.21 cusr + 32.81 csys = 350.02 CPU)
-** POE 0.1205 on Linux (titanic)
+** POE 0.1206 on Linux (titanic)
Hardware: dual Celeron 500; 265MB RAM
System : Linux 2.2.15 SMP
@@ -168,7 +168,7 @@ Event : 0.79
IO::Pty : 0.01
All tests successful, 2 tests skipped.
-Files=24, Tests=438, 106 wallclock secs (22.53 cusr + 0.84 csys = 23.37 CPU)
+Files=24, Tests=438, 99 wallclock secs (16.34 cusr + 0.77 csys = 17.11 CPU)
** POE 0.1205 on Solaris/SunOS 5.7 (hfb)
View
@@ -256,6 +256,13 @@ ListenAccept performs ye olde non-blocking socket listen and accept.
It's great for programs that can't use SocketFactory and instead must
listen and accept connections from sockets created elsewhere.
+=item POE::Wheel::ReadLine
+
+The ReadLine wheel accepts console input as lines only. It handles
+many of the common shell command editing keystrokes, making it pretty
+easy to input things. It's event driven, unlike Term::ReadLine, and
+it cooperates nicely with the rest of POE.
+
=item POE::Wheel::ReadWrite
ReadWrite is the star of POE's default I/O layer. It performs
Oops, something went wrong.

0 comments on commit 6747785

Please sign in to comment.