This is the mail archive of the
mailing list for the newlib project.
Re: (Q) what is __lock_close() ? can I leave it empty?
- From: Freddie Chopin <freddie_chopin at op dot pl>
- To: newlib at sourceware dot org
- Date: Wed, 03 Apr 2013 18:45:58 +0200
- 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> <515C5258 dot 2080705 at gatech dot edu>
W dniu 2013-04-03 18:01, Min Lee pisze:
thanks for reply, Freddie..
I don't know about "dynamic" locks.. also I don't see any lock_open
thank you anyway..
Take a look at newlib\libc\sys\linux\sys\lock.h - these are defines of
these locks for Linux. This is the only place which actualy defines
these lock functions. I guess that close() is only for cases where
__lock_init() actually allocates some resources (these should be treated
as "open"). If that's not the case then __lock_close() can probably be