15,905,912 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 Bruno van Dooren (Top 9 by date)
Bruno van Dooren
3-Jan-24 8:38am
View
Ok, but the pragma directives you mentioned only change where exactly in the binary pe image, certain pieces of compiled code are stored. What I do not yet understand is how the exact layout of the compiled code in the executable changes the coding job.
Bruno van Dooren
19-Dec-23 4:38am
View
I got downvoted for saying this :)
Bruno van Dooren
18-Dec-23 12:15pm
View
YOU say: if it's x = (char*) y it will still shift by 4 bytes when x + 1, etc
x is a char*.
If you declare x as int* you are ignoring compiler warnings.
Bruno van Dooren
18-Dec-23 10:55am
View
>> if I write *((char*)ptr + 2) then the arithmetics changes and instead of 2*sizeof(int) changes into 2*sizeof(char) ??
that is correct.
>> if it's x = (char*) y it will still shift by 4 bytes when x + 1, etc
No, it won't. if X is of type char* and you do +1 it will shift by 1 byte.
Bruno van Dooren
25-Jun-23 7:07am
View
I agree with most of your comments, except the one about memory.
This is an assignment for a HFT firm. Algorithm speed is everything to those people. Anything else is a secondary concern if at all. Int64 is the native integer length and can be done in a single instruction. It could be that Int32 is equally fast but I would benchmark them both and go with the fastest one because that's what they are after.
Bruno van Dooren
22-Jun-23 1:48am
View
Fair point. Gather what info you can, log some state and then continue the crash.
Bruno van Dooren
21-Jun-23 17:13pm
View
using try ... catch across dll boundaries is a bad idea though. There are no guarantees that this will work properly unless everything is built against the same runtime version with compatible compiler and linker settings.
Either the DLL should catch everything before the exception leaves the dll, and properly terminate, or the app should be allowed to crash. Undefined behavior is often worse than a crash.
Bruno van Dooren
3-Feb-23 12:11pm
View
On Windows, Named Pipes can be used for communications between systems and it's a much better alternative than direct TCP / UDP because they are tied in with Windows security so not only can the server restrict access, but the server can -depending on system config, security settings and client's approval- impersonate the client for passing client-server calls, or checking group membership of the calling token.
Bruno van Dooren
18-Jan-23 9:57am
View
It is very similar. It's a different way of approaching the same solution, with an explanation of why your original approach doesn't work
Show More