This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Still improving! (Was: Re: [PATCH] Avoid strtok for thread safety)

From: Paolo Carlini <pcarlini at unitus dot it>
To: libstdc++ at gcc dot gnu dot org
Cc: Martin Sebor <sebor at roguewave dot com>
Date: Wed, 27 Nov 2002 17:11:38 +0100
Subject: Re: Still improving! (Was: Re: [PATCH] Avoid strtok for thread safety)
References: <3DE2BF34.5030500@unitus.it> <20021126234925.A2489@cantrip.org> <3DE2BF34.5030500@unitus.it> <3DE40B90.5070108@unitus.it> <20021127003425.B2489@cantrip.org> <20021127061047.B50009@cantrip.org> <3DE48538.2020208@unitus.it> <3DE4EE59.5090606@roguewave.com>

Martin Sebor wrote:

Sorry for butting in, but the code above doesn't seem exception
safe :) (I.e., it will leak if any of the new expressions except
the first one throws).

Thanks!

What about Nathan's solution? At this point I was meaning to finalize *that* one, indeed:

http://gcc.gnu.org/ml/libstdc++/2002-11/msg00297.html

Ciao, Paolo.

Follow-Ups:
- Re: Still improving! (Was: Re: [PATCH] Avoid strtok for thread safety)
  - From: Nathan Myers

References:
- [PATCH] Avoid strtok for thread safety
  - From: Paolo Carlini
- Re: [PATCH] Avoid strtok for thread safety
  - From: Nathan Myers
- Re: [PATCH] Avoid strtok for thread safety
  - From: Paolo Carlini
- Re: [PATCH] Avoid strtok for thread safety
  - From: Nathan Myers
- Re: [PATCH] Avoid strtok for thread safety
  - From: Nathan Myers
- Still improving! (Was: Re: [PATCH] Avoid strtok for thread safety)
  - From: Paolo Carlini
- Re: Still improving! (Was: Re: [PATCH] Avoid strtok for thread safety)
  - From: Martin Sebor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]