Cobra Forums

It's been kind of quiet. What's everyone up to?

I'm currently refactoring the compiler to put phases in classes/objects instead of methods. It's an internal thing, though, that won't affect your code. After that I'll probably do a hopscc patch. After that I want to axe the "is shared" requirement for "def main".

I've been looking into using MakeMSI to make a windows installer for Cobra. That said, I've got a lot on in the next few weeks, and then I'm away for a few, so I don't know that I'll have anything solid for a month or so.

- Caligari

Just resynced to src tree
Looks like from Changeset 2060 - build tree is broken

Phases/BindImplementationPhase.cobra isnt under version control
- presume its addition was missed when compiler.bindImp was removed (2060)

....

Getting some minimal form of ** arithmetic expression working (ticket 114)
( and putting back wall on greenhouse).

Fixed.

I have been quite busy with personal tasks, but I got some time to check what I could need from cobra compiler to get sharp develop 3.0 addin.
I have started with the Boo addin as a template. Boo developers have broken appart the compiler executable from the compiler library (Boo.Lang.Compiler.dll) so one can "easily" use those libraries to get access to the AST, Parser, tokenizer, etc...

I have found that difficult with Cobra as most of Cobra compiler classes are not public. So I have been making most of them public to test some things.
is that a good idea?

Should we split cobra complier in some libraries?

First of all, thanks for working on this.

What you describe is already done as far as I know:

Classes are public by default in Cobra. So when you see "class Expr", that's a public class.

Also, you will see in the Source directory a file called comp-compiler-dll.bat with contents:
comp -t:lib -namespace:Cobra.Lang.Compiler -out:Cobra.Lang.Compiler.dll %*

So if you run this, you will get a Cobra.Lang.Compiler.dll to use.

HTH. Keep the questions coming.