Yeah /not crashing/ is good. Although you can also "not crash" more elegantly by treating oversized data we can't store as invalid, so store that as empty; length zero or something indicating a definite overflow. Which sounds better than storing truncated (and thus confusingly invalid) data.
Yeah /not crashing/ is good. Although you can also "not crash" more elegantly by treating oversized data we can't store as invalid, so store that as empty; length zero or something indicating a definite overflow. Which sounds better than storing truncated (and thus confusingly invalid) data.