/macosx-10.9.5/OpenLDAP-491.1/OpenLDAP/tests/scripts/ |
H A D | test047-ldap | 250 dn: ou=Same as above,$BASEDN 253 ou: Same as above 267 dn: ou=Same as above,ou=Meta,$BASEDN 270 ou: Same as above 274 dn: cn=Added User,ou=Same as above,ou=Meta,$BASEDN 598 -D "cn=Added User,ou=Same as above,ou=Meta,$BASEDN" \ 621 -s meta "cn=Added User,ou=Same as above,ou=Meta,$BASEDN" \ 651 -D "cn=Added User,ou=Same as above,ou=Meta,$BASEDN" \ 675 -D "cn=Added User,ou=Same as above,ou=Meta,$BASEDN" \ 700 -D "cn=Non-existing User,ou=Same as above,o [all...] |
/macosx-10.9.5/bind9-45.100/bind9/bin/tests/ |
H A D | named.conf | 6 * purpose with or without fee is hereby granted, provided that the above 421 // 'transfer-format' above)
|
/macosx-10.9.5/ruby-104/ruby/ext/tk/lib/tk/ |
H A D | canvas.rb | 100 if args[0] && mode =~ /^(above|below|with(tag)?)$/ 107 addtag(tagOrId, 'above', tagid(target)) 231 find('above', tagid(target)) 557 def raise(tag, above=nil) 558 if above 559 tk_send_without_enc('raise', tagid(tag), tagid(above))
|
/macosx-10.9.5/tcl-102/tcl_ext/tklib/tklib/modules/widget/ |
H A D | mentry.tcl | 197 # for -direction above, below. 212 above { if {$y >= $mh} { incr y -$mh } { incr y $bh } }
|
/macosx-10.9.5/vim-53/runtime/syntax/ |
H A D | sgml.vim | 133 " above, except the `matchgroup=sgmlEndTag for highlighting 237 " cluster which contains the above two elements
|
/macosx-10.9.5/CPANInternal-140/Sub-Exporter/lib/Sub/ |
H A D | Exporter.pm | 98 configuration. That is, you might have seen something like the above 183 In addition to the basic options above, a few more advanced options may be 305 For example, the C<build_analyzer> generator that we saw above could be 584 C<setup_exporter> without providing any of the three above arguments, it will 913 C<build_exporter> routines described above. It also provides a special "setup" 916 Note that the "setup" collector (seen in examples like the L</SYNOPSIS> above) 1053 behavior, as shown above.)
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/lib/Log/Log4perl/ |
H A D | FAQ.pm | 132 the example above shows how to pass in a configuration as text in a 327 The configuration file above is assuming that both appenders are 398 in the pseudo signal handler above merits a more detailed explanation. With 399 the setup above, if a module calls C<die()> in one of its functions, 561 function shown above calls C<caller(1)> which determines the name 574 above. 605 file, it will notice the assignment above because of its 616 Here's some sample code implementing the command line interface above: 781 code snippet above is not one but two log messages written 933 The new() method listed above store [all...] |
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/ |
H A D | README | 146 With the configuration file above, "Log::Log4perl" will write "Error 150 above. 170 file above didn't specify anything about "My::MegaPackage". And yet, 174 the case above, the log level at the root (root *always* defines a log 259 The to-be-logged message passed to all of the functions described above 268 Note that even if one of the methods above returns true, it doesn't 396 Once the initialization shown above has happened once, typically in the 418 The screen appender above, on the other hand, uses a "SimpleLayout", 425 In the configuration sample above, we chose to define a *category* 462 As shown above, yo [all...] |
/macosx-10.9.5/CPANInternal-140/Pod-WSDL/lib/Pod/ |
H A D | WSDL.pm | 504 Put the pod directly above the subroutines which the web service's client is going to call. There may be whitespace between the pod and the sub declaration but nothing else. 598 Put this pod anywhere within the package My::Type. Pod::WSDL will find it (if it is in @INC), parse it and integrate it into the WSDL document. The C<_ATTR> instruction works exactly as the C<_IN>, C<_OUT> and C<_INOUT> instructions for methods (see above). 626 withDocumentation - If true, put available documentation in the WSDL (see "Pod Syntax" above). For used own complex types ('modules') this will be the output of Pod::Text on these modules. The software generating the client stubs might give a damn, but a person reading the WSDL won't! 644 withDocumentation - If true, put available documentation in the WSDL (see "Pod Syntax" above). For used own complex types ('modules') this will be the output of Pod::Text on these modules. The software generating the client stubs might give a damn, but a person reading the WSDL won't! 689 Of course, one subroutine declaration might take a lot of different sets of parameters. In Java or C++ you would have to have several methods with different signatures. In perl you fix this within the method. So why not put several WSDL pod blocks above the method so the web service's client can handle that.
|
/macosx-10.9.5/CPANInternal-140/Pod-WSDL-0.061/lib/Pod/ |
H A D | WSDL.pm | 504 Put the pod directly above the subroutines which the web service's client is going to call. There may be whitespace between the pod and the sub declaration but nothing else. 598 Put this pod anywhere within the package My::Type. Pod::WSDL will find it (if it is in @INC), parse it and integrate it into the WSDL document. The C<_ATTR> instruction works exactly as the C<_IN>, C<_OUT> and C<_INOUT> instructions for methods (see above). 626 withDocumentation - If true, put available documentation in the WSDL (see "Pod Syntax" above). For used own complex types ('modules') this will be the output of Pod::Text on these modules. The software generating the client stubs might give a damn, but a person reading the WSDL won't! 644 withDocumentation - If true, put available documentation in the WSDL (see "Pod Syntax" above). For used own complex types ('modules') this will be the output of Pod::Text on these modules. The software generating the client stubs might give a damn, but a person reading the WSDL won't! 689 Of course, one subroutine declaration might take a lot of different sets of parameters. In Java or C++ you would have to have several methods with different signatures. In perl you fix this within the method. So why not put several WSDL pod blocks above the method so the web service's client can handle that.
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/ |
H A D | README | 146 With the configuration file above, "Log::Log4perl" will write "Error 150 above. 170 file above didn't specify anything about "My::MegaPackage". And yet, 174 the case above, the log level at the root (root *always* defines a log 252 The to-be-logged message passed to all of the functions described above 371 Once the initialization shown above has happened once, typically in the 393 The screen appender above, on the other hand, uses a "SimpleLayout", 400 In the configuration sample above, we chose to define a *category* 406 As shown above, you can define "Log::Log4perl" loggers both from within 619 named "value" as an argument. The anonymous hash in the call above wil [all...] |
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/ |
H A D | Log4perl.pm | 778 With the configuration file above, C<Log::Log4perl> will write 782 configuration file shown above. 804 C<Log::Log4perl> works with inheritance: The config file above didn't 810 defined somewhere. In the case above, the log level at the root 902 message passed to all of the functions described above can 911 Note that even if one of the methods above returns true, it doesn't 1044 Once the initialization shown above has happened once, typically in 1067 screen appender above, on the other hand, 1075 In the configuration sample above, we chose to define a I<category> 1114 As shown above, yo [all...] |
/macosx-10.9.5/CPANInternal-140/SOAP-Lite-0.69/lib/SOAP/ |
H A D | Serializer.pm | 131 If the value/object being encoded was part of a C<SOAP::Data> object (as in the above example), then the second, third and fourth parameter will be the C<SOAP::Data> element's name, type, and attribute set respectively. If on the other hand, the value/object being encoded is I<not> part of a C<SOAP::Data> object, as in the code below: 139 Then the second and third parameters will be the class name of the value/object being encoded (e.g. "MyModule::MyPackage" in the example above), and the fourth parameter will be an empty hash. 238 I<Tip: As a short hand, you could just as easily use an anonymous test subroutine when registering the new datatype in place of the C<urlReferenceTest> subroutine above. For example:>
|
/macosx-10.9.5/CPANInternal-140/Class-Accessor-Grouped/inc/Module/ |
H A D | AutoInstall.pm | 192 # no need to check $arg as _version_cmp ($cur, undef) would satisfy >= above 440 *** Could not find a version $ver or above for $pkg; skipping. 541 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/Class-C3-XS/inc/Module/ |
H A D | AutoInstall.pm | 402 *** Could not find a version $ver or above for $pkg; skipping. 503 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/Class-Data-Accessor-0.04004/inc/Module/ |
H A D | AutoInstall.pm | 402 *** Could not find a version $ver or above for $pkg; skipping. 503 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/inc/Module/ |
H A D | AutoInstall.pm | 192 # no need to check $arg as _version_cmp ($cur, undef) would satisfy >= above 440 *** Could not find a version $ver or above for $pkg; skipping. 541 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/script/ |
H A D | dbicadmin | 44 ['op:s' => 'compatiblity option all of the above can be suppied as --op=<action>'], 210 compatiblity option all of the above can be suppied as --op=<action>
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class-Schema-Loader/inc/Module/ |
H A D | AutoInstall.pm | 192 # no need to check $arg as _version_cmp ($cur, undef) would satisfy >= above 440 *** Could not find a version $ver or above for $pkg; skipping. 541 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class-Schema-Loader-0.05003/inc/Module/ |
H A D | AutoInstall.pm | 192 # no need to check $arg as _version_cmp ($cur, undef) would satisfy >= above 440 *** Could not find a version $ver or above for $pkg; skipping. 541 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class-Schema-Loader-0.07033/inc/Module/ |
H A D | AutoInstall.pm | 205 # no need to check $arg as _version_cmp ($cur, undef) would satisfy >= above 472 *** Could not find a version $ver or above for $pkg; skipping. 590 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/JSON-Any/inc/Module/ |
H A D | AutoInstall.pm | 402 *** Could not find a version $ver or above for $pkg; skipping. 503 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/JSON-Any-1.29/inc/Module/ |
H A D | AutoInstall.pm | 192 # no need to check $arg as _version_cmp ($cur, undef) would satisfy >= above 442 *** Could not find a version $ver or above for $pkg; skipping. 543 *** Could not find a version $ver or above for $pkg; skipping.
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/Log4perl/Appender/ |
H A D | File.pm | 370 the C<utf8> option (see above). 466 Authors (please contact them via the list above, not directly):
|
/macosx-10.9.5/CPANInternal-140/Net-DNS/contrib/ |
H A D | check_soa | 74 Query specific nameserver as above. 86 As above, for IPv6 address prefix of specified length.
|