• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: mulithreading, dual-core
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mulithreading, dual-core


  • Subject: Re: mulithreading, dual-core
  • From: Christopher Hunt <email@hidden>
  • Date: Tue, 27 Feb 2007 07:55:42 +1100

On 27/02/2007, at 2:12 AM, Thomas Engelmeier wrote:

Am 25.02.2007 um 23:47 schrieb Christopher Hunt:

For a command line C++ tool, you'll want to use pthreads, as someone
else explained. The basic operation of pthreads is pretty simple and
like most other similar implementations. There are a few very
important points to know:
You may also want to check out the boost library. It offers a cross platform set thread classes that I think are modeled around pthreads. It is also free. :-)

While I'm definitey a fan of boost, adding the threads abstraction over an straightforward (pthreads) API comes with quite some footprint if there's just multiple instances of one routine running multithreaded (Read: just the requirement of a single lock for one object).
That might be the requirement now... :-)

Also I don't really believe that the footprint is that large. You could indeed take this same view with using STL... but I don't think we should go there.

- In shared development, colleagues already used to pthreads (low level) have to read up the (high level) boost::threads documentation
Sure, as with any new library. I was merely suggesting that they'd be some familiarity.

- boost itself has quite some footprint to put into that projects SCM.
Why? It isn't something you have to SCM... you don't SCM other libraries do you?

Striping boost into only the project relevant pieces is usually not simply "OK, I just need boost::threads and boost::shared_ptr, so I can get rid of all other directories"
Why get rid of the other directories? Just do the simple install and leave it. Use what you want to use. I did indeed use boost given its shared_ptr classes (which are excellent) and then started using the other bits.

YMMV, but it's a decision that should be carefully evaluated.
With respect I disagree. boost is mature, established and highly respected. A great deal of ratification occurs prior to boost modules becoming accepted.

Cheers,
-C
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: mulithreading, dual-core
      • From: Thomas Engelmeier <email@hidden>
References: 
 >Re: mulithreading, dual-core (From: Christopher Hunt <email@hidden>)
 >Re: mulithreading, dual-core (From: Thomas Engelmeier <email@hidden>)

  • Prev by Date: Re: staticly linked libc ?
  • Next by Date: Re: Libstdc++ problems
  • Previous by thread: Re: mulithreading, dual-core
  • Next by thread: Re: mulithreading, dual-core
  • Index(es):
    • Date
    • Thread