How to add 0 as 08 but not if 25 as 025

Question

3.00/5 (2 votes)

See more:

Hi Guys,

I have a quick question once again and that is how to add 0 infront of the integar even if the user don't enter it e.g. user enters 3,4,5,6 and it prints as 03,04,05,06 but not when user enters 10,11,12,13 as 010,011,012,013 etc.

Much appreciate your help and suggestions in advance.

Cheers

Posted 10-Jul-12 3:37am

Salman Ali Hero

Add a Solution

Comments

Aescleal 11-Jul-12 1:54am

Have a 5 to balance out whoever gave you a 1 - this seems like a legit enquiry to me as formatted I/O is a bit of a bugger to get your head around in C or C++.

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

nv3 · Accepted Answer · 2012-07-10T03:49:00

Solution 1

printf ("%02d", 5);
printf ("%02d", 13);

Posted 10-Jul-12 3:49am

nv3

Comments

Salman Ali Hero 10-Jul-12 10:16am

cheers mate, working all good

nv3 10-Jul-12 10:29am

You're welcome!

Richard MacCutchan · Accepted Answer · 2012-07-10T05:59:00

Solution 3

A good idea before asking basic questions like this is to check ther documentation[^] first. That has the double benefit of getting the answer more quickly, and also learning other facts and features that you may need in the future.

Posted 10-Jul-12 5:59am

Richard MacCutchan

Comments

Salman Ali Hero 12-Jul-12 0:04am

Thanks Richard,

For your kind suggestion.

Cheers

Aescleal · Accepted Answer · 2012-07-10T04:18:00

Solution 2

nv3's answer is the way to go if you're using C.

C++

std::cout << std::setw( 2 ) << std::setfill( '0' ) <<  5 << std::endl;
std::cout << std::setw( 2 ) << std::setfill( '0' ) << 25 << std::endl;

is the C++ way. If you're using C++ then don't use printf, it's not the safest way of doing output in the world.

Posted 10-Jul-12 4:18am

Aescleal

Comments

Salman Ali Hero 10-Jul-12 10:25am

Thanks for your answer but actually I am writing a program in C

Aescleal 10-Jul-12 10:29am

Your question had C and C++ tags, might be an idea in future to check them before posting. I'll leave the solution here though 'cause it provides a contrast between the C and ++ style and it might help someone else in the future.

Salman Ali Hero 12-Jul-12 0:06am

yeah thanks for tht, I was thinking about getting familier with C++ aswell but never tried :-0

pasztorpisti 10-Jul-12 10:50am

+5 because this is also a good answher, however I rarely seen c++ streams even in production code. Lot of ppl don't like this kind of abuse of operator overloading. :D

Aescleal 10-Jul-12 12:36pm

Just to provide a bit of balance (thanks for the 5 BTW)...

- I've personally used streams almost exclusively for I/O since 1999
- Every project I've worked on since 2004 has used them extensively (even in code to control hard disks, games, security, futures trading)
- They work on just about any hosted environment (including modern games consoles) and a fair number of embedded ones
- They're a superb abstraction when you have to substitute I/O facilities when unit testing
- They're incredibly customisable; add boost and it becomes trivial
- Very little chance of making a type snafu

About the only downside is that their syntax is a bit cumbersome. And as for operator overloading these days I tend to think the abuse is using the insertion and extraction operators for bit shifting.

Maximilien 10-Jul-12 13:27pm

+1.

Nice.

pasztorpisti 10-Jul-12 17:51pm

LOL :D

nv3 10-Jul-12 16:25pm

I am always impressed by people using the stream stuff; they are probably the right way to go. I just got never the hang on them myself -- too much typing for a little bit of output. Nevertheless my 5.

pasztorpisti 10-Jul-12 17:50pm

The first 3 reasonings aren't strong enough.

- They're a superb abstraction when you have to substitute I/O facilities when unit testing
You can write an IOStream interface in no time, I usually copy the java IOStream interface solutions. They work perfectly, you see the whole interface in about 1 page code without weird syntax. Pure clean feeling. Easy customization for my needs. Don't understand why iostreams bloat is better than this. Since its an interface you can replace the implementation at runtime (for test cases). Virtual function calls are not a problem if you use buffering (for small writes), not to mention that the time a virtual call takes is usually only a fraction of the IO operation.

- Very little chance of making a type snafu
I usually use binary streams (the IOStream interface/interfaces). If I want to handle other types I make additional layers on top of binary. Type safety can be provided anywhere with good design (except sometimes when you want some magic or optimization but you can encapsulate/hide the messy part).

I don't want to discourage anyone wanting to use std libraries. Just sharing my opinion about them: Their source is a mess and bloated - makes it harder to understand and debug the code. The same is true for some boost libraries (despite the fact that they contain some really good pieces of code and sometimes nice ideas/implementation). Lots of lots of template code that make your compile time much more. (sometimes its an issue - continuous integration systems) For example in case of std containers you can get away with much less template code, much human readable and debug friendly code that sometimes can perform better.

EDIT: I don't like reinventing the wheel either. For small projects its OK to go with std. For project with long development cycle (many years or decades) its a good idea to avoid std solutions if you optimize and it pays off well in many ways I described above. A solution isn't the best solution just because its a standard. In fact, sometimes neither of the available solutions is good, you just have to use one of them because you don't have the time/knowledge/mood to make a better one. XD

Sergey Alexandrovich Kryukov 10-Jul-12 15:55pm

I can just feel how the inventors of these operators blow their chicks out of pride. It even looks an elegant idea -- before you look at the usage. I hear your negative assessment on this matter from you for the second time, and I kind of agree. Not a very important stuff though...
--SA

pasztorpisti 10-Jul-12 18:00pm

Yea, maybe I should stop this before an std religious sect attacks me... :D

Sergey Alexandrovich Kryukov 11-Jul-12 14:46pm

Well maybe. Or maybe not. Russians say: "To be afraid of wolves would mean not going to the forest"... :-)
--SA

pasztorpisti 11-Jul-12 16:15pm

LOL, I like this kinda wisdom! :D:D:D