Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

Comparison of Matlab and C++

Status
Not open for further replies.
speed of matlab vs c

Matlab handle matrix or vectorization as soneone said. So it is
easier to create an algorithm and test it without being a full
programmer. Matlab is for the DSP designer and C/C++ is
for the DSP implementator. If you try to bypass Matlab in order
to go directly to C/C++ for implementation you find yourself
in a big problem. Simplication is what Matlab does. But implementation
can't be done in Matlab.
 

c better than matlab

Let's just put it this way. If you are going into a job that requires MATLAB, not knowing C/ASM or HDL is not going to get you anywhere. So thinking that MATLAB is better than C/C++ and hence we should forget about C/C++ is pure wishful thinking.
 

matlab gpu slower than c

So thinking that MATLAB is better than C/C++ and hence we should forget about C/C++ is pure wishful thinking.
Click to expand...
Thinking that you should forget about Matlab and goes directly to C/C++ for
implementation you will get a lot of headaches. Matlab should be used to
simplicity and verification of the algorithm. If the algorithm is easy or
the problem is not too complicated you can go directly to C/C++....
but if your algorithm is too complicated, starting with C/C ++ and trying
to complete the job you will get a big mess that never will be completed
or at least will take a awful a lot more time.
 

runtime matlab vs c++

jallem said:
So thinking that MATLAB is better than C/C++ and hence we should forget about C/C++ is pure wishful thinking.
Click to expand...
Thinking that you should forget about Matlab and goes directly to C/C++ for
implementation you will get a lot of headaches. Matlab should be used to
simplicity and verification of the algorithm. If the algorithm is easy or
the problem is not too complicated you can go directly to C/C++....
but if your algorithm is too complicated, starting with C/C ++ and trying
to complete the job you will get a big mess that never will be completed
or at least will take a awful a lot more time.
Click to expand...
Not trying to squabble here. But I never did mention that we should forget about MATLAB. My main idea is to point out that over-reliance on MATLAB will lead you nowhere.
 

fft matlab systemc

matlab is good for simulation. In order to run faster, use vector in matlab instead of elements.
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top