On some level, you can. On another level, you're setting yourself up for pain by doing that.
The level where you can use a char variable is when it's only your code. All things considered, if you want to create char variables where each bit is a different boolean variable, you could do that. Again, it's your code.
However, it's not that "we can use" integers. It's that the C standard library widely does use an integer as its returned status code. So, if you decide to manage your yes/no values in some other way, you need to yank the relevant bits out of that return value to fit it into your new scheme. So, that's potentially significant overhead. In fact, even if it's your own code, if you write if (booleanInChar) { /* ...*/ }, that char variable is going to get "promoted" to an int, because that's the type the conditional statement requires.
But really, bytes are cheap. And, if you're not writing embedded code, you're probably not going to notice any memory savings, because your program is going to be loaded into a multi-megabyte memory segment to run, anyway. So, you're better off keeping it simple.
I see, yes I agree that simple code is better than clever code. Sometimes other users will find it weird or might not undertsand if we don't use the standard convention.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
On some level, you can. On another level, you're setting yourself up for pain by doing that.
The level where you can use a
charvariable is when it's only your code. All things considered, if you want to createcharvariables where each bit is a different boolean variable, you could do that. Again, it's your code.However, it's not that "we can use" integers. It's that the C standard library widely does use an integer as its returned status code. So, if you decide to manage your yes/no values in some other way, you need to yank the relevant bits out of that return value to fit it into your new scheme. So, that's potentially significant overhead. In fact, even if it's your own code, if you write
if (booleanInChar) { /* ...*/ }, thatcharvariable is going to get "promoted" to anint, because that's the type the conditional statement requires.But really, bytes are cheap. And, if you're not writing embedded code, you're probably not going to notice any memory savings, because your program is going to be loaded into a multi-megabyte memory segment to run, anyway. So, you're better off keeping it simple.
I see, yes I agree that simple code is better than clever code. Sometimes other users will find it weird or might not undertsand if we don't use the standard convention.