what hex strings do you use for debugging?
category: residue [glöplog]
No, that would be not so clear,. just geeky :P
I DON'T KNOW WHAT DEBUGGING IS AND WHAT THESE HEX CODES HAVE TO DO WITH DEBUGGING, OK THNXBYE LOL GTP
I DON'T KNOW WHAT DEBUGGING IS AND WHAT THESE HEX CODES HAVE TO DO WITH DEBUGGING, OK THNXBYE LOL GTP
0x%08x, works nice for any type of value on a 32 bits machine :).
I'm with Preacher on this one. Never used weird hex markers for debugging
pfft, atari coders. :D:D:D
pfft, coders. :D:D:D
pfft, . :D :D :D
:D :D :D
@xenon, thank you. $c0cac01a is awesome.
$c0cac01a is my invention. I want my credits :(
;)
;)
$deadbeef
$cafebabe
$cafebabe
cout<<"before"<<endl;
...
cout<<"after"<<endl;
...
cout<<"after"<<endl;
how is "before" or "after" a hex string? :D
bonzaj: I'll drink to that :)
0xDECAFBAD
0xDEADBABE
$5ad0babe
$B00B1E5
$CA7F00D
$A55FACE
$AC1DBEEF
$DEADCA7
..
etc.
$CA7F00D
$A55FACE
$AC1DBEEF
$DEADCA7
..
etc.
0xB10D10AD
0xdeadbeef and 0x900df00d :D
0xC0DEBABE
strings? hhmm although the amount of screen time is important... on interrupts =)
start routinue-1
inc $d020 / border colour
....
dec $d020
start routinue-2
dec $d020
...
$inc $d020
end routinue 2
etc
start routinue-1
inc $d020 / border colour
....
dec $d020
start routinue-2
dec $d020
...
$inc $d020
end routinue 2
etc
hehe oldc64scener, you're missing the point.. the Shadow Government has long since replaced our C64s by P4 systems in our collectively induced sleeps ((c) 2003 by Shifter :)).
..but..
move.w #$f00, $dff180
; do stuff
move.w #$000, $dff180
used to do that trick also very well ;)
..but..
move.w #$f00, $dff180
; do stuff
move.w #$000, $dff180
used to do that trick also very well ;)
0xADD1C7ED 0x101CA722
64bit systems needs longer hex strings?