#heap
Explore tagged Tumblr posts
Visit Tumblr Blog
Explore Tumblr blogs with no restrictions, modern design and the best experience.
Last Seen Tumblr Blogs
Fun Fact
Tumblr was created by web developers David Karp and Marco Arment.
Photo
Romans 12:20 (NKJV) - Therefore
“If your enemy is hungry, feed him; If he is thirsty, give him a drink; For in so doing you will heap coals of fire on his head.”
181 notes
·
View notes
Text
( ၴႅၴImogen Heap ( ၴႅၴ
#shes so beautiful#girlblogger#girlblogging#tumblr girls#girlblog#imogen#heap#imogen heap#pop#pop music#electropop#music#flowers
22 notes
·
View notes
Text
Currently reading:
SWAMP THING #47 (1986)
Script: Alan Moore
Art: Stan Woch, Ron Randall & Tatjana Wood
John Constantine introduces the Swamp Thing to the Parliament of Trees. As his mind enters the Green, you can see sneaky cameo appearances by Marvel’s Man-Thing and Airboy’s The Heap!
8 notes
·
View notes
Text
Thinking about making a post, or a series about stuff that I wish I was taught about C in school.
I might just do it regardless of interest, it would be nice to just get my thoughts written down somewhere.
Also feel free to give me some topic suggestions, like bitwise operations, memory management, object oriented-ness, fun with undefined behaviors, advanced(?) topics, etc...
#computer science#c99#C#linuxposting#deepdive#gcc#GDB#valgrind#coredump#stackdump#heap#stack#stack collision
5 notes
·
View notes
Text
Top of the heap | Limited edition fine art print from an original drawing. My sketches start life as hand-drawn graphite images made on cartridge paper. I often work on these with charcoal, oil pastel or Caran d'Ache to create the look I'm after. The artwork is then scanned and finessed digitally ready for fine art printing. This process often referred to as Giclée printing uses the highest standard of printing methods to give gallery quality results that maintain all the details of the original sketch. The graphite pencils I use are Faber-Castel, the oil pastels are Sennelier and the china-graph is Caran d’Ache. The inks are pigment based archive quality (100years+). The heavyweight specialist papers I use are of the best professional quality having a wonderful surface designed specifically for fine art drawings and illustrations. Very limited editions with only ten per size printed. All artwork is signed and includes a certificate of authenticity. The A5 are 5.8" x 8.25" (14.8cm x 21cm) The A4 are 8.25" x 11.7" (21cm x 29.8cm) The A3 are 11.7" x 16.5" (29.8 cm x 42cm) The A2 are 16.5" x 23.4" (42 cm x 59.4cm) Originals are A3 11.7" x 16.5" (29.8 cm x 42cm) Frames not included in price. Free shipping on artwork to all destinations. https://www.seanbriggs.co.uk/product/top-of-the-heap/?feed_id=3328&_unique_id=65fe85a3d20b1
4 notes
·
View notes
Video
flickr
jimmy heap 1955 by Al Q
0 notes
Text
You’re awful but tenacious
221 notes
·
View notes
Text
Winter in Illinois, especially in areas like Chicago and St. Charles, brings biting cold and increased heating expenses. The Home Energy Assistance Program (HEAP) offers critical financial support of up to $900 to help eligible households manage their heating costs. Here’s a guide to understanding this program, how to apply, and how Eco Temp HVAC can help you stay warm this winter.
0 notes
Text
0 notes
Text
26 Strong Alternatives to Google Analytics to Explore
Google Analytics is a popular tool. It helps track and analyze how customers behave online. It gives a lot of data about website and app traffic. Some businesses choose other tools instead of Google Analytics. This is because Google Analytics is better for companies selling to consumers (B2C). It may not fit the needs of businesses selling to other businesses (B2B). Luckily, there are many…
#Adobe Analytics#Ahrefs#Chartbeat#Clicky#Contentsquare#Fathom#FoxMetrics#Google Analytics#Google Analytics Alternatives#GoSquared#Heap#Hotjar#HubSpot#Kissmetrics#Leadfeeder by Dealfront#Matomo#Mention#Mixpanel#Optimizely#Piwik PRO Analytics Suite#Plausible#PPAS#SE Ranking#Semrush#Serpstat#Simple Analytics#Smartlook#Statcounter#Woopra
1 note
·
View note
Text
Dear Diary,
Today I encountered a mysterious deer lady who follows me around and calls herself the Shadoe. I also met Tessa, the only other deer in all of Heap. I suspect the two may be related.
#call me crazy but i think maybe this broad is up to something#funny business#smells fishy#up to no good see#don't mind me and my noir detective dreams#Lemuria#w101#Heap#my wizposts
0 notes
Text
"I thought maybe I could say something. Tell you what a rare and wonderful thing you are to find amidst all this... darkness."
#dragon age#alistair theirin#alistair#this was one of my first prints ever#with reason of course look at this little awkward heap of a man#digital art#art#print
5K notes
·
View notes
Text
Mystery solved
I believe I've solved the mysterious/scary bug I blogged about yesterday.
Last week I tried to eliminate some repeated code by turning it into "inline" methods that return references to objects. I changed code like this (simplified for clarity):
float getForceX(jlong bodyVa) { Body *pBody = reinterpret_cast<Body *> (bodyVa); const Vec3& result = pBody->GetForce(); return vec3.GetX(); } float getForceY(jlong bodyVa) { Body *pBody = reinterpret_cast<Body *> (bodyVa); const Vec3& result = pBody->GetForce(); return vec3.GetY(); } float getForceZ(jlong bodyVa) { Body *pBody = reinterpret_cast<Body *> (bodyVa); const Vec3& result = pBody->GetForce(); return vec3.GetZ(); }
into code like this (also simplified):
inline const Vec3& getF(jlong bodyVa) { Body *pBody = reinterpret_cast<Body *> (bodyVa); const Vec3& result = pBody->GetForce(); return result; }
float getForceX(jlong bodyVa) { const Vec3& vec3 = getF(bodyVa); return vec3.GetX(); } float getForceY(jlong bodyVa) { const Vec3& vec3 = getF(bodyVa); return vec3.GetY(); } float getForceZ(jlong bodyVa) { const Vec3& vec3 = getF(bodyVa); return vec3.GetZ(); }
In the back of my mind, I assumed Body::GetForce() was returning a reference to a Vec3, so it made sense for getF() to do likewise. But in fact, Body::getForce() returns a copy of a Vec3. Because of this, the compiler allocated stack space for a copy, then returned a reference to that copy. But the copy is only live during execution of getF(). Once the function returns, the copy can (and does) get trashed.
The correct solution, I think, is for getF() to likewise return a copy:
inline static const Vec3 getF(jlong bodyVa) { Body *pBody = reinterpret_cast<Body *> (bodyVa); const Vec3 result = pBody->GetForce(); return result; }
Two little ampersands can make a big difference!
This bug illustrates a couple subtle differences between C++ and Java. In Java, objects are passed and returned by reference, never by copy, so the latter possibility didn't occur to me. Furthermore, Java objects live on a heap, not a stack; as long as a reference lives, objects don't get trashed. Upshot: I'm out of practice thinking about this sort of issue.
Part of what made the bug hard to find was that it only caused failures when optimization was turned on. For various reasons, most of my testing is done with optimization turned off.
I'm not 100% sure how compiler optimization surfaced this bug, but I have some ideas. I could disassemble the compiled code, but I'm not curious enough to do that today.
The interesting question is: how does one solve a bug like this? I wish I'd used some clever tools or techniques, which I could now recommend. In fact, I solved it by trial and error, and my only relevant advice is to be persistent.
#software development#software bugs#war stories#c++#java#troubleshooting#debugging#vectors#heap#coding#persistence#trial and error#ampersand#compiler#reference#advice
0 notes
