| /macosx-10.9.5/CPANInternal-140/DBIx-Class-Schema-Loader-0.07033/lib/DBIx/Class/Schema/Loader/ |
| H A D | Base.pm | 313 The first is that you can create two tables named C<table_comments> and
324 only supported for PostgreSQL, Oracle and MySQL. To create comments in
326 '...'>, the same syntax is used in Oracle. To create comments in MySQL you add
338 section to be generated with the comment always, only use C<NAME>, or choose
339 the length threshold at which the comment is forced into the description.
360 When pod_comment_mode is set to C<auto>, this is the length of the comment at
371 same database and schema as the table whose comment is being retrieved.
379 same database and schema as the table/column whose comment is being retrieved.
520 C<['name']>, in the order those parts are used to create the moniker name.
718 that directory this module will create
[all...] |
| /macosx-10.9.5/vim-53/runtime/ftplugin/ |
| H A D | sql.vim | 13 " If additional features are required create:
70 " c Auto-wrap comments using textwidth, inserting the current comment
193 command! -nargs=* -complete=custom,SQL_GetList SQLSetType :call SQL_SetType(<q-args>)
292 " create[ or replace] procedure|function|event
316 \ '\%(\<create\s\+' . s:or_replace . '\)\?'.
351 let g:ftplugin_sql_statements = 'create'
406 " Find the start of the next comment
409 " Find the end of the previous comment
412 " Skip over the comment
468 " <C-Right> is not recognized on most Unix systems, so only create
[all...] |
| /macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/ |
| H A D | Log4perl.pm | 785 not C<Log::Log4perl-E<gt>new>? We don't want to create a new
786 object every time. Usually in OO-Programming, you create an object
915 (DEBUG) through. But after this check, Log4perl will eventually apply custom
918 impossible to know what a custom filter does with a message without
2042 First off, let me tell you that creating custom levels is heavily
2049 Log4perl provides a nice way to create custom levels via the
2051 before the first call to init() or get_logger(). Say you want to create
2073 their appenders are used, you may add mappings for custom levels as well:
2078 For example, if your new custom "NOTIF
[all...] |
| /macosx-10.9.5/CPANInternal-140/Pod-WSDL/lib/Pod/ |
| H A D | WSDL.pm | 96 ## we create the object, and
117 $me->writer->comment("WSDL for " . $me->{_location} . " created by " . ref ($me) . " version: $VERSION on " . scalar localtime);
554 SOAP faults are usually translated into exceptions in languages like Java. If you set up a web service using SOAP::Lite, SOAP will trap your dying program and generate a generic fault using the message of C<die>. It is also possible to access SOAP::Lite's SOAP::Fault directly if you want more control - but this is not our issue. If you want to use custom-made fault messages of your own, define them in C<_FAULT> instructions, which look like this:
576 Quite often it will be the case that you have to use complex types as parameters or return values. One example of this we saw when talking about faults: you might want to create custom fault types (exceptions) of your own to fullfill special needs in the communication between web service and client. But of course you also might simply want to pass a complex parameter like a address object containing customer data to your application. WSDL provides the means to describe complex types borrowing the xsd schema syntax. Pod::WSDL makes use of this by allowing you to add WSDL pod to your own types. Assuming you have some own type like
|
| /macosx-10.9.5/CPANInternal-140/Pod-WSDL-0.061/lib/Pod/ |
| H A D | WSDL.pm | 96 ## we create the object, and
117 $me->writer->comment("WSDL for " . $me->{_location} . " created by " . ref ($me) . " version: $VERSION on " . scalar localtime);
554 SOAP faults are usually translated into exceptions in languages like Java. If you set up a web service using SOAP::Lite, SOAP will trap your dying program and generate a generic fault using the message of C<die>. It is also possible to access SOAP::Lite's SOAP::Fault directly if you want more control - but this is not our issue. If you want to use custom-made fault messages of your own, define them in C<_FAULT> instructions, which look like this:
576 Quite often it will be the case that you have to use complex types as parameters or return values. One example of this we saw when talking about faults: you might want to create custom fault types (exceptions) of your own to fullfill special needs in the communication between web service and client. But of course you also might simply want to pass a complex parameter like a address object containing customer data to your application. WSDL provides the means to describe complex types borrowing the xsd schema syntax. Pod::WSDL makes use of this by allowing you to add WSDL pod to your own types. Assuming you have some own type like
|
| /macosx-10.9.5/emacs-92/emacs/lisp/progmodes/ |
| H A D | sql.el | 69 ;; entry function used to create the SQLi buffers is shown with
92 ;; and the custom package
93 ;; <URL:http://www.dina.kvl.dk/~abraham/custom/>.
233 (require 'custom)
445 '(("Rules/Defaults" "^\\s-*create\\s-+\\(\\w+\\s-+\\)*\\(rule\\|default\\)\\s-+\\(\\w+\\)" 3)
446 ("Sequences" "^\\s-*create\\s-+\\(\\w+\\s-+\\)*sequence\\s-+\\(\\w+\\)" 2)
447 ("Triggers" "^\\s-*create\\s-+\\(\\w+\\s-+\\)*trigger\\s-+\\(\\w+\\)" 2)
448 ("Functions" "^\\s-*\\(create\\s-+\\(\\w+\\s-+\\)*\\)?function\\s-+\\(\\w+\\)" 3)
449 ("Procedures" "^\\s-*\\(create\\s-+\\(\\w+\\s-+\\)*\\)?proc\\(edure\\)?\\s-+\\(\\w+\\)" 4)
450 ("Packages" "^\\s-*create\\
[all...] |
| /macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/ |
| H A D | README | 153 want to create a new object every time. Usually in OO-Programming, you
154 create an object once and use the reference to it to call its methods.
272 will eventually apply custom filters and forward the message to one or
274 reason that it's impossible to know what a custom filter does with a
1336 First off, let me tell you that creating custom levels is heavily
1342 Nevertheless, Log4perl provides a nice way to create custom levels via
1344 before the first call to init() or get_logger(). Say you want to create
1365 their appenders are used, you may add mappings for custom levels as
1371 For example, if your new custom "NOTIF
[all...] |
| /macosx-10.9.5/CPANInternal-140/Mail-Sender/ |
| H A D | Sender.pm | 36 # messages you may comment out these lines.
175 # create a hash with accepted authentication protocols
592 Please keep in mind though that it's not currently possible to create nested parts with Mail::Sender.
1445 The module was made so that you could create an object initialized with
1448 one mail using MailMsg() or MailFile() you do not have to create a named
1724 In particular if you use several such to create one part,
2572 If you create a file named Sender.config in the same directory where
2614 You may even "install" your custom function that will be evaluated for
2618 All you have to do is to create a function named SiteHook in
2651 it may include the full name of the user or any other comment
[all...] |
| /macosx-10.9.5/CPANInternal-140/Log-Log4perl/lib/Log/ |
| H A D | Log4perl.pm | 641 not C<Log::Log4perl-E<gt>new>? We don't want to create a new
642 object every time. Usually in OO-Programming, you create an object
1793 First off, let me tell you that creating custom levels is heavily
1800 Log4perl provides a nice way to create custom levels via the
1802 before the first call to init() or get_logger(). Say you want to create
1901 create a STDERR appender and a root logger as in
2123 In environments lacking Log::Log4perl, just comment out the first line
2133 because everything's a regular comment now. Alternatively, put the
2134 magic Log::Log4perl comment resurrectio
[all...] |
| /macosx-10.9.5/CPANInternal-140/Mail-Sender-0.8.22/ |
| H A D | Sender.pm | 31 # messages you may comment out these lines.
216 # create a hash with accepted authentication protocols
693 You may use this parameter to add custom headers into the message. The parameter may
1721 The module was made so that you could create an object initialized with
1724 one mail using MailMsg() or MailFile() you do not have to create a named
1995 In particular if you use several such to create one part,
2875 If you create a file named Sender.config in the same directory where
2917 You may even "install" your custom function that will be evaluated for
2921 All you have to do is to create a function named SiteHook in
2954 it may include the full name of the user or any other comment
[all...] |
| /macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.69/lib/OldDocs/SOAP/ |
| H A D | Lite.pm | 210 Supports custom serialization.
214 Provides exception transport with custom exceptions
647 One more comment. One case when SOAP::Lite will change something that
1109 SOAP::Schema gives you ability to load schemas and create stubs according
1139 You can create stub with B<stubmaker> script:
1280 ->faultactor('http://www.soaplite.com/custom');
1348 nothing in common. It lets you create default object and all objects
1503 SOAP::Lite provides an autodispatching feature that lets you create
1808 In addition see comment about default incoding in .NET Web Services below.
|
| /macosx-10.9.5/CPANInternal-140/SOAP-Lite_new/lib/OldDocs/SOAP/ |
| H A D | Lite.pm | 210 Supports custom serialization.
214 Provides exception transport with custom exceptions
647 One more comment. One case when SOAP::Lite will change something that
1109 SOAP::Schema gives you ability to load schemas and create stubs according
1139 You can create stub with B<stubmaker> script:
1280 ->faultactor('http://www.soaplite.com/custom');
1348 nothing in common. It lets you create default object and all objects
1503 SOAP::Lite provides an autodispatching feature that lets you create
1808 In addition see comment about default encoding in .NET Web Services below.
|
| /macosx-10.9.5/CPANInternal-140/Perl-Tidy-20121207/lib/Perl/ |
| H A D | Tidy.pm | 35 # create a Perl::Tidy module which can operate on strings, arrays, etc.
86 # given filename and mode (r or w), create an object which:
285 # ',' character is a token, and so is an entire side comment. It handles
779 Die "unable to create directory $new_path: $!\n";
1015 # create a formatter for this file : html writer or
1048 # create the tokenizer for this file
1616 $add_option->( 'closing-side-comment-else-flag', 'csce', '=i' );
1617 $add_option->( 'closing-side-comment-interval', 'csci', '=i' );
1618 $add_option->( 'closing-side-comment-list', 'cscl', '=s' );
1619 $add_option->( 'closing-side-comment
[all...] |
| /macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.715/lib/SOAP/ |
| H A D | Lite.pm | 363 # their literal form only when used as markup delimiters, or within a comment,
3420 # CLASS, either get self or create new and assign to self
3422 # function call, either get self or create new and assign to self
3855 sub create; *create = \&new; # make alias. Somewhere 'new' is registered keyword
3941 L<SOAP::Packager> - Provides an abstract class for implementing custom packagers.
4050 A common option is to create a instance of HTTP::Cookies and pass it as
5207 In addition see comment about default incoding in .NET Web Services below.
|
| /macosx-10.9.5/CPANInternal-140/SOAP-Lite_new/lib/SOAP/ |
| H A D | Lite.pm | 364 # their literal form only when used as markup delimiters, or within a comment,
3287 # CLASS, either get self or create new and assign to self
3289 # function call, either get self or create new and assign to self
3722 sub create; *create = \&new; # make alias. Somewhere 'new' is registered keyword
3808 L<SOAP::Packager> - Provides an abstract class for implementing custom packagers.
3917 A common option is to create a instance of HTTP::Cookies and pass it as
4952 In addition see comment about default incoding in .NET Web Services below.
|
| /macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.69/lib/SOAP/ |
| H A D | Lite.pm | 436 # their literal form only when used as markup delimiters, or within a comment,
3082 # CLASS, either get self or create new and assign to self
3084 # function call, either get self or create new and assign to self
3464 sub create; *create = \&new; # make alias. Somewhere 'new' is registered keyword
3541 L<SOAP::Packager> - Provides an abstract class for implementing custom packagers.
4216 In addition see comment about default incoding in .NET Web Services below.
|