11 replies to this topic

[delphiproblematic]

Does anybody know anyway ?

[WingedPanther]

99% of C code is valid C++ code.

[delphiproblematic]

cout , cin different with printf scanf :(

[veda87]

delphiproblematic said:

cout , cin different with printf scanf :(

Even printf and scanf will work on C++... if you haven't know that, then do try them and check it...

[WingedPanther]

delphiproblematic said:

cout , cin different with printf scanf :(

printf and scanf are valid C++ functions. This is an issue of standard style, rather than valid code.

[Ancient Dragon]

The largest problem converting c to c++ is typecasting void* return values, such as the return value of malloc(). c++ requires typecast, c does not.

You might also want to read some of these links, which discuss the problems you might encounter.

[instantcake]

only bad coding is a problem when converting c to c++. the truth is c++ is just better, and has many functions that replace c functions. more than 99% of your c code is valid, but some purists hate seeing c code in c++ programs. bottom line is it really doesn't matter if you want to update it with new functions or not its up to you.

[omega]

C++ = C + V + OOP

simple, not ?

from .c works to .cpp there are some changes:

1. C-STYLE structures are not supported
2. C-STYLE MACRO is not supported (you might never use this these days)

and to work that out you go on with these steps:

1. put all of your C codes into functions like this,

#ifdef __cpp__
  extern "C" {
#endif

 // C  functions OR code

#ifdef  __cpp__
  };
#endif

[instantcake]

omega said:

C++ = C + V + OOP

simple, not ?

from .c works to .cpp there are some changes:

1. C-STYLE structures are not supported
2. C-STYLE MACRO is not supported (you might never use this these days)

and to work that out you go on with these steps:

1. put all of your C codes into functions like this,

#ifdef __cpp__
  extern "C" {
#endif

 // C  functions OR code

#ifdef  __cpp__
  };
#endif

acctually this means that you have to qualify everything in the global namespace using the :: operator if you use using namespace std; AND that is inaccurate you CAN use c structures. C++ extends C and does not take out using structures, it just makes them Public by default, and they can contain functions

[Ancient Dragon]

omega said:

1. C-STYLE structures are not supported

Wrong. structures are still supported.

omega said:

2. C-STYLE MACRO is not supported (you might never use this these days)

wrong again.

omega said:

1. put all of your C codes into functions like this,

#ifdef __cpp__
  extern "C" {
#endif

 // C  functions OR code

#ifdef  __cpp__
  };
#endif

That's only necessary if you want to call the C functions compiled as C code from functions compiled as c++ code. When you compile the c code with c++ compiler then that is not necessary.

[instantcake]

Ancient Dragon said:

Wrong. structures are still supported.


wrong again.




That's only necessary if you want to call the C functions compiled as C code from functions compiled as c++ code. When you compile the c code with c++ compiler then that is not necessary.

exactly my point

[marwex89]

omega said:

1. C-STYLE structures are not supported
2. C-STYLE MACRO is not supported (you might never use this these days)

and to work that out you go on with these steps:

1. put all of your C codes into functions like this,

#ifdef __cpp__
  extern "C" {
#endif

 // C  functions OR code

#ifdef  __cpp__
  };
#endif

Yeah, that's pretty much plain wrong, sorry. In addition to what AD said,
this:

#ifdef __cpp__
  extern "C" {
#endif

 // C  functions OR code

#ifdef  __cpp__
  };
#endif

should be

#ifdef __cpp__
  extern "C" {
#endif

 // C  functions OR code

#ifdef  __cpp__
  }
#endif