|
The complete background is not changing
|
|
|
|
|
Hi
1) I have huge C++ code, that I need to refactor. I am using RAD Studio- code gear
Please advise free Tool to refactor C++ code. Thanks you
2)The code is very bad. it has around 3000 compiler warning. I know it is bad to automate fixing the warnings  but Is there any tool, or automated process to fix the warnings
Thanks you!!
|
|
|
|
|
It is most unlikely that any tool could do this. You will need to get your "code analysis head" on and knuckle down to a few days (or weeks) of hard work.
|
|
|
|
|
The best tool is Elbow Grease and Visual Studio Level 4 warning level and "Stop on Warning" .
I'd rather be phishing!
|
|
|
|
|
A warning typically means that while the code is legitmate with respect to the C++ syntax, the compiler suspects that it might be doing something else than what the programmer intended. Since the computer can't guess what's in the head of the programmer, there's no safe way for it to automatically fix it.
If you have so many warnings, it's probably best to watch out for very common types of warnings, pick one of these, and focus on fixing that warning everywhere in the code, ignoring other warnings. Most of the time you'll quickly be able to spot certain patterns, and fixing these errors should therefore be possible almost without thinking after a while. It will still take time, but that way it's probably a lot faster than working on all warnings by order of occurrence.
P.S.: if your goal is refactoring the entire code, then eliminating warnings is the last of your concerns! First you need tests, to ensure that the refactored code really produces the same results. Then you need to start with the lowest level functions, and then work your way up. Chances are, that changes in your low level functions require adjustments higher up, and that could very well affect code that currently issues warnings. It would be pointless to fix warnings first and then change that same code again due to low-level refactoring, so you better don't do that so early!
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
modified 25-Jan-19 10:04am.
|
|
|
|
|
I'm going to embedd the Python in my MFC/C++ application(interactive Python console) and extend the Python with the application's API.
Since any script can be malformed, what are the risks in this particular case?
Is there any technics to protect the main C++ application?
Would appreciate the feedback from programmers who was experienced this kind of scenario, and also the security experts.
Thanks.
|
|
|
|
|
Immense, but not because of Python, but that you are adding scripting to your app, opening up a lot of vectors for software with bad intent and plain bad software.
|
|
|
|
|
Hello! What extensions, plug-ins, additional programs for working with Visual Studio do you use? I'm interested in memory usage reports, code optimization. What can you to advise. What can be useful for beginner? For Windows
|
|
|
|
|
|
Thank you, I think I watched that post. I also watched many articles such as "5, 10, 20... best extensions" for Visual Studio. It seemed to me most of the items from the list are rarely used.
modified 23-Jan-19 10:21am.
|
|
|
|
|
Somewhat helpful:
Hide Suggestions And Outlining Margins: removes whitespace at the beginning of lines, near the line numbers.
Editor Guidelines: adds a vertical line at a given column, I have it at 80. This allows me to comfortably have the project explorer on the left, two editor panes and the test explorer on the right.
Also, Macros for Visual Studio (it lets you to record and replay keyboard macros). Really handy tool for me
|
|
|
|
|
Be sure I'll try this plugins. Macro seems to be very useful.
|
|
|
|
|
You can use IntelliCode, it's good plugin for novice programmers. Also, I use VLD, Deleaker or standard debugger.
|
|
|
|
|
Thanks for participating. I researched your recommendations. I will use not all the plugins, but some of them I added in VS
|
|
|
|
|
Im using MFC GridControl 2.7 taken from code proejct in my application.In my grid control, im making second column as check box column. The default state of check box should be true. Later, user can uncheck the checkbox and depends on the state, furthur functinoality wil go. Here i dont know how to set checkbox as checked in default.
m_ctLstCtrl.Create(listRect, this, IDC_TRENDLISTCTRL);
m_ctLstCtrl.SetEditable(TRUE);
try {
m_ctLstCtrl.SetRowCount(9);
m_ctLstCtrl.SetColumnCount(15);
m_ctLstCtrl.SetFixedRowCount(1);
m_ctLstCtrl.SetFixedColumnCount(1);
}
catch (CMemoryException* e)
{
e->ReportError();
e->Delete();
return -1;
}
for (int row = 0; row < m_ctLstCtrl.GetRowCount()-1; row++)
{
m_ctLstCtrl.SetCellType(row+1,1,RUNTIME_CLASS(CGridCellCheck));
}
Anu
|
|
|
|
|
You should post your question in the forum at the end of the article. I know for a fact that the author spends much of his time on CodeProject.
|
|
|
|
|
|
Okay.
Thank you.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
|
Amazing implementation; so much functionality in so little code.
|
|
|
|
|
This forum is for asking questions about problems with code you wrote, not asking for code.
Hint: if the problem you have is a very common one, a simple search in your favorite search engine is much more likely to turn up results.
But if this is homework, you really should at least try to solve it. Homework is rarely about finding the solution, it is about trying to find the right way towards the solution. Asking for code is the opposite direction - sorry, no points.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
I started programming in high school in C about 15 years ago as a hobby and did not follow programming as my career path but it has served as a useful tool periodically since then.
I was more or less told that C would be a good entry language, that it would be a good foundation if I decided to learn others. That Java is bloated and grossly resource inefficient, as well as sacrificing quite a lot to be fully cross platform. That C++'s OOP leads to less resource efficient programming and that classes were a crutch to help structure code in lieu of skillfully choosing one's own good designs. But that they would make it easier to work with others by giving greater standardization to interfaces.
Today I observe as follows:
C was designed for specific purposes and to specific ideals, and I mostly align with them. It's small, clean, and efficient. You're free to shoot yourself in the foot, all 12 toes. Proper design practices are your responsibility (or willful irresponsibility). If you want something you can build it or borrow/get it from someone else. It's not large.
On the other hand, pure speed and efficiency is not critical in all applications. If you are doing desktop development with a moderate amount of data, and let's say not computationally intensive graphics, the efficiency may be unnecessary. Rapid development is more critical to me now.
The very minimal provisioning of the standard library slows development time, like a mostly empty toolbox. Not only mostly empty, but the tools of the standard library are very traditional and sometimes crude for what you might need. Other languages provide a much greater toolset of readily usable and easily importable features.
C is not entirely outmoded but its popularity is marginal, and with that marginalization a lot of the contributions made to programming as a whole are largely unavailable. Its use is declining further with the rise of C#.
Projects | The State of the Octoverse[^]
I think the logical choice would be to learn C++ next.
|
|
|
|
|
HS_C_Student wrote: I think the logical choice would be to learn C++ next.
Most languages have their place in development, and none can really be said to be better (certainly not objectively) than the others. The choice really depends on what sort of applications you want to develop. If you are looking at Windows or Web applications then C# would be a much more logical choice these days.
|
|
|
|
|
I love C++ primarily because I like the type of projects where C++ is the best solution. This is the approach I recommend--what kind of projects do you want to work on? Then ask what platforms you want to target and in what way. (For example, if you want a rich native GUI experience on Linux and Windows, C# won't work, but C++ with Qt will.)
Also be aware that C++ has an incredibly rich set of libraries available in addition to the standard library.
|
|
|
|
|
HS_C_Student wrote: That C++'s OOP leads to less resource efficient programming and that classes were a crutch to help structure code in lieu of skillfully choosing one's own good designs.
There are so many ... misconceptions in that sentence alone, I wonder why you're actually thinking of C++ as your next language. I do agree that C++ is a good language to learn, but maybe I should clarify a few things:
1. C++ is not an OOP language! While it's often declared as such because its support for OOP is the most prominent feature that distinguishes it from C, C++ (as well as C) is a general purpose language! You can use it effectively for pretty much any programming paradigm you can think of: procedural, modular, object oriented, functional, you name it. Most other programming languages are not nearly as flexible. And that is the main reason why I love this language more than any other.
2. C++ is not less efficient than C. Neither with respect to use of resources nor with respect to speed. It used to be somewhat slower in some areas, but not the assembly that modern compilers can generate from modern C++ code. Of course, if you turn, say, some procedural code into OO code, use a lot of virtual functions and class hierarchies, that will likely cause some losses - but (if you do it right) you get clearer, more comprehensible code in return. It's not really a loss, it's a tradeoff, and it's for the programmer to decide whether he's willing to make that tradeoff or not.
3. I'm not sure what gave you the impression that classes are a crutch!? When I look at some code from less skilled programmers, yes that code may appear that way. But if you do understand the OO principles, and use it correctly, a well designed class hierarchy can give you extremely clear and comprehensible code, without sacrifcing anything, really.
That said, I'll have to give you a fair warning: programmers coming from a C background tend to stick with the programming techniques they know, because, in C++, they can! That is not necessarily a bad thing, but when these techniques creep into the class design, then, yes, what you get is a crutch! When you move to C++ from C, you need to take a step back every time you're about to design a class, and make sure that you drop any notion of using known principles and techniques, until you at least managed to specify what, exactly, the class needs to be able to do - and what not! The latter is really the key to good class design: making sure that a class does no more than what it's intended for. Otherwise you won't be able to benefit from the good aspects of OO, and you'll end up with the worst aaspects of both the procedural and the OO paradigm.
4. One extra tip: as I said, OOP is just one of many paradigms that C++ supports. Don't get too crazy with classes! The perception of many programmers that C++ is an OO-language, and only an OO-language, led to massive overuse of the OO principles. Programmers (including myself) were suffering from "when all you have is a hammer, everything looks like a nail" syndrome. It is not a good idea to turn everything into classes just because you can. Sometimes a struct and a set of polymorphic (or otherwise generic) functions is better design.
Therefore, when learning C++, you should also learn about the other paradigms: templates, generic programming and meta programming are diffcult to understand and learn, but there are many good articles and sites, and you can always come here for help. Functional programming got a lot of support with the more recent C++ standards and are well worth investigating. And, of course, sometimes there's really nothing wrong with plain old C structs and functions.
C is a great toolbox. But it's just the starter set with little more than a hammer, a screwdriver, and pincers. With C++ you get the advanced toolset! That doesn't mean you no longer need your hammer. Just that you now have a lot more specialized tools that can make specific tasks so much easier to complete.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
