purr changed the topic of #elliottcable to: a
_better_ cult || topics << 'gamedev'
sharkbot has quit [Remote host closed the connection]
sharkbot has joined #elliottcable
Nuck has joined #elliottcable
Nuck has quit [Quit: Computer has gone to sleep.]
Nuck has joined #elliottcable
audy has joined #elliottcable
eligrey has quit [Quit: Leaving]
kaplan_ has joined #elliottcable
kaplan has quit [Ping timeout: 255 seconds]
Nuck has quit [Quit: Computer has gone to sleep.]
jwilkins5 has quit [Read error: No route to host]
jwilkins4 has joined #elliottcable
Aria has quit [*.net *.split]
Cheery has quit [*.net *.split]
Cheery has joined #elliottcable
aredridel has joined #elliottcable
<
kaplan_>
Cheery, hi
<
kaplan_>
Cheery, are you Brit?
Nuck has joined #elliottcable
eligrey has joined #elliottcable
<
kaplan_>
hi eligrey
<
Cheery>
I'm surprised. I actually managed to type in infix expressions without a problem.. and it parsed them into structure I wanted.
<
Cheery>
requires lot of tabbing through.. but after an improvement to the parser it shouldn't
<
eligrey>
hey kaplan_
<
eligrey>
kaplan_: why aren't you in #oftn?
<
kaplan_>
Should I be?
<
eligrey>
if you are a member
<
eligrey>
i thought you were for a sec
<
eligrey>
nvm i was thinking of a kaplun
<
Cheery>
I should think out the schema right.
<
kaplan_>
eligrey, What do you guys do at oftn?
<
eligrey>
any cool open source projects that we feel like working on
<
eligrey>
kaplan_: github.com/oftn
<
Cheery>
the basis is that it's still a context free grammar
<
Cheery>
list of generative rules.
<
Cheery>
there should be clear validation and context though
<
kaplan_>
eligrey, how does an identity verification system sound?
<
eligrey>
kaplan_: sounds like Persona or OpenID
<
eligrey>
kaplan_: what did you have in mind?
<
kaplan_>
eligrey, the opposite of anon ID
<
kaplan_>
you upload your identity to be verified by humans(or computers if possible)
<
Cheery>
I can't get over this.
<
Cheery>
the context free grammar looks like it looks
<
Cheery>
it's got terminals "+" "-" "<<"
<
Cheery>
it's got nonterminals <expr> <stmt> so on.
<
Cheery>
it's got generative rules
<
Cheery>
to map this into my tree structure, I need to give some of the generative rules a naming.
<
Cheery>
the given rule can appear in several contexes
cloudhead_ has quit [Read error: Connection reset by peer]
yrashk has quit [Write error: Connection reset by peer]
ELLIOTTCABLE has quit [Write error: Connection reset by peer]
ohhmaar has quit [Ping timeout: 265 seconds]
cloudhead_ has joined #elliottcable
ELLIOTTCABLE has joined #elliottcable
ohhmaar has joined #elliottcable
incomprehensibly has quit [Ping timeout: 250 seconds]
incomprehensibly has joined #elliottcable
yrashk has joined #elliottcable
<
Cheery>
incomprehensibly: ELLIOTTCABLE mentioned you've got something to say about visual programming
alexgordon has joined #elliottcable
<
Cheery>
Only my capability as a programmer lets me to continue this project.
<
Cheery>
in that sense I feel that it's sort of failed
<
Cheery>
there's no interesting theory behind that'd need to be solved and that would make it work
<
Cheery>
just lot of small knife-hits
<
Cheery>
in many ways it feels like some early version of text editing. I don't think the thing I'm writing is particularly long-lived.
<
Cheery>
it solves one problem.
<
Cheery>
plain text editing the way we do it today shifts similar set of problems to language implementations
<
Cheery>
it introduces both and advantage and a deficit
<
Cheery>
the visual representation of the code isn't allowed to be ambiguous. This potentially prevents many problems
<
Cheery>
but it's also a deficit. The language cannot be extended.