Branko Äibej wrote:
Cool, well if someone who has commit access could do that, I'd
appreciate it.
/me picks up his magic wand... and finds there's also a
threadproc/beos/threadcancel.c, whereupon he decides to wait for further
responses before removing both.
Neither seems to be mentioned in an
Garrett Rooney wrote:
Branko Äibej wrote:
I'd say yes. We can always ressurect it if it becomes interesting.
Cool, well if someone who has commit access could do that, I'd
appreciate it.
/me picks up his magic wand... and finds there's also a
threadproc/beos/threadcancel.c, whereupon he decides t
Branko Äibej wrote:
Garrett Rooney wrote:
I'm playing around with autogenerating dsp files again, and ran into a
few weird things I wanted to ask about...
First of all, threadproc/win32/threadcancel.c doesn't seem to be
built. Or to be finished for that matter, the only function in there
that
Garrett Rooney wrote:
I'm playing around with autogenerating dsp files again, and ran into a
few weird things I wanted to ask about...
First of all, threadproc/win32/threadcancel.c doesn't seem to be
built. Or to be finished for that matter, the only function in there
that isn't commented out
I'm playing around with autogenerating dsp files again, and ran into a
few weird things I wanted to ask about...
First of all, threadproc/win32/threadcancel.c doesn't seem to be built.
Or to be finished for that matter, the only function in there that
isn't commented out is ap_cancel_thread, w
