@julszinha@ZanfaVive Eu comprei por uma questão de reconhecer o tanto que esse programa já me ajudou!
Com ou sem licença funciona igual, sem diferenças.
@mooseincrisis “i wasn’t???”
Dude, you literally crashed into the house like a wrecking ball and you’re still denying it??
Yeah we’re going drinking, but you’re buying the new door, you chaotic idiot 😂
Un profesor se volvió viral después de perder la paciencia en clase mientras explicaba la importancia de hacer cálculos precisos en construcción.
Visiblemente frustrado, recordó a sus alumnos que un error en ingeniería no es solo “suspender un ejercicio”, sino algo que puede terminar afectando la seguridad y la vida de otras personas.
Y probablemente por eso hablaba con tanta intensidad: hay profesiones donde un pequeño fallo en papel puede convertirse en un desastre real fuera del aula.
Last time you checked? Bold of you to assume void* points to a 'data type' and not an object.
C has objects, my friend. The standard literally defines an object as 'a region of data storage in the execution environment, the contents of which can represent values'. It's been that way since before most of us were born.
What C doesn't have are the shiny OOP objects with vtables, inheritance and marketing slides. Different meaning of the word, same spelling. Classic mix-up.
The problem isn’t converting an int value to a double value.
The problem is silently making an int* variable point to a double object through a void**.
After that, the program still thinks it has an int*, but it no longer points to an int. That’s not a VM-style value conversion; it’s breaking the type promise behind the pointer.