• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

The meaning of \--->

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
author
Posts: 9050
21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 ]
 
reply
    Bookmark Topic Watch Topic
  • New Topic