/macosx-10.9.5/vim-53/runtime/indent/ |
H A D | awk.vim | 84 " -> attempt to indent on first ' ' or '(' of prev line, just like we 106 " If the previous line doesn't need continuation on the current line we are 107 " on the start of a new statement. We have to make sure we align with the
|
H A D | sqlanywhere.vim | 277 " Based on this line, we can determine how much to indent the new 330 " This is a new blank line since we just typed a carriage return 363 " But we do not want to unindent a line like:
|
/macosx-10.9.5/vim-53/runtime/keymap/ |
H A D | kana.vim | 290 " Historic `wi' and `we' 292 we ��� 600 " Historic `wi' and `we'
|
/macosx-10.9.5/CPANInternal-140/Parse-Yapp/t/ |
H A D | stress.t | 357 By putting them before the `parm' rule, we get 681 so there is nothing we can do. Fortunately, 682 begin_new_placement does nothing harmful. When we rewrite 1005 and would be discarded after we finish compiling foo. We don't need to 1006 worry once we see a type. */ 1047 Once we have seen one of these in a declaration, 1100 we need that reduce so we prefer fn_dot_def1 when appropriate. */ 1153 shouldn't we include them? */ 1173 /* If we ar [all...] |
/macosx-10.9.5/CPANInternal-140/Parse-Yapp-1.05/t/ |
H A D | stress.t | 357 By putting them before the `parm' rule, we get 681 so there is nothing we can do. Fortunately, 682 begin_new_placement does nothing harmful. When we rewrite 1005 and would be discarded after we finish compiling foo. We don't need to 1006 worry once we see a type. */ 1047 Once we have seen one of these in a declaration, 1100 we need that reduce so we prefer fn_dot_def1 when appropriate. */ 1153 shouldn't we include them? */ 1173 /* If we ar [all...] |
/macosx-10.9.5/vim-53/runtime/syntax/ |
H A D | ada.vim | 107 " We won't map "adaAssignment" by default, but we need to map ":=" to 178 " We see the "end" in "end record" before the word record, so we match that 234 " If we have vim 6.0 or later, we'll use its advanced pattern-matching 235 " capabilities so that we won't match leading spaces.
|
H A D | lpc.vim | 154 " the constants we used to add to this list. 157 " two underscores. Do we need to include all of that? 159 " from the documentation we know that these constants remains only for 173 " LPC programmers are also C programmers, so we don't need separate settings 241 " Here we should consider the array ({ }) parenthesis and mapping ([ ]) 343 " Make sure these options take place since we no longer depend on file type
|
/macosx-10.9.5/CPANInternal-140/Class-DBI/lib/Class/ |
H A D | DBI.pm | 123 # SQL we'll need 267 # 'dbi:Pg:dbname=foo' we want 'Pg'. I think this is enough. 316 # we don't use get() here because all objects should have 379 # method is constructed for it. If they differ we create both a read-only 457 my $info = { %{ +shift } }; # make sure we take a copy 528 # not in the object_index, or we don't have all keys yet 688 # we pass. Used by copy() and move(). 859 # We also override set() from Class::Accessor so we can keep track of 1210 # Only ignore "Can't locate" errors for the specific module we're loading 1813 return 0 if !ref($self); # This is a create, so we ca [all...] |
/macosx-10.9.5/CPANInternal-140/Tree-Simple/lib/Tree/ |
H A D | Simple.pm | 103 # and now bubble up to the parent (unless we are the root) 114 # and now bubble up to the parent (unless we are the root) 218 # make sure we fix the height 223 # so we change its parent to ROOT 225 # and now we make sure that the depth 244 # now that we are confident it's a reference 407 # we must find the tallest sub-tree 416 # if there is no change, then we 422 # now we need to bubble up through the parents 472 # we d [all...] |
/macosx-10.9.5/CPANInternal-140/Tree-Simple-1.18/lib/Tree/ |
H A D | Simple.pm | 103 # and now bubble up to the parent (unless we are the root) 114 # and now bubble up to the parent (unless we are the root) 218 # make sure we fix the height 223 # so we change its parent to ROOT 225 # and now we make sure that the depth 244 # now that we are confident it's a reference 407 # we must find the tallest sub-tree 416 # if there is no change, then we 422 # now we need to bubble up through the parents 472 # we d [all...] |
/macosx-10.9.5/tcl-102/tcl_ext/snack/snack/demos/tcl/ |
H A D | formant.tcl | 7 # there is no way (?) to find out from Tk if we can display UNICODE IPA 283 grid .f1.l .f1.gt .f1.b .f1.c -sticky we -padx 5 284 grid .f1.gf -columnspan 4 -sticky we 285 grid .f1.ga -columnspan 4 -sticky we 286 grid .f1.gs -columnspan 4 -sticky we 294 grid .f2.l -columnspan 5 -sticky we -padx 5 -pady 5
|
/macosx-10.9.5/zsh-60/zsh/Src/ |
H A D | lex.c | 52 * zshlex() unless we have reached an error. So it is always 83 * set when we detect a lookahead that stops the word from 98 /* inwhat says what exactly we are in * 109 /* wb and we hold the beginning/end position of the word we are completing. */ 112 mod_export int wb, we; variable 120 * If non-zero, we are parsing a line sent to use by the editor, or some 625 /* we haven't got anything to unget */ 667 /* Check whether we're looking at valid numeric globbing syntax * 766 * is not normal command input: lexflags implies we ar [all...] |
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/ |
H A D | Storage.pm | 91 Returns true if we have an open storage connection, false 179 failed halfway through the transaction, in which case we reconnect and 302 release all savepoints created after the savepoint we rollback to.
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/lib/Log/Log4perl/ |
H A D | Appender.pm | 42 # appended ';' in $appenderclass variable). Fail if we see 72 # Set min_level to the lowest setting. *we* are 407 and most of the time this is I<not> what you want, we've instructed 479 If (and now we're getting fancy) 480 an appender expects message chunks, but we would
|
/macosx-10.9.5/CPANInternal-140/Template-Toolkit/lib/Template/Plugin/ |
H A D | Table.pm | 47 # or subclass thereof, we call its get_all() method to extract all 275 So if we had a sample C<alphabet> list contained the letters 'C<a>' to 'C<z>', 341 or the number of entries in a list. The following example shows how we might 365 with data ordered across rather than down, we specify C<rows=5> to order
|
/macosx-10.9.5/CPANInternal-140/Template-Toolkit-2.24/lib/Template/Plugin/ |
H A D | Table.pm | 47 # or subclass thereof, we call its get_all() method to extract all 275 So if we had a sample C<alphabet> list contained the letters 'C<a>' to 'C<z>', 341 or the number of entries in a list. The following example shows how we might 365 with data ordered across rather than down, we specify C<rows=5> to order
|
/macosx-10.9.5/vim-53/runtime/ftplugin/ |
H A D | ocaml.vim | 201 " The source code is quite radically different for we not use python anymore. 277 " 1. Finding the annotation file even if we use ocamlbuild 341 " -> we relax the constraints, it should work in most cases 343 " 4a. we suppose the renamed _build directory is in the current directory 351 " this will work if the file for which we are looking annotations has a unique name in the whole project 489 "Out: the borders of the expression we are looking for the type
|
/macosx-10.9.5/CPANInternal-140/Net-DNS/lib/Net/DNS/ |
H A D | Resolver.pm | 351 Gets or sets the port to which we send queries. This can be useful 360 Gets or sets the port from which we send queries. The default is 0, 368 Gets or sets the source address from which we send queries. Convenient 571 Returns the IP address from which we received the last answer in 578 Returns the size in bytes of the last answer we received in 636 For example, if we wanted to cache lookups:
|
/macosx-10.9.5/CPANInternal-140/Pod-WSDL/lib/Pod/ |
H A D | WSDL.pm | 96 ## we create the object, and 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. 522 WSDL differentiates between in-, out- and inout-parameters, so we do that, too. A different matter is the question, if the client can do this too, but now we are talking about possibilities, not actualities. 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. 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 705 If you use complex types for parameters that are not your own (we assume, that the module containing the web service always is your own), you might not be able to put the WSDL pod into the module files. So why not fetch it from somewhere else like a configuration file?
|
/macosx-10.9.5/CPANInternal-140/Pod-WSDL-0.061/lib/Pod/ |
H A D | WSDL.pm | 96 ## we create the object, and 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. 522 WSDL differentiates between in-, out- and inout-parameters, so we do that, too. A different matter is the question, if the client can do this too, but now we are talking about possibilities, not actualities. 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. 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 705 If you use complex types for parameters that are not your own (we assume, that the module containing the web service always is your own), you might not be able to put the WSDL pod into the module files. So why not fetch it from somewhere else like a configuration file?
|
/macosx-10.9.5/llvmCore-3425.0.33/examples/OCaml-Kaleidoscope/Chapter6/ |
H A D | codegen.ml | 73 (* Grab the first block so that we might later add the conditional branch 138 * shadows an existing variable, we have to restore it, so save it 146 * current BB. Note that we ignore the value computed by the body, but
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/Storage/DBI/ |
H A D | MSSQL.pm | 161 # this should bring back the result of SELECT SCOPE_IDENTITY() we tacked 165 # SCOPE_IDENTITY failed, but we can do something else 303 Be aware that we have tried to make things as simple as possible for our users. 305 explicit value for an autoincrementing column, we will try to issue the
|
/macosx-10.9.5/CPANInternal-140/Data-Page/lib/Data/ |
H A D | Page.pm | 162 that a result set is returned that is larger than we want to display 172 For example, say we wished to page through the integers from 1 to 100
|
/macosx-10.9.5/groff-38/groff/arch/djgpp/ |
H A D | config.bat | 63 Rem various Makefile install-foo targets, so we MUST have it before the
|
/macosx-10.9.5/ruby-104/ruby/ext/tk/sample/tkextlib/tile/themes/blue/ |
H A D | blue.tcl | 115 Horizontal.Scrollbar.thumb -side left -expand true -sticky we
|