Re: [TCLCORE] Porting 8-3-1-branch IO changes to 8-4

[Andreas K. <a.k...@we...>]

> OK, so the major IO rewrite for 8.3.2 is mostly finished (the new
> interfaces need to be doc'ed).  Now we have to deal with moving
> those code changes up into the mainline (8.4).
 
> One of the conflicts is that generic declarations were added to both
> 8.3 (Tcl_Channel* funcs) and 8.4 (funcs for sharing channels among
> threads, some UniChar and HashTable funcs).  Since the 8.4 only saw
> one alpha, the 8.3 entries will have precedence and keep their
> numbers.  I'll renumber the 8.4 entries.  This means that extensions
> compiled against 8.4a1 stubs may have incompatabilities and should
> be recompiled with 8.4a2 if they use the new stub calls.

The only extension I currently know of using the new calls is
'Thread'.


> Of course, we managed to focus new development in both branches on
> the IO layer (8.4 getting work in the sharing of channels between
> threads).  Since 8.3 is by far the larger of the rewrites, I'd like
> to basically move the IO changes complete up from 8.3 and then
> regraft the 8.4 changes onto the new system.
 
> Anyone forsee further complications with this, or has comments, or
> would like to help?

I see no big complications with that. ... Ok, the changes I did are in

	2000-05-03-20-24.diff.gz 

of my cvs snapshots. There are some other changes in as well (joinable
threads), but it should be possible to trim it down to contain just
the changes to the IO-system. We'll have to see how many chunks are
still applicable. File attached.

~~~~~~~~~~~~~~~

Excerpt of ChangeLog of the lastest 8.3.2-io-rewrite.

* tests/all.tcl: corrected additional sets by Kupries for testing.

I'm chagrined. My apologies for that oversight.

I truly wish there was some way to set such things separately during
development without having to modify the distributed files
themselves. => Some idea for Jennifer Hom and her planned changes to
tcltest.


-- 
So long,
	Andreas Kupries <a.k...@we...>
			<http://www.purl.org/NET/akupries/>
-------------------------------------------------------------------------------