Prashant Rahul commented on a discussion: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/74#note_136126 > The expected behaviour should be to create both if both flags are given > that's along the lines any other tool. While the current tool doesn't support > that having an extra file is not a huge deal. Not creating anything at all > when both flags are given would be a bigger issue but I don't know why those > two flags would be mutually exclusive. I agree that it shouldn't be mutually exclusive, I was trying to maintain compatiblity with the older script as much as possible. Said that, I think we can change it to something like: 1. Create both files by default when neither of the flags are given 2. You can disable specific file by specifying its respective flag (`-H` to disable header file, and `-C` to disable source file) 3. Remove mutual exclusivity rule and simply dont create any file when both flags are given, not sure why anyone would want that tho > Also thanks for rewriting this it's a huge help to get these tools moved out > of C to Python. Welcome! I was looking for something simpler to get started on with rtems and its eco system. -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/74#note_136126 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
