> "Loic Dachary" <[EMAIL PROTECTED]> writes:
>
> It's ok to use the pokersource SVN for "work in progress". Specially
> for something new such as a thread safe C++ wrapper. The worst that can
> happen is that I take a look and make usel{ess,full} comments.
I had a deeper look at poker-eval, and the handeval functions look
threadsafe to me. what isn't threadsafe are all the enumeration functions.
So I'll likely make own implementations of those.
But that's ok, as handval code takes up the biggest chunk(*) of cpu-time,
and the enum-functions are easy to reimplenent. the core (handeval logic
etc, cardsets, etc...) i can just use poker-eval directly.
there will be some overhead regarding thread creation/management, but i
estimate an 80% performance increase on dual-core machines (not to wet
some mouthes here :=))...and in 10 years, on 16 core machines, this will
rock :=)
> It's not tagged ? Bad. It should. That's the latest version anyways.
> The SVN did not change much.
yeah, i was wondering also. got sources from snapshots now (download
directory)
> There is little risk that you face a massive divergence from the
> source.
i won't need to dublicate much code...probably only the enum_
functions/defines, so this looks sweet.
* > 92%, tests done on modified hcmpn sample, on windows xp, vs 2003.
--
gjn
_______________________________________________
Pokersource-users mailing list
[email protected]
https://mail.gna.org/listinfo/pokersource-users
