[Seaside-dev] Issue 320 in seaside: WAMutex portability

[codesite-noreply at google.com]

Comment #6 on issue 320 by wembley.instantiations: WAMutex portability
http://code.google.com/p/seaside/issues/detail?id=320

I don't think you completely misunderstand the reason for WAPlatform and its
subclasses, but I do think you are missing a subtle distinction.  The  
difference
between #reducedConflictDictionary, #doTransaction:, etc. and  
#isProcessTerminated:
is that the former methods are portable across ALL platforms (that is, they  
do not
refer to any class or method that is not available on all platforms) --  
that's why
there are so few methods with actual implementations.  They might not  
provide the
correct (or optimal) implementation for a particular platform, in which  
case the
platform subclass will override them.

The issue is not whether the supplied code will execute on VA Smalltalk --  
I don't
expect it to.  The issue also is not whether it will load on VA Smalltalk  
-- it will.
The issue is that every time someone browses WAPlatform in VA Smalltalk,  
this method
is red with a warning icon because it is not implemented.  This is the one  
and only
method in the whole Seaside set of packages that shows as red in our  
browser.  So, to
fix this, I will have to implement Process>>#isTerminated.  Now I don't  
mind doing
that -- I've added a whole lot of methods to support running Seaside on VA  
Smalltalk
-- but it doesn't seem to be in the spirit of WAPlatform for me to have to  
do that
for an acknowledged platform-dependent method.



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings