xorblurb

29 ms·

181.
by xorblurb 11y ago
What you write is all very meta, so maybe enlighten us on their motivations and why they should continue in that way? And on how using a language is the same as implementing it and how it seems that the application space has magically folde
182.
by xorblurb 11y ago
You can't infer shit, because of the way current compiler writers are interpreting the standard today. At one point in the 90's it was obvious for the entire planet including compiler authors that some undefined behaviors did not
183.
by xorblurb 11y ago
About the memcpy stuff, when you consider the whole picture, this is ridiculous though. There should be no reason for any sane implementation to ever do nasty stuff about void copy_8_bytes(char *dst, const char *src) { *(uint64_
184.
by xorblurb 11y ago
I completely agree. A spec of a quarter page can already be incredibly convoluted and with very hard to anticipate consequences -- even more so when crazy people are interpreting it without caring about the consequence of their acts in the
185.
by xorblurb 11y ago
Well, in the model, there is no such thing as effective type of objects loosing their power at TU boundaries, and otherwise no relationship defined between effective types and linkage. An implementation that tags all accesses to dynamically
186.
by xorblurb 11y ago
Translation phases are all fun and games, but WPO can still break your code thanks to as-if rules - and because nothing prevent alias analysis to be performed regardless of the TU boundaries. And compilers are doing it.
187.
by xorblurb 11y ago
It's preemptive arguing :P
188.
by xorblurb 11y ago
At the end, all things are equivalent, however for example explaining that to complete beginners (vector growing rules, their relationship to underlying memory allocation and pointers, the fact that "raw" memory allocation exists
189.
by xorblurb 11y ago
instantaneous != retroactively, neither it is the same as "5 years after". And all major compiler vendors have since learned that they need to be up to date with the standard ASAP, even before official publication when it is possi
190.
by xorblurb 11y ago
>This has nothing to do with vector vs arrays, and actually works the same for vectors and arrays (if you realloc a C array, you have the same issue as if you append to a vector). If you realloc a C array, you have "realloc" wr
191.
by xorblurb 11y ago
Well this is my opinion on the linked webpage, which I agree with you is worthless in this form, so here is a hopefully more interesting one: this is a set of arbitrary rules, some are basic and would be only of interest for beginners, some
192.
by xorblurb 11y ago
You don't but I do: you don't want to replace all your exec of e.g. "cp" with "cp.exe", .exe are not very often handled in real Unix environments, results of build without .exe under a real Unix would already c
193.
by xorblurb 11y ago
VMs can share host volumes, Cygwin can suddenly become buggy and has no release (it is currently doing shit with ACL on my install, to the point of being unusable, and this seems to have affected other people too), so is not completely suit
194.
by xorblurb 11y ago
About Cleanroom, the prohibition on unit testing is insane; CPU and compiler bug exists, so do subtleties in languages, and even good quality models in formalized forms have some defects that probably prevent to get a mathematical proof of
195.
by xorblurb 11y ago
There is utterly no content in this reponse. ( edit: s/this/there/ )
196.
by xorblurb 11y ago
Also remember about Sourceforge. I guess some people could have been in the mood to write gratitude letters to them at some point in the past. (Does not mean that GitHub is "bad" or be useful for some free software projects right
197.
by xorblurb 11y ago
Some applications are not designed to be portable to 32-bits targets, regardless of memory usage... (whether or not this is a bad thing is another story, but at a point where such non-trivial application exist and has to be checked this is
198.
by xorblurb 11y ago
99% of them did not even know exactly what they "voted" for...
199.
by xorblurb 11y ago
Very interesting. I'm glad they were sufficiently pushed to eventually start thinking about remoting. I get that X protocol was not that good -- but I'm still not convinced that their model is, not even talking about future proof,
200.
by xorblurb 11y ago
Yes, Wayland doesn't dictate anything, and that's the problem! It is the moral equivalent of a glorified framebuffer. Number of subjects relevant in today interfaces interactions? I'm not sure there are any. Meanwhile graphic
201.
by xorblurb 11y ago
Its very doubtful that Wayland will happen in 2016. I'm not sure it does anything to solve real GNU/Linux problems for consumer and/or workstation devices. At least not without breaking everything else far more. The idea to l
202.
by xorblurb 11y ago
It is a very different issue but can be very much in favor of GNU/Linux distribution when they work on a given piece of hardware: they are far more likely to be able to get version N+1 of said distribution than Windows N+1. Now Windows
203.
by xorblurb 11y ago
Exactly. A non negligible part of his rant was about proprietary graphic drivers. Free software developers can't do anything about that, and anyway what is the point? Today, if you want to game just use Windows, if you want a fine Linu
204.
by xorblurb 11y ago
Honestly Linus is a genius about the social side of big projects. He managed to scale Linux development very well, even writing Git in the middle. About the technical parts in their epoch context, it is more mixed: technically before 2.6 ve
205.
by xorblurb 11y ago
> The monolithic Linux kernel is just too big. What is it now, 20,000,000 lines? There's no hope of debugging that. It shows. That makes no sense. Most of that are drivers and platforms you won't ever use. And some forms of sym
206.
by xorblurb 11y ago
Journalists should be educated on effects of false positives even at low proba (which is not even the case here) on random investigations. Actually, police and justice should be, but when they are not at least we should hope that journalist
207.
by xorblurb 11y ago
Well at least the section explaining why they think C is not Turing complete is beyond ridiculous (TLDR: memory is not infinite so there exist a state machine... WTF????? technically mathematically true but has always been completely irrele
208.
by xorblurb 11y ago
Compared to the economic cost of bugs, bound checks everywhere are (very very) cheap. Even more so with the CPU and compilers we have today, which are more than sufficiently smart from the point of view of when C was created. Intel is even
209.
by xorblurb 11y ago
At this point you pretty much want an alternative language more than a compiler: one that looks like C, but is completely defined. And this makes kinda sense, yet is IMO still quite dangerous (less than the actual situation but still too mu
210.
by xorblurb 11y ago
I live in France and I pay 50€ for 3GB of 4G per month (then bw limited) _and_ 200Mb/s down 50Mb/s up fixed Internet (official speeds but I speedtest them at something like 270 / 70 Mb/s) There are other operators which

More ›