retrun value (thread id) for seq()

["Kim, Kukhee" <khkim@slac.stanford.edu>]

Hi Benjamin and everyone;

The seq() has returned the thread id in the previous version, but it does not return the thread id anymore in the new the implementation.
We know that, if there are multiple state sets in the SNL program, then the seq() creates multiple threads which are corresponded to each state set. So, the thread id returning is not meaningful, it only shows the thread id for the first one.

But, the thread id returning is still valid for single state set, and also need to consider for the backward compatibility.
One of our colleague in SLAC has used the thread id returning from the seq(), and has trouble now with the new implementation of the seq().

I am wondering, if someone else uses the thread id returning.
And, I would like to discuss, if we can switch it back to the old way.
Even, the seq() returns the thread id, it is not harmful and we can keep the backward compatibility.

Please, give me your advice.


Thank you.
Best regards,
Kukhee
-------------------------------------------
Kukhee Kim
SLAC National Accelerator Laboratory
2575 Sand Hill Rd, MS 64
Menlo Park, CA 94025
Email: khkim@SLAC.Stanford.EDU
Phone: (650)926-4912