michallenc commented on PR #10602: URL: https://github.com/apache/nuttx/pull/10602#issuecomment-1719851812
> You apparently seem focused on avoiding a clean context switch (which I believe is the correct, clean, flexible solution). @patacongo My main argument againts hooks you described above (various notifications, events, signal handlers etc.) is that it would lead to additional requirements for user application (different from how `fopencookie` is used in GNU/Linux). I havent had time to go through all code you suggested (graphics etc) so maybe I am missing something. But I think we should keep it in simple `fseak`, `fputs` etc operations. @mu578 I like the structure you proposed, that would solve a lot of issues with current `file_struct` and as @xiaoxiang781216 mentioned it should not be that difficult (mostly renaming etc.). We could still keep pointers to read/write/seek at `file` in `fs/vfs` as it is now for drivers and just add the possibility for custom streams if required. I would do this primarily for `fopencookie` and than build `fmemopen` and `open_memstream` on that if the community would agree as I think it is still beneficial to have `fopencookie` implemented (and its presence in Linux should justify that in my opinion). I also think we should probably move this discussion to mailing list now. -- 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
