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.
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.
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?
doesn't heart kinda solve the cyclic "who restarts who thing". I think heart (if enabled) sits there until the erlang process exits, restarts the erlang vm, which in turn also brings up an instance of heart. yeah, complicated and not perfect, but it works.
what's even more instesting, is that cirfu.net also has this notice up, which is very very strange. Surely they wouldn't take their own site down for gambling offences
Sometimes yes, sometimes no. it depends on the alcohol, how much and other external factors like my levels of motivation or tiredness.
It would be clichéd to say that some of my best work was done drunk, but i'd also like to point out that some of my worst has been done when drunk too.
This i found very enlightening to read. I wonder how many accounting apps actually store their data as he describes in this article, to aid their calculations
Thinking over this comment, would it be weird to set up an office where the managers all are in an open-plan setup, and the developers all have their own private offices? I think it would be interesting to see what the outcome was
(Disclaimer: i'm a developer who works in an open-plan office and hates it)
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.