發文回覆瀏覽次數：2639

推到 Plurk!

推到 Facebook!

BDS 2006 Borland Developer Studio 2006, Update 2 Release Notes

axsoft
版主

發表：681
回覆：1056
積分：969
註冊：2002-03-13

發送簡訊給我

#1 引用回覆回覆

發表時間：2006-07-12 15:49:59

IP:61.219.xxx.xxx 未訂閱

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Borland Developer Studio 2006, Update 2 Release Notes</TITLE><br /><META http-equiv=Content-Type content="text/html; charset=iso-8859-1"><br /><STYLE>BODY {
MARGIN-TOP: 12pt; FONT-SIZE: 12px; MARGIN-LEFT: 12pt; COLOR: #000000; MARGIN-RIGHT: 12px; FONT-FAMILY: "Arial"
}
P {
MARGIN-TOP: 6pt; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: normal; FONT-SIZE: 100%; MARGIN-BOTTOM: 6pt; FONT-STYLE: normal; TEXT-ALIGN: left
}
P.comment {
MARGIN-TOP: 3pt; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: normal; FONT-SIZE: 100%; MARGIN-BOTTOM: 3pt; COLOR: silver; FONT-STYLE: normal; TEXT-ALIGN: left
}
P.sub {
MARGIN-TOP: 0pt; DISPLAY: block; FONT-WEIGHT: normal; FONT-SIZE: 100%; MARGIN-BOTTOM: 6pt; FONT-STYLE: normal; TEXT-ALIGN: left
}
H1 {
BORDER-TOP: activecaption groove; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: bold; FONT-SIZE: 190%; MARGIN-BOTTOM: 10pt; BORDER-LEFT: activecaption groove; COLOR: navy; FONT-STYLE: normal; TEXT-ALIGN: left
}
H2 {
BORDER-TOP: activecaption groove; MARGIN-TOP: 20pt; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: bold; FONT-SIZE: 150%; MARGIN-BOTTOM: 6pt; FONT-STYLE: normal; TEXT-ALIGN: left
}
H3 {
MARGIN-TOP: 18pt; DISPLAY: block; PADDING-LEFT: 5pt; FONT-WEIGHT: bold; FONT-SIZE: 130%; MARGIN-BOTTOM: 6pt; FONT-STYLE: normal; TEXT-ALIGN: left
}
UL {
MARGIN-TOP: 6pt; MARGIN-BOTTOM: 3pt; LIST-STYLE-TYPE: square
}
UL UL {
MARGIN-TOP: 3pt; MARGIN-BOTTOM: 3pt; LIST-STYLE-TYPE: disc
}
OL {
MARGIN-TOP: 6pt; MARGIN-BOTTOM: 3pt; MARGIN-LEFT: 42pt
}
OL OL {
MARGIN-TOP: 3pt; MARGIN-BOTTOM: 3pt; MARGIN-LEFT: 24pt; LIST-STYLE-TYPE: disc
}
LI {
MARGIN-TOP: 0pt; MARGIN-BOTTOM: 3pt; MARGIN-LEFT: -12pt
}
TABLE {
BORDER-TOP: silver 1.5pt solid; MARGIN-TOP: 3pt; FONT-WEIGHT: normal; FONT-SIZE: 95%; MARGIN-BOTTOM: 10pt; MARGIN-LEFT: 5pt; BORDER-BOTTOM: silver 1.5pt solid; TEXT-ALIGN: left
}
TR {
VERTICAL-ALIGN: top
}
TH {
PADDING-RIGHT: 3pt; FONT-WEIGHT: bold; FONT-SIZE: 90%; VERTICAL-ALIGN: bottom; COLOR: navy
}
TD {
PADDING-RIGHT: 3pt; BORDER-TOP: silver 1pt solid; VERTICAL-ALIGN: top
}
CODE {
COLOR: #001095; FONT-FAMILY: courier
}
PRE {
PADDING-RIGHT: 5pt; MARGIN-TOP: 3pt; PADDING-LEFT: 5pt; FONT-SIZE: 100%; VISIBILITY: visible; MARGIN-BOTTOM: 0pt; PADDING-BOTTOM: 3pt; MARGIN-LEFT: 5pt; OVERFLOW: visible; WIDTH: 2pc; COLOR: #001095; PADDING-TOP: 3pt; FONT-FAMILY: "Courier New"; BACKGROUND-COLOR: #f5f5f5
}
</STYLE></p>

Borland Developer Studio 2006, Update 2 Release Notes

This file contains important supplementary information about the features and
fixes that are included in this updated release of Borland Developer Studio
2006. Update 2 is a cumulative release, and contains all of the code from
Borland Developer Studio 2006, plus the enhancements and fixes that were added
for Update 1 and Update 2.

This file includes installation instructions for this update, information
about issues that were resolved for Update 1 and Update 2, and information about
issues that we are currently working on (known problems). This information may
not appear in the main product documentation. Borland recommends that you read
this file in its entirety.

In addition to this update, there is now a new version of Intraweb available
on the Intraweb website, and there is an InterBase 7.5.1 SP1 update available
for Windows, at the following website: href="InterBase">http://support.borland.com/entry.jspa?externalID=4107&categoryID=40">InterBase
7.5.1 SP1.

For information about installation, deployment, and licensing issues, see the
Install, Deploy, and License files located, by default, at C:\Program
Files\Borland\BDS\4.0.

Update Installation Instructions

Note: This update can only be applied to the English version
of Borland Developer Studio 2006.

This update can be applied to either the initial release of BDS 2006 or BDS
2006, Update 1. This update cannot be removed. To uninstall this update, you
will have to remove the full product and re-install the product, including
Update 1 if necessary.

Close Borland Developer Studio 2006 before installing this update.
If you have MSI 3.0 or above, double-click on the .msp file to begin
installation. Otherwise, navigate to the System32 folder in a command window
and type the following to start the installation.
Type in the command line syntax for your MSI version.

Command line syntax for MSI 2.0:

msiexec.exe /p /L*v DEBUG_MODE=ON REINSTALL=ALL REINSTALLMODE=omus

where:

/L*v and DEBUG_MODE=ON are optional.

For example, if you have the .msp file in C:\temp directory, then
msiexec.exe /p "C:\temp\bds2006_arch_upd2.msp" REINSTALL=ALL REINSTALLMODE=omus will install the update.

The following example will also generate a log file named
bds2006upd2.log under C:\temp
msiexec.exe /p "C:\temp\bds2006_arch_upd2.msp" /L*v "C:\temp\bds2006upd2.log" REINSTALL=ALL REINSTALLMODE=omus DEBUG_MODE=ON
Command line syntax for MSI 3.0 or above:

msiexec.exe /update /L*v file> DEBUG_MODE=ON

where:

/L*v and DEBUG_MODE=ON are optional.

For example, if you have the .msp file in C:\temp directory, then
msiexec.exe /update “C:\temp\bds2006_arch_upd2.msp” /L*v “C:\temp\bds2006_arch_upd2.log” DEBUG_MODE=ON will install the update.

For more information on MSI command-line options, please visit href="Microsoft">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/command_line_options.asp">Microsoft
MSI Command Line Options.
The final dialog of the update installer indicates whether the update was
successful. You can also verify using one of the following methods:

Open the Windows Control Panel, click Add/Remove Programs, and then choose
the Borland Developer Studio 2006 product. Use the Click here for support information link and verify that the version is 10.0.2.

Open the registry using regedit and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\BORLAND\BDS\4.0 and verify that the
ProductVersion and UpdatePackInstalled string values
are 10.0.2 and 2, respectively.

With the IDE open, choose Help | About to display the About
dialog box. Verify that Update 2 appears after the product
version number.

Resolved Defects

To view the list of resolved defects for Borland Developer Studio 2006,
Update 2, go to the following website: href="http://bdn.borland.com/article/0,1410,33463,00.htmlhttp://bdn.borland.com/article/0,1410,33463,00.html">http://bdn.borland.com/article/0,1410,33463,00.html>
To look up the resolution for specific bugs you have reported, you can go to the
following website: href="http://qc.borland.com/wc/qcmain.aspxhttp://qc.borland.com/wc/qcmain.aspx">http://qc.borland.com/wc/qcmain.aspx>
and look up the resolutions for defects you reported by Quality Central bug
number.

Known Issues

The following are known issues in Borland Developer Studio 2006, Update
2.

General

The behavior of WideChar/String compatibility has changed in Borland
Developer Studio 2006. Specifically, in Borland Developer Studio 2005, and
earlier, the following function would produce the result TRUE. Now it produces
FALSE.
```
function DoIt: Boolean;
var
  C: WideChar;
begin
   C := #0;
   if C = '' then
      Result := TRUE
  else
     Result := FALSE;
end;
```
This behavior is consistent with the behavior of the .NET compiler, but
could break your existing code.

Similar behavior exists with AnsiChar
in Win32, but that function has not yet been modified to be consistent with
the .NET compiler, so it still produces a TRUE result.
There is some confusion about how to compile a SOAP server application
when you are using Borland Developer Studio 2006 with Indy10.

To
compile a SOAP server application using Indy10: include the VCL source in your
project; add C:\Program Files\Borland\BDS\4.0\source\Win32\Internet;C:\Program Files\Borland\BDS\4.0\source\Win32\Indy9;C:\Program Files\Borland\BDS\4.0\source\Win32\soap to your search path; and
recompile.

C

To resolve issues with C name-mangling when using C and Delphi
together, a change has been made in the Delphi to C header file generation.
This change may cause some of your existing code to not compile due to cast
errors during the processing of the .HPP files, such as "Cannot convert..." or "Type mismatch in parameter...".

Three of the errors that commonly occur with this issue (or while
trying to fix this issue) are:
```
Cannot convert 'TPropInfo * *' to 'TPropInfo * ( *)[16380]'
```
```
Type mismatch in parameter 'PropList' (wanted 'TPropInfo * ( *)[16380]', got 'TPropInfo * *')
```
and
```
Pointer to structure required on left side of -> or ->*
```
To
correct these errors, it may be necessary to change the declaration type
and/or add casts. For example, the following snippets of code show some
typical changes that may be necessary to avoid errors.

Code created
before Update 2:
```
TButton* btn = new TButton((void*)0);
 PTypeInfo TypeInfo = reinterpret_cast(btn->ClassInfo());
 PTypeData TypeData = GetTypeData(TypeInfo);
 PPropList PropList = new PPropInfo[TypeData->PropCount];
 GetPropInfos(TypeInfo, PropList);
 for( int i =0; i<5; i   )
    ShowMessage(AnsiString(PropList[i]->Name));
```
needs to be changed to the following (so that it will work with and
after Update 2):
```
TButton* btn = new TButton((void*)0);
 PTypeInfo TypeInfo = reinterpret_cast(btn->ClassInfo());
 PTypeData TypeData = GetTypeData(TypeInfo);
 PPropInfo* PropList = new PPropInfo[TypeData->PropCount];
 GetPropInfos(TypeInfo, (PPropList)PropList);
 for( int i =0; i<5; i   )
    ShowMessage(AnsiString(PropList[i]->Name));
```
Compiling C Win32 source code that was previously generated
via importing a Type Library, may result in these types of errors. Similarly,
these errors can be resolved via casts or changes in type declaration.
Alternatively, a new import using post-patch import tools will result in the
necessary casts in the resultant generated source code.

For example,
the following previously imported generated code results in an error:
```
TControlData TSomeControl::CControlData =
{
  TFontIDs, //Error E2034 Cannot convert 'int *' to 'int ( *)[65536]'
```
A re-import will result in casts in the generated code:
```
TControlData TSomeControl::CControlData =
{
  Activex::PDispIDList(TFontIDs), //No Error
```

Compiler

Certain ActiveX projects may encounter an Internal Compiler Error (ICE)
when compiling the project source of the project. (The project source of a
project is the .cpp file that contains either the DllEntryPoint or WinMain
routine). The error will typically be encountered on the line that creates an
instance of a TComModule. The following snippet illustrates an example of such
code:
```
#include 
#pragma hdrstop
TComModule _ProjectModule(0 /*InitATLServer*/);  << Compiler Error Here
TComModule &_Module = _ProjectModule;
```
This error is related to the compiler using precompiled header to
instantiate the TComModule instance. To workaround this problem, move the
‘#pragma hdrstop’ directive to the very top of the .cpp file as shown below:
```
#pragma hdrstop   << First line of project source
#include 
TComModule _ProjectModule(0 /*InitATLServer*/);  << Compiler Error Here
TComModule &_Module = _ProjectModule;
```
NOTE: The line above with the compiler error is
slightly different for In-Proc servers: the object is constructed without the
'0' parameter. However, the behavior is still the same.

If the
solution above doesn't work then the most effective work around is to turn off
the precompiled headers. Do this by going to Project, Options, C Compiler,
Pre-compiled headers and uncheck -He, -H=, -Hc and -Hs. The next time you
build you won't get an internal compiler error.

Also delete the
external types files in the same directory. These files will have the
extension #nn where n is a number. For example, if vcl100.csm is
the name of the precompiled header, delete vcl100.#*.

ECO

When upgrading an ECO II model to an ECO III model, the method AsIObject
sometimes converts with the wrong visibility, strict private instead of
public, possibly causing a compilation error. Should this happen, the
visibility can be adjusted manually in the generated source; insert a line
with the “public” access modifier directly before the AsIObject function,
like:
```
public
    function AsIObject: IObjectInstance;
```

There is a known issue in the translation of Ocl expressions to SQL
queries that occurs under some circumstances when navigating a relation from a
loop-variable, such as:
```
Person.allInstances->select(home.address = 'myAddress')
```
This results in a stack overflow exception. This issue affects both
OclPsHandle and IOclPsService.

IDE

Some users are not able to drag and drop items successfully from the Tool
Palette. If you are experiencing this issue, you may have to change the 'Show
Windows contents while dragging' option on your computer.

If you are
using Windows 2000, open the Control Panel and choose Display | Effects. Make
sure the 'Show Windows contents while dragging' option is enabled, and Apply
your changes.

If you are using WindowsXP, open the Control Panel and
choose System. Click the Performance button. Select Settings. Make sure the
'Show Windows contents while dragging' option is enabled, and Apply your
changes.

.NET/BDE

If you're using the Borland Database Engine (BDE) within the Delphi.NET
personality, meta data such as table names, field names, and stored procedure
names are truncated if the name string uses international characters.

Copyright © 2006
Borland Software Corporation. All Borland brand and product names are trademarks
or registered trademarks of Borland Software Corporation in the United States
and other countries. All other marks are the property of their respective
owners.

</BODY></HTML>

axsoft
版主

發表：681
回覆：1056
積分：969
註冊：2002-03-13

發送簡訊給我

#2 引用回覆回覆

發表時間：2006-07-12 16:30:52

IP:61.219.xxx.xxx 未訂閱

Borland Developer Studio 2006, Update 2 Release Notes

This file contains important supplementary information about the features and fixes that are included in this updated release of Borland Developer Studio 2006. Update 2 is a cumulative release, and contains all of the code from Borland Developer Studio 2006, plus the enhancements and fixes that were added for Update 1 and Update 2.

This file includes installation instructions for this update, information about issues that were resolved for Update 1 and Update 2, and information about issues that we are currently working on (known problems). This information may not appear in the main product documentation. Borland recommends that you read this file in its entirety.

In addition to this update, there is now a new version of Intraweb available on the Intraweb website, and there is an InterBase 7.5.1 SP1 update available for Windows, at the following website: InterBase 7.5.1 SP1.

For information about installation, deployment, and licensing issues, see the Install, Deploy, and License files located, by default, at C:\Program Files\Borland\BDS\4.0.

Update Installation Instructions

Note: This update can only be applied to the English version of Borland Developer Studio 2006.

This update can be applied to either the initial release of BDS 2006 or BDS 2006, Update 1. This update cannot be removed. To uninstall this update, you will have to remove the full product and re-install the product, including Update 1 if necessary.

Close Borland Developer Studio 2006 before installing this update.
If you have MSI 3.0 or above, double-click on the .msp file to begin installation. Otherwise, navigate to the System32 folder in a command window and type the following to start the installation.
Type in the command line syntax for your MSI version.
Command line syntax for MSI 2.0:

msiexec.exe /p /L*v DEBUG_MODE=ON REINSTALL=ALL REINSTALLMODE=omus

where:

/L*v and DEBUG_MODE=ON are optional.

For example, if you have the .msp file in C:\temp directory, then msiexec.exe /p "C:\temp\bds2006_arch_upd2.msp" REINSTALL=ALL REINSTALLMODE=omus will install the update.

The following example will also generate a log file named bds2006upd2.log under C:\temp
msiexec.exe /p "C:\temp\bds2006_arch_upd2.msp" /L*v "C:\temp\bds2006upd2.log" REINSTALL=ALL REINSTALLMODE=omus DEBUG_MODE=ON
Command line syntax for MSI 3.0 or above:

msiexec.exe /update /L*v DEBUG_MODE=ON

where:

/L*v and DEBUG_MODE=ON are optional.

For example, if you have the .msp file in C:\temp directory, then msiexec.exe /update “C:\temp\bds2006_arch_upd2.msp” /L*v “C:\temp\bds2006_arch_upd2.log” DEBUG_MODE=ON will install the update.

For more information on MSI command-line options, please visit Microsoft MSI Command Line Options.
The final dialog of the update installer indicates whether the update was successful. You can also verify using one of the following methods:
Open the Windows Control Panel, click Add/Remove Programs, and then choose the Borland Developer Studio 2006 product. Use the Click here for support information link and verify that the version is 10.0.2.

Open the registry using regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\BORLAND\BDS\4.0 and verify that the ProductVersion and UpdatePackInstalled string values are 10.0.2 and 2, respectively.

With the IDE open, choose Help | About to display the About dialog box. Verify that Update 2 appears after the product version number.

Resolved Defects

To view the list of resolved defects for Borland Developer Studio 2006, Update 2, go to the following website: http://bdn.borland.com/article/0,1410,33463,00.html To look up the resolution for specific bugs you have reported, you can go to the following website: http://qc.borland.com/wc/qcmain.aspx and look up the resolutions for defects you reported by Quality Central bug number.

Known Issues

The following are known issues in Borland Developer Studio 2006, Update 2.

General

The behavior of WideChar/String compatibility has changed in Borland Developer Studio 2006. Specifically, in Borland Developer Studio 2005, and earlier, the following function would produce the result TRUE. Now it produces FALSE.
```
function DoIt: Boolean;
var
  C: WideChar;
begin
   C := #0;
   if C = '' then
      Result := TRUE
  else
     Result := FALSE;
end;
```
This behavior is consistent with the behavior of the .NET compiler, but could break your existing code.

Similar behavior exists with AnsiChar in Win32, but that function has not yet been modified to be consistent with the .NET compiler, so it still produces a TRUE result.
There is some confusion about how to compile a SOAP server application when you are using Borland Developer Studio 2006 with Indy10.

To compile a SOAP server application using Indy10: include the VCL source in your project; add C:\Program Files\Borland\BDS\4.0\source\Win32\Internet;C:\Program Files\Borland\BDS\4.0\source\Win32\Indy9;C:\Program Files\Borland\BDS\4.0\source\Win32\soap to your search path; and recompile.

To resolve issues with C name-mangling when using C and Delphi together, a change has been made in the Delphi to C header file generation. This change may cause some of your existing code to not compile due to cast errors during the processing of the .HPP files, such as "Cannot convert..." or "Type mismatch in parameter...".

Three of the errors that commonly occur with this issue (or while trying to fix this issue) are:
```
Cannot convert 'TPropInfo * *' to 'TPropInfo * ( *)[16380]'
```
```
Type mismatch in parameter 'PropList' (wanted 'TPropInfo * ( *)[16380]', got 'TPropInfo * *')
```
and
```
Pointer to structure required on left side of -> or ->*
```
To correct these errors, it may be necessary to change the declaration type and/or add casts. For example, the following snippets of code show some typical changes that may be necessary to avoid errors.

Code created before Update 2:
```
TButton* btn = new TButton((void*)0);
        PTypeInfo TypeInfo = reinterpret_cast(btn->ClassInfo());
        PTypeData TypeData = GetTypeData(TypeInfo);
        PPropList PropList = new PPropInfo[TypeData->PropCount];
        GetPropInfos(TypeInfo, PropList);
        for( int i =0; i<5; i   )
           ShowMessage(AnsiString(PropList[i]->Name));
```
needs to be changed to the following (so that it will work with and after Update 2):
```
TButton* btn = new TButton((void*)0);
        PTypeInfo TypeInfo = reinterpret_cast(btn->ClassInfo());
        PTypeData TypeData = GetTypeData(TypeInfo);
        PPropInfo* PropList = new PPropInfo[TypeData->PropCount];
        GetPropInfos(TypeInfo, (PPropList)PropList);
        for( int i =0; i<5; i   )
           ShowMessage(AnsiString(PropList[i]->Name));
```
Compiling C Win32 source code that was previously generated via importing a Type Library, may result in these types of errors. Similarly, these errors can be resolved via casts or changes in type declaration. Alternatively, a new import using post-patch import tools will result in the necessary casts in the resultant generated source code.

For example, the following previously imported generated code results in an error:
```
TControlData TSomeControl::CControlData =
{
  TFontIDs, //Error E2034 Cannot convert 'int *' to 'int ( *)[65536]'
```
A re-import will result in casts in the generated code:
```
TControlData TSomeControl::CControlData =
{
  Activex::PDispIDList(TFontIDs), //No Error
```

Compiler

Certain ActiveX projects may encounter an Internal Compiler Error (ICE) when compiling the project source of the project. (The project source of a project is the .cpp file that contains either the DllEntryPoint or WinMain routine). The error will typically be encountered on the line that creates an instance of a TComModule. The following snippet illustrates an example of such code:
```
#include 
#pragma hdrstop    TComModule _ProjectModule(0 /*InitATLServer*/);  << Compiler Error Here
TComModule &_Module = _ProjectModule;
```
This error is related to the compiler using precompiled header to instantiate the TComModule instance. To workaround this problem, move the ‘#pragma hdrstop’ directive to the very top of the .cpp file as shown below:
```
#pragma hdrstop   << First line of project source
#include     TComModule _ProjectModule(0 /*InitATLServer*/);  << Compiler Error Here
TComModule &_Module = _ProjectModule;
```
NOTE: The line above with the compiler error is slightly different for In-Proc servers: the object is constructed without the '0' parameter. However, the behavior is still the same.

If the solution above doesn't work then the most effective work around is to turn off the precompiled headers. Do this by going to Project, Options, C Compiler, Pre-compiled headers and uncheck -He, -H=, -Hc and -Hs. The next time you build you won't get an internal compiler error.

Also delete the external types files in the same directory. These files will have the extension #nn where n is a number. For example, if vcl100.csm is the name of the precompiled header, delete vcl100.#*.

ECO

When upgrading an ECO II model to an ECO III model, the method AsIObject sometimes converts with the wrong visibility, strict private instead of public, possibly causing a compilation error. Should this happen, the visibility can be adjusted manually in the generated source; insert a line with the “public” access modifier directly before the AsIObject function, like:
```
public
    function AsIObject: IObjectInstance;
```

There is a known issue in the translation of Ocl expressions to SQL queries that occurs under some circumstances when navigating a relation from a loop-variable, such as:
```
Person.allInstances->select(home.address = 'myAddress')
```
This results in a stack overflow exception. This issue affects both OclPsHandle and IOclPsService.

IDE

Some users are not able to drag and drop items successfully from the Tool Palette. If you are experiencing this issue, you may have to change the 'Show Windows contents while dragging' option on your computer.

If you are using Windows 2000, open the Control Panel and choose Display | Effects. Make sure the 'Show Windows contents while dragging' option is enabled, and Apply your changes.

If you are using WindowsXP, open the Control Panel and choose System. Click the Performance button. Select Settings. Make sure the 'Show Windows contents while dragging' option is enabled, and Apply your changes.

.NET/BDE

If you're using the Borland Database Engine (BDE) within the Delphi.NET personality, meta data such as table names, field names, and stored procedure names are truncated if the name string uses international characters.

Copyright © 2006 Borland Software Corporation. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners.

系統時間：2024-04-19 9:48:15

聯絡我們 | Delphi K.Top討論版

本站聲明

1. 本論壇為無營利行為之開放平台，所有文章都是由網友自行張貼，如牽涉到法律糾紛一切與本站無關。
2. 假如網友發表之內容涉及侵權，而損及您的利益，請立即通知版主刪除。
3. 請勿批評中華民國元首及政府或批評各政黨，是藍是綠本站無權干涉，但這裡不是政治性論壇！