Skip to content
Browse files

final doc tweaks for 0.1104 release

  • Loading branch information...
1 parent b4d115e commit ed14a9386ae7289956a52f10f5ea2dfff0f35d12 @rcaputo rcaputo committed Aug 13, 2000
Showing with 11 additions and 23 deletions.
  1. +4 −16 Changes
  2. +7 −7 README
View
20 Changes
@@ -26,11 +26,6 @@ Version numbers have four fields: X.YYZZAA
,----- To Do -----
|
-| Filehandles are bad. Check t/04_selects.t and lines in
-| POE::Kernel beginning with /^#-/. Must allow 2+ selects for
-| the same fileno/handle, even if it's meaningless, so that
-| handles can be passed between wheels, etc.
-|
| How about Gtk support?
|
| Better alarms API. Roderick has threatened to do something.
@@ -61,7 +56,7 @@ Version numbers have four fields: X.YYZZAA
`-----------------
-0.1104 2000.??.??
+0.1104 2000.08.12
-----------------
Jaxdahl donated some shell time on his Win32 machine, allowing me to
@@ -80,16 +75,9 @@ delivered when child processes exited by signal.
Added t/20_accept.t to test Wheel::ListenAccept.
-Wrote lib/TestPipe.pm. This file tries to make a two-way pipe at any
-cost. It tries socketpair(2) in the UNIX domain, socketpair(2) in the
-INET domain, a pair of pipe(2)s, and finally a plain INET domain
-socket. This would make a great basis for an open3 thingy.
-
-select(2) bits are keyed on fileno. POE's selects were keyed on file
-handle. Several dup(2)'d handles could have the same fileno. POE
-would manage the select(2) bits based on reference counts for handles.
-This was bad. Changed POE to manage its own selects by fileno
-instead of filehandle. This worked, much to my surprise.
+Wrote lib/TestPipe.pm. This file tries to make a portable two-way
+pipe. It uses a pair of pipe(2)s, or a plain INET socket if that
+fails. This would make a great basis for an open3 thingy.
0.1103 2000.08.06
View
14 README
@@ -68,14 +68,14 @@ Event.
All tests successful, 3 tests skipped.
Files=21, Tests=365, 190 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00 CPU)
-These are the `make test' results for POE 0.1103. Hardware: AMD
+These are the `make test' results for POE 0.1104. Hardware: AMD
486-40 (overclocked to 50); 16MB RAM. Software: FreeBSD 4.0-STABLE;
perl 5.6.0; Perl/Tk 800.021; Event 0.79.
All tests successful.
- Files=20, Tests=377, 551 wallclock secs (267.15 cusr +23.68 csys =290.83 CPU)
+ Files=21, Tests=381, 577 wallclock secs (297.42 cusr + 25.35 csys = 322.77 CPU)
-These coverage results are for POE 0.1103 on the FreeBSD machine.
+These coverage results are for POE 0.1104 on the FreeBSD machine.
This machine more thoroughly tests different POE options, so the
coverage results are more meaningful. Even at their best, however,
the results are highly misleading. They are, in fact, slightly low
@@ -84,21 +84,21 @@ figures with a grain of salt.
Source File = Ran / Total = Covered
POE.pm = 19 / 19 = 100.00%
- POE/Component/Server/TCP.pm = 22 / 23 = 95.65%
+ POE/Component/Server/TCP.pm = 23 / 23 = 100.00%
POE/Driver/SysRW.pm = 42 / 54 = 77.78%
POE/Filter/Block.pm = 37 / 37 = 100.00%
POE/Filter/HTTPD.pm = 11 / 100 = 11.00%
POE/Filter/Line.pm = 83 / 88 = 94.32%
POE/Filter/Reference.pm = 60 / 66 = 90.91%
POE/Filter/Stream.pm = 11 / 11 = 100.00%
- POE/Kernel.pm = 700 / 937 = 74.71%
+ POE/Kernel.pm = 698 / 931 = 74.97%
POE/Preprocessor.pm = 119 / 138 = 86.23%
POE/Session.pm = 85 / 194 = 43.81%
POE/Wheel/FollowTail.pm = 68 / 86 = 79.07%
- POE/Wheel/ListenAccept.pm = 5 / 43 = 11.63%
+ POE/Wheel/ListenAccept.pm = 32 / 45 = 71.11%
POE/Wheel/ReadWrite.pm = 106 / 185 = 57.30%
POE/Wheel/SocketFactory.pm = 195 / 278 = 70.14%
- All Told = 1563 / 2259 = 69.19%
+ All Told = 1589 / 2255 = 70.47%
Good luck, and thank you for reading!

0 comments on commit ed14a93

Please sign in to comment.
Something went wrong with that request. Please try again.