<fossy>I didnt make the bison and flex bootstrap, all gio <xentrac>where I come from, bugs aren't fixed until we get through a QA cycle <xentrac>I mean they're fixed but not "fixed" <OriansJ>I might have to abandon the current mes-m2 approach to supporting macros as it appears syntax-case can not be avoided and needs to be fully supported in mes-m2 to get alot of things working. >.< fuck that is going to be a bitch to write in C. <OriansJ>fossy: the best part of failure is that we now are free to choose different paths. The logical options are: scheme without macros (Serious scheme revolt there) or do macros 100% right <OriansJ>as mes-m2 breaks macro expansion into an entirely seperate source file, it becomes trivial to switch between them. <fossy>hey janneke (or anyone else) can you tell me why "expr->register: not supported:" i get this rather often compling tinycc? <fossy>it's rather trivial to remove it out but im not sure why i am getting that <fossy>it has something to do with #define and/or -D <OriansJ>fossy: actually expr->register is defined in module/mescc/compile.scm <fossy>so the message pretty much dosen't make sense :P <fossy>um, maybe module/mescc is not in GUILE_LOAD_PATH ***ChanServ sets mode: +o rekado_
***rekado_ is now known as rekado
<OriansJ>janneke: That assembler sounds interesting, it'll be interesting to see it. Not to mention the harmonic possibility that arises if it is of sufficient quality. <janneke>OriansJ: it's probably 16 bit, or even 8? <OriansJ>with possible enhancements for the assembly syntax <OriansJ>but we will not know for sure until we can see something solid to play with.