-
im going insane
i got the signed32BitIntBigEndian function almost working
but for some reason the second byte is deciding to not show up when i flatten the lists of base2 represented bytes together
it works with all other bytes but this specific fucking byte decides it does not want to be put into a flattened list todayit isnt the value of the byte thats bad or anything, i double checked right before i attempted flattening it into the list and its completely fine
out of my desparation i changed the name of it to “byte1workpls” but it did not want to listen
i even tried taking the byte out to mcdonalds to calm it down but still it didnt listenthen i realized i forgot to capitalize a letter in one of the variable’s names and it fucking worked finally holy shit im so stupid i went through all of that how did i not realize




forgot to capitalize a letter in one of the variable’s names
wow python sounds like php
that is to say it sounds like hell
for some reason visual studio doesnt put red lines on some errors so you cant tell what the fuck is wrong with your code
worse, it didnt even highlight the error after the code was executed so i took an extremely long time just to narrow down the error to a single point
that’s gotta be a setting
it shouldn’t compile and run without yelling at you, unless it just ends up deploying an old build because the new one has syntax errors
It compiles and yells at me sometimes depending on what kinda error it is
The reason it wasnt yelling at me must be because visual studio’s syntax error detection isnt case sensitive
and its not an old build either because i got errors that were occurring *because* byte1 didnt want to appear in the flattened list
Ok the 32 bit signed int big endian converter is finally finished holy fuck that took days
but now that i know how it works, it wont be hard to implement the others
unless its a floating point