A "code-what"? Unless you have spent some time working in the area of reverse engineering, chances are you have not heard of the term "codecave" before. If you have heard of it, you might not have read a clear definition of it or quite understand what it is or why it is useful. I have even asked seasoned assembly programmers about the term before and most of them had not heard of it. If it is new to you, do not worry, you are not the only one. It is a term that is scarcely used and is only useful in a reverse engineering context. Furthermore, is it "codecave" or "code cave"? I am not quite sure, but I will try my best to refer to it consistently as a "codecave". A space may sneak in there from time to time
THE SYNTAX OF A PROGRAMMING LANGUAGE tells you what code it is possible
to write—what the machine will understand. Style tells you what you ought to write—
what the humans reading the code will understand. Code written with a consistent, simple
style will be maintainable, robust, and contain fewer bugs. Code written with no regard to
style will contain more bugs. It may simply be thrown away and rewritten rather than
maintained.
What Does the code DO? Sometimes we may desire to hide our file contents from others.One of the possible way is encrypting these files.Here a simple encryption technique is used(In VB - The same technique can be implemented in "c" also.) Program flow Explained * Open the File to be encrypted for Binary Access Read(Say Source File) * Open a temparory file where encrypted data is stored for Binary Access Write(Say Destination File) * Loop through the Source File Byte by Byte * For each byte read from the file, Complement the data. (Using Not operator (in C we have to use "~" operator) * Write Complemented Data to Destination File * Delete the Source File * Rename Destination file as Source File(Now Encryption is over)
The Gray Watson debugging malloc library is C source code for a drop in replacement for the system malloc & other memory manage ment routines. What is unique about this library is that it contains a number of powerful debugging facilities including very comprehensive heap testing and ex- cellent run-time debugging information.
Overview In this chapter I introduce Borland C++Builder (BCB) and explain what it is about. I also devote considerable time to explaining the purpose of this book and the philosophy behind my approach to technical writing. Technical subjects covered in this chapter include Creating a simple Multimedia RAD program that plays movies, WAV files, and MIDI files. Shutting down the BCB RAD programming tools and writing raw Windows API code instead. Creating components dynamically on the heap at runtime. Setting up event handlers (closures) dynamically at runtime. A brief introduction to using exceptions. This topic is covered in more depth in Chapter 5, "Exceptions." A brief introduction to ANSI strings. This subject is covered in more depth in Chapter 3, "C++Builder and the VCL." Using the online help. Greping through the include and source files that come with the product and with this book.
The code assumes a two-dimensional computational domain with TMz polarization (i.e., non-zero field Ez, Hx, and Hy). The program is currently written so that the incident field always strikes the lower-left corner of the total-field region first. (If you want a different corner, that should be a fairly simple tweak to the code, but for now you ll have to make that tweak yourself.) I have attempted to provide copious comments in the code and hope that a knowledgeable C programmer can quickly map the approach as described in the paper to what is in the program.
This code detects memory leaks in embedded VC++ almost the same way crtdbg does in VC++. At the end of program execution it will display in the debug window if there were any memory leaks and how the memory looks so you can identify where your memory leak occurred. It will display in the debug window a message saying no memory leaks detected if there are no memory leaks. Similar to what crtdbg.h does in VC++. The code detects memory leaks generated with calls to new and delete operators in C++. The code doesn t detect memory leaks generated with C functions: malloc, calloc, free, but that can be done in the future. Let me know and I will program it.
Just what is a regular expression, anyway?
Take the tutorial to get the long answer. The short answer is that a regular expression
is a compact way of describing complex patterns in texts. You can use them to search
for patterns and, once found, to modify the patterns in complex ways. You can also use
them to launch programmatic actions that depend on patterns.
A tongue-in-cheek comment by programmers is worth thinking about: "Sometimes you
have a programming problem and it seems like the best solution is to use regular
expressions now you have two problems." Regular expressions are amazingly
powerful and deeply expressive. That is the very reason writing them is just as
error-prone as writing any other complex programming code. It is always better to
solve a genuinely simple problem in a simple way when you go beyond simple, think
about regular expressions.
Tutorial: Using regular expressions
// Hint: These classes are intended to be used as base classes. Do not
// simply add your code to these files - instead create a new class
// derived from one of CSizingControlBarXX classes and put there what
// you need. See CMyBar classes in the demo projects for examples.
