Forgot your password?
Sign in with
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Python questions
View Java questions
All Message Boards...
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Design and Architecture
Internet of Things
C / C++ / MFC
ATL / WTL / STL
Objective-C and Swift
Hardware & Devices
Hosting and Servers
.NET (Core and Framework)
Site Bugs / Suggestions
Spam and Abuse Watch
The Insider Newsletter
The Daily Build Newsletter
Most Valuable Professionals
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
What is 'CodeProject'?
Ask a Question
Bugs and Suggestions
Article Help Forum
Comments by Dmitriy Gakh (Top 21 by date)
Yes. It is about robots. But a specialized literature magazine is better place because it has auditory who interested in sci-fi. The best way is to publish my story in the magazine, but here a technical article discussing possibilities of technical achievements described in the story would be seen attractive and useful.
Reason for my vote of 2 \n You study and state the problem from your personal narrow vision. I see a lot of problems relating to these:
1) Modern successful SW develppment processes involved many developers. Even system SW is written by many peple. And the SW is developed with vertical layered structure (source, preprocessor, static code analyser, compiler, tests, ...). In this complex environment close cooperation and common vision is essential.
2) Level of abstraction (OOP/OOD, patterns, best practices, ...) forms specific vision of developers. In many cases "goto" can break the picture and contradict with rules that work for SW development methodologies.
3) The text that you have been published cannot be considered as an article because it does not refer to literature and work of other people. It is a big flaw and root of many "downvotes". You shoud form this as an question named for example as "Why goto has so bad reputation".
As a conclusion - the article is too smal and does not consider influence of SW development methodologies, OOP/OOD, patterns, best practices, e.t.c.
Conversion operators - see my solution and reference below. If you will stuck, I can help you because I have big experience with conversion operators.
I improved the solution stating copying instances, not classes.
This solution is the best indeed because it points to Class/Instance mistake and based on interface that is best from architectural point of view (the best practice).
It is possible without reflection.
To insert one document into another without changing header/footer you need inserting section break in way you new text will be in new section.
Reason for my vote of 4 \n In one hand it is an unuseful tip - you did not describe which benefits gain a programmer from this knowledge. In another hand you have risen an important question. It would be better to write more detailed article showing advantages of using this knowledge.
I also did not understand what exactly is the problem. Did you considered use Session instead of ViewState ? Try learn how to use Session - it could be helpful.
I think call
dtvregister.DataSource = list;
deletes all in dtvregister and take new data from the list. So, you should delete entry only in the list, should not ?
It is new question :-) You asked about unexpected error. The error is fixed. Let's do next step. I think you should better understand what you should delete. I think you should delete an item in the your list in place I commented for deleting code.
log should be replaced by Log.
You could put remove commands in place commented as "Try remove commands here". Try do different options and see results. Hope it will be helpful.
You are in right way. :-)
You are right. I tech my students to use debugger as soon as they started coding. Step by step operations show many details.
But here people even did not read comments before acting...
You should create your list first. Your list is null when you call RemoveAl.
List<log> list = null;
And after debug your code and fix logical problems using debugger.
Reason for my vote of 5 \n Your method saves heap and GC time because avoid string manipulations. It is excellent from memory save perspective.
Reason for my vote of 5 \n Simple and useful.
Reason for my vote of 4 \n The Title promises to explain different types of sending data in IPC. It should be named somewhat as "One way to ...".
Reason for my vote of 4 \n Too small to be an article.
Last Updated 1 Jan 1900
All Rights Reserved.