Re: cache G_BROKEN_FILENAMES



> Thread safety problems here. You could either:

I don't think so. I agree that calling getenv repeatedly is not a good idea,
since gtenv isn't very efficient.

If you make broken and initialized volatile, you do not have concurrency issues.
At worst, you will have a few concurrent calls to getenv, but so what ?
They will all result in the same setting.

Arno



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]