15,886,518 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Andrea Simonassi (Top 3 by date)
Andrea Simonassi
19-Oct-16 1:47am
View
Reason for my vote of 2 \n I agree goto is not evil in some cases, but it is evil in 99.9% of cases. Last time I had to use it it was long time ago with C language and only as a shortcut to cleanup subroutines. Anyway I won't blame who use a goto to quit a deeply nested loop in some circumstances.
But your reasons "goto is the same as a function call" it is not correct, in my opinion, because, even at programmable hardware level, they behave quite differently: a CALL instruction write on the stack the return address that is automatically used from the RET instruction, while JMP don't.
Andrea Simonassi
26-Feb-16 6:49am
View
I'd use MaskedTextBox instead of TextBox, various implementation exists depending on environment (web, forms, wpf, ...).
Andrea Simonassi
26-Feb-16 6:22am
View
In my opinion the error cannot be in the code you posted, that code cannot corrupt the managed heap; maybe other parts of your code is using marshaling, pinvoke or unsafe code, you should look there.