Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgraded from 2.x to 4.x, missing length #57

Open
alexgorbatchev opened this issue Aug 8, 2015 · 3 comments
Open

Upgraded from 2.x to 4.x, missing length #57

alexgorbatchev opened this issue Aug 8, 2015 · 3 comments

Comments

@alexgorbatchev
Copy link

Hey friends,

I've just upgraded from 2.x to 4.x and now my buffers are missing length property... is that expected? What's the alternative I should be using?

@dcodeIO
Copy link
Member

dcodeIO commented Aug 8, 2015

length was a bit misleading and this property has been renamed to limit with 3.X.

@alexgorbatchev
Copy link
Author

Thanks for pointing that out. Curious if they can be used interchangeably?
It doesn't feel like the same thing at first glance.

On Fri, Aug 7, 2015, 17:36 Daniel Wirtz [email protected] wrote:

This property has been renamed to limit with 3.X.


Reply to this email directly or view it on GitHub
#57 (comment)
.

@englercj
Copy link

length implies the underlying buffer is of that length, which it isn't necessarily. limit is more accurate as it is the largest index at which the ByteBuffer will read to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants