Chapter 16. Unsafe Code
IN THIS CHAPTER
Until now, we've seen what is called safe code. Safe code means that we have used a high abstraction level. Some C programmers among you will have noticed that we haven't used pointers up to now. Pointers are a real source of trouble. In C code, problems related to pointers are hard to find and lead to unpredictable errors. Therefore, C# tries to get rid of pointers whenever it's possible to do so. The problem with pointers is that internal pointers can damage almost everything that's within the scope of an application.
In this chapter, we deal with what is known as unsafe code.
Get Mono Kick Start now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
