jckarter

7 ms·

1.
by jckarter 10y ago
Looking at the generated code, we have a couple issues that prevent full optimization. One of them I already knew about ( https://bugs.swift.org/browse/SR-2926 ) -- as a debugging aid, we guard every trap we emit with th
2.
by jckarter 15y ago
Clay has shared and unique pointer implementations in its library. Naive channels could be mostly implemented in the library as well, but I think they might need language support to pull some of the tricks Rust and Go do to make them fast,
3.
by jckarter 15y ago
Clay is a lot more flexible and metaprogrammable than Rust. Clay allows ad-hoc overloading with predication based on arbitrary compile-time computation, whereas Rust's polymorphism support is more strictly based on Hindley-Milner parametric
4.
by jckarter 15y ago
What build information is missing? The README.txt describes how to build the compiler; it's a fairly typical cmake setup.
5.
by jckarter 15y ago
You're correct; Clay's type system doesn't help much with memory safety. It's flexible enough to express RAII-based ownership semantics like C++, so you can manage dynamic memory with reference counted, uniquely-owned, or other policy-enfor
6.
by jckarter 15y ago
The more fundamental mismatch is that they're testing an interpreter (libc's printf implementation) against a compiler (pypy's format string jit). A C++0x or D library that parsed format strings at compile time would likely still beat pypy.
7.
by jckarter 15y ago
If you're banned here, you aren't locked out of the site or prevented from posting. Your posts are just marked so that only you (and other users who have chosen "show dead comments" in their preferences) can see them, and there's no indicat
8.
by jckarter 15y ago
jashkenas (CoffeeScript author) replied to you, but for some reason he's deadbanned: > Thanks for mentioning it -- the fix was actually to correct a regression from a previous commit, not a true bugfix versus 1.0.1. I've removed that li
9.
by jckarter 16y ago
It's C++ and of course dependent on Unix/Windows memory mapping APIs, but you might like asmjit: http://code.google.com/p/asmjit/
10.
by jckarter 16y ago
Sad, but understandable. "OpenBSD writes their own ROFF interpreter" isn't very interesting, but "OpenBSD purges C++ from core" appeals to developers' strong emotional responses toward C++.
11.
by jckarter 16y ago
Not everywhere needs to become Silicon Valley. IT is well-trodden ground with established players and power centers now. Smaller cities like Portland would do better promoting emerging industries than trying to catch up to the web startup b
12.
by jckarter 16y ago
I see. So does this purge only consist of compiled executables then, with the standard C++ headers and libstdc++ still getting a pass?
13.
by jckarter 16y ago
Orthogonal to bloat, libstdc++ is a large, ugly, and hard-to-audit attack surface that I'm sure OpenBSD is glad to push out of core.
14.
by jckarter 16y ago
Every Mac still ships with Xcode on the OS install disc, as do the OS X upgrade discs. Let's wait until Lion comes out before assuming that won't be the case anymore.
15.
by jckarter 16y ago
The language in the standard may have changed in C99 due to unprototyped functions being deprecated. In C89, however, I'm pretty sure that unprototyped and prototyped functions need to have compatible calling conventions. In practice, there
16.
by jckarter 16y ago
This is incorrect. It's not possible to implicitly use an incompatible ABI for prototyped and vararg functions, since a foo f(bar, bas) function needs to be callable via an unprototyped foo (* )() pointer. Thus, even prototyped C functions
17.
by jckarter 16y ago
I wonder if they'll stick to this for the final version. They tried to remove 256-color mode support in 10.5.something but backpedaled when the Mac Starcraft players went nuts.
18.
by jckarter 16y ago
There are lots of edge cases where the sign of zero affects computation. In floating-point, zero values represent not only the exact value zero but the result of an underflowed computation too small to represent as a non-zero floating point
19.
by jckarter 16y ago
That's just for the framebuffer. All the intermediate textures flying around will need four times the memory too, and could easily eat up several hundred megabytes.
20.
by jckarter 16y ago
Crackers aren't your customers. Don't waste time/money on them.
21.
by jckarter 16y ago
A big difference between iOS and OS X is that desktop applications have more than 20 years of UI research and convention behind them, while touch interfaces have less than half (maybe even less than a quarter) that. There's thus a lot more
22.
by jckarter 16y ago
There's actually a dedicated Script menu available in the OS. Instead of deploying .apps and taking up space in the Dock, you can start up AppleScript Editor and check "Show Script menu in menu bar" in its Preferences. Then place your scrip
23.
by jckarter 16y ago
"copy"ing an immutable string just retains it, so there's little benefit to using a retain property for NSString properties, or for properties of the other NSMutableCopying type families. As a best practice you should always use copy proper
24.
by jckarter 16y ago
Aside from a tiny VM written in C++, nearly all of Factor ( http://factorcode.org/ ), including its parser, optimizing compiler, and code generator, is written in itself. The author of Clay ( http://tachyon.in/clay/ ) is working on a new ve
25.
by jckarter 16y ago
In my experience, bitbucket has been extremely unreliable and creaky compared to github. I see frequent random unscheduled outages where the ssh connection won't connect, ssh won't authenticate, or hg won't respond from the other side. The
26.
by jckarter 16y ago
I don't know about how that font looks on the iPad, but my first reaction looking at it on my laptop was that it looks extremely awkward with those thick character-wide serifs. I know this is a bikesheddy thing to bitch about, but I'd perso
27.
by jckarter 16y ago
That the author more or less admits to confirmation bias in the very first paragraph kind of colors their conclusions, regardless of whether Ping actually sucks or not.
28.
by jckarter 16y ago
When you're done with that you should also read through the examples John Benediktsson's been posting to his blog: http://re-factor.blogspot.com
29.
by jckarter 16y ago
The area around 24th Street BART isn't so bad, and trips downtown on BART are faster and cheaper than taking the 12, 14, or 27.
30.
by jckarter 16y ago
There were a number of talks in that vein. Rich Hickey's talk about his experimental "pod" feature in Clojure for safe scoped mutation, Joe Pamer's talk about making F# suitable as a first-class .NET language, and Jonathan Shapiro's talk ab

More ›