def resolve_property(p) return send(p) if respond_to?(p) return parent.resolve_property(p) unless parent.nil? return class_for_property(p).new end
/* 400 lines of resolve_property_ref<SvgProperty>::whatever omitted. */`
I promised myself I’d never write another line of autotools noise after an m4 explosion in the code mines a few years back.
My first thought was to see how usable Rake was in a non-Rails context. Turns out, it’s awesome for building C++ even outside of the pretty example rules in the docs.
I’ve noticed that, after a three year break in Ruby-land, my first big C++ project since uses a hell of a lot more dynamic_casts, and I’ve found a use a few real uses for typeid().
Same vertices triangulated by poly2tri. (Note, in both of these photos, the visual paths don’t match the vertices submitted to the triangulators because they’ve been simplified before tessellating.)