nuancing the C part of the go article!

This commit is contained in:
Wouter Groeneveld 2021-04-15 13:12:04 +02:00
parent 5b0454d28b
commit c3fd39264a
1 changed files with 1 additions and 1 deletions

View File

@ -132,7 +132,7 @@ No more fighting with Gradle transitive dependencies, or .NET DLL hells.
## Go fixed C
The last few years, I find myself writing a bit of C/C++ code. It's safe to say that I hate every minute of it. Go is heavily influenced by C, but luckily comes with a garbage collector. Furthermore, the designers of Go were smart enough to only steal the best features of C - and not to look at C++ at all. For example, there is no pointer arithmetic. At least not without resorting to the `unsafe` package and `uintptr`. Another blessing and ease-of-use is the implicit conversion of values to pointers and pointers to values. Consider the following example in C:
The last few years, I find myself writing a fair bit of C++ code. It's safe to say that I detest every minute of the "++" part... Go is heavily influenced by C, but luckily comes with a garbage collector. Furthermore, the designers of Go were smart enough to only steal the best features of C - and not to look at C++ at all. For example, there is no pointer arithmetic. At least not without resorting to the `unsafe` package and `uintptr`. Another blessing and ease-of-use is the implicit conversion of values to pointers and pointers to values. Consider the following example in C:
```C
struct elephant {