Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better unexpected message behaviour for methods with self-sends #38

Open
dionisiydk opened this issue Dec 20, 2022 · 0 comments
Open

Better unexpected message behaviour for methods with self-sends #38

dionisiydk opened this issue Dec 20, 2022 · 0 comments

Comments

@dionisiydk
Copy link
Owner

The following test shows the issue:

MockAcceptanceTests>>testUnexpectedMessageDefinedInObjectUsingAnotherObjectMethod
	| actual |	
	actual := mock printString.
	
	actual should be: 'a GHEmptyMetaMessages'

The unexpected message leads to #stubDoesNotExpect: hook which is trying to use Object real methods as default action to handle the message. It does not work well for Object methods with self sends.
Possible improvement would be to use standard meta level for meta messages sent under deep meta call (which is happens in the example).

@dionisiydk dionisiydk changed the title Better unexpected message behaviour for complex method defined in Object Better unexpected message behaviour for methods with self-sends Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant