-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename .bmx folder to .bmxng ? #87
Comments
I think ".ng" looks better than ".bmxng". |
It is not about the looks ... NG is normally named "BlitzMax" (hence the https://blitzmax.org) - but as we cannot rename the closed source 1.50 BlitzMax folder ".bmx" we would then have to rename the BlitzMax NG one. Naming it ".ng" might be less obvious (between potential other "hidden folders") then a second folder ".bmxng". |
Oh I'm well aware of the . folders. |
I'm with @GWRon; I'd prefer ".bmxng" too. Not everyone uses legacy BlitzMax and NG in parallel and ".ng" alone seems particularly cryptic. If I was a new user, I'd ask "Why on earth is this language named BlitzMax creating folders named .ng"? |
But the language is called BlitzMax NG though, isn't it?
Or is it just the compiler?
I mean; NG has enums and stuff which BlitzMax doesn't, so the language is
different.
Different language, different compiler.
But yeah, I'm fine with either.
Den lör 22 juni 2019 23:03HurryStarfish <notifications@github.com> skrev:
… I'm with @GWRon <https://github.com/GWRon>; I'd prefer ".bmxng" too. Not
everyone uses legacy BlitzMax and NG in parallel and ".ng" alone seems
particularly cryptic. If I was a new user, I'd ask "Why on earth is this
language named *BlitzMax* creating folders named *.ng*"?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#87?email_source=notifications&email_token=AANFYNLWSY3NR34XCSLMBKLP32HSDA5CNFSM4HYQ6DSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYKRKQI#issuecomment-504698177>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANFYNIQHYDICD6DPBNYTO3P32HSDANCNFSM4HYQ6DSA>
.
|
Good question... I see BlitzMax-NG mostly as the name for the compiler, although we are of course extending the language itself too. "NG" itself is a fairly common acronym for "next generation", so it is quite... generic. |
For now BMK puts precompilates of sources into the ".bmx" folder regardless of whether you compile something with legacy or NG.
Sometimes I compile stuff with legacy as it contains less (or "other") bugs. With bigger projects a compilation can take a while. Compiling with one of the compilers (NG or legacy) first will lead to some files which both tool-chains see as "valid". This would result in files being used (without recompilation) which where compiled by the opposite toolchain (NG vs Legacy).
This enforces a complete recompilation once I switched toolchains - especially in a VM this means to wait 10-15 minutes until the binary is built.
So this is why I suggest to make the ".bmx" name configurable - or depending on whether compiled with vanilla or NG.
means ".bmx" for vanilla/legacy
and ".bmxng" for NG compilations.
Edit: Modules are the only portion creating files outside of the ".bmx" folder - but modules are most likely not shared across legacy/NG tool-chains.
Except for a little bit of added code - what disadvantages would you see having such a thing?
The text was updated successfully, but these errors were encountered: