Java (She/they)
The older versions asked Error if she named her clone after coffee or the coding language. Error will not answer, she thinks it’s funnier to keep it a mystery.
Java doesn’t have as bad touch issues as Error, but they do have some verbal tics from their glitching. Apparently being a glitch can do odd things if you try to clone yourself. The tics get a lot worse when they’re stressed or flustered.
Error taught her how to use the strings, but also many fiber crafts. Xena tried to learn too but she didn’t have the patience for it, and Java teases her about it. It’s not that hard girl you just have the patience of an angry rhino.
Java can use a staff, should she need to get in closer, but she’s also very resourceful and will utilize just about anything in her environment to help her and the others in a fight.
Between her and Xena, she’s more likely to try to mediate in a conflict. She’s also more likely to resort to violence than Error. Mostly because Xena keeps picking fights she won’t commit to and Java has to save her fool ass. Error keeps trying to get her to do that Less but with no success.
Cross & Error
These two probably did about second best in terms of parenting. At least, Xena and Java still consider them family. They treated the clones more like little siblings than their kids, though. They were the ones who suggested the parenting support group.
They are some of the worst role models of everyone. ‘Do as I say not as I do’ but Cross in particular feels really hypocritical so she’s very lenient on it. Xena got her habit of stirring the shit from Cross. And Cross is like ‘listen either commit to the bit or stop goading people into trying to kick your ass’
Error tries to set a better example but she’s only slightly better.
They both try to make up for it by hanging out with the kids/clones and spend time with them. Xena and Java tend to call them their aunts.
Other Stuff:
I somehow forgot error's eyes were different colors and at first made Java's blue. i think i was thinking of Koroit. I realized what I was doing and immediately had flash backs to that one person who thought Byte had blue eyes
Java's alignment is chaotic neutral
error doesn't Big Stick as well as Java, but she does okay. Well enough that she can help Java with their training. She thinks it's a good idea to have an extra weapon skill just in case, anyways.
Xena and Java have matching tattoos on their lower shins! It was Xena’s first one and she was scared to go alone and asked Java to come with her.
Java has a pretty long scar over their chest from a sparring accident with Xena. It’s an old scar, and the initial wound wasn’t as bad as it looked, but Xena still feels horrible about it.
Also Java’s hair is actually really long and in a big bushy ponytail
4 notes
·
View notes
guys...I made like a bunch of icons but I cannot find a single theme for icons that works...HELP I JUST WANNA SHARE SOME ICONS
5 notes
·
View notes
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.
0 notes
From Confusion to Clarity: Resolving Java Error Code 1603 Step-by-Step
Understanding Java Error Code 1603:
Java Error Code 1603 typically occurs during the installation or update of Java Runtime Environment (JRE) on Windows systems. It indicates that the installation process has encountered an unexpected error and has failed to complete successfully. The exact cause of this error can vary, ranging from issues with system permissions to conflicts with existing…
View On WordPress
0 notes
Dbeaver Java heap space error during SQL Query
How to fix Dbeaver java heap space error while executing SQL Query
While executing the SQL Query in Dbeaver, I am getting java heap space error. It occurred due to large tables not able to fetched in Dbeaver heap space.
java.lang.OutOfMemoryError: Java heap space
Solution:
From open the dbeaver shortcut you can add the following line in dbeaver shortcut key:
-vmargs -Xmx*m * -- 2048 or…
View On WordPress
0 notes
Am I the only one who thinks Python should throw the error "this isn't fucking java, dumbass" if you do || instead of or or .length instead of len()?
1 note
·
View note
Sunfall Master post
There's individual posts but there's also this big doc with everything in it, and that may be easier if you want to read everything at once. but if you want individual bits here's the posts!
Glaze and Tempera (+ Ink)
Wren (+ Finch)
Orion
Corvus
Xena
Java (+ Cross & Error)
Aster (+ Blue)
✨Plot✨
Endings 1-3
The Maelstrom and the beasts
Random other stuff
4 notes
·
View notes
Reading the Tea Leaves! Understanding Java Stack Traces for Exception Troubleshooting
Understanding a Java stack trace can be important when troubleshooting errors in a Java application. Stack traces can tell us about the exception thrown as well as the method calls that resulted in that exception. #java #exceptionHandling #stackTrace
Table of Contents
Table of ContentsIntroductionCausing an ExceptionReading the Stack TraceReading from Bottom-UpReading A Single Line – Outer ClassReading a Single Line – Inner ClassReading the Exception ThrownCatching and Throwing New Exceptions – The Caused By ClauseSummary
Introduction
Java stack traces in the logs or console output from a Java application can help us understand where…
View On WordPress
0 notes
Discover the solution to Java Error Code 1603 with our comprehensive guide. Resolve installation problems and optimize Java performance effortlessly for seamless functionality.
0 notes