Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem


naming conventions

Posted by tns1 on August 26, 2008
I am not seeing anything in the docs about the coding standard used in FreeRtos. I assume the prefixes are along the lines of 'u'=unsigned,'s'=signed (or short?),'p'=ptr ... so what is the 'x' and 'v' prefix supposed to mean?

RE: naming conventions

Posted by Richard on August 26, 2008
See http://www.freertos.org/a00017.html#NamingConventions although this is a little old. 'x' is also used for variables of type portBASE_TYPE, which is the most efficient type for the architecture, typically char for 8bitters, short for 16bitters and long for 32bitters.


RE: naming conventions

Posted by Richard on August 26, 2008
'v' is also missing. v for void. So vTaskDelete() is defined in Task.c (from name) and returns a void.


[ Back to the top ]    [ About FreeRTOS ]    [ Privacy ]    [ Sitemap ]    [ ]

Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

FreeRTOS v10.2.0 is available for immediate download. MIT licensed, and including RISC-V and ARMv8-M (Cortex-M33) demos.

NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.

View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.


FreeRTOS and other embedded software careers at AWS.

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Cadence Tensilica Cortes

Espressif ESP32

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers





STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS

Xilinx Microblaze and Zynq partner