Re: [Algorithms] General purpose task parallel threading approach

[<asy...@gm...>]

>The problem, Alexander, is that once you address point one, you are
>disposing of the vast majority of the functionality that you're
>library provides
That's not really true, you can still execute other tasks the same way in a
recursive manner (but keep away of dependencies on something up the worker
thread's stack).
Besides, even if it would be fully true, then "the vast majority of the
functionality" is actually a ~2k of code which you never execute, is this a
"generalization" overhead you can't afford?

Alexander.

2009/4/15 Nicholas "Indy" Ray <ar...@gm...>

> On Tue, Apr 14, 2009 at 2:42 PM,  <asy...@gm...> wrote:
> > Now regarding point 1:
>
> The problem, Alexander, is that once you address point one, you are
> disposing of the vast majority of the functionality that you're
> library provides, and at that point, we have a lot of extra runtime
> sitting there being useless. I think this falls in a case of a
> component being too general for the job.
>
> Indy
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> GDAlgorithms-list mailing list
> GDA...@li...
> https://lists.sourceforge.net/lists/listinfo/gdalgorithms-list
> Archives:
> http://sourceforge.net/mailarchive/forum.php?forum_name=gdalgorithms-list
>



-- 
Regards,
Alexander Karnakov