Closed zquestz closed 7 years ago
Fixed, sorry about that.
Thanks for the speedy fix. =)
@davecheney, just out of curiosity, how did that compile? Where was print()
defined??
Not a worry, that was my mistake.
On Tue, 27 Sep 2016, 08:39 Josh Ellithorpe notifications@github.com wrote:
Thanks for the speedy fix. =)
— You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/davecheney/httpstat/issues/73#issuecomment-249718456, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAcA0lVdHwVcymObMz3-SKelgBL1WY_ks5quEmegaJpZM4KHELS .
facepalm
Nevermind. Forgot that print
and println
are part the Go core spec. I never use them when I probably should!
print is a builtin
On Tue, 27 Sep 2016, 08:40 Cameron Moore notifications@github.com wrote:
@davecheney https://github.com/davecheney, just out of curiosity, how did that compile? Where was print() defined??
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/davecheney/httpstat/issues/73#issuecomment-249718643, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAcA8bn4wPIdldBuO0TpORQt_21BZs9ks5quEnbgaJpZM4KHELS .
Notice this in my testing.
If you query with https then the output looks right.