Need how to: Non Block-nested critical regions

[TriSebastian]

Hi!

I need to implements a logik like this C# routine:

Monitor.Enter(monitor);
...do something...
if (childCount > 0) {
Monitor.Enter(childMonitor);
Monitor.Exit(monitor);
... do something...
Monitor.Exit(childMonitor);
}
else {
Monitor.Exit(monitor);
}

I'm not sure whether this is the same in VASmalltalk:

|lock childlock|
lock := Semaphore forMutualExclusion.
childlock := Semaphore forMutualExclusion.

lock critical: [
.... do something...
self childCount > 0
ifTrue:[
childlock critical: [... do something...].
]
].

In Smalltalk/X there's a similar implementation of Monitor like in .Net but I didn't surely find on in VASmalltalk.

Any advice?

Thanks!
Sebastian

[tc]

The two pieces of code look equivalent if the 'do something' in your code is creating other processes. If not then the code does not make sense because when you enter the first critical block, all other processes have to wait and the second critical block is not needed.

If the first critical block entered creates other processes that must wait then the second critical block makes more sense.

--tc

[TriSebastian]

Thanks tc,

yes they do!

I need to implement a server client session logging framework, having several loggers for on session and additional to that some loggers are shared between several sessions.....

But any way.
How could I implement a logic, allowing a parent logger to add/receive new data into/for it's buffers, after he has called his children to log the actual given data.

Just change the blocks like that?
self lock critical: [... do something ...].
self hasChildren
ifTrue:[ self childlock critical:[... let children do something...]].

[marten]

Thanks tc,

yes they do!

I need to implement a server client session logging framework, having several loggers for on session and additional to that some loggers are shared between several sessions.....

But any way.
How could I implement a logic, allowing a parent logger to add/receive new data into/for it's buffers, after he has called his children to log the actual given data.

Just change the blocks like that?
self lock critical: [... do something ...].
self hasChildren
ifTrue:[ self childlock critical:[... let children do something...]].

Consider about using SstSharedQueues for data sharing between application logic and logger logic and each logger is an own process ...