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

Calling UDPSocket functions in REPL causes error. #14552

Open
abhijithanilkumar opened this issue Jan 3, 2016 · 8 comments
Open

Calling UDPSocket functions in REPL causes error. #14552

abhijithanilkumar opened this issue Jan 3, 2016 · 8 comments
Labels

Comments

@abhijithanilkumar
Copy link
Contributor

It seems the following UDPSocket functions are broken.

julia> nb_available(s)
ERROR: type UDPSocket has no field buffer
 in nb_available at stream.jl:254

julia> isreadable(s);
ERROR: type UDPSocket has no field buffer
 in isreadable at stream.jl:243

julia> isopen(s);
ERROR: type UDPSocket has no field buffer
 in print at strings/io.jl:8
 in print_to_string at strings/io.jl:36
 in isopen at stream.jl:317
@yuyichao
Copy link
Contributor

yuyichao commented Jan 3, 2016

Didn't you fix this in #14325 ?

@tkelman
Copy link
Contributor

tkelman commented Jan 3, 2016

That was where the errors were initially reported, but that PR only fixed show.

@abhijithanilkumar
Copy link
Contributor Author

What message has to be displayed for these functions? @tkelman

@tkelman
Copy link
Contributor

tkelman commented Mar 11, 2016

I'm having trouble finding the last discussion on this with @JeffBezanson and @vtjnash but the conclusion was that the hierarchy of IO types probably needs some rearranging given this type doesn't support the stream interface.

@abhijithanilkumar
Copy link
Contributor Author

Is this the discussion?

@kshyatt
Copy link
Contributor

kshyatt commented May 10, 2016

I'm bumping this - @abhijithanilkumar and @tkelman, was that the discussion? Can we add these in? Is this still a problem?

@tkelman
Copy link
Contributor

tkelman commented May 10, 2016

Happened in a few other places as well. There's some rearrangement of the IO type hierarchy that's still an outstanding TODO here, things are grouped in a funny way where some subtypes of the same abstract type don't implement the same interface at all. But I don't think this needs to happen before 0.5.

@vtjnash
Copy link
Member

vtjnash commented May 10, 2016

the main fix probably required here is that UDPSocket isn't really an IO (stream/file) type

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

No branches or pull requests

6 participants