FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [June 2013 Threads] Environment independencePosted by Mark on June 3, 2013 I was surprised to see sprintf() in the core code and it got me wondering . .
For purity sake why wouldn't all of the library functions be brought out into a port-specific file so they can be identified and assigned an implementation. I know memcpy, memset and sprintf are all common implementations, but they 'may' not be thread-safe in a particular library.
@Richard Incidently, I'm working on the eZ80 (Zilog) port found in the in the community section. I fixed one problem with it and it seems stable so far. After I add some device drivers I'll contact you about sharing it.
RE: Environment independencePosted by Richard on June 3, 2013 sprintf() is not used by the kernel - but does exist in some utility functions that provide debugging information in a nicely formatted way (?). There is also a tiny sprintf() implementation provided in an external file.
That said, I agree it is not nice, and there is already a change request to add functions that allow the same debugging information to be output in binary (rather than ASCII) form for external formatting.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|