Searched +refs:custom +refs:add +refs:see +refs:also (Results 1 - 25 of 27) sorted by relevance

12

/macosx-10.9.5/CPANInternal-140/Data-Dumper-Concise/lib/Data/Dumper/
H A DConcise.pm110 to eval this back in you probably wanted to remove subrefs first and add them
111 back in a custom way anyway. Note that this -does- force using the pure perl
119 happy. Then tell us so we can add it to the see also section.
123 This package also provides:
/macosx-10.9.5/CPANInternal-140/Net-DNS/lib/Net/DNS/
H A DResolver.pm105 environment variables can also contain configuration information; see
118 This is supported on both UNIX and Windows. Values pulled from a custom
123 values of the custom configuration file, if any. The following
270 See also L</axfr_start> and L</axfr_next>.
316 See also L</axfr>.
325 Also see the IPv6 transport notes below
407 Reads the answer from a background query (see L</bgsend>). The argument
450 You can also sign packets manually -- see th
[all...]
/macosx-10.9.5/CPANInternal-140/Sub-Exporter/lib/Sub/
H A DExporter.pm13 Sub::Exporter - a sophisticated exporter for custom-built routines
97 This also avoids a common form of ugliness seen in many modules: package-level
109 Generators can also allow you to export class methods to be called as
128 Building custom routines with generators isn't the only way that Sub::Exporters
130 also be renamed to avoid naming collisions.
199 For information on how these callbacks are used, see the documentation for
296 Another group is also created if not defined: C<all>. The C<all> group
340 Collector coderefs can also be used as hooks to perform arbitrary actions
809 ## Cute idea, possibly for future use: also supply an "unimport" for:
912 Sub::Exporter also offer
[all...]
/macosx-10.9.5/CPANInternal-140/Template-Toolkit/lib/Template/Plugin/
H A DFilter.pm71 # the "suck it and see" approach, comment it out, and wait for someone to
180 To use your custom plugin, you have to make sure that the Template
200 'C<MyFilter>'. When you come to use it as a C<FILTER>, you should add
203 'C<MyFilter>', which is an entirely different thing (see later for
271 will now also get passed a reference to an array of postional
312 You can also have your plugin install itself as a named filter by
/macosx-10.9.5/CPANInternal-140/Template-Toolkit-2.24/lib/Template/Plugin/
H A DFilter.pm71 # the "suck it and see" approach, comment it out, and wait for someone to
180 To use your custom plugin, you have to make sure that the Template
200 'C<MyFilter>'. When you come to use it as a C<FILTER>, you should add
203 'C<MyFilter>', which is an entirely different thing (see later for
271 will now also get passed a reference to an array of postional
312 You can also have your plugin install itself as a named filter by
/macosx-10.9.5/CPANInternal-140/Tree-Simple/lib/Tree/
H A DSimple.pm80 || die "Insufficient Arguments : parent also must be a Tree::Simple object";
278 || die "Insufficient Arguments : cannot add a sibling to a ROOT tree";
285 || die "Insufficient Arguments : cannot add siblings to a ROOT tree";
377 # since each time you either add a child
482 # add them to the clone, you end up setting
519 # see if we can clone it
604 # explicity add a child to it
614 # add more than one child at a time
620 # add siblings
635 object also ha
[all...]
/macosx-10.9.5/CPANInternal-140/Tree-Simple-1.18/lib/Tree/
H A DSimple.pm80 || die "Insufficient Arguments : parent also must be a Tree::Simple object";
278 || die "Insufficient Arguments : cannot add a sibling to a ROOT tree";
285 || die "Insufficient Arguments : cannot add siblings to a ROOT tree";
377 # since each time you either add a child
482 # add them to the clone, you end up setting
519 # see if we can clone it
604 # explicity add a child to it
614 # add more than one child at a time
620 # add siblings
635 object also ha
[all...]
/macosx-10.9.5/CPANInternal-140/Pod-WSDL/lib/Pod/
H A DWSDL.pm512 Any subroutine not preceeded by WSDL pod will be left unmentioned. Any standard pod will be ignored (though, for an exception to this, see the section on own complex types below).
518 How do we use Pod::WSDL? In describing a web service's method we have to say something about parameters, return values and faults. In addition you might want to add some documentation to these items and to the method itself.
536 You will easily guess what C<_IN>, C<_OUT> and C<_INOUT> stand for so we can move on. C<NAME> is the name of your parameter. It does not have any real function (the order of the parameters being the only important thing) but it is nice to have it since in a WSDL document the parameters need to have names. So instead of having Pod::WSDL automatically generate cryptic names (it cannot do that right now) be nice to the client and use some sensible name. The C<TYPE> of the parameters can be any of the xsd (schema) standard types (see [5]) or a type of your own creation. The C<$> resp. C<@> symbols tell Pod::WSDL and your client if it is a scalar or array parameter. Everything following the type up to the next instruction is treated as the parameter's documentation. If you call the constructor of Pod::WSDL with the argument C<withDocumentation =E<gt> 1>, it will be added to the WSDL.
550 If you want some method to be a one way operation (see [4], ch. 2.4.1), say so by using the instruction C<_ONEWAY> in the pod. In this case no response message will be generated and a C<_RETURN> instruction will be ignored.
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:
562 Since you probably won't return an array of fault objects, you do not need to use the C<($|@)> tokens. Just say that you return a fault, declare it's type and add an optional description.
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 WSD
[all...]
/macosx-10.9.5/CPANInternal-140/Pod-WSDL-0.061/lib/Pod/
H A DWSDL.pm512 Any subroutine not preceeded by WSDL pod will be left unmentioned. Any standard pod will be ignored (though, for an exception to this, see the section on own complex types below).
518 How do we use Pod::WSDL? In describing a web service's method we have to say something about parameters, return values and faults. In addition you might want to add some documentation to these items and to the method itself.
536 You will easily guess what C<_IN>, C<_OUT> and C<_INOUT> stand for so we can move on. C<NAME> is the name of your parameter. It does not have any real function (the order of the parameters being the only important thing) but it is nice to have it since in a WSDL document the parameters need to have names. So instead of having Pod::WSDL automatically generate cryptic names (it cannot do that right now) be nice to the client and use some sensible name. The C<TYPE> of the parameters can be any of the xsd (schema) standard types (see [5]) or a type of your own creation. The C<$> resp. C<@> symbols tell Pod::WSDL and your client if it is a scalar or array parameter. Everything following the type up to the next instruction is treated as the parameter's documentation. If you call the constructor of Pod::WSDL with the argument C<withDocumentation =E<gt> 1>, it will be added to the WSDL.
550 If you want some method to be a one way operation (see [4], ch. 2.4.1), say so by using the instruction C<_ONEWAY> in the pod. In this case no response message will be generated and a C<_RETURN> instruction will be ignored.
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:
562 Since you probably won't return an array of fault objects, you do not need to use the C<($|@)> tokens. Just say that you return a fault, declare its type and add an optional description.
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 WSD
[all...]
/macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.69/lib/OldDocs/SOAP/
H A DLite.pm210 Supports custom serialization.
214 Provides exception transport with custom exceptions
356 (service address) and also loads the required module at the same time. It is
407 added for readability. Useful in the case you want to see the generated code
454 see L</"SOAP::Serializer">.
501 You can mix C<SOAP::Header> parameters with other parameters and you can also
510 (see L</"DEFAULT SETTINGS">) or locally, for a particular object.
516 may change this behavior globally (see L</"DEFAULT SETTINGS">) or locally, for a
527 See also: L<SOAP::Trace>;
730 An interface for specific attributes is also provide
[all...]
/macosx-10.9.5/CPANInternal-140/SOAP-Lite_new/lib/OldDocs/SOAP/
H A DLite.pm210 Supports custom serialization.
214 Provides exception transport with custom exceptions
356 (service address) and also loads the required module at the same time. It is
407 added for readability. Useful in the case you want to see the generated code
454 see L</"SOAP::Serializer">.
501 You can mix C<SOAP::Header> parameters with other parameters and you can also
510 (see L</"DEFAULT SETTINGS">) or locally, for a particular object.
516 may change this behavior globally (see L</"DEFAULT SETTINGS">) or locally, for a
527 See also: L<SOAP::Trace>;
730 An interface for specific attributes is also provide
[all...]
/macosx-10.9.5/emacs-92/emacs/etc/
H A Dorgcard.tex9 % This file can be printed with 1, 2, or 3 columns per page (see below).
37 % along with GNU Emacs; see the file COPYING. If not, write to
157 \output={% %see The TeXbook page 257
184 % we also need the tilde, for file names.
276 (add-to-list 'auto-mode-alist '("\\\\.org\$" . org-mode))
324 To set archive location for current file, add a line like$^2$:
429 \key{edit (also hidden part of) link at point}{C-c C-l}
550 \key{Toggle custom format display for dates/times}{C-c C-x C-t}
571 \key{add/move current file to front of agenda}{C-c [}
582 \key{configure custom command
[all...]
/macosx-10.9.5/CPANInternal-140/Class-DBI/lib/Class/
H A DDBI.pm829 # method. We also allow get to be called with a list of keys, instead of
859 # We also override set() from Class::Accessor so we can keep track of
1314 $cd->delete; # also deletes the tracks
1412 your columns, see L</"LAZY POPULATION">
1507 This can also be passed as a second argument to 'table':
1608 also, recursively (cascading delete). $obj is no longer usable after
1655 You may also specify the sort order of the results by adding a final
1672 You can also use 'order_by' with these, as with search().
1681 Any of the above searches (as well as those defined by has_many) can also
1701 You can also subclas
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/
H A DLog4perl.pm55 #see Log::Log4perl::Appender::DBI
698 You also specify which so-called I<appenders> you want to feed your
699 log messages to ("Print it to the screen and also append it to /tmp/my.log")
840 you could also call the C<log()> method with the appropriate level
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
951 also pass the stringified message to their companions in the Carp package:
985 Chainsaw (see
990 C<Log::Log4perl> also supports I<Dave Rolskys> excellent C<Log::Dispatch>
1059 for the file appender is logging not only the message but also th
[all...]
/macosx-10.9.5/CPANInternal-140/Crypt-SSLeay-0.64/
H A DSSLeay.pm62 requests. Please see LWP for more information on POST requests.
68 This distribution also makes following deprecated modules available:
141 custom location. If everything builds OK, but you get failures when during
219 C<Crypt::SSLeay> from an alternative repository (see L<PPM::Repositories>).
226 do it, please open a ticket on RT with the information so I can add it to
232 proxy support. Please read these sections to see which one
473 under the terms of Artistic License 2.0 (see
/macosx-10.9.5/CPANInternal-140/DBIx-Class-Schema-Loader-0.07033/lib/DBIx/Class/Schema/Loader/
H A DBase.pm170 The option also takes a hashref:
243 table names is also done better (but best in v8.)
245 CamelCase column names in case-preserving mode will also be handled better
325 PostgreSQL you add statements of the form C<COMMENT ON TABLE some_table IS
326 '...'>, the same syntax is used in Oracle. To create comments in MySQL you add
328 restricts the length of comments, and also does not handle complex Unicode
401 Can also be a coderef, for more precise control, in which case the coderef gets
503 To prefix/suffix all monikers with the database and/or schema, see
710 L<DBIx::Class::Schema/load_classes>. When using this option you can also
788 This attribute can also b
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/lib/Log/Log4perl/
H A DFAQ.pm201 also runs smoothly on all other major flavors (Windows NT, 2000, XP, etc.).
203 It also runs nicely with ActiveState 5.8.0, and, believe me,
235 anyway), just tell ppm the first time you call it to add the Log4perl
238 ppm> repository add http://log4perl.sourceforge.net/ppm
299 =head2 My application is already logging to a file. How can I duplicate all messages to also go to the screen?
313 just add another appender to the configuration file and you're done:
355 stealth loggers (see L<Log::Log4perl/"Stealth Loggers">),
441 C<trace()> uses C<DEBUG> and C<conns()> also logs with C<DEBUG> --
581 But, you also want it to take command line parameters to set values
659 code for custom conversio
[all...]
/macosx-10.9.5/CPANInternal-140/Class-DBI-v3.0.17/lib/Class/
H A DDBI.pm834 # method. We also allow get to be called with a list of keys, instead of
864 # We also override set() from Class::Accessor so we can keep track of
1304 $cd->delete; # also deletes the tracks
1402 your columns, see L</"LAZY POPULATION">
1453 The RootClass of L<DBIx::ContextualFetch> in also inherited from L<Ima::DBI>,
1499 This can also be passed as a second argument to 'table':
1601 the foreign elements also, recursively (cascading delete). $obj is no
1653 You may also specify the sort order of the results by adding a final
1673 You can also use 'order_by' with these, as with search().
1682 Any of the above searches (as well as those defined by has_many) can also
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/Log4perl/
H A DFAQ.pm201 also runs smoothly on all other major flavors (Windows NT, 2000, XP, etc.).
203 It also runs nicely with ActiveState 5.8.0, and, believe me,
235 anyway), just tell ppm the first time you call it to add the Log4perl
238 ppm> repository add http://log4perl.sourceforge.net/ppm
299 =head2 My application is already logging to a file. How can I duplicate all messages to also go to the screen?
313 just add another appender to the configuration file and you're done:
355 stealth loggers (see L<Log::Log4perl/"Stealth Loggers">),
443 C<trace()> uses C<DEBUG> and C<conns()> also logs with C<DEBUG> --
583 But, you also want it to take command line parameters to set values
661 code for custom conversio
[all...]
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/lib/Log/
H A DLog4perl.pm55 #see Log::Log4perl::Appender::DBI
554 You also specify which so-called I<appenders> you want to feed your
555 log messages to ("Print it to the screen and also append it to /tmp/my.log")
692 you could also call the C<log()> method with the appropriate level
813 Chainsaw (see
818 C<Log::Log4perl> also supports I<Dave Rolskys> excellent C<Log::Dispatch>
887 for the file appender is logging not only the message but also the number of
901 For more detailed info on layout formats, see L<Log Layouts>.
921 examples (also derived from [2]), which should also illustrat
[all...]
/macosx-10.9.5/CPANInternal-140/Mail-Sender-0.8.22/
H A DSender.pm653 the recipients to see each other's address set the C<fake_to> parameter to some informative,
693 You may use this parameter to add custom headers into the message. The parameter may
712 You may also use the nickname "subtype".
788 ENVID - used to propagate an identifier for this message transmission envelope, which is also
839 You may add support for other authentication protocols yourself. See below.
856 Please see the authentication section bellow.
898 If you want to specify a message id you can also use the "messageid" parameter for the Open, OpenMultipart,
1772 see C<new Mail::Sender> for info about the parameters.
1881 Prints the strings to the socket. Doesn't add an
[all...]
/macosx-10.9.5/CPANInternal-140/Mail-Sender/
H A DSender.pm89 ## you could also use this code by "John W. Krahn" <krahnj@acm.org>
538 the recipients to see each other's address set the C<fake_to> parameter to some informative,
573 You may use this parameter to add custon headers into the message.
590 You may also use the nickname "subtype".
691 You may add support for other authentication protocols yourself. See below.
708 Please see the authentication section bellow.
1497 see C<new Mail::Sender> for info about the parameters.
1611 Prints the strings to the socket. Doesn't add any end-of-line characters.
1669 Prints the strings to the socket. Doesn't add any end-of-line characters.
1740 Prints the strings to the socket. Doesn't add an
[all...]
/macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.715/lib/SOAP/
H A DLite.pm1005 # add new schema into namespaces
1124 local %objectstack = %objectstack; # want to see objects ONLY in the current tree
1126 # did we see this object in current tree? Seems to be recursive refs
1167 # we could also check for CODE|GLOB|LVALUE, but we cannot serialize
1242 # TODO: add support for multidimensional, partially transmitted and sparse arrays
1268 # TODO: add support for multidimensional, partially transmitted and sparse arrays
1544 # ? '', but see coment below
1707 # So first check to see if a context exists.
2165 $som->context($self->context); # TODO - try removing this and see if it works!
2406 # first time to see thi
[all...]
/macosx-10.9.5/CPANInternal-140/SOAP-Lite_new/lib/SOAP/
H A DLite.pm967 # add new schema into namespaces
1071 local %objectstack = %objectstack; # want to see objects ONLY in the current tree
1072 # did we see this object in current tree? Seems to be recursive refs
1108 # we could also check for CODE|GLOB|LVALUE, but we cannot serialize
1182 # TODO: add support for multidimensional, partially transmitted and sparse arrays
1215 # TODO: add support for multidimensional, partially transmitted and sparse arrays
1442 # ? '', but see coment below
1607 # So first check to see if a context exists.
2033 $som->context($self->context); # TODO - try removing this and see if it works!
2274 # first time to see thi
[all...]
/macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.69/lib/SOAP/
H A DLite.pm975 # add new schema into namespaces
1078 local %objectstack = %objectstack; # want to see objects ONLY in the current tree
1079 # did we see this object in current tree? Seems to be recursive refs
1113 # we could also check for CODE|GLOB|LVALUE, but we cannot serialize
1173 # TODO: add support for multidimensional, partially transmitted and sparse arrays
1203 # TODO: add support for multidimensional, partially transmitted and sparse arrays
1415 # ? '', but see coment below
1550 # So first check to see if a context exists.
1954 $som->context($self->context); # TODO - try removing this and see if it works!
2170 # first time to see thi
[all...]

Completed in 343 milliseconds

12