Difference between revisions of "Tutorials"
m (→How To: added link to Read table data from file) |
(→How To: Add link to Unilink config guide) |
||
| Line 20: | Line 20: | ||
* [[Bind D to C]] | * [[Bind D to C]] | ||
* [[Compiling_and_linking_with_DMD_on_Windows|Compile and link with DMD on Windows]] | * [[Compiling_and_linking_with_DMD_on_Windows|Compile and link with DMD on Windows]] | ||
| + | * [[Linking_With_Unilink|Link with the Unilink linker on Windows instead of Optlink]] | ||
* [[Convert header files with SED]] | * [[Convert header files with SED]] | ||
* [[Defining custom print format specifiers|Define custom print format specifiers]] | * [[Defining custom print format specifiers|Define custom print format specifiers]] | ||
Revision as of 21:22, 13 September 2013
Best Practices
- Order of import statements
- Portability and performance
- Conventional module name for importing all modules in a package
Common Idioms
Although D inherited much of its syntax from C and C++, the new features that it introduces lead to some common idioms that are unique to D.
- Initializing variables
- Declaring constants
- Looping over integers
- Unittest placement
- Commenting out code
- Declaring dense multidimensional arrays
- Voldemort types
How To
- Bind D to C
- Compile and link with DMD on Windows
- Link with the Unilink linker on Windows instead of Optlink
- Convert header files with SED
- Define custom print format specifiers
- Function literals
- Getting Started with the D Programming Language -- Mike "Aldacron" Parker
- Implicitly convert a user-defined type to a builtin type
- Output locale character (MBS) to console
- printf
- Promote D Projects
- Regular expressions
- Runtime type information (RTTI)
- Run D in a CGI (web) environment
- Tame OPTLINK
- Run unit tests
- Using NASM with D
- Split file into multidimensional dynamic string array
