Demonen to Programmer [email protected]English • 1 year agoGotta watch them nil pointers!lemmy.mlimagemessage-square23fedilinkarrow-up1588arrow-down123
arrow-up1565arrow-down1imageGotta watch them nil pointers!lemmy.mlDemonen to Programmer [email protected]English • 1 year agomessage-square23fedilink
minus-square@[email protected]linkfedilink58•1 year agoYou gotta allocate your GFs statically or this just keeps happening.
minus-square@[email protected]linkfedilink20•1 year agoI tried to declare my GF global, but she became an astronaut, and I get linking errors
minus-square@[email protected]linkfedilink35•1 year agoMate, your GF is definitely global. I was able to access her just fine… read AND write.
minus-square@[email protected]linkfedilink11•1 year agoAs low as my opinion on some exes may be, I still don’t believe it’s appropriate to mark them as candidates for garbage collection.
minus-square@datelmd5sumlink10•1 year agoI’d add an imaginary boolean flag to the GF class and always have an initial GF where imaginary == True.
minus-squareN3Cr0link10•1 year agoThe struct and its CRUD functions seem to be all implemented. Problem is: The Create method is never be called.
You gotta allocate your GFs statically or this just keeps happening.
I tried to declare my GF global, but she became an astronaut, and I get linking errors
Mate, your GF is definitely global. I was able to access her just fine… read AND write.
Plus you won’t worry that you forget to free her
As low as my opinion on some exes may be, I still don’t believe it’s appropriate to mark them as candidates for garbage collection.
I’d add an imaginary boolean flag to the GF class and always have an initial GF where imaginary == True.
The struct and its CRUD functions seem to be all implemented. Problem is: The
Create
method is never be called.Might be a problem with the factory then.