Is this normal?

[Claire_CJS]

I’m just surprised at "-0". If anything, if you round to 0.0, and you’re negative, it should just be 0, right? Or at the very least "-0" might make more sense?

I’m just curious for the working-as-designed story here, or if it’s really a bug. Sorry!!!

 

[vefatica]

"0-" ... that's gotta be a bug.

v:\> echo %@formatn[02.0,-0.01]
0-

 

[Claire_CJS]

Yea. I noticed a free-space-gained report was saying i’d gained "-" megs of free space. Eventually I realized it was "0 megs", but actually a negative number rounded to 0.

 

[vefatica]

PRINTF does it too.

 

[vefatica]

And FWIW, TakeCmd.dll's Printf does it and C's wprintf does not.

These

    Printf(L"%02.0f\r\n", -0.01);
    wprintf(L"%02.0f\r\n", -0.01);

produce

0-
-0

 

[rconn]

It's an RTL peculiarity; not sure it rises to the "bug" level. But I've added a check for that case to strip the '-'.

 

[Claire_CJS]

Maybe the development world needs a word for something that’s not quite a bug, like "varmint".

 

[rconn]

In this instance, you're passing a value and then telling the function to ignore the value. You could simplify your code to just say "echo 0".

Not quite a PIBCAK error, but not quite a serious bug either.

 

[Claire_CJS]

The example here was the simplified example

In my actual case, it’s a calculated value of how much harddrive space was freed via free-up-harddrive-space.bat

It measures before/after for terabytes, gigabytes, and megabytes.

None of the numbers were actually 0. I just don’t care about megabytes or gigabytes past the integer level, only terabites do i start to care about the 1ˢᵗ decimal place.

So I was getting reports that i’d freed up, for example, 150 megs, but "-" gigs (rounded from 0.150) and "-" terabytes (rounded from 0.000150 or something like that).