/get great

technically lf = f, but a long time ago f means float lf means double

lf like long float, iirc.

lf like long float, iirc.

Long float not exists

Long float not exists

But it stands for that, like there's long long or long double afaik

It's stands there because d is for int

lf = double

It's stands there because d is for int

I found that quite weird when learning printf() in C ..

It's just it

There's only few modifiers

l ll h hh

With different letters we got different types

hhd = char

hd = short int

d for int, lf for double ... may have historical reasons, consider the time C was invented, but still ...

As I said f is double now

hhd = char

O.o

So what is float ?

You just can't send float

Also .. does a long long float make sense ?

Probably it will be long double but I'm not sure

lld is long long int 100%

In my printf I used "Lf" to long double

ll = L in GNU but it's not portable

Guys,,oop using c++ & HDL Which one is better?

Guys,,oop using c++ & HDL Which one is better?

HDL ?

Hardware description language

How to use python code in C ( visual studio )

Can anyone tell me a good stuff for this

I got this code from internet. I neee to convert it into kottlin. I had problem with some code that I dont understand. can anyone tell me what is thiss code suppose to do:

#ifndef NAN # define NAN (std::numeric_limits<double>::quiet_NaN()) #endif // check whether of not a floating point value is not a number inline int isNAN(const double v) { return(v != v); }

It defines a macro called NAN.

Every istance of NAN is replaced by that code snippet.

Here is what it does:

https://en.cppreference.com/w/cpp/types/numeric_limits/quiet_NaN

and the inline function below that is obvious.

As you see, NaN != NaN, but every other value v satisfies v == v

SO you can use that fact to check whether a number is NaN or not.

Why they return an int instead of a bool? No clue, maybe they have to be C-compatible.

thank you

No problem.

You misspelled the constructor

Anyone Solevbing This please tell me.\

You misspelled the constructor

line?

also, please use something like ideone.com

line 12

thx for advice

smile sign?

You're using pretty old C++ btw.

let me see

wow, g++ refuses to compile it for me.

he

let me renew your code a tad bit

turbo c++ maybe system error

You're dealing with very, very old c++, and my compiler won't even compile it.

I don't think you'll get much help with such old c++

I suggest you begin learning C++11

or even C++98

https://stackoverflow.com/questions/15680190/what-is-the-diff%C3%A9rence-between-include-iostream-h-and-include-iostream

/get findprojects

turbo c++ maybe system error

To make it more modern you should change the includes to #include <iostream> and #include <cstring> (although <string.h> would work too.)

and then use using namespace std;

That is, if your compiler even supports newer C++.

I suggest you begin learning C++11

sure.

Thank you.! I have read the pinned message now. 😊

and then use using namespace std;

no, please never do that https://stackoverflow.com/questions/1452721/why-is-using-namespace-std-considered-bad-practice

I use it carefully. Never had any trouble with it.

I never use it in headers though.

I use it carefully. Never had any trouble with it.

It's still bad practice and I would strongly advise against it

It's still bad practice and I would strongly advise against it

Well, I don't use many external libraries (yet), but I can see the potential problems, so yeah, I'll consider switiching

Thanks.

I only advised him to use using so he could run his code with minimal effort.

I only advised him to use using so he could run his code with minimal effort.

The thing is, people who started using it tend to keep on doing so. So I'd rather prevent people from doing so in the beginning. You probably wouldn't suggest to omit free calls in C because it's "less effort" not that important anyway :D - I just think the best way is to "learn it the right way from the beginning" because changing is hard

True, strangely most people I've seen teach it with using namespace std;

Bad education I guess.

True, strangely most people I've seen teach it with using namespace std;

because most lectures / teaching regarding C++ is bad

The reason is written right there....

have you read the rules? You don't want people to steal your work either

On a side note, I didn't notice there was a rule about turbo c++...ah well