The Dink Network

Reply to Re: Before...

If you don't have an account, just leave the password field blank.
Username:
Password:
Subject:
Antispam: Enter Dink Smallwood's last name (surname) below.
Formatting: :) :( ;( :P ;) :D >( : :s :O evil cat blood
Bold font Italic font hyperlink Code tags
Message:
 
 
October 21st 2018, 11:54 AM
spike.gif
SlipDink
Peasant He/Him United States bloop rumble
2nd generation. No easy way to be free. 
@toof:

Okay, so I reformatted your binary_change(3, 1) function a bit and changed it to reference and change the global &status_bd. Then, I added some logging statements. I also set &counter to 32, because the point of this exercise is to be able to set, reset and check a particular bit within a single global DinkC integer. Next, I corrected all "*=" multiplication invocations to use "*". Finally, I changed the way you handled the &arg1 and &arg2 pseudo variables so that their use seems a bit safer to me. Since any Dink procedure can have a function within it that uses these pseudo variables, I think it best to copy the values to something local right away.

At the moment, we still lack a procedural way to test bits within &status_bd, (our binary data global using "binary_change()"). However, I set out to test how your code could set and reset bits within a global DinkC integer.

And, in my testing (using key-84.c, pressing the [T] for testing toof.c), I found that the procedure seemed to cause DinkC to hang when called. Perhaps this is because you don't change &crap within your loop anywhere?

Anyway, since you use linux, I've turned over the work I did on toof2.c and it's testing module, plus some other items of interest for you to help you continue to test and develop your idea. You can download a zip archive file of this stuff I made up at this URL. Let me know when you reach success. I'll leave that zip file up there for a few days. Good Luck!

I'm going to get back to working on my dmod "Before...", since it seems checkbit.c does all I need it to do.