Ary Manzana wrote:
> jcc7 wrote:
>> Speaking of advertisement, I created a wiki page for it based on a couple of Ary's
>> newsgroup posts since it sounds like such a cool project. I'm not what the name of
>> this new Eclipe project is, but I set up the wiki page as:
>> http://www.prowiki.org/wiki4d/wiki.cgi?DescentUI
> 
> Thanks a lot!!
> 
> I'm considering putting the code into dsource. I'm going on a trip for the weekend so next week I'll do this. Also I'll make a list of things done and (a short list of) things to be done, similar to the "future" page on digitalmars.
> 
> As anyone tried the plugin? I'm looking for some feedback...

Also, please add a link from your project page to the wiki page jcc7 set up.

> As anyone tried the plugin? I'm looking for some feedback...

I can't get it to work, I unzip the package , it expands to

features/descent.ui_1.0.0.jar
plugins/*core*
plugins/*tests*
plugins/*ui*

But I don't see any option to choose D Project.

I'm really looking forward to trying this plugin, I would love to see a plugin on par with PHPEclipse - and think it would draw allot of attention to D to have a great eclipse plugin.

Ary Manzana wrote:
> jcc7 wrote:
>> == Quote from Walter Bright (newshound@digitalmars.com)'s article
>>> Ary Manzana wrote:
>>>> Well, I've cleaned up a bit the code and here it is:
>>>>
>>>> http://www.esperanto.org.ar/d/descent.ui.zip
>>> It'd be nice if you could put together a web page about it explaining
>>> what it is, how to use it, basically what your post said. A web page
>>> would make it much more findable and popular, and perhaps can help
>>> attract developers to help expand it.
>>
>> That's a good idea. A proper web page is a good way to show how serious of an
>> effort this project is. (Not to say that I don't believe it's a serious project,
>> but that a good web page can be a great means of advertisement.)
>>
>> Speaking of advertisement, I created a wiki page for it based on a couple of Ary's
>> newsgroup posts since it sounds like such a cool project. I'm not what the name of
>> this new Eclipe project is, but I set up the wiki page as:
>> http://www.prowiki.org/wiki4d/wiki.cgi?DescentUI
> 
> Thanks a lot!!
> 
> I'm considering putting the code into dsource. I'm going on a trip for the weekend so next week I'll do this. Also I'll make a list of things done and (a short list of) things to be done, similar to the "future" page on digitalmars.
> 
> As anyone tried the plugin? I'm looking for some feedback...

Bruno Medeiros escribió:
> Ary Manzana wrote:
> Hi, yes, I'm working on an Eclipse plugin too. I've started very recently (about two weeks ago), so I don't have anything significant to show yet, but I'm doing this as my degree final project, so I will be working on it during all school year.
> 
> We definitely should talk and see if we can combine efforts, but the approach I was thinking was to build a parser using ANTLR, similar to what the previous eclipse plugins did (Blackbird, DDT). However, you seem to be far ahead of I've done. You say you've converted the whole D frontend to Java? (to descent\internal\core\dom\Parser.java I presume) That must have been a lot of work. I'd actually like to know how long it took for you to do that

About a month and a half? (in my precious little spare time, of course :-P). I don't remember...

, and if it's working correctly. I'm gonna take a
> better look at your code.
> 
> 

Great! I would be very happy to combine efforts. The project now has a webpage in dsource.org:

http://www.dsource.org/projects/descent/

There I wrote an explanation about why not to use ANTLR (I started doing that, then I changed to using DMD source code and it was *way* faster and better).

I only converted parser.h, parser.c (yes, descent\internal\core\dom\Parser.java) , lexer.h, lexer.c (descent\internal\core\dom\Lexer.java) and the classes/functions referenced there: just the clean model with no semmantic stuff. Porting c++ to Java was not an easy task, especially since Java has no powerful "goto" (oh my, 732 in the whole code), so I had to change some of the code, or duplicate it (I don't want to break anything at first).

Is it working ok? Check descent.test.jar. You can find cases to test both the parser and the lexer. I just downloaded the excelent Coverclipse ( http://coverlipse.sourceforge.net/ ): the parser is %65 tested; the lexer %68. That's more than half of it! :-)

And it's not just copy-paste and test. The Token class now has two properties to tell its start position and length, as well as every class in the model, since a regular compiler dosen't need it, but a visual does. And I've written nice interfaces to the model (check descent.core.dom).

The first step would be to get (close to) %100 test coverage on parser and lexer, then move on to the big (juicy) stuff.

Read the last sentence I wrote on the dsource page: wait for me until then :-)

(I will write all of these explanations in the webpage, and more, when I'll come back, I promise)

Ok I see, I have to first install DDT , then unzip the package.

Then it gives me *two* D project options, and only the icon is different.

After finding out that the open folder with the D is the descent project type I get it working, and the parser works great!  I would think this is one of the hardest parts so its cool to see how far you've developed it.

I didn't get highlighted errors as I typed however.

This looks like its going to be a great project.

Charlie

Charlie wrote:
>  > As anyone tried the plugin? I'm looking for some feedback...
> 
> I can't get it to work, I unzip the package , it expands to
> 
> features/descent.ui_1.0.0.jar
> plugins/*core*
> plugins/*tests*
> plugins/*ui*
> 
> But I don't see any option to choose D Project.
> 
> I'm really looking forward to trying this plugin, I would love to see a plugin on par with PHPEclipse - and think it would draw allot of attention to D to have a great eclipse plugin.
> 
> Ary Manzana wrote:
>> jcc7 wrote:
>>> == Quote from Walter Bright (newshound@digitalmars.com)'s article
>>>> Ary Manzana wrote:
>>>>> Well, I've cleaned up a bit the code and here it is:
>>>>>
>>>>> http://www.esperanto.org.ar/d/descent.ui.zip
>>>> It'd be nice if you could put together a web page about it explaining
>>>> what it is, how to use it, basically what your post said. A web page
>>>> would make it much more findable and popular, and perhaps can help
>>>> attract developers to help expand it.
>>>
>>> That's a good idea. A proper web page is a good way to show how serious of an
>>> effort this project is. (Not to say that I don't believe it's a serious project,
>>> but that a good web page can be a great means of advertisement.)
>>>
>>> Speaking of advertisement, I created a wiki page for it based on a couple of Ary's
>>> newsgroup posts since it sounds like such a cool project. I'm not what the name of
>>> this new Eclipe project is, but I set up the wiki page as:
>>> http://www.prowiki.org/wiki4d/wiki.cgi?DescentUI
>>
>> Thanks a lot!!
>>
>> I'm considering putting the code into dsource. I'm going on a trip for the weekend so next week I'll do this. Also I'll make a list of things done and (a short list of) things to be done, similar to the "future" page on digitalmars.
>>
>> As anyone tried the plugin? I'm looking for some feedback...

Charlie escribió:
> Ok I see, I have to first install DDT , then unzip the package.

No, it dosen't depend on DDT. In fact I guess they conflict with each other.
> 
> Then it gives me *two* D project options, and only the icon is different.

The one from the descent plugin creates a "src" folder, check this to be sure.

> 
> After finding out that the open folder with the D is the descent project type I get it working, and the parser works great!  I would think this is one of the hardest parts so its cool to see how far you've developed it.
> 
> I didn't get highlighted errors as I typed however.

Probably because my editor wasn't being used: instead, the DDT editor was used.

> 
> This looks like its going to be a great project.
> 
> Charlie
> 
> Charlie wrote:
>>  > As anyone tried the plugin? I'm looking for some feedback...
>>
>> I can't get it to work, I unzip the package , it expands to
>>
>> features/descent.ui_1.0.0.jar
>> plugins/*core*
>> plugins/*tests*
>> plugins/*ui*

Copy what is found in "features" to the "features" folder under eclipse. The same goes for the "plugin" folder. And delete plugins provided by DDT (I guess org.dsource.ddt.*). I guess they conflict with each other.

You _should_ see the new D Project option in the "New Project" wizard just doing that... If you get it to work, please leave some answer to some FAQ in:

http://www.prowiki.org/wiki4d/wiki.cgi?DescentUI

Thanks!

Ary Manzana wrote:
> I only converted parser.h, parser.c (yes, descent\internal\core\dom\Parser.java) , lexer.h, lexer.c (descent\internal\core\dom\Lexer.java) and the classes/functions referenced there: just the clean model with no semmantic stuff. Porting c++ to Java was not an easy task, especially since Java has no powerful "goto" (oh my, 732 in the whole code), so I had to change some of the code, or duplicate it (I don't want to break anything at first).

I deliberately avoided using things like exceptions in it to make it easy to port, but I didn't think about the goto's.

> shinichiro!).  Here is a link to that post:
> 
> http://www.digitalmars.com/d/archives/digitalmars/D/32313.html

I think it only works on win32? I didn't say that, but I use linux, so I cannot use or test this solution :(

Walter Bright wrote:

> I deliberately avoided using things like exceptions in it to make it easy to port, but I didn't think about the goto's.

It's ok, you make an excellent use of them. But later in the development process I will need a hand with "Parser::isBasicType", "Parser::parseBasicType" and "Parser::parseDeclDefs(bool)". Just take a look at this:

---
int Parser::isBasicType(Token **pt)
{
    // This code parallels parseBasicType()
    Token *t = *pt;
    Token *t2;
    int parens;

    switch (t->value)
    {
	CASE_BASIC_TYPES:
	    t = peek(t);
	    break;

	case TOKidentifier:
	    t = peek(t);
	    if (t->value == TOKnot)
	    {
		goto L4;
	    }
	    goto L3;
	    while (1)
	    {
	L2:
		t = peek(t);
	L3:
		if (t->value == TOKdot)
		{
	Ldot:
		    t = peek(t);
		    if (t->value != TOKidentifier)
			goto Lfalse;
		    t = peek(t);
		    if (t->value != TOKnot)
			goto L3;
	L4:
		    t = peek(t);
		    if (t->value != TOKlparen)
			goto Lfalse;
		    if (!skipParens(t, &t))
			goto Lfalse;
		}
		else
		    break;
	    }
	    break;

	case TOKdot:
	    goto Ldot;

	case TOKtypeof:
	    /* typeof(exp).identifier...
	     */
	    t = peek(t);
	    if (t->value != TOKlparen)
		goto Lfalse;
	    if (!skipParens(t, &t))
		goto Lfalse;
	    goto L2;

	default:
	    goto Lfalse;
    }
    *pt = t;
    return TRUE;

Lfalse:
    return FALSE;
}
---

I was thinking of sending a feature request to Java just for this tiny function :-P

Frank Benoit (keinfarbton) wrote:
>>shinichiro!).  Here is a link to that post:
>>
>>http://www.digitalmars.com/d/archives/digitalmars/D/32313.html
> 
> 
> I think it only works on win32? I didn't say that, but I use linux, so I
> cannot use or test this solution :(

Bummer :(

Even so, I still think phobos should have backtrace on windows since it has been done already and is also very helpful.  Hopefully someone will do a linux version at some point.

Ok with a fresh eclipse install , it works perfect.  It was that I had DDT installed prior to Descent, then used the Manage Configuration to uninstall DDT ( after I copied the Descent folders over ) , which also deleted descent from the New Project list for some reason.  Trying after the DDT uninstall to copy the Descent folders to eclipse continues to fail, so people installing Descent make sure DDT is uninstalled first. Ill add this to the forum / wiki page.

Awesome job though, highlights errors per file, and a great outline as well.  This is going to make life much easier!


Ary Manzana wrote:
> Charlie escribió:
>> Ok I see, I have to first install DDT , then unzip the package.
> 
> No, it dosen't depend on DDT. In fact I guess they conflict with each other.
>>
>> Then it gives me *two* D project options, and only the icon is different.
> 
> The one from the descent plugin creates a "src" folder, check this to be sure.
> 
>>
>> After finding out that the open folder with the D is the descent project type I get it working, and the parser works great!  I would think this is one of the hardest parts so its cool to see how far you've developed it.
>>
>> I didn't get highlighted errors as I typed however.
> 
> Probably because my editor wasn't being used: instead, the DDT editor was used.
> 
>>
>> This looks like its going to be a great project.
>>
>> Charlie
>>
>> Charlie wrote:
>>>  > As anyone tried the plugin? I'm looking for some feedback...
>>>
>>> I can't get it to work, I unzip the package , it expands to
>>>
>>> features/descent.ui_1.0.0.jar
>>> plugins/*core*
>>> plugins/*tests*
>>> plugins/*ui*
> 
> Copy what is found in "features" to the "features" folder under eclipse. The same goes for the "plugin" folder. And delete plugins provided by DDT (I guess org.dsource.ddt.*). I guess they conflict with each other.
> 
> You _should_ see the new D Project option in the "New Project" wizard just doing that... If you get it to work, please leave some answer to some FAQ in:
> 
> http://www.prowiki.org/wiki4d/wiki.cgi?DescentUI
> 
> Thanks!