"Charlie" <charles@jwavro.com> wrote in message news:d2kj5p$1on1$1@digitaldaemon.com...
>> I was going to read in class source and write out D code for class(es)
> that
>> implement a reflection API that resembles Java's reflection API. In other words if the input source code looks like
>
> Ahh cool didnt know Java did it like this.

For more info about the Java API for the curious check out
http://java.sun.com/j2se/1.5.0/docs/guide/reflection/spec/java-reflection.doc.html#8589
Basically you query the JVM for Class, Field, Method and Constructor objects
and can apply them to instances or use them to construct instances. Since D
doesn't have a JVM the only thing that knows the class layout is the
compiler and so I think the best way to do reflection is to feed more code
through the same compiler.

> Attached is a simple php script to convert the front-end to be compilable
> by
> MSVC.  It doesnt catch everything ( sys/time.h ) but it should catch most
> things.

nifty. I'll stick it in the zip file if you don't object.

"Charlie" <charles@jwavro.com> wrote in message news:d2kbrj$1hu4$1@digitaldaemon.com...
>> I'm working on getting a basic dlint going and hooking it up to the emacs mode for error and warning highlighting
>
> Coolness.

Attached is a sneak-peak at dlint minor-mode in emacs (using the D major-mode). There are two warnings in the code- one about a function that should return a value that doesn't and another about a narrowing cast. I'll clean things up over the weekend and make another post when dlint (and the d-mode update) is ready. Thanks to Walter for the wonderful front-end code and warning implementation.

-Ben

ps -notice the cute little Dlint menu, too. It basically came for free from the mlint highlighter I'm using (written by my buddy Eric Ludlam - Emacs hacker extraordinaire) :-)

"Ben Hinkle" <bhinkle@mathworks.com> wrote in message news:d2k6ff$1cca$1@digitaldaemon.com...
>
> "Lynn Allan" <l_d_allan@adelphia.net> wrote in message news:d2k3fj$19b0$1@digitaldaemon.com...
> >> Currently only Windows is supported (but that's probably just
> > becuase I
> >> haven't made a Makefile for Linux yet). The project is GPL.
> >
> > Just curious why you are using gpl ... was that necessary based on derivation, or your preference? If preference, why?
>
> The dmd source allows either GPL or the artistic license and I just chose GPL because I understand it. I haven't looked closely at the artistic
one -
> would you prefer that license? I'm not really sure how it differs from
GPL,
> to be honest. Maybe I should keep the same style as dmd and say "either
GPL
> or Artistic". That would probably be the best approach.

The artistic license applies if you want to make a close source version.

Umm ... amazing!  I didn't even know they had a lint mode, how cool!


>nifty. I'll stick it in the zip file if you don't object.

No not at all



"Ben Hinkle" <ben.hinkle@gmail.com> wrote in message news:d2kuks$22a8$1@digitaldaemon.com...
>
> "Charlie" <charles@jwavro.com> wrote in message news:d2kbrj$1hu4$1@digitaldaemon.com...
> >> I'm working on getting a basic dlint going and hooking it up to the emacs mode for error and warning highlighting
> >
> > Coolness.
>
> Attached is a sneak-peak at dlint minor-mode in emacs (using the D major-mode). There are two warnings in the code- one about a function that should return a value that doesn't and another about a narrowing cast. I'll clean things up over the weekend and make another post when dlint
(and
> the d-mode update) is ready. Thanks to Walter for the wonderful front-end code and warning implementation.
>
> -Ben
>
> ps -notice the cute little Dlint menu, too. It basically came for free
from
> the mlint highlighter I'm using (written by my buddy Eric Ludlam - Emacs
> hacker extraordinaire) :-)
>
>
>

Do you mind if I use this for elephant ?

C

"Ben Hinkle" <ben.hinkle@gmail.com> wrote in message news:d2kuks$22a8$1@digitaldaemon.com...
>
> "Charlie" <charles@jwavro.com> wrote in message news:d2kbrj$1hu4$1@digitaldaemon.com...
> >> I'm working on getting a basic dlint going and hooking it up to the emacs mode for error and warning highlighting
> >
> > Coolness.
>
> Attached is a sneak-peak at dlint minor-mode in emacs (using the D major-mode). There are two warnings in the code- one about a function that should return a value that doesn't and another about a narrowing cast. I'll clean things up over the weekend and make another post when dlint
(and
> the d-mode update) is ready. Thanks to Walter for the wonderful front-end code and warning implementation.
>
> -Ben
>
> ps -notice the cute little Dlint menu, too. It basically came for free
from
> the mlint highlighter I'm using (written by my buddy Eric Ludlam - Emacs
> hacker extraordinaire) :-)
>
>
>

"Charlie" <charles@jwavro.com> wrote in message news:d2pn5u$8i9$1@digitaldaemon.com...
> Do you mind if I use this for elephant ?
>
> C

Please do. That's what it's there for. I'll post a real announcement now that I put it up.

"Ben Hinkle" <bhinkle@mathworks.com> wrote in message news:d2k6ff$1cca$1@digitaldaemon.com...
>
> "Lynn Allan" <l_d_allan@adelphia.net> wrote in message news:d2k3fj$19b0$1@digitaldaemon.com...
> >> Currently only Windows is supported (but that's probably just
> > becuase I
> >> haven't made a Makefile for Linux yet). The project is GPL.
> >
> > Just curious why you are using gpl ... was that necessary based on derivation, or your preference? If preference, why?
>
> The dmd source allows either GPL or the artistic license and I just
chose
> GPL because I understand it. I haven't looked closely at the
artistic one -
> would you prefer that license? I'm not really sure how it differs
from GPL,
> to be honest. Maybe I should keep the same style as dmd and say
"either GPL
> or Artistic". That would probably be the best approach.

<alert comment="IANAL">

And I'm also not a fan of gpl. From a developer's point of view, I've only seen downsides to using gpl compared to other common open source licenses (mpl, Artistic, LGPL, etc.), and no upside.

Whenever I see a project with gpl, I just groan. "Crud, another library / tool that will be harder to work with than it has to be." I would come close to recommending public domain over gpl, but Artistic seems like quite a good choice. I remember trying to sort out the different license choices some time back, and Artistic was the choice I was going to use.

A possible problem with Artistic is that I recall some time back, SourceForge didn't have "Artistic" as one of the options in the drop-down menu for which license you wanted to select. Or maybe it was some variant of "Modified Artistic"? It may very well have been added since then, so this is moot.

</alert>

> Whenever I see a project with gpl, I just groan. "Crud, another library / tool that will be harder to work with than it has to be." I would come close to recommending public domain over gpl, but Artistic seems like quite a good choice. I remember trying to sort out the different license choices some time back, and Artistic was the choice I was going to use.

It's funny you say that because I totally agree. Most of my stuff is public domain.