Help On Linking

Full text search for "macros"

C++/SAL 표준 표식 언어 . . . . 14 matches
 The macros are defined in 3 layers:
 _In_\_Out_ Layer: ---------------- This layer provides the highest abstraction and its macros should be used in most cases. Its macros start with _In_, _Out_ or _Inout_. For the typical case they provide the most concise annotations.
 _Pre_\_Post_ Layer: ------------------ The macros of this layer only should be used when there is no suitable macro in the _In_\_Out_ layer. Its macros start with _Pre_, _Post_, _Ret_, _Deref_pre_ _Deref_post_ and _Deref_ret_. This layer provides the most flexibility for annotations.
 Implementation Abstraction Layer: -------------------------------- Macros from this layer should never be used directly. The layer only exists to hide the implementation of the annotation macros.
 If the buffer size is given by a limiting pointer use the ptrdiff_ versions of the macros.
 // convenience macros for nullterminated buffers with given capacity#define _Deref_pre_z_cap_(size) _Deref_pre3_impl_(_$notnull, _$zterm,_$cap(size)) _Deref2_pre1_impl_(_$valid)#define _Deref_pre_opt_z_cap_(size) _Deref_pre3_impl_(_$maybenull,_$zterm,_$cap(size)) _Deref2_pre1_impl_(_$valid)#define _Deref_pre_z_bytecap_(size) _Deref_pre3_impl_(_$notnull, _$zterm,_$bytecap(size)) _Deref2_pre1_impl_(_$valid)#define _Deref_pre_opt_z_bytecap_(size) _Deref_pre3_impl_(_$maybenull,_$zterm,_$bytecap(size)) _Deref2_pre1_impl_(_$valid)
 // convenience macros for nullterminated buffers with given capacity#define _Deref_post_z_cap_(size) _Deref_post3_impl_(_$notnull, _$zterm,_$cap(size)) _Deref2_post1_impl_(_$valid)#define _Deref_post_opt_z_cap_(size) _Deref_post3_impl_(_$maybenull,_$zterm,_$cap(size)) _Deref2_post1_impl_(_$valid)#define _Deref_post_z_bytecap_(size) _Deref_post3_impl_(_$notnull, _$zterm,_$bytecap(size)) _Deref2_post1_impl_(_$valid)#define _Deref_post_opt_z_bytecap_(size) _Deref_post3_impl_(_$maybenull,_$zterm,_$bytecap(size)) _Deref2_post1_impl_(_$valid)
 // Convenience macros for more concise annotations
 Advanced annotations describe behavior that is not expressible with the regular buffer macros. These may be used either to annotate buffer parameters that involve complex or conditional behavior, or to enrich existing annotations with additional information.
 /* In the primitive __declspec("SAL_*") annotations "SAL" stands for Standard Annotation Language. These __declspec("SAL_*") annotations are the primitives the compiler understands and all high-level SpecString MACROs will decompose into these primivates. */
 /* __exceptthat Given a set of annotations Q containing __exceptthat maybeP, the effect of the except clause is to erase any P or notP annotations (explicit or implied) within Q at the same level of dereferencing that the except clause appears, and to replace it with maybeP. Example 1: __valid __exceptthat __maybenull on a pointer p means that the pointer may be null, and is otherwise valid, thus overriding the implicit notnull annotation implied by __valid on pointers. Example 2: __valid __deref __exceptthat __maybenull on an int **p means that p is not null (implied by valid), but the elements pointed to by p could be null, and are otherwise valid. */ #define __exceptthat __declspec("SAL_except") #define __execeptthat __exceptthat /* _refparam Added to all out parameter macros to indicate that they are all reference parameters. */ #define __refparam __deref __notreadonly
 /* __inner_* Helper macros that directly correspond to certain high-level annotations. */
 /* Macros to classify the entrypoints and indicate their category. Pre-defined control point categories include: RPC, LPC, DeviceDriver, UserToKernel, ISAPI, COM. */ #define __inner_control_entrypoint(category) __declspec("SAL_entrypoint(controlEntry, "SPECSTRINGIZE(category)")")
 Any of these may be used to directly annotate functions, and may be used incombination with each other or with regular buffer macros. For an explanationof each annotation, see the advanced annotations section.-------------------------------------------------------------------------------*/
HelpOnMacros . . . . 3 matches
     == Macros ==
     Macros allow the insertion of system features into normal wiki pages; the only thing that makes those pages special is that they contain macros. If you edit pages like RecentChanges or SystemInfo, you'll see what that means.
     === Search macros ===
     We don't show examples for all macros here, because that would make this page quite long. Here is is the replacement text for the {{{[[SystemInfo]]}}} macro:
HelpOnActions . . . . 2 matches
Actions are tools that work on a page or the whole wiki, but unlike macros do not add ''to'' the page content when viewing a page, but work ''on'' that page content. They either produce some output based on page contents (navigational actions like searching) or implement functions that are not related to viewing a page (like deleting or renaming a page).
The following is a list of ''internal'' actions that are used to implement the various menus and links at the top and bottom of pages, or supplement certain macros.
CommentMacro . . . . 1 match
$extra_macros=array('FootNote','Comment');
HelpOnUpdating . . . . 1 match
* somewhat dangerous macros that won't be activated by default, because they're not advisable for public wikis. You need to explicitely activate those by adding an {{{allowed_actions}}} list to the config. Currently, protected actions {{{DeletePage}}} are always needs 'admin password'.
LocalKeywords . . . . 1 match
macro macros plugin processor plugins
WikiSlide . . . . 1 match
     == Macros ==
      * Macros allow dynamic (computed) content to be inserted into pages.
      * The most important macros:
     For details see HelpOnMacros.

Found 7 matching pages out of 1201 total pages

HyacinthWiki

In Search of the Miraculous

Help On Linking

Full text search for "macros"

You can also click here to search title.