Well, the problem here is that I seem to have gone quite overboard in my implementation. It meets my needs, sure, because I'm trying to maximise my Python...
This is fairly minor, but I like clean-looking implementations of stuff as long as it doesn't forgo (much) speed or functionality. Also, as I said in another...
This seems pretty useful to me, and I hope it will be to someone else too. I am extending the hooks functionality to include Python functions. The way it works...
For no reason whatsoever, other than it seemed easier intrinsically, all of my new code where I once would have used a bitvector I have started using the...
It's good to know others are out there trying to divorce from C as much as possible (although C certainly has it uses!), and it's good to know that my efforts...
... The difference isn't huge, so if you're more comfortable with one rather than another, use the one. I personally like the BITVECTOR structure because it...
Oh dear, after fiddling with hooks.c for a while I became quite dismayed at the un-safeness of that code. If you accidentally call a hook with too few ...
... dismayed at ... easier to ... I think you are nuts... hooks are a very deliberate thing to add- you don't usually add one copy and paste style like you...
... Stand back, I'm feeling ornery! This is exactly what I'm talking about. As long as you feel like you're an invincible coder, then go ahead and do what you...
I definitely am not interested in polluting anyone else's project. I am content to make my own mess. However, over the night I have thought of a more...
Yeah, I agree hooks could use some work. There are problems with the current version for reasons that were pointed out by Brian. Mainly its finicky and...
... The thing is, the more I thought about it the more I came to agree with this position too. I think a stern warning will probably suffice, rather than ...
In light of the recent discussions on bitvectors I want to show both Geoff and Brian (and anyone else with an opinion) a problem I have run into that has...
These things can be hard to diagnose. Could you post the entirety of the file in question? I'd like to see the basic struct and how it is stored as well. -B...
... yeh figured as much- I can't even venture a guess as to whats going on and thats pretty rare for me- I'm hoping I just missed something silly. //---- ...
Problem #1: In deleteWeaponData() you should not be calling free(data->type)and free(data->range). The deleteBitVector() functions do that work for you, and ...
... free(data->type)and ... you, and ... to me ... printf-alikes ... on the ... implemented ... does is ... Thank you! It seems that problem just needed a...
... I wouldn't have thought that was the problem, but it does make a kind of sense in pointer logic, especially since you said the behavior was erratic. It...
... erratic. ... bytes ... Actually that was part of the problem but not the whole thing- the crashing was due to doublefreeing memory, but the bit-crossovers...
... This was intentional. I use static buffers lots (perhaps too much) when returning informative text. The motivation is to ease the garbage collection...
... That is actually a perfectly good way to handle the issue. I would guess the reason you got a warning about local values is that char bits[MAX_BUFFER] is ...
Oh, and my I add that after scrubbing quite hard through the bitvector.ccode I'm impressed with it. I wish it had been thought of 15 years ago when I first...
Caution: in order to get the hooks that are added in inform.c to cooperate, you need to switch the order of their arguments to match what hooks.c wants. -B...
Gah, I keep thinking of things I should have posted in the first place: The hooks.c I posted also addresses a bug I found that would probably never be ...
... looks perfectly legit to me. I personally would do the strduping *outside* the function -- don't have to do garbage collection as often that way. But...
Wouldn't you know, as I write, Geoff posts a response. Thanks for the information. I think providing a buffer to be filled would be much better too. (I...
... These warnings are probably nothing to worry about. See here: http://mail.python.org/pipermail/python-bugs-list/2001-November/008453.html The MUD crashes...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
