scross

5 ms·

1. 1.▲
   by scross 12y ago

   I think this page answers your question: http://loci-lang.org/LanguageGoals.html Basically I've had a lot of experience working with C++ on various projects and while I like it very much I've also observed its wea
2. 2.▲
   by scross 12y ago

   This question was asked by someone else earlier and I answered it in full here: https://github.com/scross99/locic/issues/1 I hope this helps.
3. 3.▲
   by scross 12y ago

   Well, theoretically, you have two choices: * Use the garbage collector. * Don't use the garbage collector. I'd expect most users to choose option (2), however the idea is to support garbage collection for those users who find it t
4. 4.▲
   by scross 12y ago

   The intention is to avoid any kind of name clashes; I don't think this really inhibits readability.
5. 5.▲
   by scross 12y ago

   Yep, it's not the most attractive parser ever. I chose to use Bison in order to save a lot of time/work and to take advantage of its GLR implementation; unfortunately its interaction with C++ isn't pleasant (due to the use of
6. 6.▲
   by scross 12y ago

   Yes, this is true; the point was to highlight more generally the complexity of ensuring correctness when moving/copying C++ objects versus doing the same thing in Loci.