anchao commented on PR #15551: URL: https://github.com/apache/nuttx/pull/15551#issuecomment-2591754930
> > > > > > > why not? they are kernel characteristics as far as i know. > > > > > > > > > > > > > > > > > > Let me clarify further, should be"define", not "use" > > > > > > > and also not suitable for **define** in the sched directory. > > > > > > > > > > > > > > > well, to me, it seems more natural to define kernel constants in kernel than libc. > > > > > > > > > > > > actually no one in the sched directory is using these definitions > > > > > > > > > if you move them to fs, it might make sense. but why libc? > > > > > > Most of the limit macros are Unix-specific and are more likely to be defined in libc unistd > > https://pubs.opengroup.org/onlinepubs/009696799/functions/fpathconf.html > > sorry, i don't understand your logic. i expect these constants (eg. PATH_MAX) are defined in a userland header (eg. limits.h) to match the kernel counterpart. (eg. CONFIG_PATH_MAX) defining them in the opposite way sounds a bit awkward to me. I just need a more suitable place to define these macros, not sched. unistd is the best choice I see. If you think there is a better place, please suggest instead of constantly saying no. What I need is the method, not your challenge. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
