Skip to content

Review the decision to refer to com-ports by name #5

@tarefa

Description

@tarefa

This was designed as a convenience for use at the REPL.

It isn't idiomatic Clojure but we are already dealing with I/O here: global resources (global to the OS, not just Clojure instance or even the JVM) which are not only stateful, they mutate outside our control.

Is there a better abstraction I can use?

Should I ensure the implementation details don't leak out (all public functions to return explicit return values or nil if they are purely side-effectual)? In that case, do I need functions to retrieve the baud rate, parity setting, etc?

Metadata

Metadata

Assignees

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions