-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Description
Zephyr 4.2 appears to have logging functions that use arg0 as an argument name. Because we have a macro called arg0 this breaks a lot of things.
/** @brief Create log message using simplified method for string with two arguments.
*
* @param source Pointer to the source structure.
* @param level Severity level.
* @param fmt String pointer.
* @param arg0 String argument.
* @param arg1 String argument.
*/
__syscall void z_log_msg_simple_create_2(const void *source, uint32_t level,
const char *fmt, uint32_t arg0, uint32_t arg1);So we should probably rename our macros, one of the options is warg0, warg1, and so on. This makes it clear it's a WebAssembly argument and it's specific to WARDuino (it starts with war). This decreases the chances of a name collision in the future while keeping the macro relatively short.
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Scheduled