Custom Query (257 matches)
Results (25 - 27 of 257)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #235 | ph3-der-loewe | ph3-der-loewe | fixed | roar_err_from_errno() and friends should handle win32 error codes |
| Description |
roar_err_from_errno() and friends should handle win32 error codes (converting them to RA error codes). |
|||
| #237 | ph3-der-loewe | chrysn | fixed | command line arguments for rpld-* |
| Description |
rpld-play & co don't respond to --help being passed, as it is common with unix tools. those tools that require arguments (eg rpld-import) give meaningless error messages when called without arguments instead of presenting a usage message. to the best of my knowledge, perl modules exist that make that feature quite easy to implement. in the course of that, it might be useful to parse generic rpld options as well (eg to specify a socket/tcp destination of the server, in case different servers are run in a network). |
|||
| #241 | ph3-der-loewe | fixed | Add tests for arumentlist to be present | |
| Description |
The simple protocol driver module should check if the argument list is present in all commands using it. This should be done using an universal macro so there is only one location of possible errors. This is strictly speaking not needed, it should just avoid errors in per-command code not checking correctly. A protocol error should be returned in case of a missing argument list on commands needing one. |
|||
