Wow, that's a lot of code for something that's really simple.

Well, it's a collection of functions rather than just the one or two I really need. Technically, I could probably pare that down quite a bit if I ended up using it.

But truthfully, it's normal for a VB program to get wordy for certain things that are done very simply in C. By the same token, a lot of the windows-specific stuff that takes pages and pages of code to do in C is handled with essentially no code at all in VB because it's built-in. That's why I like VB, the basic bits of creating windows and handling input/output are already done for me, so I don't have to spend time on those things.

I suppose you've already run both it and the C version, to verify that they produce the exact same output for a given input, right?

Not yet. I'm not worried about it too much, I'll look into it more when I get down to brass tacks and actually do the work.