D
Der Witzbold
Am 13.09.2010 15:45, schrieb Victor Bazarov:
Better than non-visual C++.
Better than non-visual C++.
J
James Kanze
I'd probably say, "make sure you know where the standard C++
ends and those additional libraries begin", instead of just
"don't use them", but that's just me...
In general, yes. I did qualify my statement with "if your goal
is to learn portable C++". For other things, of course, it
depends, and there are certainly cases where using the libraries
is acceptable (or even necessary).
V
Victor Bazarov
What's a "non-visual C++"?
V
R
Richard
[Please do not mail me a copy of your followup]
Victor Bazarov <[email protected]> spake the secret code
gcc.
Visual C++ is more comparable to Eclipse.
Victor Bazarov <[email protected]> spake the secret code
gcc.
Visual C++ is more comparable to Eclipse.
C
Cplus_addicted
I dont know Delphi, but I got basic C knowledge of 1 year during my
univ study. That is why I dont wanna discover America again, and I
wanna go through Visual C++. Because, all I need to make are human-
machine interfaces to control machines in automation systems.
Ö
Öö Tiib
Hmm. Maybe tell us 5 years later how far you got with your "simple"
SCADA system made with TwinCAT OPC servers/controllers and PLC and
what you had there using you basic one course knowledge of C ... and
how many people your devices did kill.
C
cpp4ever
That's somewhat harsh, just because someone has an idea of rewriting
some existing code, you suggest they may end up killing people. Surely a
nuch more constructive approach would be to make clear the cost in time,
effort, and actual benefits.
I remember some years ago, a similar suggestion was made when the
company,(where I was employed), wanted to move code from 16 bit to 32
bit architecture. My response was to highlight the financial cost, time,
and people required to have a chance of achieving that. Then I suggested
an approach that would reuse the existing code and would require less
cost, time, and people. This is the approach that was finally taken, and
successfully I may add.
Finally, any company that cannot manage quality control of it's
development and release of products will very quickly be lacking any
significant customer numbers, and hence go bust. Unfortunately most
management I've experience of is nore interested in jargon laden
slogans, and meaningless company philosophies that pay no attention to
the quality of what the company actually produces.
cpp4ever
Ö
Öö Tiib
Some ideas *are* dangerous. Failing with something harmless and
failing with something dangerous are different lessons. My comment was
meant like a friendly warning. Lot of industrial devices are capable
of killing people. So ... a young man not too familiar with the
programming tools nor languages has to be motivated to soberly
consider the risks too. Other factors you mention are heavily related
with safety and quality goals of such projects.
B
BGB / cr88192
<--
I dont know Delphi, but I got basic C knowledge of 1 year during my
univ study. That is why I dont wanna discover America again, and I
wanna go through Visual C++. Because, all I need to make are human-
machine interfaces to control machines in automation systems.
-->
sadly, 1 year of classes is not likely far enough for one to realize just
how far there is to go...
even "simple" things may not be so simple on the inside, and bad
considerations may turn out being costly.
part of this is learning ones' own capabilities and limits, since one may
end up seeming like a jerk, or worse, if they step too far outside their
bounds.
it is best not to mess with things that work unless one has a good idea what
they are doing (as in the cliched saying "if it aint broke, don't fix
it"...).
with a little more experience, one may realize that most of these
(mainstream) languages are basically about the same anyways. differences in
exact syntax, semantics, and available API's, but nothing preventing one
from moving from one to another (apart from code migration, for example,
porting code between C and Java can be painful, for example...).
so, moving between one language and another is not quite the same as
relearning the world, as most things learned in one can be applied to the
others (as much as some "style purists" may object...).
so, procede with caution...
or, hell, try to learn both languages...
K
Krice
Or you could compile the project with gcc.
Visual C++ IDE is really nice, maybe even the best and the
compiler is fast. But I always make a final release with
gcc, because the executables of gcc don't seem to need some
external Microsoft DLLs and they run better in Linux Wine.
And of course the source code is slightly more portable after
it goes through gcc.