Ant wrote:
> In article <ce6cjk$2j32$1@digitaldaemon.com>, stonecobra says...
> 
>>
>>Now, just to poison this thread (so you'll post over on the new thread: Source Level Java to D converter), which license should I use for it ;) ?
> 
> 
> isn't Walter fan of Artistic+GPL?
> GPL by itself is too restrictive.
> 
> Ant
> 

CPL seems to work well, but anything that's dual and has artistic or BSD would be fine.

John Reimer wrote:
>>
>>I've heard rumors of this tool, with the XML intermediate language, and am
>>looking forward to putting SWT code through it.  Scott, let me know when
>>it's ready, or if you want someone to kick the tires.  And if Walter fixes
>>the FRef bug with your example, we may get somewhere with DWT...
>>
>>BA
> 
> 
> Uhh... might be a little late in the game for DWT, as far along as it is
> now. DWT is a pretty complicated beast.  I wouldn't be surprised if such a
> tool would choke on SWT as much as we have personally in doing the
> conversion. I don't think the issues we experience from manual conversion
> magically disappear by using a automated tool. Problems with DWT right now
> are mostly dmd compiler and language oddities. I'd like to be wrong on
> this one, though!
> 
> It's certainly good to see such a tool becoming available.  I'm sure it
> will be exceedingly useful in future projects.
> 

Yes, but while they're fresh in our minds, the conversions we did may make sense to include in Scott's tool.  If not, they stay manual.  We would just bring a bit of experience to the table, at least from a SWT to DWT standpoint.

BA

>> 
> Yes, but while they're fresh in our minds, the conversions we did may make sense to include in Scott's tool.  If not, they stay manual.  We would just bring a bit of experience to the table, at least from a SWT to DWT standpoint.
> 
> BA

Ah yes, I see your point.