This is the mail archive of the newlib@sourceware.org mailing list for the newlib 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: (Q) what is __lock_close() ? can I leave it empty?

From: Min Lee <min dot lee at gatech dot edu>
To: newlib at sourceware dot org
Date: Wed, 03 Apr 2013 12:01:28 -0400
Subject: Re: (Q) what is __lock_close() ? can I leave it empty?
References: <515B78A6 dot 8030508 at gatech dot edu> <515BC6FA dot 2080700 at op dot pl>

thanks for reply, Freddie..
I don't know about "dynamic" locks.. also I don't see any lock_open things..
thank you anyway..
Regards,
Min


On 4/3/2013 2:06 AM, Freddie Chopin wrote:

W dniu 2013-04-03 02:32, Min Lee pisze:

what is close() operation on locks and can I leave them empty? would it
be safe?


I guess it's for locks that are "dynamic" - obtained with lock_open()
operation instead of declaring them to be a static variable with initializer.

Regards,
FCh

Follow-Ups:
- Re: (Q) what is __lock_close() ? can I leave it empty?
  - From: Freddie Chopin

References:
- (Q) what is __lock_close() ? can I leave it empty?
  - From: Min Lee
- Re: (Q) what is __lock_close() ? can I leave it empty?
  - From: Freddie Chopin

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