Re: [boost] Re: Re: Re: Re: Re: Re: the boost::signal sample crashes

[E. Gladyshev]

--- Bohdan <[EMAIL PROTECTED]> wrote:
> Not really. Example:
> Link to static or dynamic (i mean import lib)
> thread library problem. This decision can be made
> only by linker option or by #pragma comment.
> IMHO, traits can't help here.

Traits have nothing to do with the lib-link problem it
in my sample.

> This means that they are
> not portable to other OSes and boost::thread
> has nothing to do with them. If i don't mind boost
> main objective is portability.

You just are not getting it :).  My suggestion won't
make boost unportable.  It'll simply let the user to
customize the class in a generic way. Do you see the
difference? Generic customization is one of the main
objectives of generic and template programming in
modern C++. IMHO when a modern C++ library doesn't
allow it (for no reasons practically), it looks
crippled.

> Anyway, if your implementation can't fix
> link-to-correct-library
> problems ... than what we are discussing ? :)
> I was thinking that THIS was discussion subject.
> Am i wrong ?

Sorry, you are wrong.  This discussion subjects were
the link problem and be able to to use boost::thread
with my toy OS and/or with different threading models
without mocking with boost sources.

Eugene



__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

[boost] Re: Re: Re: Re: Re: Re: the boost::signal sample crashes

[Bohdan]

"E. Gladyshev" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> --- Bohdan <[EMAIL PROTECTED]> wrote:
>
> > If you mean your threads snipped: Yes i've seen it.
> > IMO it is more complicated and YES it has compile
> > time problems, unless you put traits implementation
> > in cpp files and move #include   to
> > cpp files, but in this case you have
>
> Yes, it was my suggestion. I have put traits
> implemenations in cpp file in my proposal.  #include
>  are in cpp files as well.  Sorry if my
> description was not clear.  I hope you agree that in
> this case, there are not any performance issues?
>
> > link-to-correct-library problems again.
>
> We have it anyway. My solution didn't claim to resolve
> it completely, did it?  However if I use thread_core.h
> directly and provide my own trait (my toy OS), it
> resolves the link-to-correct-library problems
> automatically, does it?

Not really. Example:
Link to static or dynamic (i mean import lib)
thread library problem. This decision can be made
only by linker option or by #pragma comment.
IMHO, traits can't help here.


> Win32 has really different thread models. I have
> mentioned it several times in my posts. They have
> normal threads and fibers, do they?
>

Ah ... sorry i've missed this point.
AFAIK fibers are present only on particular OSes.
If i don't mind they are supported for all windows
starting from win2k.  This means that they are
not portable to other OSes and boost::thread
has nothing to do with them. If i don't mind boost
main objective is portability.
Anyway, if your implementation can't fix link-to-correct-library
problems ... than what we are discussing ? :)
I was thinking that THIS was discussion subject.
Am i wrong ?

regards,
bohdan





___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost