I really need to do a basic D -betterC project, just using it as a basic low level language, maybe with a dash of DbC. Probably with embracing some Oberon concepts (static imports, single return etc.)
> With this release it is now possible to install and activate compilers from the Windows command prompt directly.
> Assuming an MSYS2 installation is present in C:\msys64, necessary decompression tools can be installed from the Windows command prompt
Huh? I would think the whole point of running from command prompt would be that MSYS2 is not needed. And the reality is its probably not. Someone would just need to reimplement the Bash script as a PowerShell script.
Any bash environment on Windows will do. install.sh serves a specific use case for those who need it. It installs dmd in the user's home directory along with a script that enables/disables that specific version in the environment, so multiple dmd versions can be installed side-by-side, and the user can switch between versions as needed. It's a convenience script, more than anything else. More suited for people used to developing in Linux who need to work in Windows from time to time (with or without WSL) than regular Windows developers. The latter group will certainly prefer the Windows installer.
I do not follow D closely, but i get the impression that the language breaks backwards compatibility every now and then - i remember some posts here or Reddit some months ago by someone complaining that Walter Bright introduced some changes to the language that broke existing code.
IMO a mature language is a language that you can depend on for your existing code to keep working in a timespan of decades - like C and C++ for example. A language that willingly breaks backwards compatibility is a toy, not something to be taken seriously for long term work.
[+] [-] crazypython|5 years ago|reply
[+] [-] mhd|5 years ago|reply
[+] [-] crazypython|5 years ago|reply
[+] [-] qznc|5 years ago|reply
[+] [-] svnpenn|5 years ago|reply
> Assuming an MSYS2 installation is present in C:\msys64, necessary decompression tools can be installed from the Windows command prompt
Huh? I would think the whole point of running from command prompt would be that MSYS2 is not needed. And the reality is its probably not. Someone would just need to reimplement the Bash script as a PowerShell script.
[+] [-] tastyminerals2|5 years ago|reply
I never used the "install.sh" but just tried and since I have Windows git installed (which comes with MSYS2) it just worked without any issues.
[+] [-] johannes1234321|5 years ago|reply
... and then maintain it.
[+] [-] aldacron|5 years ago|reply
[+] [-] AnIdiotOnTheNet|5 years ago|reply
Wow, really? Hardcoded paths in 2020?
[+] [-] tastyminerals|5 years ago|reply
If you're looking for magnitutes faster scripting alternative to Python like once me, take a peek!
[+] [-] throwaway_pdp09|5 years ago|reply
[+] [-] macleginn|5 years ago|reply
[+] [-] badsectoracula|5 years ago|reply
I do not follow D closely, but i get the impression that the language breaks backwards compatibility every now and then - i remember some posts here or Reddit some months ago by someone complaining that Walter Bright introduced some changes to the language that broke existing code.
IMO a mature language is a language that you can depend on for your existing code to keep working in a timespan of decades - like C and C++ for example. A language that willingly breaks backwards compatibility is a toy, not something to be taken seriously for long term work.