This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In HF EIB book, when describing the method call stack in transactions, a flow chart is often used, Method 1 (tx) --> Method 2(tx) -->Method 3 (tx) \\--> Method 4 (tx) \--> Method 5 (tx) For the first line, it means method 1 calls method2 and method 2 calls method 3, then method 3 returns and method 2 returns. But how about the second and third line?
Hi Boyan, Sorry that those diagrams weren't a little clearer! Here's what they mean: If you see multiple methods on the same line, they are nested, i.e. method 1 calls method 2, which calls method 3, which calls method 4... If you see something like this (excuse the ascii art) :
It means, m1 calls m2, once m2 completes, m1 calls m3, once m3 completes, m1 calls m4 Hope that helps. Bert [ December 30, 2003: Message edited by: Bert Bates ] [ December 30, 2003: Message edited by: Bert Bates ] [ December 30, 2003: Message edited by: Bert Bates ]
Spot false dilemmas now, ask me how!
(If you're not on the edge, you're taking up too much room.)