They are likely to remove this in the next C standard (or may have already), because a declaration with a static size is “compatible” with a declaration with no static size, and thus you can get unsoundness.
So your compiler should accept (though the semantics of static suggest this program would be wrong):
void foo(int a[static 3]);
void foo(int a[]);
According to the spec, this is fine, but when you come to define the function foo, should it respect the ‘static’ annotation? The spec doesn’t say, and doing static analysis of subsumption for the expressions after ‘static’ is much more complex to keep sound than C prefers in its specification.
Weird to see the cost excuse in there, since the cost of judging 100 teams on 100 maps for 3 minutes each on 1Ghz 1GB-RAm machines is 30,000 minutes = 500hrs < $50 on EC2 small machines
is it just me, or does anyone else think that though the design is prettier, it kinda makes other parts of the app look bad - for instance compare the commit style to the tree listings. it's not that one or the other look bad, it's just the dissimilarity is jarring.
I agree, the new commits use a different motif than the old ones and it definitely looks odd (especially on the code tree pages). Maybe this is the sign of a coming design refresh?
no need to restart the server. if you're using passenger, just `$ touch tmp/restart.txt` (in your rails app). That will restart just that app in passenger (and lots of other servers too)
this is not quite what it makes out to be. of course at one level you only need an ethernet cord, but at some level you need to supply power to the cord itself. That power requires a power cable + PoE box if done close to the monitor, or you can buy a rack PoE unit and do it further away, which will have a limit on how far away from the unit you can be.
PoE units are useful when having only one cable enter the housing for waterproofing issues. otherwise, why go to all the hassle?
In environments like hospitals, needing only one cable and one jack, I think this is a major advantage. Techs only need to unplug/plug one cable, there is less cable to get cluttered up, you only need half the amount of different types of cables in stock (no more different power and comms cables), ...
When renovating a section of a building, you only need to put in one new jack; that's half the cost saved, because you only need one guy running cable, not two (often different companies run electricity and network cables). So it's a major saving in installation costs.
If you wanted to be able to mount one monitor or several on a flexible arms so you can drag it around a room, it would be good to reduce cable clutter. This is a project I've been thinking for my space.
So your compiler should accept (though the semantics of static suggest this program would be wrong):
According to the spec, this is fine, but when you come to define the function foo, should it respect the ‘static’ annotation? The spec doesn’t say, and doing static analysis of subsumption for the expressions after ‘static’ is much more complex to keep sound than C prefers in its specification.