Splatoon 2: Difference between revisions

No edit summary
Line 12: Line 12:
* A bunch of funcs had {clamp to max value} added:
* A bunch of funcs had {clamp to max value} added:
** This is done with <code>enl::ContentTransporterCommon<enl::SystemInformation>::readyReceiveStream()</code> and <code>enl::ContentTransporterCommon<enl::SystemRequestInfo>::readyReceiveStream()</code>. These funcs call <code>sead::ReadStream::readMemBlock</code>, with the returned value now being clamped to a max value.
** This is done with <code>enl::ContentTransporterCommon<enl::SystemInformation>::readyReceiveStream()</code> and <code>enl::ContentTransporterCommon<enl::SystemRequestInfo>::readyReceiveStream()</code>. These funcs call <code>sead::ReadStream::readMemBlock</code>, with the returned value now being clamped to a max value.
** <nowiki>enl::PiaTransportManager::receiveFromLib()</nowiki>: Now clamps the output size returned by <code>nn::pia::transport::UnreliableProtocol::Receive()</code> against the input size which was passed to Receive(), instead of using it directly.
** <code>enl::PiaTransportManager::receiveFromLib()</code>: Now clamps the output size returned by <code>nn::pia::transport::UnreliableProtocol::Receive()</code> against the input size which was passed to Receive(), instead of using it directly.
** Two sets of two deconstructors now have value clamping: <code><enl::WriteStream::~WriteStream()></code> and <code><enl::RamWriteStream::~RamWriteStream()></code>.
** Two sets of two deconstructors now have value clamping: <code><enl::WriteStream::~WriteStream()></code> and <code><enl::RamWriteStream::~RamWriteStream()></code>.
* <code>enl::TransportManager::updateReceiveBuffer_()</code>:
* <code>enl::TransportManager::updateReceiveBuffer_()</code>: