OK I found Ometa.pdf . Thank you for that. BorgLisp is a generalization of the COLA idea if mixing Smalltalk with Lisp. Instead of limiting it to just Smalltalk and Lisp it is very easy to generalize it to all languages by using the lisp idiom of using the first thing in the list to specify the compiler that will be used to compile the rest of the list.
( c ... ( prologLisp ... ) ... ( lambdaLisp ... ( prologLisp ... ) ... ( assemblerLisp ... ) ) ) I hope that Maru will incorporate this idea if it seems good. Then Maru would become BorgLisp. If you will. If you did it this way then perhaps you wouldn't need the funny names for the C Lisp expressions inside of Maru. I have lambdaLisp working ( I tried to do two optimizations and got stuck in a debugging fuge. Never try to optimize )( note to the future. ) I have the ADD instruction working in assemblerLisp and all addressing modes work. This would be a Smalltalk rendition of llvm. Which gives me pause. That's why there are no other assembler instructions implemented I guess. I would like to add PrologLisp. To show how two languages could interact. And then I should have a third language to show how three languages could interact. If it was simple and easy to implement in Smalltalk that would be cool. I think the same source level debugger that I have working now could work for each of the languages. So anyhow. If Maru could become BorgLisp by incorporating multiple languages like COLA did but generalizing it to all languages and not just the 2. And then Maru/BorgLisp could be a new and better Smalltalk if you gave it an image. It would be cool to make it so that you could run it with an image or without an image. You choose. So anyway. I hope Maru becomes BorgLisp by incorporating multiple languages. How can I run Maru in Windows? I have a VMWare Ubuntu appliance which is a server version of Ubuntu. Will that work? Is there any documentation? All I saw was line after line of undocumented code. Which seemed opaque to even the most casual observer. So anyway. On Sat, Feb 9, 2013 at 8:12 PM, Julian Leviston <jul...@leviston.net> wrote: > "Borglisp", hey? > > Sounds like Ometa to me. > > Julian > > On 10/02/2013, at 6:27 AM, Kjell Godo <squeakl...@gmail.com> wrote: > >> What will this book be called? I would like to get one when it comes out. >> >> Why do you always start with C? Why not start with a higher language >> like Smalltalk? You could compile ByteArrays that could then run >> fast. Wouldn't it be more self documenting? You would have access to >> all the Smalltalk resources. >> >> Because C is the portable assembler. >> Because C has better access to all of the OS and all other languages. >> By starting with C you leverage the C compiler. >> You would have to write a C compiler in Smalltalk to get the same thing. >> >> I am writing BorgLisp in Smalltalk which is supposed to asimilate all >> other computer languages into itself as dialects of lisp. Like >> Clojure asimilates Java into itself. Like Cola was a combination of >> Lisp and Smalltalk and C. >> >> I have one dialect of Lisp in BorgLisp so far and a source level >> stepping debugger that can handle macros( it should ). It's written >> in Dolphin Smalltalk but I would like to port it over to Pharo or >> VisualWorks. If I tried to do the same thing in C I don't think I >> could. >> >> Please explain why starting with C is better than this. >> >> Is there a debugger for C that is as good as the one in Smalltalk? >> Do you use Test Driven Development as a way to get around not having a >> debugger? >> What programming environment do you use? >> >> I look at Maru and there are absolutely no comments in there. >> A litterate version of Maru would be way too cool to ever actually >> happen in this cursed universe we live in. I hope Maru is what I'm >> talking about but I can't remember if it is or not. >> >> I hope you write this book with the literate meta compiler compiler in it. >> >> I hope I get my hands on it. I wish Maru was literate. >> >> Now what Favorite shall I put this link under so that I might have >> some chance of ever seeing it again. I suppose my Git account would >> be a good place to do that. But I don't Git over there that much. >> >> If I seem scattered maybe it's because I am a high functioning autistic. >> >> He said. >> >> On Fri, Feb 8, 2013 at 8:08 PM, Charles Perkins <ch...@kuracali.com> wrote: >>> Thank you, Alan! >>> >>> That means quite a bit to me. >>> >>> I was so looking forward to a good pillage. Ah well… to follow your metaphor >>> (a kinder one and more inclusive to be sure) I am most appreciative of the >>> generous sharing of seeds going on around here. >>> >>> Chuck >>> >>> On Feb 8, 2013, at 5:42 PM, Alan Kay <alan.n...@yahoo.com> wrote: >>> >>> Looks nice to me! >>> >>> But no ivory towers around to pillage. (However planting a few seeds is >>> almost always a good idea) >>> >>> Cheers, >>> >>> Alan >>> >>> >>> ________________________________ >>> From: Charles Perkins <ch...@kuracali.com> >>> To: Fundamentals of New Computing <fonc@vpri.org> >>> Sent: Friday, February 8, 2013 3:52 PM >>> Subject: [fonc] yet another meta compiler compiler >>> >>> While we're all waiting for the next STEP report I thought I'd share >>> something I've been working on, inspired by O'Meta and by the Meta-II paper >>> and by the discussions on this list from November. >>> >>> I've written up the construction of a parser generator and compiler compiler >>> here: >>> https://github.com/charlesap/ibnf/blob/master/SyntaxChapter.pdf?raw=true >>> >>> The source code can be had here: https://github.com/charlesap/ibnf >>> >>> Don't be fooled by the footnotes and references, this is a piece of outsider >>> literature. I am a barbarian come to pillage the ivory tower. Yarr. >>> >>> Chuck >>> _______________________________________________ >>> fonc mailing list >>> fonc@vpri.org >>> http://vpri.org/mailman/listinfo/fonc >>> >>> >>> _______________________________________________ >>> fonc mailing list >>> fonc@vpri.org >>> http://vpri.org/mailman/listinfo/fonc >>> >>> >>> >>> _______________________________________________ >>> fonc mailing list >>> fonc@vpri.org >>> http://vpri.org/mailman/listinfo/fonc >>> >> _______________________________________________ >> fonc mailing list >> fonc@vpri.org >> http://vpri.org/mailman/listinfo/fonc > > _______________________________________________ > fonc mailing list > fonc@vpri.org > http://vpri.org/mailman/listinfo/fonc _______________________________________________ fonc mailing list fonc@vpri.org http://vpri.org/mailman/listinfo/fonc
