Christian Kamm schrieb:
> I'm now also subscribed to D.debugger and saw your post there. Let's move
> the discussion.
I appended my answer to the existing thread 'Debugging LDC executables'.
Best regards,
Timo
Robert Fraser escribió:
Ary Borenszweig Wrote:
Ary Borenszweig escribió:
http://www.youtube.com/watch?v=rtYCFVPfx4M
Bah... I just realized debugging that kind of things might be really
hart to do. Imagine this:
---
char[] something() {
return "x *= 3; x += 4;";
}
mixin("int bla(int
Ary Borenszweig Wrote:
> Ary Borenszweig escribió:
> > http://www.youtube.com/watch?v=rtYCFVPfx4M
>
> Bah... I just realized debugging that kind of things might be really
> hart to do. Imagine this:
>
> ---
> char[] something() {
> return "x *= 3; x += 4;";
> }
>
> mixin("int bla(int x)
> Sweet! Does the code want a license?
The thread-pool is just one little part of my plan migrating acl_project written
with C to adl_project written with D. The original acl_project has many server
framework. Anyone can use it under the GPL.
On Sat, 30 May 2009 08:14:08 +0400, zsxxsz wrote:
Hi, I written one thread pool in which each thread is semi-resident. The
thread-pool is different from the Tango's one. Any thread of the
thread-pool
will exit when it is idle for the timeout. That is to say, all threads
for
jobs, and no job
zsxxsz wrote:
Hi, I written one thread pool in which each thread is semi-resident. The
thread-pool is different from the Tango's one. Any thread of the thread-pool
will exit when it is idle for the timeout. That is to say, all threads for
jobs, and no job no thread. The thread-pool was from my C
