Changes between Version 6 and Version 7 of News

Author:

sagitario (IP: 217.232.64.101)

Timestamp:

05/30/13 12:56:08 (11 years ago)

Comment:

--

News

@@ -7 +7 @@
-</a>
-</div>
+
+<div id="navbar">
+<table width="160" cellspacing="0" style="border: 1px solid #ccc; padding: 0.5em; margin: 0 0 0em 0em;" bgcolor="#F0F0F0">
+<th bgcolor="#bbbbbb"><strong><center>Navigation</center></strong></th>
+<tr bgcolor="#F0F0F0"></tr>
+<tr><td><a href="/projects/visuald/wiki/News" title="Latest changes">News</a></td></tr>
+<tr><td><strong><a href="/projects/visuald/wiki/VersionHistory" title="Version History">Version History</a></strong></td></tr>
+<tr><td><a href="/projects/visuald/wiki/Features" title="Visual D Features">Features</a></td></tr>
+<tr><td>Tour</td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/GlobalOptions" title="Global options">Global options</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/ProjectWizard" title="Project Wizard to create new projects">Project Wizard</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/Editor" title="Language support in the editor">Editor</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/Search" title="Search symbols and files">Search window</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/TokenReplace" title="Token Search and Replace">Token Replace</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/ProjectConfig" title="Setting up build settings">Project config</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/Debugger" title="Debugger support">Debugging</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/CppConversion" title="C++ to D Conversion Wizard">C++ to D Wizard</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/Profiling" title="Profiler window">Profiling</a></td></tr>
+<tr><td>&nbsp;&nbsp;<a href="/projects/visuald/wiki/Tour/BrowseInfo" title="Browse information">Browse info</a></td></tr>
+<tr><td><a href="/projects/visuald/browser/downloads" title="All Visual D downloads">Downloads</a></td></tr>
+<tr><td><a href="/projects/visuald/wiki/Installation" title="Installation">Installation</a></td></tr>
+<tr><td><a href="/projects/visuald/wiki/KnownIssues" title="Installation">Known issues</a></td></tr>
+<tr><td><a href="/forums/viewforum.php?f=265" title="Forum">Forum</a></td></tr>
+<tr><td><a href="/projects/visuald/report/1" title="Active Tickets">Active Tickets</a></td></tr>
+<tr><td><a href="/projects/visuald/wiki/Build_from_source" title="Building from source">Building from source</a></td></tr>
+</tr>
+</table>
-</div>
+
+</div>
+
-<div id="content" style="margin-left: 15em">
-}}}
-== Version 0.3.36 ==
-
-The latest release 0.3.36 of Visual D included a considerable number of bug fixes and improvements 
-(you can find all of them listed in the [VersionHistory history]), but I'd like to detail on a few 
-bigger highlights.
-
-Unit testing and code coverage
+Version News
-
-
-
-
-
-
-
-
+
+
+
+
-
-{{{
-</div>
-}}}
-
-{{{
-#!html
-<div align="center">
-}}}
-[[Image(source:wiki/compile_and_run_opt.png)]]
-{{{
-#!html
-</div>
-}}}
-
-The standard is "-unittest --main" so after successfully building the
-source file to an executable ("--main" adds an empty main function to the source to automatically create a valid executable), your unit tests will run and you will see 
-the result in the output pane.
-
-[Actually, while writing this text a number of issues have been fixed and improvements
-have been made, so please try the latest release candidate for next version of Visual D 
-from the download folder (0.3.37rc1 as of now). Especially, it will remove some of the 
-command line options used to call rdmd that make it crash pretty often.]
-
-{{{
-#!html
-<table><tr><td valign="top" width="45%">
-}}}
-If you add "-cov" to the command line aswell the executable will be instrumented to record
-the source code lines that have been executed and will mark the lines that have 
-code generated but are never executed. This information is written into files named as the 
-source files but with extension ".lst". If you enable option "Colorize Coverage" in
-the Visual D colorizer settings (easily reachable through the new entry in the Visual D
-menu), these lines will be highlighted in the editor. The highlighting will not show
-up unless the lst-file is newer than the source file as it will probably be out of sync
-otherwise.
-
-If you fix the last test and add the line
-        assert(fib(19) == 4181);
-to the unittest, and run the unittest again, all lines will become green.
-
-If you start editing the source file Visual D will try to keep coverage information in sync. If you want to get rid of the coverage coloring, just resave the source file. Visual D will assume the coverage is invalid then and stop displaying it.
-
-If you don't want syntax highlighting from coverage generated .LST files, you can disable it by disabling the respective option on the Tools->Options->Text Editor->D->Colorizer page.
-{{{
-#!html
-</td><td width="55%">
-}}}
-[[Image(source:wiki/coverage.png, 100%)]]
-{{{
-#!html
-</td></tr></table>
-}}}
-
-If you select code within the editor and issue the command "Compile and Run", only
-the selected code will be passed to rdmd through the --eval option. This allows to
-execute just a code snippet like a script and see whether it compiles and how it behaves.
-
-= New code completion engine by Alexander Bothe =
-
-While Visual D has been running a semantic analysis for about a year now to
-support code completion and type information in tool tips, I didn't have much time
-to complete it to support all aspects of the D programming language. It is especially
-lacking on topics like template instantiation, function overload resolution and 
-unified function call syntax (UFCS). Also, compile time function evaluation (CTFE) is
-pretty incomplete. 
-Due to its pretty large memory foot print the
-stop-the-world garbage collector has been interrupting the source code editing to
-inacceptable degrees, so the analyzer had been
-moved into a separate process communicating with Visual D as a local COM server.
-
-This also opens the door to easily exchange the semantic analyzer with a different engine,
-so this is where Alexander Bothe's parsing engine enters the scene, the engine that
-also powers Mono-D and D-IDE. 
-
-{{{
-#!html
-<div align="center">
-}}}
-[[Image(source:wiki/intellisense_options.png)]]
-{{{
-#!html
-</div>
-}}}
-
-Alex has put much more effort into making the semantic
-analysis complete, and it obviously does it more efficiently. I wrapped the library
-as a local COM server implementing the same interfaces as Visual D's engine (having to do
-this in C# was a bit of a downer) and just using a different factory now allows switching
-between the two. Right now, Visual D's engine is the default, but you can select 
-Alex's engine by enabling the respective checkbox in the Intellisense 
-settings page (there is a new menu entry for faster access). It provides UFCS expansion and also displays DDoc help strings in tool tips.
-
-There is currently work being done on the D front end implemented by DMD
-to be converted from C++ to D, bringing it within reach of using it as a library for IDEs.
-This might produce
-another semantic engine in the future which easily keeps in lock step with the latest 
-compiler updates.
-
-= LDC support =
-
-LDC, the D compiler built on top of the LLVM compiler infrastructure is getting
-close to being useful on Windows aswell (at least on Win64 the longest standing
-blocker exception handling is starting to work). You can grab pre-compiled binaries 
-here: http://www.redstar.de/ldc/LDC.zip (after extracting to any directory just update
-the paths specified in LDC2\etc\ldc2.conf).
-In the Visual D project options, path settings for the three major compilers have been
-separated to different pages allowing for different import and library paths aswell.
-The specified install directories are mapped to macros like $(LDCINSTALLDIR), so they
-can be reused in other places of your project configuration.
-To use LDC by your project, select the compiler with the respective option on the
-General page of your project's property page.
-
-{{{
-#!html
-<div align="center">
-}}}
-[[Image(source:wiki/ldc_compiler.png)]]
-{{{
-#!html
-</div>
-}}}
-
-
-= Trivia =
-
-If you ever wondered why Visual D versions are numbered 0.3.x, here is the explanation:
-Each package to be loaded in Visual Studio 2008 needs to be equipped with a valid identification
-called a package load key (PLK). This key is generated by Microsoft and includes
-author and package name aswell as the major and minor version of the package. It
-is used to authenticate the package to Visual Studio.
-Unfortunately the PLK generation service is no longer available as it is no more necessary
-to have a PLK for Visual Studio 2010 or 2012 extensions. Unless I choose to be inconsistent
-with the registered version and the displayed version, Visual D is stuck at version 0.3.
-