. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997 12.3 Directive Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002 equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive no longer has any effect, other than to emit a warning if it’s used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single MUTEX directive. You will need to evaluate any use of these removed di- rectives in your 2.2 configuration to determine

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997 12.3 Directive Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002 equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive no longer has any effect, other than to emit a warning if it’s used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single MUTEX directive. You will need to evaluate any use of these removed di- rectives in your 2.2 configuration to determine

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089 12.3 Directive Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094 equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive no longer has any effect, other than to emit a warning if it’s used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single MUTEX directive. You will need to evaluate any use of these removed di- rectives in your 2.2 configuration to determine

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075 12.3 Directive Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080 equivalent than the number of worker threads. The old name is still supported. • The DEFAULTTYPE directive no longer has any effect, other than to emit a warning if it’s used with any value other than none RewriteLock, SSLMutex, SSLStaplingMutex, and WatchdogMutexPath have been replaced with a single MUTEX directive. You will need to evaluate any use of these removed di- rectives in your 2.2 configuration to determine

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781 12.3 Directive Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784 discussed below. In addition, if you dynamically load the standard modules using the LOADMODULE directive, then you will need to account for the module name changes mentioned above. If you choose to use not have this directive in your config file, you can add UseCanonicalName On to retain the old behavior. • The module MOD USERDIR will no longer act on requests unless a USERDIR directive specifying a

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 12.3 Directive Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663 ACCEPTPATHINFO directive to force the core handler to accept requests with PATH INFO and thereby restore the ability to use PATH INFO in server-side includes. • The CACHENEGOTIATEDDOCS directive now takes instances of CACHENE- GOTIATEDDOCS should be replaced with CacheNegotiatedDocs on. • The ERRORDOCUMENT directive no longer uses a quote at the beginning of the argument to indicate a text message. Instead, you

. . . . . . . . . . . . . . . . . . . . 143 13 Using Windows resources 144 13.1 The resource directive $R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 13.2 Creating resources compiler directive is always specified as a comment using curly braces: {$DIRECTIVE [value]} The older (* *) notation, or the C++ notation // cannot be used for directives. The fact that a directive is specified That in turn means that if a non-existing directive is specified, the compiler does not give an error, it just gives a warning about an invalid/unknown directive. There is a distinction between local and

directory should be added to the LIBPATH directive in the config.sys file: LIBPATH=XXX;C:\PP\DLL Obviously, any existing directories in the LIBPATH directive (indicated by XXX in the above exam- ple) compile something. 3.1.3 Include files If you include a file in your source with the {$I filename} directive, the compiler will look for it in the following places: 1. It will look in the path specified in the current directory. 3.1.4 Object files When you link to object files (using the {$L file.o} directive, the compiler will look for this file in the same way as it looks for include files: 1. It will

bootstrap: [AppComponent] }) export class AppModule { } Component use other component through directive in its template using target component’s selector name. is the combination of property and event binding. NgModel NgModel is a standalone directive. ngModel directive binds form control to property and property to form control. The syntax of ngModel is

Two way binding! Hello {{ userName }}!

Here, Property is bind to form control ngModel directive and if you enter any text in the textbox, it will bind to the property. After running your application

appropriate mode. When required for a certain feature, the use of the -M command-line switch or {$MODE } directive will be indicated in the text. More information about the various modes can be found in the user’s appropriate mode. When required for a certain feature, the use of the -M command-line switch or {$MODE } directive will be indicated in the text. More information about the various modes can be found in the user’s functions or methods, properties) can have a hint directive appended to their definition: Hint directives 16 CHAPTER 1. PASCAL TOKENS -- hint directive Deprecated string constant Experimental Platform