Sponsored Content
Full Discussion: C++ application development
Top Forums Programming C++ application development Post 302701357 by Corona688 on Saturday 15th of September 2012 05:21:07 PM
Old 09-15-2012
What about it? I haven't found an IDE which is actually less work than doing the work myself, or one with an editor I can tolerate. And if you've never compiled anything yourself or used a makefile, most of the options in one will never make sense to you.

Using an IDE also means you'll probably be unable to work with anyone's code but your own unless you can convince them to use the same IDE as you.

Using an IDE usually multiplies the work in the long run, when you must keep updating and changing all your already-existing projects to keep up with changing versions of the products you built them with. Commercial products are particularly bad, since you're pretty much demanding that everyone you send your code to buys that commercial product. Sometimes -- often -- IDE's break compatibility with themselves and you must start over from scratch. Eventually, I decided enough was enough, ripped all the IDE junk out of my projects, and spent 5 minutes writing my own simple makefiles. Problem solved.

And the data-dump debugger gives you most of what people really want in an IDE without the baggage.

Last edited by Corona688; 09-15-2012 at 06:33 PM..
 

We Also Found This Discussion For You

1. Shell Programming and Scripting

Difference between development and Production unix servers for a application??

Hi all I am running a major script of my application in development for implementing code changes for process improvement in time. The script runs in production once in a month . It takes 8 hours 30 mins in Production server . what surprice me is , when I run the same script in development server... (9 Replies)
Discussion started by: sakthifire
9 Replies
pthread_exit(3C)														  pthread_exit(3C)

NAME
pthread_exit - terminate calling thread SYNOPSIS
cc -mt [ flag... ] file... -lpthread [ library... ] #include <pthread.h> void pthread_exit(void *value_ptr); The pthread_exit() function terminates the calling thread, in a similar way that exit(3C) terminates the calling process. If the thread is not detached, the exit status specified by value_ptr is made available to any successful join with the terminating thread. See pthread_join(3C). Any cancellation cleanup handlers that have been pushed and not yet popped are popped in the reverse order that they were pushed and then executed. After all cancellation cleanup handlers have been executed, if the thread has any thread-specific data, appropri- ate destructor functions will be called in an unspecified order. Thread termination does not release any application visible process resources, including, but not limited to, mutexes and file descriptors, nor does it perform any process level cleanup actions, including, but not limited to, calling any atexit() routines that might exist. An implicit call to pthread_exit() is made when a thread other than the thread in which main() was first invoked returns from the start routine that was used to create it. The function's return value serves as the thread's exit status. The behavior of pthread_exit() is undefined if called from a cancellation cleanup handler or destructor function that was invoked as a result of either an implicit or explicit call to pthread_exit(). After a thread has terminated, the result of access to local (auto) variables of the thread is undefined. Thus, references to local vari- ables of the exiting thread should not be used for the pthread_exit() value_ptr parameter value. The process exits with an exit status of 0 after the last thread has been terminated. The behavior is as if the implementation called exit() with a 0 argument at thread termination time. The pthread_exit() function cannot return to its caller. No errors are defined. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ exit(3C), pthread_cancel(3C), pthread_create(3C), pthread_join(3C), pthread_key_create(3C), attributes(5), standards(5) 23 Mar 2005 pthread_exit(3C)
All times are GMT -4. The time now is 11:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy