#26: Multi-thread safety -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | -------------------------+-------------------------------------------------- Alex Mizhari writes:
multithread safety -- while perhaps not thoroughly checked, most stuff behaves fine with multiple threads, at least i don't remember having problems with it.
#26: Multi-thread safety --------------------------+------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: too-vague Component: other | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Changes (by ehuelsmann):
* milestone: => too-vague
#26: Multi-thread safety --------------------------+------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: closed Priority: major | Milestone: too-vague Component: other | Version: Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by ehuelsmann):
* status: new => closed * resolution: => fixed
Comment:
In the past 12 months, some fixes were committed to protect the compiler from multithreading issues. Considering this otherwise too vague to keep it open.
#26: Multi-thread safety --------------------------+------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: closed Priority: major | Milestone: 0.22 Component: other | Version: Resolution: fixed | Keywords: --------------------------+------------------------------------------------- Changes (by ehuelsmann):
* milestone: too-vague => 0.22
Comment:
Selecting the last closed milestone to assign this ticket to. Taking it out of 'too vague', because it's been addressed. How vague can that be?
armedbear-ticket@common-lisp.net