|
|
On 26 Nov 2022, at 17:05, Jose Q wrote:
>
> On Friday, November 25, 2022 at 2:28:16 AM UTC-8 Ian MacArthur wrote:
> Way off-topic, but from a portability perspective having filenames (auto-generated or otherwise) that differ only in name-case is just a disaster wating to happen, really.
> It would probably be safer and more portable to make the auto-generated file have some unique name, "Just In Case"... say Fl_Flow_hdr.H or etc., just to ensure it can not "collide" with the "other" Fl_flow.h file...
>
> The files are also in different folders in this case, so a name collision won't happen on a case-insensitive file system.
Sure, but "different folders" is not always a robust solution - if the include path is such that the compiler can/will search both folders, you still can get collisions, or weird behaviour where it depends what order the include folders are searched and so on... Which can be quite confusing to debug at times!
So, I’m a big fan of keeping the names unique, basically (you may have spotted that...)
>
> Sorry for the janky quoting. It's the only way I've found to not top post when using the Web interface. What's a good client for navigating these groups?
TBH I use the web interface a fair bit, and it usually seems to work...
If you go to the end of an existing line and hit enter a few times, you get an “unquoted” line to add your own text; well, that’s what works for me at any rate.
That said, I’m also subscribed to the mailing list and so many replies (including this reply) are just via a regular email client (Apple Mail in this instance...)
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/E343316C-018A-4A71-A8F0-7304385FB93D%40gmail.com.
[ Direct Link to Message ] | |
|
| |