Ary Borenszweig schrieb:
Ok, I'll work on it. :-)
Hope you'll release it soon ;)
I'm not sure you want to see that, heh. I think I'll stick with the
hover over a symbol to see it's compile-time representation solution...
Cool, didn't know scope was just syntactic sugar for such a construct.
Well the question is what the output looks like for a test scenario that
is more
btw how do you get these information? Do you directly use the dmd
frontend source code?
Trass3r wrote:
btw how do you get these information? Do you directly use the dmd
frontend source code?
Descent has a port of DMD's frontend code to Java. It also implements
the visitor pattern in the provided AST, so it can output it as text.
Ary Borenszweig wrote:
Trass3r wrote:
btw how do you get these information? Do you directly use the dmd
frontend source code?
Descent has a port of DMD's frontend code to Java. It also implements
the visitor pattern in the provided AST, so it can output it as text.
Ummm... So I apply the
Ary Borenszweig schrieb:
Trass3r wrote:
btw how do you get these information? Do you directly use the dmd
frontend source code?
Descent has a port of DMD's frontend code to Java. It also implements
the visitor pattern in the provided AST, so it can output it as text.
Yeah I thought so.
Ary Borenszweig wrote:
Trass3r wrote:
Ary Borenszweig schrieb:
I think this point is pretty feasible. I can probably implement it as
a view. The only problem is that if I do that, I'll also have to
show the optimized version of the code (which might be very
interesting). So if you have:
Reply to Robert,
That doesn't look entirely useless, especially for optimization.
Perhaps hard to read, but easier than reading the assembly output ;-P!
ditto; now that you have it might as well make it available.
BCS wrote:
Reply to Robert,
That doesn't look entirely useless, especially for optimization.
Perhaps hard to read, but easier than reading the assembly output ;-P!
ditto; now that you have it might as well make it available.
Ok, I'll work on it. :-)
Trass3r wrote:
Ary Borenszweig schrieb:
And a question: what would you like to see next in Descent?
#1: the preprocessed-source output discussed in the learn newsgroup!
(...output a copy of what the source files look like after things like
mixins, CTFE and versions are applied? (Sort of
Ary Borenszweig Wrote:
Jacob Carlborg escribió:
Ary Borenszweig wrote:
Jacob Carlborg Wrote:
Ary Borenszweig wrote:
Ary Borenszweig escribió:
Ary Borenszweig escribió:
The Descent plugin for Eclipse provides an IDE for writing,
launching and debugging code in D.
Thank you all
Tim M wrote:
I dont think the allround ide is a problem anymore with eclipse
available. Whats missing is a good gui builder. If you know of one other
than entice though can you please reply with the links.
No top-posting, please.
I use Glade. It works reasonably well for small projects.
BCS wrote:
Reply to Ary,
And a question: what would you like to see next in Descent?
Better template support. I now have 2 libs that are just flat uneditable
under descent (scrapple.units and scrapple.dparse) both bring it down to
a stand still if not crash and hand it out right. I'd love
Thank you so much, I really appreciate this IDE.
What would make me most happy, personally, is getting Descent to parse command
line output from dmd and jump to errors in the source file.
Next up the wishlist is actually building from Descent, but this is less
important. Dsss support would
Reply to Ary,
And a question: what would you like to see next in Descent?
Better template support. I now have 2 libs that are just flat uneditable
under descent (scrapple.units and scrapple.dparse) both bring it down to
a stand still if not crash and hand it out right. I'd love to see it
15 matches
Mail list logo
