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

Replace ':' with '/' as default port separation syntax for Tcl addbot syntax #476

Open
vanosg opened this Issue Nov 10, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@vanosg
Collaborator

vanosg commented Nov 10, 2017

Make using /s for port separation the default documented method for IPv4 and IPv6, still leaving the current : support in code to maintain backwards compatibility. See #470 for background.

@vanosg vanosg added this to the v1.9.0 milestone Nov 10, 2017

@vanosg vanosg changed the title from Replace ':' with '/' as default port separation syntax for +bot syntax to Replace ':' with '/' as default port separation syntax for Tcl addbot syntax Nov 10, 2017

@Cizzle

This comment has been minimized.

Show comment
Hide comment
@Cizzle

Cizzle Nov 29, 2017

Member

Would be slightly more consistent with the +bot and chaddr partyline commands. Whatever is decided (and I think related previous discussion favoured spaces), best to be consistent all over. Would that be for 1.9 or 2.0?

Member

Cizzle commented Nov 29, 2017

Would be slightly more consistent with the +bot and chaddr partyline commands. Whatever is decided (and I think related previous discussion favoured spaces), best to be consistent all over. Would that be for 1.9 or 2.0?

@vanosg

This comment has been minimized.

Show comment
Hide comment
@vanosg

vanosg Nov 30, 2017

Collaborator

Agreed, spaces would standardize a bit more. If we wanted to pursue this, I would propose:

  • Accepting spaces or :s in 1.8.x (remove /s all together, as we haven't published the /s as a standard in 1.8 yet)
  • Making spaces default in 1.9.0, still allow :s
  • Removing :s in 2.0
Collaborator

vanosg commented Nov 30, 2017

Agreed, spaces would standardize a bit more. If we wanted to pursue this, I would propose:

  • Accepting spaces or :s in 1.8.x (remove /s all together, as we haven't published the /s as a standard in 1.8 yet)
  • Making spaces default in 1.9.0, still allow :s
  • Removing :s in 2.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment