The compiler in use reports a thread model other than 'single'. This can be tested via output from gcc -v. Multi-thread capable versions of gcc output something like this: %gcc -v Using built-in specs. ... Thread model: posix gcc version 4.1.2 20070925 (Red Hat 4.1.2-33) Requisite command-line flags are used for atomic operations and threading. Examples of this include -pthread and -march=native, although specifics vary depending on the host environment. See Machine Dependent Options.

The GNU Standard C++ Library v3 is an ongoing project to implement the ISO 14882 Standard C++ library as described in chapters 17 through 27 and annex D. For those who want to see exactly how far the project has come, or just want the latest bleeding-edge code, the up-to-date source is available over anonymous SVN, and can even be browsed over the web.

Hopefully, not much. The goal of libstdc++ is to produce a fully-compliant, fully-portable Standard Library. After that, we're mostly done: there won't be any more compliance work to do. However: The ISO Committee will meet periodically to review Defect Reports in the C++ Standard. Undoubtedly some of these will result in changes to the Standard, which will be reflected in patches to libstdc++. Some of that is already happening, see 4.3.

Generally, no (but see the next question). Many components of MapServer use static or global data that could potentially be modified by another thread. Under heavy load these unlikely events become inevitable, and could result in sporadic errors.

Complete instructions are not given here (this is a FAQ, not an installation document), but the tools required are few: A 3.x or later release of GCC. Either install a suitable package for your system, or compile GCC from the sources. Note that building GCC is much easier and more automated than building the GCC 2.[78] series was. If you are using GCC 2.

Yes. However, you should be aware that not everyone uses the phrase "thread safe" the same way. See our discussion of thread safety for our design goals.

The init() method is guaranteed to be called once per servlet instance, when the servlet is loaded. You don't have to worry about thread safety inside this method, since it is only called by a single thread, and the web server will wait until that thread exits before sending any more threads into your service() method. Every new client request generates (or allocates) a new thread; that thread calls the service() method of your servlet (which may in turn call doPost(), doGet() and so forth).

Nathan Myers gave the best of all possible answers, responding to a Usenet article asking this question: Sooner, if you help.

VR-Link is not thread-safe. However, it is possible to use VR-Link in multithreaded applications. You simply need to make sure that your VR-Link stuff is all in the same thread. So long as this is the case, VR-Link should work fine. The one case where the current version of VR-Link has problems is in applications where two completely independent threads both want to use VR-Link classes.

OEChem is designed to be thread safe, i.e., re-entrant, but as of v1.4.0 there are known areas where OEChem is not re-entrant, namely, OEThrow, and generic data (e.g. SetData/GetData). In addition, C++ STL streams are normally not thread safe, so OEChem streams are also not thread safe. Multithreaded code can be written by selective use of OEChem, but the forbidden zones are not yet well established. At the very least, separate threads should not operate on the same molecules.

Toolkit fully supports the POSIX Threads API, and the run time libraries are thread safe. Toolkit also provides emulation layers for Solaris and DCE threads. Refer to the Porting Threaded Applications chapter of the Cross-Platform Developer's Guide for more details. Yes, Toolkit provides a mechanism to change thread priorities. The APIs pthread_setschedparam(), getpriority(), setpriority(), and nice() are available.

Home| |News| |Products| | uCalc FMP| | uCalc Language Builder| | Windows Calculator| | DOS Calculator| |Downloads| |Message Forums| |Satisfaction Survey| |FAQ| |Contact| |Privacy Statement| |Purchase|

We've made some preliminary efforts at making the BeBOP Utility Library thread-safe, using Pthreads constructions. This code is disabled by default; you can enable it by setting use-pthreads=1 at the top of both Makefiles. In particular, logging (bebop_util/log.h) and random number generation (bebop_util/random_number.h) are protected. We also made efforts to remove calls to non-thread-safe functions such as strtok().

Threads provide a means of running code routines simultaneously. Local variables are separately maintained in threads so those are not a problem. Any global variables are a problem. Cogencee generates global variables so this means that Cogencee is not thread safe.

Yes, the SigLib library has been written to be completely multi-thread safe. All variables are either local to each function call or are maintained but the calling thread.

Usually, the state pattern describes the state of the context object at any point of time, all we need to do is to protect the state handler object from accepting more than one message at a time. So if more than one thread is sending messages to the same state handler object, The object needs to be protected. So the generated code is not thread safe as such. Put sending of messages in a critical section so that multiple threads wont send messages at a time and it will become thread safe.

No, this would incur a significant performance penalty for users that do not require a thread safe library. Instead, synchronize your own code to ensure multiple threads do not access the same FTPClient object. I want to get access to the InputStream of the incoming data, but I can only find a get() method that takes an OutputStream. The underlying InputStream for data is deliberately not made available. Failure to close this stream at the appropriate point will cause FTP operations to hang.

This is not a question that has a simple yes/no answer. Here are the rules for using XML4C in a multi-threaded environment: Within an address space, an instance of the parser may be used without restriction from a single thread, or an instance of the parser can be accessed from multiple threads, provided the application guarantees that only one thread has entered a method of the parser at any one time.

LAM is "thread safe" in that MPI programs may use multiple threads. It is not safe, however, to have multiple threads simultaneously executing in the MPI library. If user programs utilized multiple threads, they must ensure that only one thread uses LAM at a time. Unpredictable results (read: crash and burn) will occur if multiple threads access LAM simultaneously. There are plans to make LAM have the ability to allow multiple threads simultaneously executing within the MPI library.

I have written plenty of non-thread-safe Singletons but it wasn't until recently when I tracked it down that I realized that thread-safety could be a big problem. The problem is that in the typical Singleton implementation (at least the ones I've seen) there is the ability to create multiple versions of the single instance...I know, "But How?". Well, in the getInstance() call the instance is checked for null, and then immediately constructed if it is null, and then the instance is returned.

Yes, log4j is thread-safe. Log4j components are designed to be used in heavily multithreaded systems.

This is not a question that has a simple yes/no answer. Here are the rules for using Xerces-C++ in a multi-threaded environment: Within an address space, an instance of the parser may be used without restriction from a single thread, or an instance of the parser can be accessed from multiple threads, provided the application guarantees that only one thread has entered a method of the parser at any one time.

i want to add different resource bundle for different module in struts I'm doing validation using validation.XML,and not using bean:message how to implement different resource bundle and internationalization

Because GCC advances so rapidly, development and testing of libstdc++ is being done almost entirely under that compiler. If you are curious about whether other, lesser compilers (*grin*) support libstdc++, you are more than welcome to try. Configuring and building the library (see above) will still require certain tools, however. Also keep in mind that building libstdc++ does not imply that your compiler will be able to use all of the features found in the C++ Standard Library.