[MonoDevelop] #D coorporation
Fri, 19 Mar 2004 13:47:38 -0500
On Fri, 2004-19-03 at 14:49 +0100, Mike Krueger wrote:
> Are you guys interrested in coorporation with #D or not (if not I don't
> waste time writing about new #D technology) ?
Yes, we are very interested.
> - Have you looked at the new file templates yet?
Not yet, but it is on my list of things to do. I have been catching up
at work from my vacation, so have been a bit busy.
> - I've fixed some bugs in the projects layer
I was not aware, I will look into this.
> - I've added a new functionality to the language backend: expression
> finder -> this is used for finding the expression before the '.'.
> I changed the algorithm it works much better now.
> - I worked a bit on the pretty printer -> anybody cares to help?
> - fixed many parser bugs :) btw. isn't it really stupid to change
> namespaces of code that can be shared with ease between #D and
> MonoDevelop, what is the point?
> As long as I maintain #Refactory (and don't work for Ximian/Novell :))
> I won't change the namespace to MonoDevelop ... will you fork the whole
> stuff, change the
> namespace every release of the basic libraries or will you replace it
> with something different ?
The namespace change in #Refactory shouldnt have happened, however I
stick by the core and base namespace changes.
Part of the problem I am having working with this codebase is the
over-namespacing of all of it. Not only do you have 2 'toplevel'
namespaces, 'ICSharpCode.SharpDevelop' and 'ICSharpCode', there seems to
be a lot of seeming incoherence in the namespacing, for example:
To use a service, i have to do:
using MonoDevelop.Core.Services (To get the ServiceManager)
using MonoDevelop.Services (To get the actual service types)
The initial change is part of a bigger sweeping namespace
reorganization, of which we are happy to work with you to get somewhere
both applications are happy with.
> Monodevelop-list mailing list