Comments on: vhdTools v0.3.1 Released

By: Dav

Dav — Sat, 24 Feb 2007 21:10:45 +0000

Congratulations for this program, I was looking for something like this.
Now one question: Are you evaluating wrong parameters given by the user from the console? If not this probably a bug: when i typped “vhdConvert -help” the aplication did terminate in an unusual way… So well, i’ll give you the job of making a default routine for handling unexpected parameters .
Well for now i do not have anything else to say you, so again thanks for your hard work.

By: John

John — Wed, 10 Jan 2007 18:50:13 +0000

Thanks for the heads up Seppo – it’s all fixed now.

By: Seppo

Seppo — Wed, 10 Jan 2007 18:45:27 +0000

Not related to this blog entry, but I entered your site via the amd64 page (www.kelley.ca/amd64/), where you have putty x64 and that some other software I’ve never heard of. Anyways, the link for FileDisk points to a dubious site… Needs cleanup.

By: John

John — Tue, 12 Dec 2006 23:05:26 +0000

Yeah I’m now using uint64_t where I need 64bit unsigned integers. I usually use this style of typing but bowed to size_t to get rid of some warnings with the mistaken assumption that it was 64-bit – who knows where I got that thought from.

By: Bill Phu

Bill Phu — Tue, 12 Dec 2006 22:37:40 +0000

haha. you’re right, size_t isn’t 64-bit – but that depends on the compiler! It’s unsigned long, by default. I think that most compilers interpret ‘long’ to be 32-bit, but that’s not guaranteed. I am surprised you’re not abstracting the data types even more so that there’s never any ambiguity – in case you actually want to start porting your code