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

Standard Java I/O on physical vehicle #53

Open
arndtjonasson opened this issue Feb 27, 2015 · 2 comments
Open

Standard Java I/O on physical vehicle #53

arndtjonasson opened this issue Feb 27, 2015 · 2 comments

Comments

@arndtjonasson
Copy link
Collaborator

Try to make System.out.println in apps do something on the actual car. Now it is ignored, and output must be made some other way (does that work in the simulator?)

@arndtjonasson arndtjonasson changed the title Standard Java I/O on vehicle Standard Java I/O on physical vehicle Feb 27, 2015
@arndtjonasson
Copy link
Collaborator Author

I think the answer to the question above is that the proper way to do it is by VM.print, and that this works by virtue of methods in simulator/squawk which do System.out.println in the case of simulator, while the car implementation is in squawk/.../VM.java.

One plugin which uses VM.print is SemiAutomaticReverseParking.

@arndtjonasson
Copy link
Collaborator Author

As long as System.out is ignored in autosar, the proper thing to do is to use VM.print everywhere, but it would also be nice to be able to use plugin code outside the moped framework without changing the I/O functions.

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