1. Interop with .Net: Is it possible to use Nemerle compiled Assemblies in C# code?
   Yes, it is possible. From version 0.2, Nemerle is practically full CLS consumer and extender. Thus one can extend in Nemerle any CLS compliant class created from other language and vice versa. There are of course issues with mapping of purely Nemerle features (like variants), but as long as you do not use them in public interfaces there should be no problems.

2. Can I create a program using Windows.Forms on my Windows XP box?
   Yes, you can. You can use Windows.Forms for GUI (Windows platform, WINE emulation under Mono) or Gtk# (both Windows and Linux platforms). Simplest test applications using these libraries are within our test-cases.

3. Could you please provide an example of a macro definition, which can be compiled with ncc?
   An exemplary macro, the code using it and the full compilation process is now described on http://www.nemerle.org/macros.html#defining

4. What does "Nemerle" mean?
   It is inspired by a name of mage Nemmerle from book of Ursula K. Le Guin "A Wizard of Earthsea" (spelling with a single 'm' *is* a design decision ;-) )

5. Does Nemerle run on Mono http://mono-project.com ?
   Yes, it does. As a matter of fact, Mono is currently our primary development platform. We have developers working both on Linux (Mono) and Windows (.net Framework 1.1). We are planning to widen our support for more .Net runtime environments.

6. Why types of method parameters and return value cannot be inferred just like for local functions?
   This is because of documentation reason (it is better to explicitly give types in public methods) and interoperability. Type inference for private functions is still being considered.

7. Why doesn't fun(x){x.foo} compile?
   Please read this: http://nemerle.org/mailman/pipermail/devel-en/2004-July/000116.html and the response: http://nemerle.org/mailman/pipermail/devel-en/2004-July/000117.html Although as seen in http://www.nemerle.org/blog/archive/2004/Sep-07.html we are planning to extend our type inference engine to support this.