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.

Sign up for GitHub

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

Jump to bottom

socket:connected() always throws a "Null pointer" error #16

Open

MarkerB opened this issue Mar 17, 2019 · 0 comments

MarkerB commented Mar 17, 2019 •

edited

Loading

This bit of sample code from the docs always fails with a "Null pointer" error:

local s = require("socket").new();
print(s:connected()); -- false

Running on Windows 10, Unified Remote version 3.6.1.2342 (45)

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment