find_next_occupant vs. autonext_unit

[Hans Ronne]

>> Never seen this happen in the mac interface, but it uses
>> find_next_awake_mover instead of autonext_unit.
>
>Am I misreading the mac code?  Seems like maybe_select_next_unit in
>macconq.c will call autonext_unit first and only then
>find_next_awake_mover.

Both interfaces call autonext_unit_inbox first, which is not the same thing
as autonext_unit. The unix code then goes on to call autonext_unit, while
the mac code calls find_next_awake_mover instead.

I understood the problem was with autonext_unit, but if it is
autonext_unit_inbox that is the culprit, you would of course expect the two
interfaces to behave the same.

Hans

Hans Ronne

hronne@pp.sbbs.se