Abstract
First of all, let’s get the linguistic issue out of the way: That little curve in the letter ç is called a cedilla and the letter itself is pronounced as an S, so the word façade is pronounced fah-saad. The particularly pedantic among you are welcome to use the letter ç in your code, as compilers handle this just fine.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Over the years I have seen many tricks involving the use of Unicode (typically UTF-8) encoding in C# source files. The most insidious case is one where a developer insisted on calling his extension method’s first argument this—it was, of course, a completely valid identifier because the letter i in this was a Ukrainian letter i, not a Latin one.
- 2.
Most buffers are typically one-dimensional because it is easier to pass a single pointer somewhere than a double pointer, and using an array or vector does not make much sense when the size of the structure is deterministic and immutable. Another advantage to the 1D approach is that, when it comes to GPU processing, a system such as CUDA uses up to six dimensions for addressing anyway, so after a while, computing a 1D index from an N-dimensional block/grid position becomes second nature.
- 3.
We also use ASCII, because Unicode is rarely, if ever, required. Having 1 char = 1 byte is a good practice if you don’t need to support extra character sets. Although not relevant to the discussion at hand, it also greatly simplifies the implementation of string processing algorithms on both Graphics Processing Units (GPUs) and Field-Programmable Gate Arrays (FPGAs).
- 4.
Many trading terminals have abandoned pure ASCII representation in favor of more mixed-mode approaches, such as simply using monospace fonts in ordinary UI controls or rendering many little text-based consoles in a separate windowing API rather than sticking to a single canvas.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2019 Dmitri Nesteruk
About this chapter
Cite this chapter
Nesteruk, D. (2019). Façade. In: Design Patterns in .NET. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4366-4_11
Download citation
DOI: https://doi.org/10.1007/978-1-4842-4366-4_11
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-4365-7
Online ISBN: 978-1-4842-4366-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)