Difference between revisions of "Talk:GetSetupSetting"

From WikiPrizm
Jump to navigationJump to search
(Created page with "This syscall doesn't modify setup settings, so the comment about accidentally overwriting a byte that doesn't belong to the setup makes no sense. At most, by providing an out-...")
 
 
Line 1: Line 1:
 
This syscall doesn't modify setup settings, so the comment about accidentally overwriting a byte that doesn't belong to the setup makes no sense. At most, by providing an out-of-bounds index, one will get an out-of-bounds value, which is not unexpected and will cause no damage. --[[User:Gbl08ma|Gbl08ma]] ([[User talk:Gbl08ma|talk]]) 16:19, 14 February 2015 (EST)
 
This syscall doesn't modify setup settings, so the comment about accidentally overwriting a byte that doesn't belong to the setup makes no sense. At most, by providing an out-of-bounds index, one will get an out-of-bounds value, which is not unexpected and will cause no damage. --[[User:Gbl08ma|Gbl08ma]] ([[User talk:Gbl08ma|talk]]) 16:19, 14 February 2015 (EST)
 +
 +
That comment was meant for SetSetupSetting. I will fix it now [[User:ProgrammerNerd|ProgrammerNerd]] ([[User talk:ProgrammerNerd|talk]])

Latest revision as of 20:58, 14 February 2015

This syscall doesn't modify setup settings, so the comment about accidentally overwriting a byte that doesn't belong to the setup makes no sense. At most, by providing an out-of-bounds index, one will get an out-of-bounds value, which is not unexpected and will cause no damage. --Gbl08ma (talk) 16:19, 14 February 2015 (EST)

That comment was meant for SetSetupSetting. I will fix it now ProgrammerNerd (talk)