sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

wchar_t is a C++ built in and should not (always) be defined

Browse Source 
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4128 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2011-11-29 14:26:12 +00:00
parent 5db6e1052f
commit b2263531bd
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Documentation/NuttxUserGuide.html
View File

@ -1260,6 +1260,9 @@ interface of the same name.
If the message queue is full and <code>NON_BLOCK</code> is set, the message
is not queued and <code>ERROR</code> is returned.
</p>
<p>
<b>NOTE</b>: <i>mq_send()</i> may be called from an interrupt handler.
<p>
<p>
<b>Input Parameters:</b>
</p>
@ -2236,7 +2239,7 @@ If the value of the semaphore resulting from this operation is zero, then
on of the tasks blocked waiting for the semaphore will be allowed to
return successfully from its call to <i>sem_wait()</i>.
<p>
<b>NOTE</b>: <i>sem_post()</i> may be called from an interrupt handler.
<b>NOTE</b>: <i>sem_post()</i> may be called from an interrupt handler.
<p>
<b>Input Parameters:</b>
<ul>
@ -2250,9 +2253,9 @@ return successfully from its call to <i>sem_wait()</i>.
</ul>
<p>
<b>Assumptions/Limitations:</b> This function cannot be called
from an interrupt handler. It assumes the currently executing
task is the one that is performing the unlock.
<b>Assumptions/Limitations:</b>.
When called from an interrupt handler, it will appear as though the
interrupt task is the one that is performing the unlock.
<p>
<b> POSIX Compatibility:</b> Comparable to the POSIX
interface of the same name.