Searched refs:after_list (Results 1 - 3 of 3) sorted by relevance
/macosx-10.10.1/ncurses-44/ncurses/ncurses/tinfo/ |
H A D | comp_scan.c | 345 char *after_list; local 456 after_list = 0; 461 after_list = tok_ptr; 529 if (after_list != 0) { 531 if (*after_list == '\0') 533 else if (strchr(after_list, ' ') == 0) 537 after_list = tok_buf + strlen(tok_buf); 546 for (s = tok_buf; s < after_list; ++s) {
|
/macosx-10.10.1/ruby-106/ruby/test/minitest/ |
H A D | test_minitest_spec.rb | 598 after_list = [] 601 after { after_list << 1 } 607 after { after_list << 2 } 612 after { after_list << 3 } 621 return x, y, z, before_list, after_list 678 _, _, z, before_list, after_list = util_structure 689 assert_equal [3, 2, 1], after_list
|
/macosx-10.10.1/emacs-93/emacs/src/ |
H A D | buffer.c | 3398 struct Lisp_Overlay *before_list, *after_list; 3399 /* These are either nil, indicating that before_list or after_list 3410 The loop invariant is that before_list (resp. after_list) is a 3413 (after_list) if it is, is still uninitialized. So it's not a bug 3442 after_list = tail; 3488 after_list = tail; 3523 current_buffer->overlays_after = after_list; 3381 struct Lisp_Overlay *before_list, *after_list; local
|
Completed in 157 milliseconds