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.

Sign up for GitHub

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

Jump to bottom

Java Tokenizer should be extracted from receiver, so Client can be specific about dependencies #159

Closed
susanw1 opened this issue Aug 10, 2024 · 0 comments · Fixed by #160
Closed

Java Tokenizer should be extracted from receiver, so Client can be specific about dependencies #159

susanw1 opened this issue Aug 10, 2024 · 0 comments · Fixed by #160
Assignees
@susanw1

Comments

@susanw1
Copy link
Owner

susanw1 commented Aug 10, 2024

At the moment, Java Receiver contains the Tokenizer, which means you can't see what the Client code is really using. At the moment, it could be using the entire Java executor. If we extract it, then it becomes clearer.
@susanw1 susanw1 self-assigned this Aug 10, 2024
susanw1 added a commit that referenced this issue Aug 10, 2024
@susanw1
[#159] Moved Java Tokenizer to its own module
332407d
@susanw1 susanw1 linked a pull request Aug 10, 2024 that will close this issue
[#159] Moved Java Tokenizer to its own module #160
Merged
susanw1 added a commit that referenced this issue Aug 10, 2024
@susanw1
[#159] Moved Java Tokenizer to its own module
fcef505
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@susanw1 susanw1

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#159] Moved Java Tokenizer to its own module susanw1/zscript
1 participant
@susanw1