aboutsummaryrefslogtreecommitdiff
path: root/examples/fifop.pd
diff options
context:
space:
mode:
Diffstat (limited to 'examples/fifop.pd')
-rw-r--r--examples/fifop.pd38
1 files changed, 0 insertions, 38 deletions
diff --git a/examples/fifop.pd b/examples/fifop.pd
deleted file mode 100644
index b1546c0..0000000
--- a/examples/fifop.pd
+++ /dev/null
@@ -1,38 +0,0 @@
-#N canvas 432 159 587 516 10;
-#X text 471 31 part of;
-#X obj 533 30 zexy;
-#X msg 58 85 1 2 3 4 5;
-#X msg 69 110 list a list;
-#X msg 81 137 5;
-#X msg 199 97 bang;
-#X floatatom 200 133 5 0 0 1 priority - -;
-#X text 45 61 input lists;
-#X text 50 400 priorities can be floating-point numbers (1.8 has a
-higher priority then 10);
-#X obj 58 192 fifop;
-#X text 47 18 fifop:: First-In-First-Out stack with Priorities;
-#X text 247 80 bang to output the first list that came in \; bang again
-to output the second list \; and so on;
-#X text 54 263 [fifop] manages a number of FIFO-stacks \; each stack
-has a priority value assigned \; the lower the value \, the higher
-the priority;
-#X text 52 310 banging the object will first empty the FIFO with the
-highest priority \, then the FIFO with the second highest priority
-and so on \, until the FIFO with the lowest priority is emptied.;
-#X text 51 368 when all FIFOs are emptied \, nothing will come out
-of the object any more.;
-#X obj 58 223 print FIFO;
-#X text 52 445 note: you can store any number of lists into the [fifop]
-\, but just pushing lists on the stack without popping them back will
-eat your memory.;
-#X msg 201 159 info;
-#X text 247 158 query the number of arguments in the LIFO;
-#X obj 156 209 print info;
-#X connect 2 0 9 0;
-#X connect 3 0 9 0;
-#X connect 4 0 9 0;
-#X connect 5 0 9 0;
-#X connect 6 0 9 1;
-#X connect 9 0 15 0;
-#X connect 9 1 19 0;
-#X connect 17 0 9 0;