View Issue Details

IDProjectCategoryView StatusLast Update
0000071LDMud 3.3Networkingpublic2018-01-29 21:57
Reporterlynx Assigned ToGnomi  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.3.718 
Target Version3.3.719Fixed in Version3.3.719 
Summary0000071: binary_message cannot flush zero bytes?
Descriptionis this intended behaviour or a bug:

when using flag "1" with binary_message
zero bytes contained in the data will be
filtered, no matter if given as string or
int*

in fact i don't feel like the binmsg doc
is absolutely clear on the meaning of its
flags..

thanx
TagsNo tags attached.

Activities

Gnomi

2009-05-19 16:33

manager   ~0001123

Hmm, that's because of the connection charset. Regardless of the given bitvector, \0 and \n are always removed from it. (\n is treated specially in add_message.)
I don't see any necessity for removing \0. Any opinions on allowing \0 in a connection charset?

Gnomi

2009-05-21 05:48

manager   ~0001126

I stand corrected, there's a special condition for binary_message that a character has to be != 0. I think that condition can be removed, too.

Gnomi

2009-05-27 14:03

manager   ~0001170

I fixed this in r2597.

Issue History

Date Modified Username Field Change
2004-06-18 00:29 lynx New Issue
2009-05-19 16:33 Gnomi Note Added: 0001123
2009-05-20 11:31 Gnomi Assigned To => Gnomi
2009-05-20 11:31 Gnomi Status new => assigned
2009-05-20 11:31 Gnomi Product Version => 3.3.718
2009-05-20 11:31 Gnomi Target Version => 3.3.719
2009-05-21 05:48 Gnomi Note Added: 0001126
2009-05-27 14:03 Gnomi Note Added: 0001170
2009-05-27 14:03 Gnomi Status assigned => resolved
2009-05-27 14:03 Gnomi Fixed in Version => 3.3.719
2009-05-27 14:03 Gnomi Resolution open => fixed
2010-11-16 09:42 Gnomi Source_changeset_attached => ldmud.git master e7f9574e
2018-01-29 18:59 Gnomi Source_changeset_attached => ldmud.git master e7f9574e
2018-01-29 21:57 Gnomi Source_changeset_attached => ldmud.git master e7f9574e