summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
-rw-r--r--c.html.markdown5
-rw-r--r--es-es/c-es.html.markdown2
-rw-r--r--pt-br/c-pt.html.markdown2
-rw-r--r--ru-ru/c-ru.html.markdown2
4 files changed, 1 insertions, 10 deletions
diff --git a/c.html.markdown b/c.html.markdown
index a737696f..4e2c2cdf 100644
--- a/c.html.markdown
+++ b/c.html.markdown
@@ -909,8 +909,7 @@ Node createLinkedList(int *vals, int len);
## Further Reading
-Best to find yourself a copy of [K&R, aka "The C Programming Language"](https://en.wikipedia.org/wiki/The_C_Programming_Language)
-It is _the_ book about C, written by Dennis Ritchie, the creator of C, and Brian Kernighan. Be careful, though - it's ancient and it contains some
+Best to find yourself a copy of [K&R, aka "The C Programming Language"](https://en.wikipedia.org/wiki/The_C_Programming_Language). It is _the_ book about C, written by Dennis Ritchie, the creator of C, and Brian Kernighan. Be careful, though - it's ancient and it contains some
inaccuracies (well, ideas that are not considered good anymore) or now-changed practices.
Another good resource is [Learn C The Hard Way](http://learncodethehardway.org/c/) (not free).
@@ -921,6 +920,4 @@ It's very important to use proper spacing, indentation and to be consistent with
Readable code is better than clever code and fast code. For a good, sane coding style to adopt, see the
[Linux kernel coding style](https://www.kernel.org/doc/Documentation/process/coding-style.rst).
-Other than that, Google is your friend.
-
[1] [Why isn't sizeof for a struct equal to the sum of sizeof of each member?](https://stackoverflow.com/questions/119123/why-isnt-sizeof-for-a-struct-equal-to-the-sum-of-sizeof-of-each-member)
diff --git a/es-es/c-es.html.markdown b/es-es/c-es.html.markdown
index 249046ba..8adeda87 100644
--- a/es-es/c-es.html.markdown
+++ b/es-es/c-es.html.markdown
@@ -431,5 +431,3 @@ Es muy importante utilizar el espaciado y la sangría apropiados y ser coherente
con su estilo de codificación en general. El código legible es mejor que el
código rápido. Para adoptar un buen estilo de codificación, vea el
[Estilo de codificación del kernel Linux] (https://www.kernel.org/doc/Documentation/CodingStyle).
-
-Aparte de eso, Google es tu amigo.
diff --git a/pt-br/c-pt.html.markdown b/pt-br/c-pt.html.markdown
index 72877e84..1daee632 100644
--- a/pt-br/c-pt.html.markdown
+++ b/pt-br/c-pt.html.markdown
@@ -647,6 +647,4 @@ Se você tem uma pergunta, leia [compl.lang.c Frequently Asked Questions](http:/
Código legível é melhor que código 'esperto' e rápido. Para adotar um estilo de código bom e sensato, veja
[Linux kernel coding style](https://www.kernel.org/doc/Documentation/CodingStyle).
-Além disso, Google é teu amigo.
-
[1] http://stackoverflow.com/questions/119123/why-isnt-sizeof-for-a-struct-equal-to-the-sum-of-sizeof-of-each-member
diff --git a/ru-ru/c-ru.html.markdown b/ru-ru/c-ru.html.markdown
index a146a76b..f7b1477b 100644
--- a/ru-ru/c-ru.html.markdown
+++ b/ru-ru/c-ru.html.markdown
@@ -479,6 +479,4 @@ void str_reverse_through_pointer(char *str_in) {
Читаемый код лучше, чем красивый или быстрый код.
Чтобы научиться писать хороший код, почитайте [Linux kernel coding style](https://www.kernel.org/doc/Documentation/CodingStyle).
-Также не забывайте, что [Google](http://google.com) и [Яндекс](http://yandex.ru) – ваши хорошие друзья.
-
[1] http://stackoverflow.com/questions/119123/why-isnt-sizeof-for-a-struct-equal-to-the-sum-of-sizeof-of-each-member