I don't see why you can't test and implement the threadsuck functions before I've got the UI done, right?

I'll have to test the change as a whole then anyway, so it doesn't gain me much time.

The difference is that the threadsuck functions are add-ons. They don't affect any existing functions. And if they work, we can go ahread and start archiving old threads. It'll work without the UI.

But I think that part of the threadsuck should be part of existing functions -- I'm not just reviewing to see it works, but to see how it fits.

So I need to test my hunch, and I'd rather have all the code before I do it.

True - it could definitely be rewritten that way. But did you see how my code works? The UI just generates a URL - suckedthread.php with some parameters following. I'm saying I could give you the code so that when you type in a specific URL you get the threadsuck you want.

I appreciate the offer, but I work better with the lump of code. Really.

Okeley Dokeley. You do this professionally, not me, so I do not doubt you. Just wanted to make sure you understood what I meant.

t Columbo Just one more question... t /Columbo

Before I try and decipher this CVS thing - Does it provide me with a test PHP environment? Do I have a unique subdomain that I play with? Or am I expected to set up PHP on my PC and test here? Or do I use the old test buffistas.org playground?

Jon, I'm still working that out. CVS does not provide a playground (unless I work out how to load it on buffistas.org). But it does provide a potential mechanism to stop people from stepping on each other's toes.

Ideally, it should be on the web server. I'm still looking into that.

So can I use test in the meantime if I promise not to change any existing code? Just add functions to the classes. I could even create my own class if you prefer.

Adding functions should be okay. Yeah, that's okay.