🚀 go-pugleaf

Hi all,

Is volatile the oposite of const, and do the tricky things about const
also belong to volatile.
Exp:
	const char *foo;	/* foo points only to characters that
				 * will not be changed through foo 
				 */
	char *const foo;	/* foo is an unchanging pointer to a
				 * possibly changing char.
				 */
Does this correspond to:
	volatile char *foo;	/* foo points to characters that may
				 * be changed by other threads
				 */
	char *volatile foo;	/* foo is a pointer that may be changed
				 * by another thread.
				 */
My problem belongs to setjmp, longjmp.
I want to do a setjmp, then do some fancy mallocs. if a malloc fail,
I want to do a longjmp and I want to free everything allocated till then.

char *foo = NULL;
char *bar = NULL;
jmp_buf env;

if (setjmp(env) == 0) {
	foo = malloc(...);
	if (foo == NULL) {
		...
		longjmp(env,1);
	bar = malloc(...);
	if (bar == NULL) {
		...
		longjmp(env,1);
} else {
	if (foo != NULL)
		free(foo);
	if (bar != NULL)
		free(bar);
}
Where do I have to write the volatile qualifier to tell the compiler not 
to do anything clever.

Joachim
-- 
---------------------------------------------------------------------
Joachim Huober                                Phone: +49 731 502-6241
UDINE-Project,            URZ, University of Ulm, 89081 Ulm , Germany
E-mail: joachim.huober@rz.uni-ulm.de 
---------------------------------------------------------------------