back
user profile
uecker
2,146karma·1,822submissions·April 14, 2020
about
Computational Magnetic Resonance Imaging, Real-time Magnetic Resonance Imaging, GCC Contributor, BART Toolbox, Member of ISO C WG14
recent activity (1,822 total)
comment
Slightly tweaking might not always be sufficient. Reengineering my numerical code would certainly a bit of effort. But anyhow, I do not think C++ is better. Recently I removed one (!) file with templa…
comment
In principle, the are supported already with gcc 12 or even earlier, but this is evolving. https://godbolt.org/z/88qv3jjTM I use c23 features but also vm-types for bounds checki…
comment
I agree, but are you responding to me?
comment
Renaming c. to .cpp may work with ancient c89 code, but not with anything remotely modern. But while the code then is technically C++, it is not better. I still prefer C for new projects to any othe…
comment
This is a misrepresentation based on a misunderstanding on how standardization works. The C standard committee has long recognized the need for better safety and carefully made it possible so that C c…
comment
I mostly just install a -dev package on Linux and I am done.
comment
Well, there is Annex K which is based on a previous Microsoft effort. Almost universally it is considered terrible and few people implemented it.
comment
Thanks! Two notes: GCC has its "access" attributes which can give you similar bounds safety as clang. Please see also my experimental library. https://codeberg.org/uecker…
comment
I find it extremely useful and it works well for many use cases. This already implies that "it is useless" is pure nonsense. If it does not work for your usecase, just don't use it.
comment
I am not sure why this means why "NFS is really stupid" if the user assumes that a distributed file system can be treated just like a local system. That is provides the same interface is w…
comment
I don't think the problem is nearly as big as people claim. Experts are often right! While there are counter examples and inefficiencies in the system (and there are idea of addressing this, by d…
comment
This is exaggerating and generalizing too much. Science still works extremely well in general.
comment
I do not see what this has to do with Unix. The problem is not that programs interoperate or handle text streams, the problem is a) the supply chain issues in modern web-software (and thanks to Rust …
comment
"endless list of CVE" seems rather exaggerated for coreutils. There are only very few CVEs in the last decade and most seem rather harmless.
comment
These are not the "same risks" at all.
comment
I would say the least thing the scientific community needs is the packaging mess of Python introduced also on the lower level via Rust.
comment
According to my experience, all the "zero-cost abstractions" from C++ most of the time make it more annoying to maintain and/or understand the code, especially with respect to resource …
comment
Indeed, and this is why people who care about this are also proving memory safety in C. The issue is that we do not have good open-source tooling that specifically focuses on formal verification of me…
comment
Fair enough, but I have seen how it works and for just temporal memory safety, it could be simple.
comment
Depending on what you are doing, yes. But the statement I responded to "your only choice is crash" is certainly wrong.
comment
For temporal memory safety.
comment
Even without Fil-C I do not think it is even clear that new software should be written in Rust. It seems to have a lot of fans, but IMHO it is overrated. If you need perfect memory safety Rust has an…
comment
What makes you think that one can not add an explicit bound check in C?
comment
I do not know how Fil-C handles this, but it could raise a signal that one can then catch.
comment
The problem is not that society is too complexity but extremely unequal distribution of money. Those few that have most of it usually did not earn it by providing a useful service to society and fo…
comment
XML is already terrible. But the main problem seems to be that they created something similar but incompatible to make.
comment
There is something fundamentally wrong with Windows or Visual Studio that it requires ugly solutions.
comment
This is fitting for something simulating cargo, which is a huge supply chain risk itself.
comment
That Rust gives you correctness is very misleading claim.
comment
Memory safety is not the same a scorrectness and more advanced type is also not the same thing as correctness.