3,794 karma · joined April 29, 2015
I'm much more excited about able to be able to go fishing at 4am in the summer, NOW we're talking ;-)
I'm waiting for 8am, then feed + walk the dogs, then I'll go back to bed for 1h or a bit more (tops), and it'll still be early when I wake up again. Most of my colleagues will show up around 10 with bleary eyes while I've done most of the stuff I wanted to do already!
... So that gives me a lot of time for a good walk, or tinkering etc in the afternoon.
I used to be a 'night owl' really, going to bed at 2am; but I realized I was never really terribly efficient until about lunchtime the following day, while I was also wasting my time in the evening for no real reason. AND wasting the short winter day at my desk.
Nowadays, well, I got the whole day to myself!
It is not because it is implemented like that in gcc (requiring a space, possibly so they didnt have to modify the lexer) that it ought to be specced like that.
For example the [[keywords]] that had was rolled in because it was already out there -- imagine proposing that out of the blue and see a people self-propel into orbit...
On other hand the Case A ... B: syntax that has been out there for 30+ years, well there's a proposal for it but it won't be THAT because well it hasn't been invented here really, we'll make up a different syntax for it instead...
I also don't understand why the "C standard" hasn't evolved further -- there was a discussion lately about the committee being out of touch. Some of these extensions makes life so much easier. Instead we get stupid stuff nobody need, or have been in a header for 200 years (ie, <pthread.h>, whoohoo, I'm delighted this standard header is now a... standard!)
For nested/sub function, it makes so much sense it's not even funny. Having micro-callbacks right there before the call to qsort() (or any other) is SO much better than having to farm out a context, yet-another-static-function etc...
This allows me to switch context/projects etc and have a valuable history, instead of a whole mashup of all kind of other activities crammed into a single file in $HOME...
Perhaps I could use a single SQLITE database with a fancy invocation to do the same? Ie limit the history to the current subtree commands have been invoked in?
Early in my career I erased several megabytes of shared memory on a mini computer, ie DOZENS of users worth of memory just because I was being 'clever' and cut+pasted bits of an expression the wrong way.
Since then, as a rule, sod the priorities, parenthesis it is...
I mostly did my emu due to the rather poor quality I found for linux emulators I've seen, the 'goto' one is linapple, but the codebase is rather crusty.. I wanted a cleaner base to hack on, without the baggage -- more in the style of my own AVR emulator [1].
I've got a very big patchset to push 'soon' with a new UI library (that will be a topic of its own!) and a bunch of new features and improvements...
[0]: https://github.com/buserror/mii_emu [1]: https://github.com/buserror/simavr
All that time, I really wondered what the flip they are on about. Adding extensions that really, I really raise eyebrows at while ignoring complete elephants in the room, like the above feature.
Last year they were pontificating about something something adding some sort of (complicated) syntax to support destructor functions and were wondering about prior implementations, and I had to point to them the support of destructor function had been there as an extension of gcc for countless years.
It's like they aren't actually using the language, just speccing it. Kinda like linux maintainers who are more like some sort of priesthood and gatekeepers than actual users of the system.
This is my second X5 G05, and this one is definitely of lower quality than the first. Removed bits here/there, replaced aluminium parts inside with coated plastic, replaced leather with synthetic-like thing and plenty of other cost cutting markers.
Don't tell me 'oh don't buy another one' as demonstrated by this article (and others), they all do it to pretty much the same degree, all you can hope is not to run out of warranty before something mind bogglingly expensive breaks.
Until I told them they were voting for literally preventing their daughter and me the life we've been living. Their grandkids, everything wouldn't have been possible without her being allowed to work there, and me being able to work here...
They hadn't realized that of course, because you know, as far as immigration goes, they were just fine with the lovely polish lady at the shop, and me of course, what they didn't want is 'them' (not entirely clear who that is).
The goal was never in doubt really, and it was never the 'good of the country', or its people.
With zero notifications, refunds or anything of course.
This is a scandal that has been going on for years -- they still sell you HD versions of the movies and shows knowing full well you can't possibly play them in anything but 480p
watch : while true; do \ clear; $(MAKE) -j all tests; \ inotifywait -qre close_write src tests; \ done
More complicated project? Might shoot out to 2 pages. It'll still work in 20 years time too, the tools won't change under you (I'm looking at you, pretty much all other build systems)
Still, great editor, super fast, and the fact you can easily open a file in your currently open session (and that it supports the <filename>:<line number> convention) makes it super for checking out error message/warnings etc when compiling code that you don't have in an IDE...
I wrote and shipped C++ as a job for many years -millions of lines I'm sure- and I've 'reverted' to plain C around 2007 or so, and I couldn't be happier.
typedef union c2_rect_t {
struct {
c2_pt_t tl, br;
};
c2_coord_t v[4];
struct {
c2_coord_t l,t,r,b;
};
} c2_rect_t;