00:01 <SeanTAllen> if its similar enough to freebsd, it should be an easy port

00:01 <SeanTAllen> i tried to do netbsd this weekend

00:01 <SeanTAllen> and decided to wait until netbsd 8 is released as it will make it easier

00:02 <achamber1> im not too sure openbsd will be as easy as the others

00:02 <SeanTAllen> i dont think it will either

00:02 <achamber1> I tried to port it myself and hit an issue with __thread not being supported

00:02 <achamber1> thread local variables

00:02 <SeanTAllen> o boy!

00:02 <achamber1> i don't know if the next release supports it for clang since they changed compiler.

00:02 <achamber1> yaeh :D

00:03 <achamber1> the super old gcc they used to use might emulate thread locals, but ... it was missing a ton of headers

00:04 <achamber1> I will try again on the next release next.

01:55 <achamber1> yay, it looks like the new openbsd default compiler might work! :P

01:55 <achamber1> i will try do a port

12:35 <SeanTAllen> A new "Last Week in Pony" is out... https://www.ponylang.org/blog/2017/08/last-week-in-pony---august-27-2017/

20:21 <vaninwagen> go home pony, you are drunk: http://playground.ponylang.org/?gist=3aedc58eadfca46c5c0133fa2af4a703 (⊙.☉)7

20:30 <jemc> vaninwagen: pony doesn't currently support unicode in your source code, including string literals

20:31 <jemc> the first three seem mathematically correct, though I must admit I'm surprised to learn that you're allowed to specify multiple (or zero) bytes in a character literal at all

20:32 <vaninwagen> jemc: yeah, me too. i am about to open an issue.

20:33 <vaninwagen> i was surprised that the lexer takes the lowest 8 bytes of each character/escape sequence and just shifts the rest to the left :)

20:34 <vaninwagen> jemc: concerning unicode: this works http://playground.ponylang.org/?gist=66ac53a3bb14f62f446740feca6e4af0

20:39 <vaninwagen> i guess only if the source code is proper utf8

20:50 <vaninwagen> jemc i am puzzled. the compiler is nicely accepting all kinds of unicode i give him inside double quotes and prints them nicely. (terminal and file all utf8)

21:05 <SeanTAllen> vaninwagen: so i had this conversation with someone on here. when you print, you are going through a c funtions and will lose null terminator characters accordingly

21:06 <SeanTAllen> pony will happily accept a string with multiple zero bytes but c is going to kill them

21:07 <SeanTAllen> this could be addressed, if you care to PR it. it might take a bit of inventive-ness and we wouldn't want to harm performance.

21:07 <SeanTAllen> its never been a concern of mine when programming c, so there might be an easy way to address. not sure.

21:09 <vaninwagen> SeanTAllen but utf-8 does not have any 0 bytes but the actual 0 , right? so if my source code is proper utf-8 pony should be able to handle every unicode i give it without swallowing anything when printing, right?

21:10 <vaninwagen> SeanTAllen jemc sorry for my stubbornness but i am writing a tutorial section about literals and needed to find out myself what is possible and what not

21:11 <SeanTAllen> https://github.com/ponylang/ponyc/blob/master/src/libponyrt/lang/stdfd.c#L518

21:11 <SeanTAllen> https://github.com/ponylang/ponyc/blob/master/src/libponyrt/lang/stdfd.c#L510

21:12 <SeanTAllen> your print is going through the 2nd one

21:12 <SeanTAllen> and your null terminators will disappear

21:15 <SeanTAllen> beyond the c functions that thing go through for printing. pony is probably pretty agonstic about what is in a string.

21:15 <SeanTAllen> if strings correcting accept utf-8 unicode (which they should), i think its reasonable for string literals to do that as well.

21:15 <SeanTAllen> im not sure if that answers your question at all

21:15 <vaninwagen> SeanTAllen it gets very very close :)

21:17 <vaninwagen> if everyone, including the tutorial, says that pony does not support unicode/utf-8, how would support for unicode in string literals look like? guessing the file encoding and translating it to utf-8?

21:18 <SeanTAllen> i think "doesn't support unicode" needs to be cleared p

21:18 <SeanTAllen> pony strings dont carry any encoding info

21:18 <SeanTAllen> so you can do pretty much anything you want with them

21:18 <SeanTAllen> Pony source code expects to be given ASCII.

21:19 <vaninwagen> SeanTAllen, that was my impression as well :)

21:19 <SeanTAllen> so you can use unicode for identifiers etc

21:19 <SeanTAllen> err

21:19 <SeanTAllen> cant

21:19 <SeanTAllen> pony source code has to be ascii

21:19 <SeanTAllen> thats rather different than "pony does not support unicode"

21:19 <SeanTAllen> now

21:19 <SeanTAllen> how that works with string literals

21:20 <SeanTAllen> thats an interesting question

21:20 <vaninwagen> SeanTAllen, let me clarify that in the tutorial, while i am an at it :)

21:20 <SeanTAllen> i'm going with, string literals are special and ascii

21:20 <SeanTAllen> and i have no idea how unicode would work in them but its a good sync/rfc conversation

21:20 <vaninwagen> SeanTAllen fully agree

23:05 <achamber1> Writing pony does make me rethink how I design code. its a different mindset to Go.

23:06 <SeanTAllen> i believe it achamber1

23:07 <SeanTAllen> would you be up for doing a My First Pony blog post?

23:07 <SeanTAllen> I'm trying to capture people's early impressions, the good, the bad

23:07 <SeanTAllen> your comment sounds like an excellent basis for a post

23:16 <achamber1> I can try, I had intended to write the same application in both Go and pony as a comparison and write about that.

23:16 <achamber1> but it might take a while haha.

23:17 <SeanTAllen> the how to section has some useful info on getting going...

23:17 <SeanTAllen> https://github.com/ponylang/ponylang.github.io/blob/master/HOW_TO.md

23:17 <SeanTAllen> you can always write a follow up

23:17 <SeanTAllen> i think the "early impressions" posts are very good

23:18 <SeanTAllen> its nice to capture both early excitement and frustration

23:18 <achamber1> Cool, will do.