Path: news.daimi.aau.dk!news.uni-c.dk!newsfeed.sunet.se!news01.sunet.se!sunic!news99.sunet.se!nntp-trd.UNINETT.no!nntp.uio.no!ifi.uio.no!usenet From: olag@solva.ifi.uio.no (Ola Fosheim Grøstad) Newsgroups: comp.lang.beta Subject: Re: [Q]GuiEnv canvas.scan Date: 30 Jan 1996 00:58:03 GMT Organization: Dept. of Informatics, University of Oslo, Norway Lines: 37 Message-ID: <4ejqer$2p7@glitnir.ifi.uio.no> References: <4eg2mv$ra9@glitnir.ifi.uio.no> NNTP-Posting-Host: solva.ifi.uio.no X-Newsreader: knews 0.9.3 In article , wpp@marie.physik.TU-Berlin.DE (Kai Petzke) writes: >>Is anyone trying to make a freeware version of Beta (even if it is only >>a limited version)? >Yes. I am working on such a beast in my spare time. If things work >well (not on the compiler - but on my studies, so they leave me time Great! Are you planning to do the fragmentsystem as well? In my opinion, the fragmentsystem is what makes Beta tick. A matter of curiosity: Are you basing this solely on the Beta-book or do you use research-reports/inside-info as well? >>Would it be possible to make a Beta to C++ compiler if one ignored the >>concurrency features? >It depends, on what you want to do with the generated C++ code. If >it is only meant for feeding it into a compiler, a BETA -> C++ translator >is as feasible (or unfeasible) as a BETA -> C translator, of which an >at least halfway working model is already available. > >However, the generated C or C++ is UGLY. So, if you think about something, >which takes your BETA source tree, and outputs a C++ source tree, which >can be used for further development, well, I don't think, that such a >program could be written. No, what I had in mind was a simple compiler that didn't worry about optimization at all, but would leave that to the commercial compiler. And more importantly to allow simple interfacing to C++ modules and libraries, with virtuals and all. I can see that there are a few problems with this approach though.. -- * Ola Fosheim Groestad (http://www.ifi.uio.no/~olag) *