signed portBASE_TYPE xReturn;\r
xTimeOutType xTimeOut;\r
\r
- /* The source code that implements the light weight (fast) API is much \r
+ /* The source code that implements the alternative (Alt) API is much \r
simpler because it executes everything from within a critical section. \r
This is the approach taken by many other RTOSes, but FreeRTOS.org has the \r
- fully featured API as an alternative. The fully featured API has more \r
+ preferred fully featured API too. The fully featured API has more \r
complex code that takes longer to execute, but makes much less use of \r
- critical sections. Therefore the light weight API sacrifices interrupt \r
+ critical sections. Therefore the alternative API sacrifices interrupt \r
responsiveness to gain execution speed, whereas the fully featured API\r
sacrifices execution speed to ensure better interrupt responsiveness. */\r
\r
xReturn = queueERRONEOUS_UNBLOCK;\r
}\r
}\r
- else\r
- {\r
- \r
- }\r
}\r
}\r
while( xReturn == queueERRONEOUS_UNBLOCK );\r
xTimeOutType xTimeOut;\r
signed portCHAR *pcOriginalReadPosition;\r
\r
- /* The source code that implements the light weight (fast) API is much \r
+ /* The source code that implements the alternative (Alt) API is much \r
simpler because it executes everything from within a critical section. \r
This is the approach taken by many other RTOSes, but FreeRTOS.org has the \r
- fully featured API as an alternative. The fully featured API has more \r
+ preferred fully featured API too. The fully featured API has more \r
complex code that takes longer to execute, but makes much less use of \r
- critical sections. Therefore the light weight API sacrifices interrupt \r
+ critical sections. Therefore the alternative API sacrifices interrupt \r
responsiveness to gain execution speed, whereas the fully featured API\r
sacrifices execution speed to ensure better interrupt responsiveness. */\r
\r