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

static convenience methods for Printer #16

Closed
laforge49 opened this Issue Oct 3, 2013 · 4 comments

Comments

Projects
None yet
2 participants
@laforge49
Copy link
Owner

laforge49 commented Oct 3, 2013

Two static convenience methods on Printer would be nice:

public static SyncRequest<Void> printlnSReq(final Facility _facility, final String test) throws Exception;

and

public static SyncRequest<Void> printfSReq( final Facility _facility, final String _format, final Object... _args) throws Exception;

@laforge49

This comment has been minimized.

Copy link
Owner

laforge49 commented Oct 3, 2013

Taking this a step further, we can add these convenience methods to BladeBase:

public SyncRequest printlnSReq(final String test) throws Exception;

and

public SyncRequest printfSReq(final String _format, final Object... _args) throws Exception;

@skunkiferous

This comment has been minimized.

Copy link
Collaborator

skunkiferous commented Oct 3, 2013

To be honest, I don't think this belongs in BladeBase, because I don't think anyone is going to be using Printer apart from you ... Sorry.

@laforge49

This comment has been minimized.

Copy link
Owner

laforge49 commented Oct 3, 2013

I have also had second thoughts about inclusion in BladeBase. Because you only get the benefit if you use signal rather than send. Plus, BladeBase needs to be kept small, as the code needs to be replicated for alternate bases.

@laforge49

This comment has been minimized.

Copy link
Owner

laforge49 commented Oct 6, 2013

Also changed stdoutAReq to stdoutSReq.

closed: 869c1b2

@laforge49 laforge49 closed this Oct 6, 2013

@ghost ghost assigned laforge49 Oct 22, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment