Difference between revisions of "Tutorials"
(Added "Porting 32 Bit Code to 64 Bits") |
(Moved "Getting Started with the D Programming Languag" to the Articles page.) |
||
| Line 26: | Line 26: | ||
* [[Defining custom print format specifiers|Define custom print format specifiers]] | * [[Defining custom print format specifiers|Define custom print format specifiers]] | ||
* [[Function literals]] | * [[Function literals]] | ||
| − | |||
* [[Implicit conversions in user types|Implicitly convert a user-defined type to a builtin type]] | * [[Implicit conversions in user types|Implicitly convert a user-defined type to a builtin type]] | ||
* [[Output locale character (MBS) to console]] | * [[Output locale character (MBS) to console]] | ||
Revision as of 02:07, 24 February 2014
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
- 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
- D for Win32
- Porting 32 Bit Code to 64 Bits
