Built, Designed, Powered - Borland Developer Studio 2006
And do not forget, I like the original ones, it's just that they do not target the whole product yet.
begin
end;
Now, you would like to position the cursor (shown as "|") as following after invoking the template.begin
|
end;
The XML template for that task is rather easy, let's say you have not defined any delimiter character, so the IDE will default to the dollar "$" sign. Then you would define the template like the following snippet.<code
language="Delphi"
context="methodbody">
<![CDATA[begin
$selected$$*$$end$
end;]]>
</code>
If you want to use another delimiter you can simple declare it with a delimiter attribute like the following code snippet will show.<code
language="Delphi"
context="methodbody"
delimiter="|">
<![CDATA[begin
|selected||*||end|
end;]]>
</code>
I hope that this will help you in your endavours in creating new code templates.All you need to do is add SimpleShareMem.pas as the first unit in the .dpr
file of the exe as well as the dll (as you would have done with the old
sharemem.pas) and you can then safely share strings and dynamic arrays
between them. You don't need the borlndmm.dll if you use the SimpleShareMem
unit.
I agree with you to a large extent - the editing and debugging environment of Visual Studio is excellent. The debugging tools in particular are much better even than those in my beloved Delphi. However, speaking of Delphi… I wonder if Borland now has a realistic opportunity to offer competition to Microsoft? With the new release of the Borland Developer Studio, you’ll have the option of coding in C++ for Win32, C# for .NET and Delphi for .NET (Win Forms). Moreover, Borland has a powerful class library (VCL) that works pretty well on both Win32 and .NET. That’s why some VB developers are looking to Delphi as a serious alternative. Unlike VB, which commits you either to Win32 (VB6 and its predecessors) or .NET (VB .NET), a Delphi Win32 VCL application can be recompiled for .NET with few (or if you are careful, with no) modifications to the source code. In principle it seems to me that Borland’s .NET solution is essentially better than Microsoft’s.Now, that let's one hope for great times to come, doesn't it?