issue115:critique_litteraire
Différences
Ci-dessous, les différences entre deux révisions de la page.
Prochaine révision | Révision précédente | ||
issue115:critique_litteraire [2016/11/29 09:18] – créée d52fr | issue115:critique_litteraire [2016/12/15 15:18] (Version actuelle) – andre_domenech | ||
---|---|---|---|
Ligne 1: | Ligne 1: | ||
Object Oriented Programming with ANSI-C | Object Oriented Programming with ANSI-C | ||
- | by Axel-Tobias Schreiner | + | par Axel-Tobias Schreiner |
+ | (Programmation orientée objet en ANSI-C) | ||
- | There is something about C that many of us can't let go of it. With the advent of programming languages such as Python and Java, many others have started to wonder, is C worth learning? Or, more importantly, | + | |
+ | **There is something about C that many of us can't let go of it. With the advent of programming languages such as Python and Java, many others have started to wonder, is C worth learning? Or, more importantly, | ||
When I tried to break down what power actually meant, I stumbled upon things such as a standard template library, portability, | When I tried to break down what power actually meant, I stumbled upon things such as a standard template library, portability, | ||
- | I have never, ever read a book like this one. What makes it special is that instead of throwing the class-like syntax at you, it dwells deep into the concept of abstraction. For the first time in my life, I was able to feel polymorphism taking over my code, and dynamic linkage creating a beautiful artwork of run-time resolutions. For those of you who don't know what that means, and have already had experience with an object oriented language, it's time you step back and wonder “do you really know how your code is working?” | + | I have never, ever read a book like this one. What makes it special is that instead of throwing the class-like syntax at you, it dwells deep into the concept of abstraction. For the first time in my life, I was able to feel polymorphism taking over my code, and dynamic linkage creating a beautiful artwork of run-time resolutions. For those of you who don't know what that means, and have already had experience with an object oriented language, it's time you step back and wonder “do you really know how your code is working?”** |
- | What makes the book great altogether is that it is freely available. You can get a copy from https:// | + | Il y a quelque chose dans le ANSI-C qui empêche beaucoup d' |
+ | |||
+ | Quand j' | ||
+ | |||
+ | Je n'ai jamais, jamais, lu un livre comme celui-ci. Ce qui le rend spécial, c'est que, plutôt que de vous balancer la syntaxe d'une pseudo-classe, | ||
+ | |||
+ | **What makes the book great altogether is that it is freely available. You can get a copy from https:// | ||
Before reading this book, projects with large numbers of files would scare me. If the file count went anywhere above five or six, I found myself perplexed by the complex distribution of work into modules. But now, I am working on projects with a minimum of 25 files. I understand it all now. The book often demarcates a conceptual topic into its 'type, api, and implementation' | Before reading this book, projects with large numbers of files would scare me. If the file count went anywhere above five or six, I found myself perplexed by the complex distribution of work into modules. But now, I am working on projects with a minimum of 25 files. I understand it all now. The book often demarcates a conceptual topic into its 'type, api, and implementation' | ||
Ligne 14: | Ligne 22: | ||
The other specialty of this book is that every second or third chapter in the book is a fully fledged example of an application built using the concepts learned in the previous chapters. Dedicating an entire chapter to an example helps to explore it in detail. At the end of such chapters, one can expect to find exercise questions which build upon the application being worked on. | The other specialty of this book is that every second or third chapter in the book is a fully fledged example of an application built using the concepts learned in the previous chapters. Dedicating an entire chapter to an example helps to explore it in detail. At the end of such chapters, one can expect to find exercise questions which build upon the application being worked on. | ||
- | At the end, the book also provides hints on awk programming - a pattern scanning and processing language. | + | At the end, the book also provides hints on awk programming - a pattern scanning and processing language.** |
+ | |||
+ | Ce qui ajoute à la grandeur de ce livre, c'est qu'il est librement disponible. Vous pouvez en obtenir une copie par https:// | ||
+ | Avant de lire ce livre, les projets avec un grand nombre de fichiers m' | ||
+ | L' | ||
+ | À la fin, le livre fournit aussi des conseils sur la programmation awk, un langage d' | ||
- | Table of contents is as follows: | + | **Table of contents is as follows: |
Abstract Data Types — Information Hiding | Abstract Data Types — Information Hiding | ||
Dynamic Linkage — Generic Functions | Dynamic Linkage — Generic Functions | ||
Ligne 35: | Ligne 48: | ||
Persistent Objects — Storing and Loading Data Structures | Persistent Objects — Storing and Loading Data Structures | ||
Exceptions — Disciplined Error Recovery | Exceptions — Disciplined Error Recovery | ||
- | Forwarding Messages — A GUI Calculator | + | Forwarding Messages — A GUI Calculator** |
+ | Table des matières | ||
+ | Types d' | ||
+ | Liens dynamiques - Fonctions génériques (Dynamic Linkage — Generic Functions). | ||
+ | Économie de programmation - Expressions arithmétiques (Programming Savvy — Arithmetic Expressions). | ||
+ | Héritage - Réutilisation et raffinage du code (Inheritance — Code Reuse and Refinement). | ||
+ | Hiérarchie des classes - Maintenabilité (Class Hierarchy — Maintainability). | ||
+ | Le pré-processeur ooc - Imposer un codage normalisé (The ooc Preprocessor — Enforcing a Coding Standard). | ||
+ | Vérification dynamique des types - Programmation défensive (Dynamic Type Checking — Defensive Programming). | ||
+ | Construction statique - Auto-organisation (Static Construction — Self-Organization). | ||
+ | Délégation - Fonctions de rappel (Delegates — Callback Functions). | ||
+ | Méthodes de classe - Colmater les fuites de mémoire (Class Methods — Plugging Memory Leaks). | ||
+ | Objets persistants - Stocker et charger des structures de données (Persistent Objects — Storing and Loading Data Structures). | ||
+ | Exceptions - Récupérer une erreur avec rigueur (Exceptions — Disciplined Error Recovery). | ||
+ | Transfert de messages - Un calculateur en mode graphique (Forwarding Messages — A GUI Calculator). |
issue115/critique_litteraire.1480407515.txt.gz · Dernière modification : 2016/11/29 09:18 de d52fr