Nope, per the updated RFC (2812 for client, as this is what I look at the most), you have the following lines:
chanstring = %x01-07 / %x08-09 / %x0B-0C / %x0E-1F / %x21-2B
chanstring =/ %x2D-39 / %x3B-FF
; any octet except NUL, BELL, CR, LF, " ", "," and ":"
As long as the channel starts with "#", "+", or "&", and doesn't contain those characters mentioned, you shouldn't have a problem (with most networks only likeing the "#")
Anyway, just did /join #06all_your_base and was fine, so I for me, the bug didn't happen.
But not all networks may like it, but they are valid codes.
