My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 3: streamlining Funcito object
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  codeto...@gmail.com
Closed:  Dec 2011


 
Project Member Reported by codeto...@gmail.com, Nov 19, 2011
The Funcito.java object is clearly a keystone of the API for clients. This raises the following questions:

Q: will clients ever call getInvocationManager()?

If not, I think it should be removed from this class.

Q: Given callsTo(), will clients ever call stub()?

If not, I think stub() should not be public.


Nov 19, 2011
Project Member #1 kandpwel...@gmail.com
(No comment was entered for this change.)
Labels: Type-Design
Nov 22, 2011
Project Member #2 kandpwel...@gmail.com
(No comment was entered for this change.)
Labels: Priority-High Usability Maintainability
Nov 24, 2011
Project Member #3 codeto...@gmail.com
Submitted and ready for review
Nov 24, 2011
Project Member #4 codeto...@gmail.com
changing status. I would like to see less static in FunctionDelegate, but that might be a new issue (or related to thread-safety).
Status: CodeComplete
Nov 29, 2011
Project Member #5 kandpwel...@gmail.com
I got rid of Funcito.stub()
Dec 6, 2011
Project Member #6 kandpwel...@gmail.com
I think we can cal this one done
Status: Fixed
Owner: codeto...@gmail.com

Powered by Google Project Hosting