Out on HF and heard nobody, but didn't call CQ? Nobody heard you either. 73 de N7GH
Les Morgan wrote:looks like you have a pretty good solution there just by order the rules by the index, 2nd to last digit of rules.
There are three kinds of actuaries: those who can count, and those who can't.
Piet Souris wrote:hi Alfa,
a way to automize this, although it is not a very efficient way, is to note that (in this case) the sorting order is: 6, 8, 3, 2.
So we can use a Comparator to sort the array. For instance:
There are three kinds of actuaries: those who can count, and those who can't.
There are three kinds of actuaries: those who can count, and those who can't.
There are three kinds of actuaries: those who can count, and those who can't.
Another idea for a design:
The original employee items are saved in a list.
Each employee record has a list of its own that contains the employees that must follow.
When a processAfter rule comes in, the referenced employee is removed from the original list and added to the individual employee's list.
There are three kinds of actuaries: those who can count, and those who can't.
There are three kinds of actuaries: those who can count, and those who can't.
Norm Radder wrote:What is the purpose of the statements on lines 34 to 36?
It looks like the code is hardcoded for ONE order of events. What happens when the ordering is different?
Norm Radder wrote:Why recursive? Would a loop do?
Norm Radder wrote:loop through the list item by item
if an item has a list, loop through the items in that list
Norm Radder wrote:Right, if followers can have followers that have followers etc.
Back to the drawing board.
Does the currently posted code support that?
There are three kinds of actuaries: those who can count, and those who can't.