Joel Riedesel wrote:
In ProtocolManager.cs there is a sort occuring of the fields in a packet
block.
Why is that being done?
Is the wire format not as the fields are shown in the message template
file? And if not, it's based on this somewhat odd sort definition?
Thanks,
Joel
The latest message template doesn't require any post-sorting. I will
have to take a look at that specific code, but the most likely scenario
is mapgenerator is taking care of things enough on its own that nothing
is actually calling that ProtocolManager.cs code any more. Either way it
should be updated to reflect the latest protocol so things like sldump
(which have an optional mode that utilizes that code) continue to work
correctly.
John
_______________________________________________
libsl-dev mailing list
libsl-dev@opensecondlife.org
http://opensecondlife.org/cgi-bin/mailman/listinfo/libsl-dev
