Assimilate zThreads

Registered by Luke-Jr on 2008-11-16

This blueprint has been superseded. See the newer blueprint "Port to boost::threads" for updated plans.

Porting Armagetron to use pthreads instead of zThreads (unmaintained) seems to be just problem after problem (probably because neither epsy nor I really know how pthreads work), and only solves the zThreads dependency on a subset of our supported platforms.

Therefore, suggest assimilating the portion of zThreads that we use to our internal code. zThreads itself is small, but we only use an even smaller subset (maybe 3 or 4 classes?). Maintaining this subset in-tree should be manageable.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Not
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Superseded
Series goal:
None
Implementation:
Unknown
Milestone target:
milestone icon 0.4.0
Completed by
Luke-Jr on 2010-04-18

Related branches

Sprints

Whiteboard

https://launchpad.net/zthread-aa/

Z-Man: is this really essential for 0.2.8? ZThread is an optional library for a (still marked as) experimental component that is disabled by default, and we statically link with it in binary distributions and provide a patch. It seems more sensible to me to move the implementation to something different on the trunk (boost::thread comes to mind).

Luke: Include zThreads or port to boost::thread should happen by 0.4.0 IMO

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.