876 karma · joined March 12, 2012
It would be something I would pay for to not have to host myself, but iff there's a clear migration path, i.e. it's open-source.
I couldn't find any email on your profile, do you mind sharing it?
MinGW is alright... until you try targeting x86_64.
To expand upon my 4am ramblings:
There's two ways your code is going to fail, (a) Your Lua is going to die in a pcall (or friends); or (b) Your C/C++ (or similar) code has its front fall off.
In the former case, you just wrap with an xpcall and append your Lua callstack to your C++ callstack. Nothing fancy. You can of course go further, using lua_Debug to get the value of upvals and all that jazz.
However, in the latter case you have no guarantee that your application is in a sane state; you have no (solid) assumption that you can go the lua_Debug route, say from a segfault handler. You'll have to walk the callstack, and when you hit lua_whatever, prod internal state.
Both methods are really helpful. Say you're writing a game engine, knowing how to reproduce a catastrophic failure with a small Lua snippet, closes the feedback loop and make debugging a hell of a lot easier.
There's definitely a product and SaaS around this (much more expanded), with a Gitlab or Sentry business model.
I had a similar idea kicking around for a while (for a different market) because you end up managing disparate targets (including multiple digital distributors for one platform) each with their own slightly broken of doing things. It. Sucks. Hard.
Now that I'm only tangentially involved with the market my previous experience (of intense pain) is reduced, but has been replaced with iOS and Android.
I'm looking forward to using BuddyBuild for the next app I work on.
How are you handling the Apple side of things? Last I checked, you had to store full credentials to someone's Apple ID. Looks like you are doing exactly that.
My big concern is that you're siloing my credentials so they won't get leaked. How are you doing that?
:'(
* Modified Stillman's
* Floss properly; "scrape" gently with the floss.
* Water rinse after acidic drinks (like red wine). Brush a half hour after that.
Have you seen the new email campaign they're running?
I meant regarding the automatic application of rules based on profiling.
Would still love to have a great open-source tool for this.
drawline
You can always define an implicit constructor: Point::Point(const Library::Point &p)
Of course, you're now hiding a ticking time-bomb from a the next maintainer of that code.If you absolutely want the latter case, overloading is your friend:
drawline(int x1, int y1, int x2, int y2);
drawline(Point p1, Point p2) {
drawline(p1.x, p1.y, p2.x, p2.y);
}
This, in my opinion, is the most conducive to refactoring (and modularizing code).As an aside, you really should be doing:
drawline => drawlines
"Where's the one, there's many."What are (were?) those those few decisions? Are they generalizable?