cremno

24 ms·

181.
Introducing the Universal CRT(blogs.msdn.com)
5 points by cremno 12y ago|0 comments
182.
by cremno 12y ago
Dropbox doesn't read the file content. There is also no proof that Dropbox directly accesses those files.
183.
by cremno 12y ago
The changelog? Perhaps the _two_ listed fixed issues (ffi build failure, Symbol GC memory leak) were just the most important ones according to the maintainer.
184.
by cremno 12y ago
I don't know. I'm actually more interested in what it receives/sends.
185.
by cremno 12y ago
Yes, free(NULL) is a questionable statement. The source code comment (not the analyzer) just irritated me.
186.
by cremno 12y ago
The malloc(3C) man pages since 5.5.1 claim otherwise.
187.
by cremno 12y ago
>So do implement it then to avoid the compilation and/or linking errors, but make it crash intentionally if called. void SimpleReferenceObject::operator delete[](void * /* pPtr */) { free(NULL); } Wh
188.
by cremno 12y ago
It's legal C99. See DR258 / C99+TC3. But be careful, reading trap representations is UB. http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_283.htm http://www.open-std.org/
189.
by cremno 12y ago
I recommend checking out Corkami's articles/posters: https://code.google.com/p/corkami/wiki/PE https://code.google.com/p/corkami/wiki/PE101 https://code.go
190.
by cremno 12y ago
Linux actually has/had flowery names: https://en.wikipedia.org/wiki/List_of_Linux_kernel_names
191.
by cremno 12y ago
The commit message contains some numbers: https://github.com/golang/go/commit/6c7cbf086c34ebb88311ba12...
192.
Exploiting NVMAP to Escape the Chrome Sandbox – CVE-2014-5332(googleprojectzero.blogspot.com)
5 points by cremno 12y ago|0 comments
193.
by cremno 12y ago
Well, that status page links to http://www.w3.org/community/ortc/ , so I don't think they mean CU-RTC-WEB.
194.
by cremno 12y ago
https://status.modern.ie says WebRTC is in development and CSS 3D transforms are part of a IE preview release.
195.
Calculating day of week and Easter date(strchr.com)
1 points by cremno 12y ago|0 comments
196.
by cremno 12y ago
Oh, I am the one that has to be sorry! I didn't check the URL, even though I am aware of that issue with cgit (no line highlighting). Yeah, using alloca() (in any form, incl. VLA) isn't good style. At least it's bounded, sinc
197.
by cremno 12y ago
I don't like the usage of that attribute either (but if that's their strategy, fine by me.), but I still don't see where the obvious memory leaks are. Your first link links to a line with a strdup() call, but the correspondin
198.
by cremno 12y ago
Where are the _obvious_ memory leaks?
199.
Why does a single integer assignment statement consume all of my CPU?(blogs.msdn.com)
5 points by cremno 12y ago|0 comments
200.
Multi-threaded setxid on Linux(ewontfix.com)
19 points by cremno 12y ago|0 comments
201.
by cremno 12y ago
They're still part of C++14. You have to wait for C++1z (or use a compiler switch).
202.
by cremno 12y ago
What about normalization, which by the way, isn't actually NFD — it's just very similar to it?
203.
by cremno 12y ago
Another “funny” detail: >The maximum representable date is February 6, 2040 at 06:28:15 GMT. http://dubeiko.com/development/FileSystems/HFSPLUS/tn1150.ht...
204.
by cremno 12y ago
>So Nim really needs more active users and contributors. I've fixed an issue you're experiencing: https://github.com/Araq/Nim/issues/1804 :3
205.
by cremno 12y ago
The final draft is available: https://www.ipa.go.jp/osc/english/ruby/ But the ISO document is mostly irrelevant, if we talk about Ruby implementations like CRuby, JRuby, or Rubinius.
206.
Windows: Elevation of Privilege in Ahcache.sys/NtApphelpCacheControl(code.google.com)
2 points by cremno 12y ago|0 comments
207.
by cremno 12y ago
>why it's not as hyped I don't know how relevant that is, but Rust has Mozilla (and Samsung?) and Go has Google plus some Unix / Plan 9 people behind it. But Nim? There are probably other factors as well.
208.
by cremno 12y ago
But GCC likely isn't able to do that for libc functions like qsort(). Maybe if LTO is enabled and libc is linked statically, it might.
209.
by cremno 12y ago
Then why isn't his example stupid, but fine? They're basically doing the same bad thing - subtracting two signed integers without caring about possible overflow.
210.
by cremno 12y ago
If performance really is of concern, qsort() or similar functions probably shouldn't be used. Instead a dedicated function, which allows to choose a specific algorithm (qsort() doesn't have to use quicksort) and also doesn't

More ›