00:18 <mark4> who is jess?

00:19 <mark4> a freenode staff member!

00:19 <jess> a miserable pile of secrets

00:19 <jess> hi

00:19 <mark4> trying to get founder status back in my name lol

00:19 <jess> yes you and i spoke about this

00:19 <mark4> yea

00:19 <mark4> i emailed chuck moore

00:19 <mark4> no response yet

00:20 <mark4> its either going to happen or not. no idea

00:20 <mark4> you are of course welcome to hang in this channel :)

00:20 <mark4> and would be even if you were not a staff member :)

00:21 <mark4> you interested in learning the forth language or just monitoring the channel? no bad answers here ;)

17:35 <astrid> omg it's jess

17:36 <astrid> hi :)

17:37 <nihilazo> hi

17:45 <jess> Hi

17:46 <jess> welcome to freenode can i take your order

17:47 <f-a> a serving of banned spammers, please

17:48 <nihilazo> lol

18:33 <inode> jess: can i have a menu please?

23:05 <mark4> lol the channel is still locked to 83 users - my joke about restricting it to the 83 standard :P

23:09 <mark4> window_t *win = malloc(sizeof(window_t)); <-- first time this is called it works grea. second time it is called it segfaults.

23:09 <mark4> no freeking idea why. gotta love c

23:11 <inode> what's window_t?

23:11 <mark4> a typedef struct

23:11 <mark4> describing a window. size, position, attributes etc

23:11 <inode> doesn't sound like anything should break there then, asked valgrind for help? :)

23:12 <mark4> no idea how to use valgrind :)

23:12 <inode> valgrind --leak-check=full command-line-under-test-here

23:13 <inode> usually is enough to get by on, unless you want to attach to an already running process

23:13 <mark4> this is not a memory leak. im mallocing a window_t structure and it works great till i try allocate a new one

23:15 <inode> that might be a symptom of prior heap corruption

23:15 <mark4> valgrind: Fatal error at startup: a function redirection

23:15 <mark4> valgrind: cannot be set up. Details of the redirection are:

23:15 <mark4> valgrind: which is mandatory for this platform-tool combination

23:16 <mark4> ive not freed any allocated buffers yet. the previous *win is being held elsewhere, this is a new incantation and window_t *win is a local variable

23:16 <mark4> im just allocating space for a window_t structure

23:18 <mark4> malloc(): corrupted top size

23:18 <mark4> is the error i get on the second call :/

23:22 <xybre> hey mark4

23:25 <mark4> hi

23:27 <xybre> I'm building a new iteration of my language, the first version was a strict stack machine with some weird features with heavy borrowings from Forth and a little JVM. It was designed to be a proof of concept and I feel like it did its job.

23:30 <xybre> I keep typing out a question but the more I type the more I think about alternative solutions. hah

23:33 <xybre> Anyway, I'm working on the new parser, and I'm starting to wonder if a tokenizer is really even worth it. If the code maintains homoiconicity then it might be find to just seek the raw source. In the previous iterations I would end up with an array of references to strings, and that just seems really inefficient.