Nemerle Forum Google Group

Some more tips: generating interface properties and events

2009-11-07T23:28:18Z

Hello, I'd like to share few more tips.

Case 1: You want to define a property for an interface. The following
won't work:

def property = <[decl: $(my_prop):int {get;set;} ]>;

since Nemerle parser doesn't accept auto properties in quasi
quotations. And what to do? You may try constructing the expression

Re: Define type inside expression level macro, then use it in declarations

2009-11-05T08:14:25Z

I am indeed :)

Thanks for sharing the code.

Re: Define type inside expression level macro, then use it in declarations

2009-11-04T16:16:57Z

Andrew, are you using ASP.NET MVC framework?

About week ago I started to study this excellent web framework, and
I've got same ideas.
So, I've implemented such 'view model' in previously described way.
Usage example (this is not true controller, it just shows availability
of auto class in source code):

Re: When will the VS integration be stable?!

2009-11-04T07:58:53Z

It is very stable from my experience

Re: [nem-forum] Re: When will the VS integration be stable?!

2009-11-02T16:37:01Z

Try current version.

2 ноября 2009 г. 11:48 пользователь Andrew Davey <a.j.da...@gmail.com>написал:

--
С уважением,
Чистяков Владислав,
[link]

Re: When will the VS integration be stable?!

2009-11-02T08:48:18Z

SVN revision: 8328

Re: [nem-forum] When will the VS integration be stable?!

2009-10-30T18:23:26Z

Hi,

What version you use?
The latest build not show assertion (silently write it to log).

2009/10/30 Andrew Davey <a.j.da...@gmail.com>

--
С уважением,
Чистяков Владислав,
[link]

When will the VS integration be stable?!

2009-10-30T18:17:00Z

I just had VS throw up yet another Assert failure dialog box (about
the 1000th today).
However because I was typing something at the time and hit the "a"
key, the Abort action was invoked, killing VS along with my code :(
I'm using a fairly recently build to get access to the linq macro.
Does anyone have a build that doesn't crash all the time?

Re: Define type inside expression level macro, then use it in declarations

2009-10-22T21:46:21Z

Basically what you want is to access to the "TypeBuilder" of parent
class. The below link shows you how to do it with another namespace
So you should be able to do it something similar.

[link]

Re: Define type inside expression level macro, then use it in declarations

2009-10-22T19:17:15Z

I think, you should create types, which are used within the same
assembly, only by meta-attributes.
So, your code turns to:

public class HomeController : Controller
{
[ViewModel(x)]
public Index() : ActionResult {
View(viewmodel { x = 1 });
}

or with special syntax form:

Define type inside expression level macro, then use it in declarations

2009-10-22T16:53:17Z

If I define a new type from an expression level macro, can I then use
that in another class declaration?
For example:

public class HomeController : Controller
{
public Index() : ActionResult {
View(viewmodel { x = 1 });
}

The "viewmodel" macro defines a class called "HomeIndexViewModel" and

Re: New XML macro idea

2009-10-20T08:14:42Z

That's exactly what I have in mind. I have a view engine for asp.net
mvc called Hasic ([link]) that uses
VB.NET's XML literals. I want to do something similar in Nemerle. But,
I don't fancy writing a full parser, so using list literals is quick
and easy!

Re: [nem-forum] Re: New XML macro idea

2009-10-19T21:10:03Z

Yes, but then anything, which does not look exactly like XML isn't
going to be very readable / useful. Also, I guess you don't want to
write templating engine, which is trying to transform written html
into real .NET XML objects... this would most likely:
1) suck in performance
2) won't be very convenient, since every tiny mistake, which HTML

Re: New XML macro idea

2009-10-19T19:48:54Z

It might be useful for a tempate/view engine may be.

Re: [nem-forum] New XML macro idea

2009-10-19T19:14:11Z

Yeah, that could work, but I'm not sure this is really an improvement
over any other encoding of xml literals... even strings.

BTW. are you really going to insert lots of xml literals inside your code?

--
Kamil Skalski
[link]