ELLIOTTCABLE changed the topic of #elliottcable to: a _better_ cult ˙ ͜ʟ˙ embrace, extend, extinguish.
oldskirt_ has quit [Ping timeout: 260 seconds]
Sorella has quit [Quit: Ex-Chat]
gozala has joined #elliottcable
alexgordon has quit [Quit: Textual IRC Client: www.textualapp.com]
eligrey has quit [Read error: Connection reset by peer]
gq has joined #elliottcable
eligrey has joined #elliottcable
<joelteon> what is it with libraries where you have to make CC="$CC"
<gq> -fingernails @ joelteon
<purr> joelteon: they're weird
<gq> heehe
<gq> srsly tho i don't know
<gq> hi again eligrey
<joelteon> just pick $CC out of the environment
<gq> i remember when eligrey was just a little sephr
* gq wipes a tear
<gq> they grow up so fast!!!!!1
<gq> -sephr
<purr> gq: sephr isn't a country and if he was a country his name isn't anguilla
<joelteon> it really sucks not to have a "gcc" binary doesn't it cocksuckers
<gq> excuse you. i only suck my husband's cock.
<gq> WHICH IS NONE OF YOUR BUSINESS OMFG WTF BBQ
* gq bored
<eligrey> play the vidya games
<eligrey> with eligrey
<gq> omg vidyas
<gq> -vidyas
<gq> -white goo
<purr> gq: dreeping down my strema
Sgeo has quit [Read error: Connection reset by peer]
Sgeo has joined #elliottcable
<gq> -fingernails
<purr> gq: they're weird
eligrey has quit [Quit: Leaving]
prophile has joined #elliottcable
gq has quit []
Sorella has joined #elliottcable
joelteon has quit [Remote host closed the connection]
joelteon has joined #elliottcable
nuck has quit [Ping timeout: 264 seconds]
nuck has joined #elliottcable
Sgeo has quit [Read error: Connection reset by peer]
gq has joined #elliottcable
<gq> -white goo
<purr> gq: dreeping down my strema
* gq shivers
gq has quit []
Rusky has quit [Ping timeout: 250 seconds]
Rusky has joined #elliottcable
Rusky has quit [Client Quit]
Rusky has joined #elliottcable
sharkbot has quit [Remote host closed the connection]
sharkbot has joined #elliottcable
vil has quit [Quit: :qa!]
jeannicolas has quit [Quit: ZNC - http://znc.in]
jeannicolas_ has joined #elliottcable
jeannicolas_ is now known as jeannicolas
alexgordon has joined #elliottcable
oldskirt has joined #elliottcable
eligrey has joined #elliottcable
oldskirt_ has joined #elliottcable
oldskirt has quit [Ping timeout: 272 seconds]
<purr\Paws> [Issues] ELLIOTTCABLE labeled issue #16: Add SSA to the Tires syntax https://github.com/Paws/Issues/issues/16
prophile has quit [Quit: The Game]
<ELLIOTTCABLE> devyn: Driving, can't really talk right now,
<ELLIOTTCABLE> but I'm back from Montana. ish.
<ELLIOTTCABLE> and diving back into Paws. or, more specifically, integrating Tires semantics into Paws, which is almost a completely new thing.
<ELLIOTTCABLE> solved some of the major problems I had with it on my drive(s), but, still got a couple.
<joelteon> guys, who's good at C++
<joelteon> anyone
<purr\Paws> [Issues] ELLIOTTCABLE opened issue #17: De-linearize executions https://github.com/Paws/Issues/issues/17
<ELLIOTTCABLE> joelteon: alexgordon.
<joelteon> alexgordon: hi
<joelteon> alexgordon: please you're my only hope
<alexgordon> hi ELLIOTTCABLE
<alexgordon> hi joelteon
<joelteon> hi
<purr> joelteon: hi!
<joelteon> alexgordon I have a question about C++
* alexgordon always likes some C++
<joelteon> cool
<joelteon> hang on i'll pastebin
<purr\Paws> [Issues] ELLIOTTCABLE comment on issue #17: The most obvious problem with this change, from where I'm standing, is that it, well, “breaks Executions.” The famous old move-foward Execution semantics upon which huge swaths of Paws' semantics depend make little or no sense here: an Execution can only ‘move forward’ to next node of a Script, if that Script is strictly linear (thus providing such a “next node” *to* move to.) With no
<alexgordon> joelteon: I always use -fno-exceptions so I might not be the best person to ask :P
<alexgordon> but I'll try
<joelteon> well this library likes exceptions
<alexgordon> joelteon: I think I see the problem
<joelteon> oh good
<alexgordon> lol
<purr> lol
<alexgordon> well I'm not sure, like I say I never use exceptions
<alexgordon> but you need to make them const references
<alexgordon> const nix::Exit& e
<joelteon> ok i'll try that
<joelteon> sec
<joelteon> i don't understand
<joelteon> okay
<joelteon> that didn't help
<alexgordon> damn
<alexgordon> try just making it
<alexgordon> nix::Exit e
<alexgordon> joelteon: a special feature in C++ is that if you pass a temporary object to a "const T&" then your code won't break
<alexgordon> because the temporary will be promoted to a variable with a lifetime exceeding that of the reference
<joelteon> okay, just so you know, this works as expected with g++ but not with clang++
<joelteon> and i'm using clang
<joelteon> okay, THAT didn't help either
<alexgordon> joelteon: whereas for T& (no const) there is no such guarantee, and the temporary may be destroyed before it ever gets to the reference
<joelteon> if I do a strcmp on typeid(e).name() and then cast it if strcmp succeeds, I get expected behavior :/
<joelteon> wtf is going on
<alexgordon> joelteon: std::exception has a virtual destructor
<alexgordon> that means it's not designed to be stack allocated
<joelteon> oh, i see
<alexgordon> or rather, it can be stack allocated, but...
<joelteon> it shouldn't be
<joelteon> it's not a good idea
<alexgordon> well possibly not with this interaction with exceptions
<alexgordon> I dunno
<alexgordon> I never use exceptions! :P
<joelteon> tell you what, clang fucking sucks
<joelteon> it doesn't accept nearly as much broken code as g++ does
<alexgordon> joelteon: but just try `throw new nix::Exit(0);`
<alexgordon> joelteon: LOL
<purr> LOL
<joelteon> like, last week i spent about 3 days debugging an error that came from this same guy that wrote this same library passing a stale stack pointer to something
<alexgordon> joelteon: you don't actually have to inherit from std::exception at all
<alexgordon> man C++ exception handling is broken as shit
<alexgordon> I tell you, -fno-exceptions is your god
<joelteon> and clang is like "ok, that's a temp variable, we'll just optimize it away" and g++ says "naw dude"
<joelteon> so then you get an execve() call half of whose arguments are null pointers
<alexgordon> heh
<joelteon> also, clang isn't called "gcc", and some libraries really hate that
<alexgordon> it makes it easy to spot the bad ones!
<joelteon> if only people would standardize an environment variable for which C compiler the user wants to use
<joelteon> they could call it $C_COMPILER
<purr\Paws> [Issues] ELLIOTTCABLE labeled issue #18: Create a system of addressable instructions https://github.com/Paws/Issues/issues/18
<joelteon> or $CC for short
<alexgordon> woah man
<joelteon> ok, new Exit doesn't help either
<alexgordon> clang's status page already has c++1z
<alexgordon> and everything there is implemented!
<alexgordon> granted, three of those things are easy
<ELLIOTTCABLE> devyn: phew.
<ELLIOTTCABLE> devyn: gotta get back on the road.
<ELLIOTTCABLE> devyn: have fun reading all that :P
<ELLIOTTCABLE> devyn: I recall there being something you wanted to talk about right about when I got to Montana, but I don't remember what it was.
<ELLIOTTCABLE> devyn: you'd solved some sort of problem? I think? :x
<alexgordon> joelteon: well then my suggestion would be to ask someone who actually knows what they're talking about
<joelteon> i'm asking #llvm
<alexgordon> because this is way beyond me :P
<joelteon> since the behavior is different between compilers
<joelteon> i hate that shit
<joelteon> in to find out what specifically g++ is doing wrong here
<alexgordon> joelteon: std::cout is something else I never use :P
<joelteon> me neither
<joelteon> but i don't use c++ so i wouldn't know
<alexgordon> iostream is a piece of junk
<alexgordon> :P
<joelteon> i don't use c++, i wouldn't know
<joelteon> yeah, i'm really, really starting to hate exceptions
<joelteon> or rather, starting to really, really hate exceptions
<joelteon> try { ... } catch (foo& e) { ; } doesn't work
<alexgordon> LOL
<purr> LOL
<alexgordon> joelteon: oh btw which OS is this?
<joelteon> try { ... } catch (std::exception& e) { f = (foo&)e; } works
<joelteon> it is
<joelteon> osx
<joelteon> 10.10
<alexgordon> joelteon: try -stdlib=libc++
<joelteon> i'm already using that
<alexgordon> hurphf
<alexgordon> *hurmpf
<alexgordon> (get it right, alex)
<joelteon> so this is the only channel in which my question has been acknowledged
<joelteon> thanks alexgordon
<alexgordon> LOL
<alexgordon> joelteon: just an idea
<alexgordon> try using an int
<alexgordon> actually... you know what
<alexgordon> exit status can only be 0 or EXIT_FAILURE
<alexgordon> so it could just be a bool :P
<joelteon> it sure could!
<joelteon> that wouldn't make nix::Exit be in scope though
<alexgordon> throw true;
<alexgordon> lolol
<purr> lolol
* alexgordon shrugs
<purr> ¯\(º_o)/¯
<alexgordon> joelteon: you know that you can exit out at any time right?
<alexgordon> with std::exit
<joelteon> tell this guy that
<alexgordon> no need for exceptions
<joelteon> i didn't write the fucking CODE
<alexgordon> :P
<joelteon> ok
<joelteon> so there are 7 failures left in the test suite
<joelteon> and they are all of this exact pattern
<joelteon> can't catch an exception
<joelteon> because it just doesn't work
alexgordon has quit [Ping timeout: 240 seconds]
Sgeo has joined #elliottcable
<joelteon> oh
<joelteon> alexgordon left
<joelteon> FUCK
<joelteon> i can't ask ##c++ this question