The One With D

New D For XCode Releases

About a week ago, Michel Fortin released the final 1.0 version of his D plugin for XCode. A few days later, he put out a bugfix 1.0.1 release. Lots of changes since the beta version. The plugin is now compatible with XCode 2.5. I’ll reproduce the changelogs here, starting with the 1.0 release:

* New output parser with support for correctly reporting warnings
(note that warnings are deactivated by default).

* Removed the Treat Warnings as Error option. Rationale: GDC
automatically treat warnings as error when they’re enabled so this
option had no effect.

* Module Search Paths now include “/usr/include/d” by default, because
that’s where most libraries are expected to install their interface
files. You can remove it from the project or target settings.

* Version Identifiers no longer contain “Posix darwin” by default. You
can add them back in the project or target settings.
(This may be needed for Tango.)

* Inline Functions is now an option in the Code Generation category.
[-finline-functions]

* Fixed a typo which made Generate Debug Symbols off by default; it is
now on by default.

* Added a Instruction Scheduling option in the Code Generation section,
allowing generated code to be tuned for G3, G4, or G5 processors.
[-mtune=]

* Change how the linker is configured so that it now can use the
system’s libgphobos.a even when using a SDK. As a side effect, GCC
is now used as a linker instead of GDC (not that this change much
things).

* Fixed two infinite loops in the code parser which would stall
and/or crash Xcode, and preemptively reviewed the code and removed
a few other potential infinite loops.

* Added some icons to the user interface for displaying D files in
lists and for build settings.

* Added a launcher application (hidden inside the plugin bundle) which
gives an appropriate icon to .d and .di files in the Finder and
redirects opened files to Xcode. On Mac OS X 10.5 Leopard, the
launcher attempt to open D files using Xcode 2.5 (if installed at
its default location), as the plugin doesn’t work with Xcode 3.

And from 1.0.1:

* The plugin now registers its launcher application when loaded into Xcode. Previously it was counting on the Finder to register it while copying the plugin, but that isn’t always reliable; hence the need for a backup plan.

Technorati Tags: D Programming Language, XCode, Mac