oso2k

45 ms·

481.
by oso2k 11y ago
I agree. And neither is WebSQL. I was speaking to the "approach to Web Standards", not actual Web Standards. My point being that Moz used (IMO) conjecture and FUD to roadblock those technologies. No attempt on their part to ex
482.
by oso2k 11y ago
I agree. And I extend that sentiment to their approach to Web Standards a few years ago too, like WebSQL [0] and NaCl [1], Dart [2]. That felt like NIH [3] or some other non-collaborative or ultra-competitive motivation on their part. No
483.
by oso2k 11y ago
Make uses patterns as well, especially if you're "Doing It Right"(tm) [0][1][2]. [0] http://git.suckless.org/st/tree/Makefile#n6 [1] http://git.suckless.org/st/tree/Makefil
484.
by oso2k 11y ago
Said another way, the for loop can be written as FILE *fp = fopen( path, mode ); while( fp ) { fclose( fp ); fp = 0; } NULL (and 0) evaluate to false in C.
485.
by oso2k 11y ago
No, it's not an infinite loop. If fp comes back as NULL from the initializer part of the loop, then the for loop exits.
486.
by oso2k 11y ago
The files only need to be in certain logical locations (like the root of the drive), not physical locations. Fragmentation is not an issue either. See what FreeDOS say about this [0]. [0] http://help.fdos.org/en/hhstn
487.
by oso2k 11y ago
If you read the link, the file attributes (Hidden and/or System) of place no bearing on the MBR/Bootloader. Even the OP Article also acknowledged that. You can also read about this on wikipedia [0]. Bootloaders are essentially
488.
by oso2k 11y ago
I don't think that was ever true. DOS 7.x proved this as MSDOS.SYS became a text file. The DOS boot process always required IO.SYS to load MSDOS.SYS [0]. [0] http://www.dewassoc.com/support/msdos/dos_boot_pro
489.
by oso2k 11y ago
Software distribution used to be done via FTP sites, separate from the project web pages, documentation, issue tracker, etc. iBiblio [0] will still host stuff for distribution. There's also Savannah.nongnu.org [1] which is an old for
490.
by oso2k 11y ago
That's a great quote.
491.
by oso2k 12y ago
I'm not sure what you mean by 'Compiler designers hate him!'? jgc's work on Make always comes up when I having an issue implementing something. The title is link-bait, but there is a potentially very useful nugget of in
492.
by oso2k 12y ago
Imagine you happen to walk up to your ATM when it's Mother Banking System is in the middle hotspot compile followed by a GC pause. What would you do if your ATM took 5 minutes+ to respond to your Withdrawal Request? You'd probabl
493.
by oso2k 12y ago
I think the real answer is that the DCE optimizer understands that y is assigned the same address in x, x never changes (after arithmetic cancels out), y never changes, and then the difference between y & x becomes 0.
494.
by oso2k 12y ago
For me, I remember the notation by correlating it to its "high-level" equivalent. mov eax, [ ptr ] is like eax = *ptr; // or, eax = ptr[ 0 ]; The offset/multiplier memory addressing format for AT&am
495.
by oso2k 12y ago
syscall is the standard ABI for a 64-bit kernel in Long Mode [0]. [0] http://wiki.osdev.org/SYSENTER#Compatibility_across_Intel_an...
496.
by oso2k 12y ago
The syscall version isn't much more complex. You can compare the syscall ABIs here [0] [0] http://en.wikibooks.org/wiki/X86_Assembly/Interfacing_with_L...
497.
by oso2k 12y ago
Couldn't tell from the guide, is this armv6 (A/A+, B/B+, Compute) or armv7 (B2)?
498.
by oso2k 12y ago
jgc is a great resource when you got a sticky issue to resolve. For my money, the suckless guys are the guys to emulate when you start fresh with a Makefile [0][1]. [0] http://git.suckless.org/sbase/tree/Makefile
499.
by oso2k 12y ago
Haha. Good catch, I actually use $(shell cat tmp.ci.pid) to capture the PID in a var $(TMPCI) if you look at the actual Makefile I linked.
500.
by oso2k 12y ago
I like your watch target. I implemented something similar [0] with watch (bash builtin or GNU watch) & time. start_ci: watch time -p make clean all & echo $$! > tmp.ci.pid stop_ci: kill -9 `cat tmp.ci.pid` The
501.
by oso2k 12y ago
Have you read the Make pattern rules examples [0]? There's the specific example of yacc/bison doing something similar to as your describing (at least for 1:N case). %.tab.c %.tab.h: %.y bison -d $< [0] http:&#x
502.
by oso2k 12y ago
I usually add two targets for my my projects: 'help' and 'showconfig'. 'make help' explains which targets to use and/or how to combine them. 'make showconfig' shows all the important what the i
503.
by oso2k 12y ago
I get what you're saying but not seeing how to do that in make syntax. Mind giving an example?
504.
by oso2k 12y ago
You're really speaking about advanced JIT techniques. JIT isn't about switching between compiled code & interpreted code, or fast & slow code. It's about combining compilers and interpreters to get the benefits of b
505.
by oso2k 12y ago
Here's the 31 line (not sloc) echo in sbase [0]. [0] http://git.suckless.org/sbase/tree/echo.c
506.
by oso2k 12y ago
Here's an example [0] where Googles showed they preferred their ICU implementation over system, in effect, remaining self-sufficient & neutral of the embedder's concern. And as an independent embedder with a non-public projec
507.
by oso2k 12y ago
I'd argue the former.
508.
by oso2k 12y ago
I take it this is different from the NodeRED[0] thing IBM released a year or two ago? So, if node.js proper was closer to v8 HEAD, then they might find that the v8 team has recently been supportive of utilizing "precompiled scripts&qu
509.
by oso2k 12y ago
At least from what I've seen publicly on v8-users list, that is not true. Google has not, and seemingly, will not pick a side. Or, if you must, they've picked Chrome/Chromium and its 6-week version/development cycle.
510.
by oso2k 12y ago
It's sad, too, that Joyent and/or moderator Forest Norvell are rejecting posts to the Google Groups which are non-supportive of the new "Foundation". Doesn't seem like they really have the interests of the "co

More ›