diff --git a/docs/Help/Topics/Building-XSharp-apps-with-Visu.xml b/docs/Help/Topics/Building-XSharp-apps-with-Visu.xml
index 38f69c144c..59154bd949 100644
--- a/docs/Help/Topics/Building-XSharp-apps-with-Visu.xml
+++ b/docs/Help/Topics/Building-XSharp-apps-with-Visu.xml
@@ -1,6 +1,6 @@
-
+Building XSharp apps with Visual Studio and/or MsBuild.g.prg
@@ -131,15 +131,15 @@
How does MSBuild locate referenced assembliesWhen locating the referenced assemblies needed for compiling your project it looks at the following:
-
+
When the reference node has a "hintpath", it tries to locate the file through this path. That could look like <HintPath>..\\SDK_Defines.dll</HintPath>
-
When the reference node is a "normal" .Net framework assembly, it looks at the folder on your file system that matches the framework version. For example, when the framework version of your project is 4.6 (there will be a node <TargetFrameworkVersion>v4.6</TargetFrameworkVersion>), it will look for System.DLL in the folder c:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6
+
When the reference node is a "normal" .Net framework assembly, it looks at the folder on your file system that matches the framework version. For example, when the framework version of your project is 4.7 (there will be a node <TargetFrameworkVersion>v4.7</TargetFrameworkVersion>), it will look for System.DLL in the folder c:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.7
When the reference node is not a standard .Net framework assembly and the third party vendor has registered a folder in a specific location, MsBuild will use that location. X# registers a folder in the HKLM\Software\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\XSharplocation. Files registered in a location like this are also shown in the "Add References" dialogs in Visual Studio.
Finally, during building, MSBuild will look in the Global Assembly Cache (GAC).
Please note that there is a difference between Compiling and Running. During compilation, the files in the reference folders take precedence over those in the GAC. However, when running the application, the GAC and/or the local folder or path are used. Files in the reference folders are NEVER used at runtime. This would also not be possible, as these files contain no executable code in them.
- The purpose of the separation is to allow you to compile against an older Framework version (e.g., 4.6), even if a newer version (e.g., 4.8) is installed. The reference assembly in the 4.6 folder contains only the subset of the API that was available in .Net Framework 4.6. This ensures that you cannot (accidentally) use methods or types introduced in later Framework versions, even though those methods or types might be present in the GAC.
+ The purpose of the separation is to allow you to compile against an older Framework version (e.g., 4.7, even if a newer version (e.g., 4.8) is installed. The reference assembly in the 4.7 folder contains only the subset of the API that was available in .Net Framework 4.7. This ensures that you cannot (accidentally) use methods or types introduced in later Framework versions, even though those methods or types might be present in the GAC.How does MSBuild locate project references
diff --git a/docs/Help/Topics/Nuget-Packages.xml b/docs/Help/Topics/Nuget-Packages.xml
index de6e51bf72..1fb2d68ce5 100644
--- a/docs/Help/Topics/Nuget-Packages.xml
+++ b/docs/Help/Topics/Nuget-Packages.xml
@@ -1,12 +1,12 @@
-
+Nuget PackagesNuget Packages
- XSharp 3 comes with nuget packages for the runtime. These packages contain assemblies and support files for both .Net Framework 4.6 and .Net 8.0
+ XSharp 3 comes with nuget packages for the runtime. These packages contain assemblies and support files for both .Net Framework 4.7 and .Net 8.0There are the following packages:
@@ -90,7 +90,7 @@
- XSharp.VOSDK For .Net framework 4.6
+ XSharp.VOSDK For .Net framework 4.7
We want the code to compile in "Safe" mode, and avoid unsafe code except when strictly needed. The biggest problem/challenge here is the PTR type. With a PTR you can access memory directly and read/write from memory, even if you don't "own" that memory. However, the same PTR type is also used as "unique identifier", for example in the low level file i/o, and in the GUI classes for Window and Control handles. These PTR values are never used to read or write memory, but are like object references. We have decided to use the .Net IntPtr type for these types of handles. Of course the compiler can transparently convert between PTR and IntPtr.
We want to prove that the X# language is a first class .Net development language, which is why we decided to write the X# runtime in X#. By doing that, we also create a large codebase to test the compiler, making it a win-win situation.
We want the runtime to be thread safe. Each thread has its own "global" state and its own list of open work areas. When a new thread is started, it inherits the state of the main thread, but it not the main thread's work areas.
-
At this moment, the X# Runtime is compiled against .Net Framework 4.6.
+
At this moment, the X# Runtime is compiled against .Net Framework 4.7.
Assemblies in the X# Runtime
@@ -52,7 +52,7 @@
X# Core
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -66,7 +66,7 @@
X# Core
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -80,7 +80,7 @@
X# non - core
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -94,7 +94,7 @@
X# core
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -108,7 +108,7 @@
X# VO and X# Vulcan
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -122,7 +122,7 @@
X# XPP
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -136,7 +136,7 @@
X# FoxPro
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -150,7 +150,7 @@
X# Core
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -164,7 +164,7 @@
X# Core
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -178,7 +178,7 @@
X# Core
- 4.6 / 8.0
+ 4.7 / 8.0
@@ -199,7 +199,7 @@
X# VO and X# Vulcan
- 4.6
+ 4.7
diff --git a/docs/Help/Topics/VersionHistory.xml b/docs/Help/Topics/VersionHistory.xml
index a0057f93f7..698ecd162d 100644
--- a/docs/Help/Topics/VersionHistory.xml
+++ b/docs/Help/Topics/VersionHistory.xml
@@ -1,8 +1,9 @@
-
+Version History
+ #2127ChangesRuntime chapterString Literals
@@ -14,7 +15,7 @@
Version HistoryNote: When an item has a matching GitHub ticket, the ticket number is behind the item in parentheses prefixed with #. You can find these tickets by going to: https://github.com/X-Sharp/XSharpPublic/issues/nnn , where nnn is the ticket number. If you find an issue in X#, we recommend that you report it on GitHub. You will be notified of the progress on the work on your issue
- Changes in XSharp 3.02
+ Changes in XSharp 3.1CompilerNew Features
@@ -31,6 +32,10 @@
Fixed parser state corruption in shared compiler-server builds (/shared), which could cause random dialect and reference errors during parallel builds (#2076)
Fixed primary-constructor edge cases, including empty primary constructors and preserving the primary constructor when a CLIPPER constructor is added
Fixed duplicate import warnings for namespaces supplied through ImplicitNameSpace/ClassLibrary attributes, and corrected problems with LOCAL ARRAY, PUBLIC ARRAY and DIMENSION declarations
+
Fixed a NullReferenceException in SemanticModel queries on compound assignments (#2096)
+
Fixed an IndexOutOfRangeException in the compiler when analyzers and .editorconfig files are used (#2098)
+
Fixed an issue with _DLL FUNCTION with PSZ arguments in .Net 5 or later (#2097)
+
Fixes two issues when including C# files in the source files for X# (#2151 and #2153)
Build System
@@ -38,10 +43,12 @@
Values set in Directory.Build.Props for DefaultItemExcludes are now preserved
Output folders are now excluded from the default globs
Prevent automatic setting from Windows platform for SDK projects
+
The Rules folder with XAML files is now included to support the new Rules based property dialog for SDK style projects
RuntimeNew Features
+
The target framework of the X# runtime is now .NET Framework 4.7
Added GETPRINTER(), PUTFILE(), LOCFILE() and INPUTBOX(), and completed WAIT WINDOW support (#1997, #1996)
Added VFP introspection functions and improved command coverage by absorbing CLEAR and RELEASE support (#1999, #2001)
Implemented ATAGINFO(), XMLTOCURSOR(), CURSORTOXML(), KEYMATCH(), LOOKUP() and basic NEWOBJECT() support in the VFP runtime (#2087, #2070, #2016, #2004, #2003)
@@ -57,6 +64,18 @@
Fixed Dbc.FindTable() to accept either an alias or a file name, and corrected long field-name collisions in DBFs
Fixed several XSharp.VFP.UI problems in grids, record-pointer preservation, transparent controls, shapes, shortcut popups, property casing, InputMask and Format handling, and icon and form behavior
Fixed wrong file offsets during shared file access on .NET 6 and later (#2082)
+
Fixed field and member lookup in __FieldGetWa2 for objects that support dynamic properties, and improved the error that is thrown when a variable cannot be found (#2092)
+
Fixed the usCulture used for conversions so it ignores Windows user overrides; this fixes Val(), Str() and Transform() when the user has a custom decimal symbol or digit grouping (#2100)
+
Fixed an issue with rounding small negative numbers (-0.0) with new .Net versions #2104
+
Fixed an issue with FindClass for types that are not yet loaded #2109
+
Nested codeblocks in macro scripts can now access locals from the surroundng code #2113
+
Allow implicit interface conversions in macros (#2114)
+
Fixed an issue with the FoxPro directory function (#2137)
+
Fixed an issue with late bound assigns to class properties in the FoxPro dialect
+
Changed the return type of the internal function that is called for the SCATTER ARRAY command from Array to FoxPro compatible array (__FoxArray)
+
SET EXACT ON in the VFP Dialect now ignores trailing blanks (#2160)
+
CURDIR() in the VFP dialect returns the directory formatted as in VFP (#2160)
+
Fixed STRTOFILE() additive clause for files that do not exist (#2160)
Visual Studio IntegrationNew Features
@@ -65,18 +84,33 @@
Added SDK-style project reference management in the IDE, including "Add Assembly Reference", "Add Project Reference" and Dependencies-node integration (#2041, #2048)
Added Target OS and runtime-identifier support to the SDK-style project property pages for modern .NET targets
Updated Visual Studio integration for the new FoxPro and XBaseNet compiler options, including /fox3-aware settings and parser support for newer language constructs
-
-
+
Added a CPS-based project system for SDK-style X# projects, with the XBaseNet dialect available in the project property pages (#2094). It also has full support for Multi-Targeting.
+
For multi targetting projects, the language service will include a project in the projects combobox for each of the targets. The intellisense information is retrieved from the framework selected in the combobox.
Added support for primary constructors and static interface constructors
+
Implemented the Project context menu option "Convert to SDK format" for projects in the legacy format. The old project file is saved with a .BAK extension.
+
The project Property pages are now based on the XAML files in the MsBuild Rules folder
+
Added support for several new Intellisense features, contributed by one of our customers (Thanks HansJoerg)
+
+
Added support for Find All References in the source code editor (#2148)
+
Added support for Renaming types and members (#2154)
+
Added support for Navigate To (Ctrl-T) for types and members (#2155) (only in VS2022 and later)
+
Added support for Goto Implementation types and members (#2156)
+ Bug Fixes
Fixed deadlocks and hangs when opening solutions or resolving references, including startup and open-from-command-line cases and UI-thread reference resolution (#2046, #2066)
Reduced UI-thread marshalling and code-model database lock contention, which improves responsiveness and SDK-style project load performance (#2084, #2043)
-
Fixed SDK-style NuGet restore and property-page handling for target frameworks with embedded platform identifiers such as net8-windows (#2085)
Improved handling of missing project files and prevented several exceptions and hierarchy hangs in the project system and designer support
Fixed the completion "Max Entries" option resetting to 25 (#2088)
-
Building for the Windows platform inside VS would create a project.assets.json file with target that did not have the platform (for example "net8.0" instead of "net8.0-windows". Building the same project from the DotNet CLI was working correctly. This is an issue in the NuGet support inside VS. We are now calling the DotNet CLI to restore the project.
+
Fixed threading issues in the VS Projectsystem (#2124, #2125, #2127)
+
Fixed an issue with the type lookup for the loop variables of a FOREACH loop (#2129)
+
Fixed an issue when closing a solution (#2138)
+
Fixed an issue with the navigation bar in the source code editor (#2144)
+
Fixed an issue when a project file contains an invalid configuration (#2145)
+
For multi-targeting projects Goto Definition could show the same definition twice. This has been solved
+
Fixed some issues when switching between Sqlite databases engines for the intellisense database. We now delete the database after changing the engine, so it will be rebuilt when the solution is reloaded.
+
Fixed an issue with Goto Definition for partial classes in other projects (#2110)
VFPExporterNew Features
diff --git a/docs/Help/Topics/command_BEGIN-CHECKED.xml b/docs/Help/Topics/command_BEGIN-CHECKED.xml
index 5f61924490..a567ce7fdd 100644
--- a/docs/Help/Topics/command_BEGIN-CHECKED.xml
+++ b/docs/Help/Topics/command_BEGIN-CHECKED.xml
@@ -19,7 +19,7 @@
PurposeThe BEGIN (UN)CHECKED and END (UN)CHECKED keywords mark a block of statements that are compiled with overflow checking enabled or disabled.Syntax
- BEGIN CHECKED statements END CHECKED
BEGIN UNCHECKED statements END CHECKED
+ BEGIN CHECKED statements END CHECKED
- The X# compiler is based on the open source project Roslyn, which contains the source to the Microsoft VB and C# compilers. Our project would have been impossible without this source. We are very grateful that Microsoft has moved this project to the open source. (github.com/dotnet/roslyn) The source code to Roslyn is published under the Apache License, version 2.
-
-
-
-
- Antlr
-
-
- The X# compiler uses Antlr 4 as parser generator to generate the front end of the compiler. We would like to thank Terence Parr and Sam Harwell for their excellent work.
- The source code to Antlr is published under the BSD License. (www.antlr.org)
-
-
-
-
- Wix (votive)
-
-
- The project system for Wix (Votive). We have been inspired by some of the code in this system. We would like to thank Rob Mensching and the other authors of this project system. (wixtoolset.org/)
-
-
-
-
- Nemerle
-
-
- The project system for Nemerle. We have been inspired by some of the solutions in their project system. We would like to thank the authors of Nemerle for showing us how to solve certain problems. (www.nemerle.org)
-
-
-
-
- F# project system
-
-
- The visual F# project system (www.fsharp.org)
-
-
-
-
- Help and Manual
-
-
- Our documentation is written with the excellent tool "Help and Manual" from Alexander Halser. (www.helpandmanual.com)
-
-
-
-
- Sandcastle Help File Builder
-
-
- The documentation for the runtime is generated with a special version of the Sandcastle Help File Builder product. (github.com/EWSoftware/SHFB)
-
-
-
-
- Paul Piko
-
-
- For his Hybrid classes that allow to mix VO GUI with Windows Forms.
-
-
-
-
- JB Evain
-
-
- We are using his Mono.Cecil library inside our project system to collect type information for external types.
-
-
-
-
- The SQLite team
-
-
- We are using their SQLite database inside our project system.
-
- Have contributed functions for the FoxPro library.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Amp_Command.xml b/docs/Help_Spanish/Topics/Amp_Command.xml
deleted file mode 100644
index 58f0b82839..0000000000
--- a/docs/Help_Spanish/Topics/Amp_Command.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- & Command
-
-
- & Command
-
- Enter topic text here.
-
-
diff --git a/docs/Help_Spanish/Topics/Apache-2.xml b/docs/Help_Spanish/Topics/Apache-2.xml
deleted file mode 100644
index 7c1fb02fe9..0000000000
--- a/docs/Help_Spanish/Topics/Apache-2.xml
+++ /dev/null
@@ -1,215 +0,0 @@
-
-
-
- Apache 2
-
-
- Apache 2
-
- Both the source code to the public elements of X# and to Roslyn are published under the Apache 2.0 license.
- You can find the public source code on Github in the XSharpPublic repository : https://github.com/X-Sharp/XSharpPublic. The full text of this license is:
-
-
- Apache License Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Array-Of-Type.xml b/docs/Help_Spanish/Topics/Array-Of-Type.xml
deleted file mode 100644
index b5ac39c0c0..0000000000
--- a/docs/Help_Spanish/Topics/Array-Of-Type.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- Array Of Type
-
- ARRAY OF
- XSharp.__ArrayBase
-
-
-
- Array Of Type
-
- This type is used for typed arrays. It has been introduced in the X# Runtime. The internal typename is XSharp.__ArrayBase The code below shows how you can use it.
- Many of the existing XBase runtime functions that accept arrays now also accept an ARRAY OF.
- Runtime functions that expect a codeblock for Arrays expect a Lambda expression for ARRAY OF.
- The difference is that the parameters to the Lambda expression will be typed, so no late binding is necessary.
- Parameters to a Codeblock are always of type usual and therefore either require Late Binding support or need to be casted to the right type inside the codeblock.
- We have also introduced a special multidimensional syntax. Given the example below you can also get the first name of the first developer in the array by using the following syntax:
- cFirst := aDevelopers[1, "FirstName"]
-
- This may be useful when you work with existing generated code and the existing code was using a define for the elements in the multidimensional array.
- If you had a (generated) define like
- DEFINE DEVELOPER_FirstName := 1
- then you can change the code generator and generate this instead
- DEFINE DEVELOPER_FirstName := "FirstName"
- The code that uses the define can remain unchanged
- cFirst := aDevelopers[1, DEVELOPER_FirstName]
- Example code
- FUNCTION Start ASVOID // declare typed array of developer objects LOCAL aDevelopers AS ARRAY OF Developer // Initialize the array with the "normal" array syntax aDevelopers := {} // AAdd also supports typed arrays AAdd(aDevelopers, Developer { "Chris","Pyrgas"}) AAdd(aDevelopers, Developer { "Nikos", "Kokkalis"}) AAdd(aDevelopers, Developer { "Fabrice", "Foray"}) AAdd(aDevelopers, Developer { "Robert", "van der Hulst"}) // AEval knows that each element is a developer AEval(aDevelopers, { d => Console.WriteLine(d)}) // ASort knows the type and passes the correct types to the lambda expression. // The compiler and runtime "know" that x and y are Developer objects and will produce early bound code ASort( aDevelopers, 1, ALen(aDevelopers), { x, y => x:LastName < y:LastName}) // Foreach knows that each element is a Developer object FOREACHVAR oDeveloper IN aDevelopers ? oDeveloper:LastName, oDeveloper:FirstName NEXT RETURN
- Store the value of the second operand in the object specified by the first operand (simple assignment).
-
-
-
-
- =
-
-
- x = y
-
-
- Store the value of the second operand in the object specified by the first operand (simple assignment). This is allowed in the VFP dialect only! In all other dialects, assigning a value with a '=' operator will generate a warning.
-
-
-
-
- +=
-
-
- x += y
-
-
- Add the value of the second operand to the value of the first operand; store the result in the object specified by the first operand
-
-
-
-
- -=
-
-
- x -= y
-
-
- Subtract the value of the second operand from the value of the first operand; store the result in the object specified by the first operand.
-
-
-
-
- /=
-
-
- x /= y
-
-
- Divide the value of the first operand by the value of the second operand; store the result in the object specified by the first operand.
-
-
-
-
- %=
-
-
- x %= y
-
-
- Take modulus of the first operand specified by the value of the second operand; store the result in the object specified by the first operand.
-
-
-
-
- *=
-
-
- x *= y
-
-
- Multiply the value of the first operand by the value of the second operand; store the result in the object specified by the first operand.
-
-
-
-
- ^= or **=
-
-
- x ^= y
-
-
- Calculate the exponent of the first operand and the second operand; store the result in the object specified by the first operand. Please note that in languages such as C# the ^= operator performs a Bitwise XOR.
-
-
-
-
- |=
-
-
- x |= y
-
-
- Obtain the bitwise inclusive OR of the first and second operands; store the result in the object specified by the first operand.
-
-
-
-
- &=
-
-
- x &= y
-
-
- Obtain the bitwise AND of the first and second operands; store the result in the object specified by the first operand.
-
-
-
-
- ~=
-
-
- x ~= y
-
-
- Obtain the bitwise exclusive OR of the first and second operands; store the result in the object specified by the first operand.
-
-
-
-
- <<=
-
-
- x <<= y
-
-
- Shift the value of the first operand left the number of bits specified by the value of the second operand; store the result in the object specified by the first operand.
-
-
-
-
- >>=
-
-
- x >>= y
-
-
- Shift the value of the first operand right the number of bits specified by the value of the second operand; store the result in the object specified by the first operand.
-
-
-
-
- ?=
-
-
- a ?= "somevalue"
-
-
- When a is NULL then it will be assigned "somevalue". Otherwise a is not changed
-
-
-
- Assignment operators and XBase types
- See the topic about Binary operators to see which complex assignment operators are supported.
-
-
diff --git a/docs/Help_Spanish/Topics/BEGIN-NAMESPACE.xml b/docs/Help_Spanish/Topics/BEGIN-NAMESPACE.xml
deleted file mode 100644
index 94c9656509..0000000000
--- a/docs/Help_Spanish/Topics/BEGIN-NAMESPACE.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- BEGIN NAMESPACE
-
- BEGIN
- BEGIN NAMESPACE
- END
- END NAMESPACE
- NAMESPACE
-
-
-
- BEGIN NAMESPACE
-
- Purpose
- The BEGIN NAMESPACE and END NAMESPACE keyword pairs declare a scope and add a namespace prefix to all types declared inside this scope.
-
- Syntax
- BEGIN NAMESPACE namespaceName typeDeclarations namespaceDeclarations END NAMESPACE
- Arguments
-
- namespaceNameThe name of the namespace being declared.
- typeDeclarations One or more type declarations (CLASS, STRUCTURE, etc.).
- namespaceDeclarations Zero or more namespace declarations.
-
-
- Any types declared within a namespace scope have the namespace name prepended to the type name. For example, a class named "MyClass" that is declared within a namespace named "MyNamespace" will have a type name of "MyNamespace.MyClass".
-
- Types declared outside any namespace scope are declared in the "global" or "unnamed" namespace.
-
- BEGIN NAMESPACE ... END NAMESPACE blocks can be nested to any depth. Nested namespace names have the enclosing namespace name prepended to it, separated by a period.
-
- The same namespace name may be declared multiple times in the same or different files. The BEGIN NAMESPACE and END NAMESPACE statements do not cause any code to be generated, they simply affect the name of any types declared within the namespace block.
-
- using directives that appear within a namespace are only in effect within the enclosing namespace block, and any nested namespace blocks.
- Compatibility Note:
- Code migrated from Visual Objects to Vulcan.NET using the Transporter is not placed within any BEGIN NAMESPACE ... END NAMESPACE blocks, because Visual Objects has no concept of namespaces. Therefore, all classes in transported code are in the global or "unnamed" namespace and do not have a namespace name prepended to them.
-
- Example
- BEGINNAMESPACE a CLASS one // actual type name is 'a.one' ... ENDCLASS BEGINNAMESPACE b // the namespace name is 'a.b' CLASS two // actual type name is 'a.b.two' ... ENDCLASS ENDNAMESPACE ENDNAMESPACE CLASS three // actual type name is 'three' ... ENDCLASS
-
-
diff --git a/docs/Help_Spanish/Topics/BINARY.xml b/docs/Help_Spanish/Topics/BINARY.xml
deleted file mode 100644
index 1b7b81f4a6..0000000000
--- a/docs/Help_Spanish/Topics/BINARY.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- BINARY
-
- BINARY
-
-
-
- BINARY
-
- The BINARY type is represented a series of bytes.
-
-
-
Binary literals are written as 0h12345678abcdef.
-
The value behind 0h is a sequence of hex numbers. Each pair of hex numbers (nibble) represents 1 byte. There must be an even number of 'nibbles'.
-
The binary literals are encoded in an array of bytes. In the Core dialect, the binary literals are represented as a byte[]. In the other dialects, the binary literals are a new type (XSharp.__Binary), which can be specified as the new BINARY keyword.
-
The UsualType() of BINARY is 29.
-
The XSharp.__Binary type has operators to add a string to a binary and add a binary to a string. Binary + String will return a Binary. String + Binary will return a String. Binary + Binary will return a Binary. There are also comparison operators on the Binary type (>, <, >=, <=). These will use the string comparison routines that are defined with SetCollation(), with the exception that an = comparison with a single equals operator does not return TRUE when the Right hand side is shorter than the Left hand side and the first bytes match.
-
Conversions from Binary to String are done with the Encoding.GetBytes() and Encoding.GetString() functions for the current Windows Encoding. That means that on single byte code pages each character in the string will result in one byte and each byte will result in one character. For multibyte code pages (Chinese, Japanese, Korean, etc.), some characters will result in more than one byte, and some byte pairs will result in a single character.
-
There are implicit operators that convert a BINARY to a byte[] and back. There are also implicit operators that convert a Binary to a String and back.
-
When compiling with the Vulcan Runtime, the byte[] array is stored in a USUAL value for the non core dialects.
-
- Implementation
- The BINARY type is implemented in the class XSharp.__Binary. The Usualtype of BINARY has the value 29.
-
-
diff --git a/docs/Help_Spanish/Topics/BSD.xml b/docs/Help_Spanish/Topics/BSD.xml
deleted file mode 100644
index c48783eae3..0000000000
--- a/docs/Help_Spanish/Topics/BSD.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- BSD
-
-
- BSD
-
- The Antlr source that we have used in our product is published under the BSD license. The full text of this license is:
-
- [The "BSD license"]
- Copyright (c) 2015 Terence Parr, Sam Harwell
- All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
- 3. The name of the author may not be used to endorse or promote products
- derived from this software without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
- IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
- IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
- NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
- DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
- THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
- (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
- THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-
diff --git a/docs/Help_Spanish/Topics/BYTE.xml b/docs/Help_Spanish/Topics/BYTE.xml
deleted file mode 100644
index 8f3214d6e7..0000000000
--- a/docs/Help_Spanish/Topics/BYTE.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- BYTE
-
- BYTE
-
-
-
- BYTE
-
- The BYTE keyword denotes an integral type that stores unsigned 8-bit values with values that range from 0 to 255.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Binary-Literals.xml b/docs/Help_Spanish/Topics/Binary-Literals.xml
deleted file mode 100644
index 7b5147d001..0000000000
--- a/docs/Help_Spanish/Topics/Binary-Literals.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Binary Literals
-
- BINARY
- Binary Literals
-
-
-
- Binary Literals
-
- Binary literals are written as 0h12345678abcdef
- The value behind 0h is a sequence of hex numbers. Each pair of hex numbers (nibble) represents 1 byte. There must be an even number of 'nibbles'.
- The compiler compiles these literals into a byte[] array, which is stored into a variable of the type BINARY.
-
-
diff --git a/docs/Help_Spanish/Topics/Binary_Operators.xml b/docs/Help_Spanish/Topics/Binary_Operators.xml
deleted file mode 100644
index af5b4f2c63..0000000000
--- a/docs/Help_Spanish/Topics/Binary_Operators.xml
+++ /dev/null
@@ -1,205 +0,0 @@
-
-
-
- Binary
-
- -
- %
- *
- **
- /
- ^
- +
- binary operators
- operator
-
-
-
- Binary Operators
-
- X# uses the following binary operators:
-
-
-
-
- Operator
-
-
- Example
-
-
- Meaning
-
-
-
-
- +
-
-
- x + y
-
-
- addition
-
-
-
-
- -
-
-
- x - y
-
-
- subtraction
-
-
-
-
- *
-
-
- x * y
-
-
- multiplication
-
-
-
-
- /
-
-
- x / y
-
-
- division. If the operands are integers, the result is an integer truncated toward zero (for example, -7 / 2 is -3).
-
-
-
-
- %
-
-
- x % y
-
-
- modulus. If the operands are integers, this returns the remainder of dividing x by y. If q = x / y and r = x % y, then x = q * y + r.
-
-
-
-
- ^ or **
-
-
- x ^ y or x ** y
-
-
- power of. x ^ y returns x to the power of y
-
-
-
-
- default or ??
-
-
- x DEFAULT y x ?? y
-
-
- When x is not null then x, otherwise y. Can be chained: x DEFAULT y DEFAULT z or x ?? y ?? z
-
-
-
-
-
-
-
-
-
-
-
-
- Binary operators and XBase types
- The following XBase types support binary operators:
-
-
-
-
- Type
-
-
- Operator
-
-
- Description
-
-
-
-
- ARRAY
-
-
- none
-
-
- Binary operators are not supported for arrays.
-
-
-
-
- DATE
-
-
- + and -
-
-
- You can add and subtract a numeric to a date, which is the equivalent of adding days. You can subtract a date from a date which will return the number of days between the dates.
-
-
-
-
- FLOAT
-
-
- all
-
-
- You can perform all binary operations on FLOATs when both operands are numeric. The compiler will automatically insert a conversion from <any numeric type> to FLOAT when the right hand side of the binary operator is not a float.
-
-
-
-
- SYMBOL
-
-
- none
-
-
- Binary operators are not supported for arrays.
-
-
-
-
- STRING
-
-
- + and -
-
-
- The + operator will add 2 strings. The - operator will add the RHS to the LHS and move all trailing spaces of the LHS to the end of the resulting string. You can also add STRING values and SYMBOL values. The SYMBOLs will automatically be converted to strings.
-
-
-
-
- USUAL
-
-
- all
-
-
- You can use all binary operators on USUALs. The code in the runtime will check to see if the 2 sides are "compatible" and will produce a runtime error when the operation is not available.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Binary_Type.xml b/docs/Help_Spanish/Topics/Binary_Type.xml
deleted file mode 100644
index 2468da3dbe..0000000000
--- a/docs/Help_Spanish/Topics/Binary_Type.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Binary Type
-
- BINARY
- XSharp.__Binary
-
-
-
- Binary Type
-
- This implements the FoxPro binary type. The internal typename is XSharp.__Binary
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Bitwise_Operators.xml b/docs/Help_Spanish/Topics/Bitwise_Operators.xml
deleted file mode 100644
index efd0af5b54..0000000000
--- a/docs/Help_Spanish/Topics/Bitwise_Operators.xml
+++ /dev/null
@@ -1,96 +0,0 @@
-
-
-
- Bitwise
-
- &
- .AND.
- .OR.
- |
- ~
- bitwise operator
- operator
-
-
-
- Bitwise
-
- X# uses the following Bitwise (binary) operators. There are simple character versions of these and also pseudo functions:
-
-
-
-
- Operator
-
-
- Pseudo Function
-
-
- Example
-
-
- Meaning
-
-
-
-
- |
-
-
- _OR(..)
-
-
- x | y, _OR(x,y)
-
-
- Returns the bitwise OR of x and y. _OR() may have more than 2 parameters.
-
-
-
-
- ~
-
-
- _XOR(..)
-
-
- x ~ y, _XOR(x,y)
-
-
- Returns the bitwise XOR of x and y.
-
-
-
-
- &
-
-
- _AND(..)
-
-
- x & y, _AND(x,y)
-
-
- Returns the bitwise AND of x and y. _AND() may have more than 2 parameters.
-
-
-
-
- ~
-
-
- _NOT(..)
-
-
- ~ x, _NOT(x)
-
-
- Returns the bitwise NOT of x (aka one's complement). _NOT() can only have one parameter.
-
-
-
-
- The result of a bitwise operation is best understood via ‘truth tables’. If two numbers can, for instance, be defined by 4 bits (expressing numbers 0 up to 15 in decimal value) then, when ‘Anding’ them, use the AND truth table for each bit in turn. If the values in decimal are 5 and 1, then their bit representations are 0101 and 0001.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Blocks2.xml b/docs/Help_Spanish/Topics/Blocks2.xml
deleted file mode 100644
index 974ee0d0e9..0000000000
--- a/docs/Help_Spanish/Topics/Blocks2.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Blocks and Namespaces
-
-
- Blocks and Namespaces
-
- There are several block statements that allow you to group a block of code. Variables declared inside a block are only visible for the duration of the block.
-
- BEGIN CHECKED
- BEGIN FIXED
- BEGIN LOCK
- BEGIN SCOPE
- BEGIN UNCHECKED
- BEGIN UNSAFE
- BEGIN USING
-
-
diff --git a/docs/Help_Spanish/Topics/Bound-Expressions.xml b/docs/Help_Spanish/Topics/Bound-Expressions.xml
deleted file mode 100644
index f5b7a9f601..0000000000
--- a/docs/Help_Spanish/Topics/Bound-Expressions.xml
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
- Bound Expressions
-
-
- Bound Expressions
-
- Bound expressions are expressions that access properties or members from objects or structures.
-
-
-
-
- Expression type
-
-
- Syntax
-
-
-
-
- Bound Member Access
-
-
- boundexpression (.|:) simpleName
-
-
-
-
- Bound Method Call
-
-
- boundexpression ( argumentlist? )
-
-
-
-
- Bound Array Access
-
-
- boundexpression [ argumentlist ]
-
-
-
-
- Bound Conditional Access
-
-
- expression ? boundexpression
-
-
-
-
- Bind Member Access
-
-
- (.|:) simpleName
-
-
-
-
- Bind Array Access
-
-
- [ argumentlist ]
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Bring-Your-Own-Runtime-BYOR.xml b/docs/Help_Spanish/Topics/Bring-Your-Own-Runtime-BYOR.xml
deleted file mode 100644
index 60ab8b2cd1..0000000000
--- a/docs/Help_Spanish/Topics/Bring-Your-Own-Runtime-BYOR.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- Bring Your Own Runtime (BYOR)
-
-
- Bring Your Own Runtime (BYOR)
-
- XSharp 3 no longer suppport "Bring Your Own Runtime". To compile in a dialect other than Core you need to include a reference to the X# Runtime.
- You can still include references to the Vulcan Runtime DLLs in your project but the types and functions in these assemblies are treated like any other .Net assembly.
-
-
diff --git a/docs/Help_Spanish/Topics/Build-Configurations.xml b/docs/Help_Spanish/Topics/Build-Configurations.xml
deleted file mode 100644
index de2d0b11d5..0000000000
--- a/docs/Help_Spanish/Topics/Build-Configurations.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- Build Configurations
-
-
- Build Configurations
-
- Build configurations are used when you need to build your projects with different settings. For example, Debug and Release are two configurations that use different compiler options during the build process. There is one configuration that is active, which is indicated in the command bar at the top of the Visual Studio IDE.
-
-
-
- The configuration and the platform control where built output files are stored. Normally, when Visual Studio builds your project, the output is placed in a project subfolder named with the active configuration (for example, bin/Debug), but you can change that.
- You can create your own build configurations at the solution and project level. The solution configuration determines which projects are included in the build when that configuration is active. Only those projects that are specified in the active solution configuration will be built. If multiple target platforms are selected in Configuration Manager, all projects that apply to that platform are built. The project configuration determines which build settings and compiler options are used when you build the project.
- To create, select, modify, or delete a configuration, you can use the Configuration Manager. To open it, on the menu bar, choose Build > Configuration Manager, or just type Configuration in the search box. You can also use the Solution Configurations list on the Standard toolbar to select a configuration or open the Configuration Manager.
-
-
-
- By default, Debug and Release configurations are included in projects that are created using Visual Studio templates. A Debug configuration supports the debugging of an app, and a Release configuration builds a version of the app that can be deployed. For more information, see How to: Set debug and release configurations. You can also create custom solution configurations and project configurations. For more information, see How to: Create and edit configurations.
- Solution Configurations
-
- A solution configuration specifies how projects in the solution are to be built and deployed. To modify a solution configuration or define a new one, in the Configuration Manager, under Active solution configuration, choose Edit or New.
- Each entry in the Project contexts box of a solution configuration represents a project in the solution. For every combination of Active solution configuration and Active solution platform, you can define how each project is used. (For more information about solution platforms, see Understand build platforms.)
- When you define a new solution configuration and select the Create new project configurations check box, Visual Studio automatically assigns the new configuration to all of the projects. Likewise, when you define a new solution platform and select the Create new project platforms check box, Visual Studio automatically assigns the new platform to all of the projects. Also, if you add a project that targets a new platform, Visual Studio adds that platform to the list of solution platforms and assigns it to all of the projects. You can still modify the settings for each project.
- The active solution configuration also provides context to the IDE. For example, if you are working on a project and the configuration specifies that it will be built for a mobile device, the Toolbox pnly displays items that can be used in a mobile device project.
- Project Configurations
- The configuration and platform that a project targets are used together, to specify the build settings and compiler options to use when it is built. A project can have different settings for each combination of configuration and platform. To modify the properties of a project, open the shortcut menu for the project in Solution Explorer, and then choose Properties. At the top of the Build tab of the project designer, choose an active configuration to edit its build settings.
- See the project properties dialogs for more information on which project properties are configuration-dependent and which are configuration-independent.
-
-
diff --git a/docs/Help_Spanish/Topics/Building-XSharp-apps-with-Visu.xml b/docs/Help_Spanish/Topics/Building-XSharp-apps-with-Visu.xml
deleted file mode 100644
index 38f69c144c..0000000000
--- a/docs/Help_Spanish/Topics/Building-XSharp-apps-with-Visu.xml
+++ /dev/null
@@ -1,229 +0,0 @@
-
-
-
- Building XSharp apps with Visual Studio and/or MsBuild
-
- .g.prg
- .rc
- .sln
- .xsproj
- Compile
- COMReference
- CreateXSharpManifestResourceName
- GAC
- HintPath
- LastXSharpNativeResourceResponseFile.Rsp"
- LastXSharpResponseFile.Rsp
- machine.config
- Native Resource compiler
- NativeResourceCompiler
- ProjectReference
- Reference
- referenced assemblies
- solution file
- TargetFrameworkVersion
- Xsc
- XSharp project file
- XSHARPDEV
-
-
-
- Building XSharp apps with Visual Studio and/or MsBuild
-
- When you build an application with MsBuild and/or Visual Studio, you work with at least two types of files:
-
-
The solution file (with the .sln extention);
-
One or more project files. XSharp projects have the .xsproj extension, CSharp projects have the .csproj extension, and Visual Basic projects have the .vbproj extension.
-
- The solution file (.sln)
- The solution file is a text file with a list of project files and other information. Each project entry looks like this:
- Project("<language guid>") = "<ProjectName>", "<Path and filename of the project file>", "<project guid>" EndProject
- The <language guid> is always "{AA6C8D78-22FF-423A-9C7C-5F2393824E04}" for X# projects. This tells Visual Studio which project system to use to open the project file.
- The <project guid> is generated and should match the project GUID that is defined inside the .xsproj file. These guids are also used in other sections of the .sln file.
- Other language guids that you may see are {FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} and {9A19103F-16F7-4668-BE54-9A1E7A4F7556} for C# and {2150E333-8FDC-42A3-9474-1A3956D46DE8} for subfolders in your solution. There are many more guids of course.
-
- Solution files also contain sections that describe the various configurations that are available for the solution (such as "Debug" and "Release") and a section that maps solution configurations to project configurations, and sometimes, also a section that indicates how the source code control bindings for each of the projects are.
-
- For the actual build process of your X# apps, we can ignore the solution file for now. Solution files are "language agnostic". The building is done based on information in the project file.
- The XSharp project file (.xsproj)
- The project file contains all instructions that are needed to build a X# project with MsBuild. The file is a Text file and contains XML contents in a specific format that MsBuild understands. The file contains all the settings that you can set from the project properties dialogs in Visual Studio, as well as a list of the items (prg files, resx files, rc files etc) in the project.
-
- The file uses some common information that is installed in a MsBuild subfolder inside the XSharp installation folder that belongs to the Visual Studio version that you are using.
- The most important pieces in the file are for now:
-
-
- This imports default settings for XSharp from the XSharp folder inside the current MsBuild folder. This file contains several default values for XSharp and also imports default values from a common file delivered by Microsoft (Microsoft.Common.props).
-
-
-
-
- Several <PropertyGroup> sections.
-
-
- These sections contain values for the several options that you can find on the Project Properties dialog in Visual Studio. Some values are for all configurations, some values are configuration specific. These settings will be transformed to command line options for the X# compiler.
-
-
-
-
- One or more <ItemGroup> sections with <Reference> items
-
-
- The <Reference> items describe so-called Assembly references that your project has. Usually, you will find something like <Reference Include="System" /> in there. Reference Items may also contain more information, such as a version number. These references will be converted to-reference command line options for the compiler.
-
-
-
-
- One or more <ItemGroup> sections with <ProjectReference> items
-
-
- The <ProjectReference> items describe so-called Project References to other projects inside the same solution. MsBuild will determine the build order inside the solution based on the various project references, and will try to build the referenced projects first before the projects referencing them. MSBuild will include a reference to the file produced by the project reference when building the command line for the compiler.
-
-
-
-
- One or more <ItemGroup> sectins with <COMReference> items
-
-
- The <COMReference> items describe references to COM components. This may be automation servers (such as Word or Excel) or ActiveX components (like the Shell Explorer that we use in the email example). Automation Servers will have a single COMReference with a <wrappertool> child node of type "tlbImp". ActiveX controls will have two COMReferences: one with the wrappertool set to "tlbimp"; and another with the wrappertool set to "aximp". See the section below on how this is processed by MSBuild.
-
-
-
-
- One or more <ItemGroup> sections with <Compile> items
-
-
- The <Compile> items describe the source code items for the X# compiler. The template for the Console application has two of these items: <Compile Include="Properties\AssemblyInfo.prg" /> <Compile Include="Program.prg" />
- The <Compile> items may have an optional <SubType>child node with the value "Code", "Form" or "UserControl". This subtype is ignored by the build process but used by Visual Studio to determine the icon that is shown before the item in the tree and to determine which editor to open when the item is double clicked. "Code" opens the source code editor by default. The other two types open the Windows Forms editor.
-
-
-
-
-
- One or more <ItemGroup> sections with <VOBinary>, <NativeResource>,<EmbeddedResource> and other types of items
-
-
- <NativeResource> items are handled specially by the X# build process. These are combined together in an unmanaged resource. See below. <EmbeddedResource> files are managed resources. These are handled by MSBuild. How this works is one of the things that is described in a file that is included below
-
- This file tells MSBuild how to handle the <Compile> and <NativeResource> items in the project file and also (indirectly) imports a file Microsoft.Common.targets that tells MSBuild how to handle XAML files and how to compile <EmbeddedResources>.
-
-
-
-
- How does MSBuild locate referenced assemblies
-
- When locating the referenced assemblies needed for compiling your project it looks at the following:
-
-
When the reference node has a "hintpath", it tries to locate the file through this path. That could look like <HintPath>..\\SDK_Defines.dll</HintPath>
-
When the reference node is a "normal" .Net framework assembly, it looks at the folder on your file system that matches the framework version. For example, when the framework version of your project is 4.6 (there will be a node <TargetFrameworkVersion>v4.6</TargetFrameworkVersion>), it will look for System.DLL in the folder c:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6
-
When the reference node is not a standard .Net framework assembly and the third party vendor has registered a folder in a specific location, MsBuild will use that location. X# registers a folder in the HKLM\Software\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\XSharplocation. Files registered in a location like this are also shown in the "Add References" dialogs in Visual Studio.
-
Finally, during building, MSBuild will look in the Global Assembly Cache (GAC).
-
-
- Please note that there is a difference between Compiling and Running. During compilation, the files in the reference folders take precedence over those in the GAC. However, when running the application, the GAC and/or the local folder or path are used. Files in the reference folders are NEVER used at runtime. This would also not be possible, as these files contain no executable code in them.
- The purpose of the separation is to allow you to compile against an older Framework version (e.g., 4.6), even if a newer version (e.g., 4.8) is installed. The reference assembly in the 4.6 folder contains only the subset of the API that was available in .Net Framework 4.6. This ensures that you cannot (accidentally) use methods or types introduced in later Framework versions, even though those methods or types might be present in the GAC.
-
- How does MSBuild locate project references
-
- When MSBuild detects a project reference, it tries to build that project first. When the project is successfully compiled, the output assembly from that project is included as "normal" reference to the X# compiler.
- How are COM references handled
- COM references require special processing. MSBuild uses two command line tools to extract the type libraries from these COM references and produces .Net assemblies (so-called Interop assemblies) that describe the COM references. There are two tools involved:
-
-
tlbimp.exe for automation servers;
-
aximp.exe for ActiveX controls.
-
-
- In our email example we are using the Shell.Explorer Active X. These two tools produce the files Interop.SHDocVw.dll and AxInterop.SHDocVw.dll. The AxInterop file describes the Windows Forms control and the Interop file the automation interface. In our Excel example we are referencing a "precompiled" assembly for Office. Therefore, we are not generating a new interop assembly, but rather, we are linking to a so-called "Primary Interop Assembly (PIA)", with the name Microsoft.Office.Interop.Excel.dll. If you include a COM component but you are not actually creating the COM objects but only consuming them, you can also set the "EmbedInteropTypes" option to true. When you do that, the X# compiler will copy the relevant information from the interop assembly and include that exe or dll, so you do not have to distribute the interop.dll with your application. In the Excel example that will not work, as we are creating an excel application. The compiler will then complain: "error XS1752: Interop type 'Microsoft.Office.Interop.Excel.ApplicationClass' cannot be embedded. Use the applicable interface instead."
- The resulting interop assemblies are produced before the compiler is called and are passed to the compiler as "normal" assembly references.
- How does MSBuild call the Native Resource compiler
- When your application contains Native resources, we must compile these native resources before the X# compiler can be used, since the result of the resource compilation must be included in the final exe/dll file. Of course, MSBuild does not "know" about X#, so we have to tell it what to do. The instructions for this are stored in the XSharp.Targets file.
- This file contains the following instructions:
- <UsingTask TaskName="NativeResourceCompiler" AssemblyFile="$(MSBuildThisFileDirectory)XSharp.Build.dll" /> <NativeResourceCompiler> .... </NativeResourceCompiler>
- The first entry tells the compiler that there is a special DLL in the XSharp folder with the name XSharp.Build.dll. This DLL contains a type NativeResourceCompile, which is a subtype of Microsoft.Build.Utilities.ToolTask.
- The second entry tells MSBuild how to pass information to this task to build the native resources. This includes a list of all items from the project file with the itemtype <NativeResource>. The task will then try to find the native resource compiler. To do that, it looks in the registry in the following key:
- - When running in 64 bit mode: "HKEY_LOCAL_MACHINE\Software\WOW6432Node\XSharpBV\XSharp"
- - When running in 32 bit mode: "HKEY_LOCAL_MACHINE\Software\XSharpBV\XSharp"
- Inside this key, it looks for the (string) value XSharpPath which is set by the installer at compile time.
- When it cannot find that path, it defaults to "C:\Program Files (x86)\XSharp".
- The task will then look for the rc.exe program in the Bin subfolder below that folder.
- When the tool is found, this task checks for the date/time stamps of the various .rc files and compares these with the date/time stamp of the output file (NativeResources.res ) in the "intermediate" folder. If the output file is older or does not exist, a command line for rc.exe is constructed and the compiler is called.
- For this call, we create a unique temporary rsp file in your temp folder. We are also saving the last version of this file in the file "LastXSharpNativeResourceResponseFile.Rsp".
- If you want to see which information was passed to the native resource compiler, you can look for this file in your temp folder.
- The resulting NativeResources.res will be passed to the X# compiler later to be included in the exe/dll. For this, we use the /win32res command line option of xsc.exe.
- How are managed resources compiled
- The compilation process for managed resources is mostly managed by MSBuild itself. It already knows how to handle these. We do declare a task :
- <UsingTask TaskName="CreateXSharpManifestResourceName" AssemblyFile="$(MSBuildThisFileDirectory)XSharp.Build.dll"/> <CreateXSharpManifestResourceName> ... </CreateXSharpManifestResourceName>
- This task is also located in the same XSharp.Build.DLL and is used to help MSBuild detect the right name space for the generated resources.
- The result of the managed resource compilation is that .resx files are compiled to one or more .resources file. These .resources files are then later passed to the compiler with the /resources command line option of xsc.exe.
- Processing of XAML files
- If you are creating a project that contains WPF windows or controls, an extra step is needed to produce the exe/dll.
- In this step MSBuild produces so called .baml files and calls a code generator to generate source code for each XAML file.
- For the WPF template 2 source files are produced:
-
-
WPFWindow1.g.prg
-
App.g.prg
-
- These source files are automatically added to the command line for the X# compiler.
- These source files contain a class declaration with a InitializeComponent() method that sets up the controls in your window. If you have named your controls, then for each control with a name, there will also be a field in the class and the generated Connect() method will set these fields to the control generated by the framework when the form is loaded.
- App.g.prg also contains a class and a function Start() that is responsible for starting up your application.
-
- Note: This source code is generated by a tool that we have registered in c:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config .
- <system.codedom>
- <compilers>
- <compiler language="XSharp" extension=".prg" type="XSharp.CodeDom.XSharpCodeDomProvider,XSharpCodeDomProvider, Version=2.1.0.0, Culture=neutral,
- PublicKeyToken=ed555a0467764586, ProcessorArchitecture=MSIL" />
- </compilers>
-
- The XSharpCodeDomProvider.dll assembly is registered in the GAC and it contains a XSharpCodeGenerator type that is responsible for the code generation.
-
- Note: this tool uses the keyword case setting that was specified in your Visual Studio options for the X# text editor.
- How does MSBuild call the X# compiler
- When MSBuild has successfully handled all external references and has created the "code behind" for XAML files compiled the native and managed resources, it calls the X# compiler. Similar to how the native resource compiler is called, the XSharp.Targets file also has instructions on how to call the compiler:
- <UsingTask TaskName="XSharp.Build.Xsc" AssemblyFile="$(MSBuildThisFileDirectory)XSharp.Build.dll"/> <Xsc> ..... </Xsc>
- Again, this describes a class in the XSharp.Build.DLL and the <Xsc> entry describes the properties of this type that need to be set.
- The Xsc task looks for the xsc.exe just like how the native resource compiler does this:
-
-
It looks for the installation location in the registry;
-
It defaults to the "C:\Program Files (x86)\XSharp" folder.
-
- There is one difference:
-
-
It also looks for an environment variable "XSHARPDEV". When this environment variable exists, it assumes that this is an alternate location where it can find the xsc.exe. We are using this internally so we can compile with a newer version of the compiler than the one that is installed inside C:\Program Files (x86)\XSharp. You may use this if you want to work with more than one version of the compiler on your machine.
-
-
- When we can find the xsc.exe compiler, we construct the command line to the compiler. We are creating a unique temporary RSP file in the temp folder, just like we do for the native resource compiler. We are also saving the last version of this file to the "LastXSharpResponseFile.Rsp" file in that folder.
- If you have enabled the "Shared" compiler on the Build page in your project properties (this defaults to true), we add the command line option /shared. This will tell xsc.exe to run XSCompiler.exe and pass the command line to that tool. XSCompiler.exe will continue to run in memory even after the compilation is finished and will cache type information from referenced assemblies. As a result, a second compilation of the same project will usually be much faster, since all the relevant type information is already cached. Of course, the compiler is smart enough to detect when a referenced DLL was changed (the reference could be generated from a referenced project) and will then reload the type information from that reference. Normally, you will only see one copy of XSCompiler.exe running memory. You may see multiple copies of xsc.exe running in memory when MSBuild detects that two projects in the same solution are "independent" and can be compiled simultaneously.
- The only situation in which you might see two copies of XSCompiler.exe running in memory is when projects are compiled with difference settings for case sensitivity (the /cs command line option). One of the two copies will then have a case-sensitive type cache and the other a case-insensitive type cache.
- Debugging MSBuild
- If you want to see what MSBuild imports when compiling your xsproj file you can call MSBuild with a special commandline option. To do so, open a visual studio developer command prompt and type the following:
- msbuild -preprocess <yourproject.xsproj> > preprocessed.proj
- The resulting preprocess.proj file will be an XML file that contains all imported instructions. You can open this inside Visual Studio. You may want to Format the document to make it a bit more readable.
- You should see that all "<Import project" nodes are now converted to comments and the contents of these imported files is inserted into the preprocessed output.
- Some imports had a condition that was not met and these are just in the file as comments.
- The generated file is HUGE. The WPF template produces a file of over 8700 lines and some of these lines are thousands of characters wide. Almost all of the first 8600 lines of this preprocessed file are imported.
- Somewhere in this file, you will see the MSBuild.
- Please note that you are NOT able to build the output file. It just serves to see what MSBuild imports to create your project.
-
- If you want to see how MsBuild resolves the various references, you should call MsBuild from the command line and add the command line option to show detailed info. The /target:rebuild on the next line makes sure that everything is rebuilt. If you are compiling a project with native resources, managed resources or xaml files, you should also see the logging of the tools that process this.
- msbuild -verbosity:detailed <yourproject.xsproj> /target:rebuild >buildlog.txt
-
-
-
diff --git a/docs/Help_Spanish/Topics/Built-in-Types.xml b/docs/Help_Spanish/Topics/Built-in-Types.xml
deleted file mode 100644
index e5ff5a02e5..0000000000
--- a/docs/Help_Spanish/Topics/Built-in-Types.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- Types
-
-
- Types
-
- The X# language knows the following data types
-
-
-
-
- Type
-
-
- Description
-
-
-
-
- Native Types
-
-
-
-
-
-
- xBase Specific Types
-
-
-
-
-
-
- User Defined Types
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/CHAR.xml b/docs/Help_Spanish/Topics/CHAR.xml
deleted file mode 100644
index cc4f9ff77e..0000000000
--- a/docs/Help_Spanish/Topics/CHAR.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- CHAR
-
- CHAR
-
-
-
- CHAR
-
- The CHAR keyword denotes an type to represent a Unicode character. The Unicode Standard identifies each Unicode character with a unique 21-bit scalar number called a code point, and defines the UTF-16 encoding form that specifies how a code point is encoded into a sequence of one or more 16-bit values. Each 16-bit value ranges from hexadecimal 0x0000 through 0xFFFF and is stored in a Char structure. The value of a Char object is its 16-bit numeric (ordinal) value.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/CODEBLOCK.xml b/docs/Help_Spanish/Topics/CODEBLOCK.xml
deleted file mode 100644
index d3a6695d68..0000000000
--- a/docs/Help_Spanish/Topics/CODEBLOCK.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- CODEBLOCK
-
- CODEBLOCK
-
-
-
- CODEBLOCK
-
- The CODEBLOCKtype was introduced in the XBase language in the Clipper days.
- They can be viewed as unnamed functions. They can have 0 or more parameters and return a value.
- The most simple codeblock that returns a string literal looks like this:
- FUNCTION Start() ASVOID LOCAL cb ASCODEBLOCK cb := {|| "Hello World"} ? Eval(cb) WAIT
RETURN
- To use a codeblock, you call the Eval() runtime function.
- Codeblocks are not restricted to fixed expressions, because they can use parameters. The following codeblock adds two parameters:
- FUNCTION Start() ASVOID LOCAL cb ASCODEBLOCK cb := {|a,b| a + b} ? Eval(cb, 1,2) ? Eval(cb, "Helllo ", "World") WAIT RETURN
- As you can see in the example, both numeric or string parameters can be used here and work. That is because the parameters to a codeblock are of the so called USUAL type; they can contain any value. Of course the following will fail because the USUAL type does not support multiplying strings:
- FUNCTION Start() ASVOID LOCAL cb ASCODEBLOCK cb := {|a,b| a * b} ? Eval(cb, 1,2) ? Eval(cb, "Helllo ", "World") WAIT RETURN
- More complicated codeblocks
- Codeblocks are not restricted to single expressions. They may also contain a (comma-separated) list of expressions. The value of the last expression is the return value of the codeblock:
-
- FUNCTION Start() ASVOID LOCAL cb ASCODEBLOCK cb := {|a,b,c| QOut("value 1", a) , QOut("value 2", b), QOut("value 3", c), a*b*c} ? Eval(cb,10,20,30) WAIT RETURN
- XSharp has also introduced codeblocks that contain of (lists of) statements:
- FUNCTION Start() ASVOID LOCAL cb ASCODEBLOCK cb := {| a,b,c| ? "value 1" ,a ? "value 2" ,b ? "value 3" ,c RETURN a*b*c } ? Eval(cb,10,20,30) WAIT RETURN
- Please note
-
-
The first statement should start on a new line after the parameter list.
-
There should be NO semicolon after the parameter list.
-
The statement list should end with a RETURN statement.
-
-
-
- Implementation
- The CODEBLOCK type is implemented in the abstract class XSharp.Codeblock.
- The Usualtype of CODEBLOCK has the value 9.
-
- In your code you will never have objects of type XSharp.Codeblock.
- Compile time codeblocks are translated into a subclass of XSharp.Codeblock.
- Runtime (macro compiled) codeblocks are translated into a subclass of the class XSharp._Codeblock, which inherits from Codeblock. Depending on the type of the runtime codeblock, this is either an instance of the MacroCodeblock class or of the MacroMemVarCodeblock class (when the macro creates dynamic memory variables).
-
-
diff --git a/docs/Help_Spanish/Topics/CURRENCY.xml b/docs/Help_Spanish/Topics/CURRENCY.xml
deleted file mode 100644
index eb2dfb16ac..0000000000
--- a/docs/Help_Spanish/Topics/CURRENCY.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- CURRENCY
-
-
- CURRENCY
-
- The CURRENCY type stored numbers with a precision of 4 decimals. Internally it contains a .Net decimal value, rounded to 4 decimals.
-
- Implementation
- The CURRENCY type is implemented in the structure XSharp.__Currency.
- The Usual type of CURRENCY is 28.
-
-
diff --git a/docs/Help_Spanish/Topics/Calling-conventions.xml b/docs/Help_Spanish/Topics/Calling-conventions.xml
deleted file mode 100644
index 0017725d15..0000000000
--- a/docs/Help_Spanish/Topics/Calling-conventions.xml
+++ /dev/null
@@ -1,93 +0,0 @@
-
-
-
- Calling conventions
-
-
- Calling conventions
-
- Calling conventions are something from the unmanaged world. They describe how parameters should be passed when you call a function or method and they also describe who is responsible for adjusting the stack when the called function/method returns.
- Different compilers have different default strategies for passing parameters to functions.
-
-
-
- Convention
-
-
- Description
-
-
-
-
- STRICT
-
-
- This is the most common calling convention in the C/C++ world. With this convention, parameters are pushed on the stack. Value types are pushed completely and for reference types, the address of the variable is pushed. When a method is called, the address of the “this” object is pushed on the stack as well.
- After the function/method returns, the calling method adjusts the stack.
- This calling convention allows for functions or methods with a variable number of arguments, like printf(). The caller knows the # of parameters that were passed, so the calling is the best candidate for adjusting the stack.
- In C/C++ this is also called __cdecl
- In VO (and X#) there is also a synonym “ASPEN” for this.
-
-
-
-
- PASCAL
-
-
- This calling convention is used a lot in the Pascal world. It looks a lot like the STRICT calling convention, but now the function / method that gets called adjusts the stack when it returns. Of course, this also means that there cannot be a variable number of arguments. If and when that is necessary, the last parameter usually becomes an array of values, so there still is some flexibility.
- In C/C++ this is called the __stdcall calling convention.
- This calling convention is used by most functions in the windows API.
- In VO this is also called WINCALL or CALLBACK. In 16bits windows, WINCALL was different from PASCAL, but 32 bits windows and later versions dropped that difference.
-
-
-
-
- THISCALL
-
-
- This is a special variant of the PASCAL calling convention, where the “this” pointer is not pushed on the stack but passed in a register (usually the ECX register). Passing the “this” in the register can be faster, especially when the register is not used for something else, so repeated calls for the same object to not have to push the “this” pointer. In C/C++ this is called __thisccall.
-
-
-
-
- FASTCALL
-
-
- This calling convention tries to pass as many parameters in registers as possible.
- In C/C++ this is called __fastcall.
-
-
-
-
- CLIPPER
-
-
- This is a special calling convention in the Xbase world, where parameters to a function are (technically) all optional and where you can also pass more values than you have declared parameters. Originally in the Xbase languages the calling code would push the values on the stack and would also pass the parameter count, so the function that is called “knows” how many parameters are passed.
- In .Net there is no real equivalent for that. To emulate the CLIPPER calling convention, we generate a special PARAMS parameter that contains an array of USUAL values. Parameters of type PARAMS must be the last (or only) parameter in the list of parameters. The Roslyn compiler (that we use for x#) will automatically wrap all values that are passed to a function/method with clipper calling convention in an array.
- Of course, when you declare a function like this
- FUNCTION Foo(a,b,c)
- Then you expect that you will have three local variables in your code with the names “a”, “b” and “c”.
- The compiler, however, generates a function with a params argument. Something like this:
- FUNCTION Foo(args PARAMSUSUAL[])
- Inside the function, we then generate local variables with the name of the parameters that you have declared:
- LOCAL a := args[1] asUSUAL LOCAL b := args[2] asUSUAL LOCAL c := args[3] asUSUAL
- In reality, the code is a bit more complex, because you may decide to call the function with less parameters than were declared. We have to take that into account.
- It looks like this then:
- LOCAL numParams := args:Length LOCAL a := iif(numParams > 0, args[1], NIL) ASUSUAL
- The names for “numParams” and “args” are generated by the complier with a special character in them, to make sure that we do not introduce variable names that conflict with names in your code.
- The X# debugger support layer also hides these special variables.
-
-
-
-
- For “normal” managed code, you really only have to deal with 2 calling conventions:
-
-
For untyped methods, the compiler uses the CLIPPER calling convention.
-
For typed methods, the compiler there is no difference between STRICT and PASCAL. They both produce the same code.
-
-
- Only when you call unmanaged code in other DLLs, you need to use one of the other calling conventions. You have to “know” what the DLL uses. One problem is that quite often, the calling convention in C/C++ code is hidden in a compiler macro.
- As a rule of thumb, you should use STRICT for C/C++ code and PASCAL for windows api funtions.
- If it does not work (for example, the .Net runtime complains about stack problems), then switch to the other calling convention.
-
-
diff --git a/docs/Help_Spanish/Topics/Catching-errors-at-startup.xml b/docs/Help_Spanish/Topics/Catching-errors-at-startup.xml
deleted file mode 100644
index 6dd11b52eb..0000000000
--- a/docs/Help_Spanish/Topics/Catching-errors-at-startup.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- Catching runtime errors at startup
-
- -main
- Start
- StartupCode
- UnhandledException
-
-
-
- Catching runtime errors at startup
-
- Sometimes, your program throws runtime errors at startup. These can be caused by missing assemblies and/or by errors in initialization code. These errors can be difficult to trap, since the errors occur inside code that is executed before the first line of code in your application.
-
- Take the following example:
- GLOBAL x ASINT GLOBAL y := 1 / x ASINT FUNCTION Start ASVOID ? "Function Start" RETURN
- This code will generate an exception at startup, which you can only see/read when you run the app from the commandline
- Unhandled Exception: System.TypeInitializationException: The type initializer for 'Application1.Exe.Functions' threw an exception. ---> System.DivideByZeroException: Attempted to divide by zero. at Application1.Exe.Functions..cctor() in C:\XIDE\Projects\Default\Applications\Application1\Prg\Start.prg:line 4 --- End of inner exception stack trace --- at Application1.Exe.Functions.Start()
- The normal program flow in an X# application is this:
-
-
Your application is started
-
The DotNet framework is initialized
-
The entrypoint is called. The normal entrypoint in an app is the Start function, which is converted by the compiler to a Start method in a compiler generated Functions class. The same class also has the globals and defines from your app. If one of these globals or defines contains an initialization expression that cannot be resolved at compile then these this code will be executed in the static constructor of the Functions class (in the error message above this is called the "type initializer").
-
The code above clearly makes a mistake which causes a divide by zero error.
-
-
- To intercept this we would like to run some other code at startup and add a try .. catch construct to make sure we can catch this kind of errors.
-
- Add the following code:
- CLASS MyStartupCode STATICMETHOD Start ASVOIDSTRICT TRY // Note that in the following line the name before .Exe must // match the file name of your EXE. In my case I am generating Application1.exe Application1.Exe.Functions.Start() CATCH e AS Exception // We should probably log this to disk as well ! Console.WriteLine("An unhandled exception has occurred") Console.WriteLine("===================================") DOWHILE e != NULL Console.WriteLine("Exception: "+e:Message) Console.WriteLine("Callstack:") Console.WriteLine(e:StackTrace) Console.WriteLine() e := e:InnerException ENDDO Console.WriteLine("===================================") Console.WriteLine("Press any to close the application") Console.ReadLine() ENDTRY RETURN ENDCLASS
-
- You may have to change the call to Application1.Exe.Functions.Start() into something that matches your EXE name.
- Now goto the General page in the application properties in VS and at the entry "Startup Object" set the value MyStartupCode.
-
-
-
- In XIDE add the command line option -main:MyStartupCode:
-
-
-
- and run the code again. The error is now trapped and shown. If you app is not a Console app but a Windows app then the console output may not be visible.
-
- Of course you can also register an UnHandledException handler in the AppDomain class inside the new startup code.
- Change the code to:
- CLASS MyStartupCode STATICMETHOD Start ASVOIDSTRICT TRY System.AppDomain.CurrentDomain:UnhandledException += ExceptionHandler Application1.Exe.Functions.Start() CATCH e AS Exception ExceptionHandler(NULL, UnhandledExceptionEventArgs{e, TRUE}) ENDTRY RETURN
STATICMETHOD ExceptionHandler( sender ASOBJECT, args AS UnhandledExceptionEventArgs) ASVOID LOCAL e AS Exception LOCAL c AS STRINGe := (Exception) args:ExceptionObject c := "An unhandled exception has occurred"+crlf c += "==================================="+crlf DOWHILE e != NULL c += "Exception: "+e:Message+crlf c += "Callstack:"+crlf c += e:StackTrace+crlf e := e:InnerException ENDDO c += "==================================="+crlf MessageBox(IntPtr.Zero, c,"Error",0x60010) // MB_OK + MB_ICONSTOP+ MB_DEFAULT_DESKTOP_ONLY + MB_TOPMOST
[DllImport("user32.dll", CharSet := CharSet.Ansi)]; STATICMETHOD MessageBox(hwnd AS IntPtr, lpText ASSTRING, lpCaption ASSTRING, uType ASDWORD) ASINTPASCAL ENDCLASS
-
- One remark:
- Do NOT use or call any Xbase types and or functions in the exception handler, since you can't be sure that the runtime was initialized properly.
- If you use classes written by yourself make sure that everything is strongly typed and uses native types only. So no USUAL, FLOAT, SYMBOL etc.
- And do not call code inside functions in the same app or DLLs, because again the type initializers for the classes in which these functions are located can also throw exceptions.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Chapter-2.xml b/docs/Help_Spanish/Topics/Chapter-2.xml
deleted file mode 100644
index 774c0d75f7..0000000000
--- a/docs/Help_Spanish/Topics/Chapter-2.xml
+++ /dev/null
@@ -1,68 +0,0 @@
-
-
-
- X# Language Reference
-
-
- X# Language Reference
-
- This section is a reference to the X# language.
-
- X# Language elements
-
- The following table shows reference topics that provide tables of keywords, symbols and literals used as tokens in X#.
-
-
-
-
- Title
-
-
- Description
-
-
-
-
- Keywords
-
-
- Contains links to information about all X# language keywords.
-
-
-
-
- Expression
-
-
- A list of possible expressions
-
-
-
-
- Symbol and Operators
-
-
- Contains a table of symbols and operators that are used in the X# language.
-
-
-
-
- Literals (X#)
-
-
- Describes the syntax for literal values in X# and how to specify type information for X# literals.
-
-
-
-
- Commands and Statements
-
-
- A list of commands and statements
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/CharLiterals.xml b/docs/Help_Spanish/Topics/CharLiterals.xml
deleted file mode 100644
index 83881eec6c..0000000000
--- a/docs/Help_Spanish/Topics/CharLiterals.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- Char Literals
-
- CHAR
- Char Literals
- Literals
-
-
-
- Char Literals
-
- There are different notations for a char literal, depending on the dialect selected. In many dialects, the single quotes are string delimiters, and therefore, the 'c' prefix is needed for character literals.
- Only in the Core and Vulcan dialects, single quotes are always reserved for character literals.
-
-
-
-
- Literal
-
-
- VO, XPP, FoxPro & Harbour
-
-
- Vulcan & Core
-
-
-
-
- c'<char>' or c"<char>"
-
-
- Char literal*
-
-
- Char literal*
-
-
-
-
- '<char>'
-
-
- String literal
-
-
- Char literal*
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Classes-and-Structures.xml b/docs/Help_Spanish/Topics/Classes-and-Structures.xml
deleted file mode 100644
index 46699d9064..0000000000
--- a/docs/Help_Spanish/Topics/Classes-and-Structures.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- Classes and Structures
-
-
- Classes and Structures
-
- In .Net, there are two kind of types that hold data; reference types (or classes), and value types (or structures). The two of them have different semantics in the way they are used, but both can contain other reference and/or value types themselves.
- Classes
- A class (or a reference type), is the most common way of storing data. Its name comes from the fact that a variable of a reference type (commonly referred to as an instance of the type) does not contain the data directly, but instead points to (references) a memory location where the actual data is stored. A class in X# is defined through the CLASS...END CLASS statement and can INHERIT from another reference type, implement one or more INTERFACES, and may contain fields, properties, constructors, methods, events and other items:
- CLASS Customer EXPORT name ASINT// exported (public) field PROTECT age ASINT// protected field, not visible to code outside the class ENDCLASS
- Typically, classes and all their members are defined in a single file of code. If it is necessary for class members to be defined in multiple files (for example, when the amount of class members is very big), then the class must be defined in every file as PARTIAL:
- PARTIALCLASS Customer // class members ENDCLASS
- Since an instance of a class is only storing a pointer to the data, one or more variables can point to the exact same object in memory. Assigning a variable of a reference type to another variable of the same type results in both representing the same data. Updating data using one reference automatically updates the other reference as well:
- FUNCTION Start() ASVOID LOCAL one, two AS Customer one := Customer{} two := one // now both vars point to the same object in memory two:name := "Robert" ? one:name // also "Robert"
- Nested Classes
- A class can even contain other types (classes or structures). In this case, the type inside the main type is called a nested type. Nested types can be used by using the name of their container class and their own name, connected by a dot:
- CLASS Customer CLASS NestedClass EXPORT FieldInNestedClass ASINT ENDCLASS ENDCLASS
FUNCTION Start() ASVOID LOCAL oNested AS Customer.NestedClass oNested := Customer.NestedClass{} oNested:FieldInNestedClass := 100 ? oNested:FieldInNestedClass
- Nested classes are particularly useful for defining helper classes, classes that are only used within the context of the parent class to hold information only relevant to that class. Creating a nested class for this data, rather than using a regular class, results in better-structured code.
- Structures
- A structure (or a value type), in contrast to reference types, stores its data directly. It shares some similarities with the Visual Objects STRUCTURE feature (renamed to VOSTRUCT in X#), but it is much more powerful than in VO, as it can contain many of the same items as reference types, such as properties, constructors, and methods. However, unlike reference types, value types cannot inherit from other types or implement interfaces. They can, however, contain nested classes or structures. Value types can be defined using the STRUCTURE Statement:
- STRUCTURE Vector2D EXPORT x ASINT EXPORT y ASINT METHOD Invert() ASVOID SELF:x := - SELF:x SELF:y := - SELF:y ENDSTRUCTURE
- Since structures hold their data directly, instantiating them does not involve any additional memory consumption beyond the memory needed for the data itself (unlike reference types, which need memory for both the data and the pointer to the data) or any garbage collector activity. They are mostly suited as lightweight data containers, typically holding a small number of fields, (usually 2-4), but can also represent a single element, such as the System.Int32 (INT) or System.Boolean (LOGIC) data types. These types simply define the INT and LOGIC data types and include several methods for manipulating their data. Other commonly used system-defined structures are System.Drawing.Point and System.Drawing.Rectangle, all of which contain a a small number of data fields.
- Structure semantics
- Structures also have different semantics when using them compared to regular classes. It is not necessary to instantiate such a variable to use it, since declaring a var of a value type results to its data being allocated directly:
- FUNCTION Start() ASVOID LOCAL vector AS Vector2D vector:x := 10 vector:y := 20
- Although, for convenience, it's possible to also define constructors in value types and instantiate them as with regular classes:
- STRUCTURE Vector2D EXPORT x ASINT EXPORT y ASINT CONSTRUCTOR(vec_x ASINT, vec_y ASINT) SELF:x := vec_x SELF:y := vec_y ENDSTRUCTURE
FUNCTION Start() ASVOID LOCAL vector AS Vector2D vector := Vector2D{10,20} ? vector:x // 10
- The most important difference that must always be taken under consideration, is that assigning a value type to another one results to the data of the source being copied to the destination, so unlike what happens with reference types, the data of the two variables are stored in separate memory locations and any changes to one variable will not affect the other:
- FUNCTION Start() ASVOID LOCAL vec_1,vec_2 AS Vector2D vec_1:x := 10 ; vec_1:y := 20 vec_2 := vec_1 ? vec_2:x // 10, value was copied from first vector
vec_2:x := 40 // put a new value to second vector ? vec_1:x // 10 again, first vector value still has its original value
- For this reason structures are not suitable for very large objects, since assigning one to another or passing one as an argument to a method involves copying all data from the source to the destination. On the other hand, with regular classes, only the pointer to the data is passed as an argument to a method.
- Equals operator
- Another important difference between reference and value types, is the behavior of the equals operator (==). For reference types, the equals operator between two variables only compares the pointers themselves, not the data of the objects. So it returns TRUE only when both variables point to the same object and in all other cases it returns FALSE, even if the data both objects contain is the same:
- CLASS ReferenceType EXPORT data ASSTRING ENDCLASS
FUNCTION Start() ASVOID LOCAL o1,o2 AS ReferenceType o1 := ReferenceType{} o1:data := "test"
o2 := ReferenceType{} o2:data := "test" ? o1 == o2 // FALSE, because o1 and o2 point to different memory locations o2 := o1 ? o1 == o2 // TRUE
- On the other hand, by default the == operator cannot be used on structures and the compiler will report an error if you try to do so. It can be made possible to use it though, by defining an OPERATOR method in the structure that implements how the comparison with == should be done. In the sample below, the == operator is implemented to compare the actual data that the two compared structures hold, so that it returns TRUE, when the data is equal:
- STRUCTURE ValueType EXPORT data ASSTRING OPERATOR == (a AS ValueType, b AS ValueType) ASLOGIC RETURN a:data == b:data // let the equals == operator return true when the data of the two arguments is the same ENDSTRUCTURE
- FUNCTION Start() ASVOID LOCAL o1,o2 AS ValueType o1:data := "test" o2:data := "nothing" ? o1 == o2 // FALSE o2:data := "test" ? o1 == o2 // TRUE
- Note that it is possible to compare values of most common system defined structures like System.Int32, System.Boolean, System.Double, because they also have defined equals operator methods like the one in the code above.
- Which one to use
- Weather to use a class or a structure for holding data depends on the specific needs related to the particular data. For data holding a lot of information (for example a customer object) you would typically use a reference type, as such objects usually don't get instantiated very often, but usually "live" long for the duration of the program. For smaller objects, that are being a created, manipulated and copied between variables a lot of times and in particular in tight loops (like for example an object representing a Complex number, consisting of a real and an imaginary part, which can be used in a lot of calculations), it is' more suitable to use a structure, as this will typically lead to faster execution, with a lot less memory consumption and garbage collector activity. In any case, it's very important to carefully consider their differences in semantics when using value vs reference types.
-
-
-
diff --git a/docs/Help_Spanish/Topics/CodeBlock2.xml b/docs/Help_Spanish/Topics/CodeBlock2.xml
deleted file mode 100644
index 7ebbf202c4..0000000000
--- a/docs/Help_Spanish/Topics/CodeBlock2.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- CodeBlock
-
- CODEBLOCK
- XSharp._CodeBlock
- XSharp.CodeBlock
-
-
-
- CodeBlock
-
- This is the parent class for compile time codeblocks.
- There is also a subclass _CodeBlock which is the parent class for macro compiled (runtime) codeblocks.
- The internal type names are XSharp.CodeBlock and XSharp._CodeBlock
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Codeblock_-Lambda-and-Anonymou.xml b/docs/Help_Spanish/Topics/Codeblock_-Lambda-and-Anonymou.xml
deleted file mode 100644
index 8e07839e44..0000000000
--- a/docs/Help_Spanish/Topics/Codeblock_-Lambda-and-Anonymou.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-
-
-
- Codeblock, Lambda and Anonymous Method Expressions
-
-
- Codeblock, Lambda and Anonymous Method Expressions
-
- X# contains 3 language constructs that are fairly similar, yet different.
- Codeblocks
- Historically, the XBase language has known the CodeBlock Type. A codeblock is specified as
-
- {| params | expression }
-
- The parameters inside a codeblock are of type USUAL and its return value is also of type USUAL. To evaluate a codeblock you call the Eval() runtime function and pass this function the codeblock and parameters when needed
-
- FUNCTION Start() ASVOID LOCAL cb asCODEBLOCK cb := { |x, y| x * y} ? Eval(cb, 2,3) // shows 6 WAIT RETURN
-
- Instead of a single expression, you can also use an expression list. The value of the last expression in the list is returned as the result of the codeblock.
-
- FUNCTION Start() ASVOID LOCAL cb asCodeBlock cb := { |x, y| x += 1, x * y} ? Eval(cb, 2,3) // shows 9 WAIT RETURN
-
- X# has also added the possibility to include a list of statements as the "body" of a codeblock. The result of the last statement is returned to the calling code. If the last statement is "Void", then a NIL will be returned. Note that the closing Curly must be on its own line, and the first statement must appear on a new line as well.
-
- FUNCTION Start() ASVOID LOCAL cb asCodeBlock cb := { |x, y| x += 1 ? x RETURN x * y } ? Eval(cb, 2,3) // prints 3 and shows the result 9 WAIT RETURN
-
- Lambda Expressions
- Lamda expressions look a lot like Codeblocks. They are usually used in combination with Delegates.
-
-
- DELEGATE MultiPlyInt( x asInt, y asInt) asInt
FUNCTION Start() ASVOID LOCAL lambda as MultiPlyInt lambda := { x, y => x * y} ? Lambda(2,3) // shows 6 RETURN
-
- Parameters are optional and the return type can be VOID, so this works as well.
-
- DELEGATE DoSomething( ) asVOID
FUNCTION Start() ASVOID LOCAL lambda as DoSomething lambda := { => Console.WriteLine("This is a Lambda")} Lambda() // prints the text RETURN
-
- The parameters of a Lambda expression may be typed. This can be convenient for documentation purposes, and it can also help the compiler to find the right overload for a method:
-
- DELEGATE CalcInt( x ASINT, y ASINT) ASINT
DELEGATE CalcReal( x ASREAL8, y ASREAL8) ASREAL8
FUNCTION Start() ASVOID TestLambda( { x ASINT, y ASINT => x * y} ) TestLambda( { x ASREAL8, y ASREAL8 => x + y} ) TestLambda( { x , y => x - y } ) // Which one will be called ? RETURN
FUNCTION TestLambda (lambda AS CalcInt) ASVOID ? "Int", lambda(2,3) RETURN
FUNCTION TestLambda (lambda AS CalcReal) ASVOID ? "Real",lambda(2,3) RETURN
-
- The body of the Lambda may also be a single expression, expression list and a statement list.
- Anonymous Method Expressions
- These work almost the same as Lambda Expressions. Take the example below:
-
- FUNCTION TestAnonymous() ASVOID LOCAL oForm AS Form oForm := Form{} oForm:Click += DELEGATE(o AS System.Object, e AS System.EventArgs ) { System.Windows.Forms.MessageBox.Show("Click from AME 1!") System.Windows.Forms.MessageBox.Show("Click from AME 2!") } oForm:Click += { o,e => System.Windows.Forms.MessageBox.Show("We can also do this with a Lambda!") } oForm:ShowDialog() RETURN
-
- The biggest difference between Lambda Expressions and Anonymous Method Expressions is that the parameters to Lambda Expressions do not have to be typed. They will be inferred from the usage. Parameters for Anonymous Method Expressions must always be typed.
-
-
diff --git a/docs/Help_Spanish/Topics/Codeblocks.xml b/docs/Help_Spanish/Topics/Codeblocks.xml
deleted file mode 100644
index 0cb20bc98a..0000000000
--- a/docs/Help_Spanish/Topics/Codeblocks.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- Codeblocks
-
- statementblock
-
-
-
- Codeblocks
-
- Codeblocks are an important part of the X# language.
-
- Traditionally, the codeblock looked as follows:
-
- codeblock : { | codeblockParamList? | expression } ; codeblockParamList : identifier (, identifier)* ;
- For example:
- {|a,b| a*b}
-
- X# has extended the Codeblock rule. We now not only accept a single expression, but also a statement list and an expression list:
-
- codeblock : { | codeblockParamList? | ( expression | eos statementblock | codeblockExpressionList ) } ;
- codeblockExprList: (expression? ,)+ expression// The last expression is the return value of the block ;
- Examples of this are:
- {|a,b| a:= Sqrt(a), a*b} {|a,b| ? a ? b }
- The second example can be seen as an anonymous method with 2 parameters.
-
-
diff --git a/docs/Help_Spanish/Topics/Combining-X-Runtime-and-Vulcan.xml b/docs/Help_Spanish/Topics/Combining-X-Runtime-and-Vulcan.xml
deleted file mode 100644
index 7196cc8a00..0000000000
--- a/docs/Help_Spanish/Topics/Combining-X-Runtime-and-Vulcan.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Combining X# Runtime and Vulcan Runtime
-
-
- Combining X# Runtime and Vulcan Runtime
-
- Technically, it is possible to include both the X# and the Vulcan runtime libraries in your application. When you do so, the compiler will assume that you want to use the X# implementations for the XBase types such as USUAL and DATE. If the compiler does not find the XSharp.Core and XSharp.VO assemblies then it will only work in the Core dialect.
- And remember: there is no automatic translation between the X# types and Vulcan types.
- If you want to convert an X# variable to a Vulcan variable, you may have to cast it to an intermediate type first.
-
- Call Vulcans implementation of Left():
- LOCAL cValue asSTRING cValue := VulcanRTFuncs.Functions.Left("abcdefg",2)
- If you want to convert an X# usual to a Vulcan usual, cast to OBJECT:
- LOCAL xUsual asUSUAL LOCAL vUsual as Vulcan.__Usual xUsual := 10 vUsual := (OBJECT) xUsual
- For dates, you can do something similar. In that case, you should cast the X# date to a DateTime:
- LOCAL xDate as DATE LOCAL vDate as Vulcan.__VODate xDate := ToDay() // will call the X# implementation of ToDay() vDate := (System.DateTime) xDate
-
-
diff --git a/docs/Help_Spanish/Topics/Command-line-Building-With-xsc.xml b/docs/Help_Spanish/Topics/Command-line-Building-With-xsc.xml
deleted file mode 100644
index ff81f56ef3..0000000000
--- a/docs/Help_Spanish/Topics/Command-line-Building-With-xsc.xml
+++ /dev/null
@@ -1,101 +0,0 @@
-
-
-
- Command-line Building With xsc.exe
-
- compiler options
- options
-
-
-
- Command-line Building With xsc.exe
-
- You can invoke the X# compiler by typing the name of its executable file (xsc.exe) at a command prompt.
-
- If you use a standard Command Prompt window, you must adjust your path before you can invoke xsc.exe from any subdirectory on your computer.
-
- You can also use MSBuild to build X# programs programmatically. For more information, see the MSBuild documentation on MSDN.
-
- The xsc.exe executable file usually is located in the {Program Files}\XSharp\Bin folder under the Windows directory.
-
- When you build programs with the Visual Studio IDE then Visual Studio will locate the X# compiler automatically for you and the build output from the compiler will be shown in the Output Windows of Visual Studio.
- You can set the verbosity level of the compiler output from the Tools/Options, Projects and Solutions, Build and Run page.
- Rules for Command-Line Syntax for the X# Compiler
-
- The X# compiler uses the following rules when it interprets arguments given on the operating system command line:
-
-
-
Arguments are delimited by white space, which is either a space or a tab.
-
The caret character (^) is not recognized as an escape character or delimiter. The character is handled by the command-line parser in the operating system before it is passed to the argv array in the program.
-
A string enclosed in double quotation marks ("string") is interpreted as a single argument, regardless of white space that is contained within. A quoted string can be embedded in an argument.
-
A double quotation mark preceded by a backslash (\") is interpreted as a literal double quotation mark character (").
-
Backslashes are interpreted literally, unless they immediately precede a double quotation mark.
-
If an even number of backslashes is followed by a double quotation mark, one backslash is put in the compiler options array for every pair of backslashes, and the double quotation mark is interpreted as a string delimiter.
-
If an odd number of backslashes is followed by a double quotation mark, one backslash is put in the compiler options array for every pair of backslashes, and the double quotation mark is "escaped" by the remaining backslash. This causes a literal double quotation mark (") to be added in compiler options array.
-
Command-line options can start with a hyphen (-) or a slash (/). On Non windows platforms the hyphen should be used because the slash may be seen as a path delimiter character
-
If you do not use the /noconfig compiler option then references to the assemblies listed in xsc.exe will be automatically included.
- Compiles all the X# files in the current directory producing a debug version of File2.dll. No logo and no warnings are displayed
-
-
-
-
-
- xsc /target:library /out:MyBase.rdd *.prg
-
-
-
- Compiles all the X# files in the current directory to MyBase.rdd (a DLL):
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Command-translate.xml b/docs/Help_Spanish/Topics/Command-translate.xml
deleted file mode 100644
index df195ae1b6..0000000000
--- a/docs/Help_Spanish/Topics/Command-translate.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-
-
-
- command-translate
-
- =>
-
-
-
- command-translate
-
- Arguments
- <matchPattern> is the pattern the input text should match.
-
- <resultPattern> is the text produced if a portion of input text matches the <matchPattern>.
-
- The => symbol between <matchPattern> and <resultPattern> is, along with #command or #translate, a literal part of the syntax that must be specified in a #command or #translate directive. The symbol consists of an equal sign followed by a greater than symbol with no intervening spaces. Do not confuse the symbol with the >= or the <= comparison operators in the xBase language.
-
- Description
- #command and #translate are translation directives that define commands and pseudofunctions. Each directive specifies a translation rule. The rule consists of two portions: a match pattern and a result pattern.
- The match pattern matches a command specified in the program (.prg) file and saves portions of the command text (usually command arguments) for the result pattern to use. The result pattern then defines what will be written to the result text and how it will be written using the saved portions of the matching input text.
-
- #command and #translate are similar, but differ in the circumstance under which their match patterns match input text. A #command directive matches only if the input text is a complete statement, while #translate matches input text that is not a complete statement. #command defines a complete command and #translate defines clauses and pseudofunctions that may not form a complete statement. In general, use #command for most definitions and #translate for special cases.
-
- #command and #translate are similar to but more powerful than the #define directive. #define, generally, defines identifiers that control conditional compilation and manifest constants for commonly used constant values such as SDK codes. Refer to any of the header files in the INCLUDE directory for examples of manifest constants defined using #define.
-
- #command and #translate directives have the same scope as the #define directive. The definition is valid only for the current program (.prg) file unless defined in Std.ch or the header specified with the /U option on the compiler command line. If defined elsewhere, the definition is valid from the line where it is specified to the end of the program file. Unlike #define, a #translate or #command definition cannot be explicitly undefined. The #undef directive has no effect on a #command or #translate definition.
-
- As the preprocessor encounters each source line preprocessor, it scans for definitions in the following order of precedence: #define, #translate, and #command. When there is a match, the substitution is made to the result text and the entire line is reprocessed until there are no matches for any of the three types of definitions. #command and #translate rules are processed in stack-order (i.e., last in-first out, with the most recently specified rule processed first).
-
- In general, a command definition provides a way to specify an English language statement that is, in fact, a complicated expression or function call, thereby improving the readability of source code. You can use a command in place of an expression or function call to impose order of keywords, required arguments, combinations of arguments that must be specified together, and mutually exclusive arguments at compile time rather than at runtime. This can be important since procedures and user-defined functions can now be called with any number of arguments, forcing any argument checking to occur at runtime. With command definitions, the preprocessor handles some of this.
-
- Because directives are processed in stack order, when defining more than one rule for a command, place the most general case first, followed by the more specific ones. This ensures that the proper rule will match the command specified in the program (.prg) file.
-
- Match Markers
-
- See the topic about Match Markers for a detailed discussion
-
- Result Markers
-
- See the topic about Result Markers for a detailed discussion
- Notes
-
-
Less than operator: If you specify the less than operator (<) in the <resultPattern> expression, you must precede it with the escape character (\).
-
Multistatement lines: You can specify more than one statement as a part of the result pattern by separating each statement with a semicolon. If you specify adjacent statements on two separate lines, the first statement must be followed by two semicolons.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Command_APPEND_FROM_ARRAY.xml b/docs/Help_Spanish/Topics/Command_APPEND_FROM_ARRAY.xml
deleted file mode 100644
index 1798ea66bc..0000000000
--- a/docs/Help_Spanish/Topics/Command_APPEND_FROM_ARRAY.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- APPEND FROM ARRAY Command
-
-
- APPEND FROM ARRAY Command (FoxPro)
-
-
- Purpose
- Adds one record to the currently selected table for each row in an array and fills each record with data from the corresponding array row.
- Syntax
- APPEND FROM ARRAY <ArrayName> [FOR <lCondition>] [FIELDS <idFieldList> | FIELDS LIKE <Skeleton> | FIELDS EXCEPT <Skeleton>]
- Arguments
- <ArrayName>Specifies the name of the array that contains the data to be copied to the new records. New records are added to the table until all rows in the array are appended.
-
-
-
- See Also
- COPY TO ARRAY, GATHER, SCATTER
-
-
diff --git a/docs/Help_Spanish/Topics/Command_CLEAR_SCREEN.xml b/docs/Help_Spanish/Topics/Command_CLEAR_SCREEN.xml
deleted file mode 100644
index eb5fa5df2d..0000000000
--- a/docs/Help_Spanish/Topics/Command_CLEAR_SCREEN.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- CLEAR SCREEN Command
-
- CLEAR SCREEN Command
- Commands
- Terminal Window
-
-
-
- CLEAR SCREEN Command
-
-
- Purpose
- Takes input from the keyboard and assigns it to a memory variable.
- Syntax
- CLEAR SCREEN
- Description
- The command CLEAR erases the screen. After execution of the CLEAR command, the cursor is positioned at 0, 0 and the functions Row() and Col() are updated.
- Examples
- This example uses ACCEPT to get keyboard input from the user:
- FUNCTION Start ASVOID SETCOLORTO gr+/B // Yellow on Blue CLEARSCREEN ? "Hello world"
-
-
-
diff --git a/docs/Help_Spanish/Topics/Command_GATHER.xml b/docs/Help_Spanish/Topics/Command_GATHER.xml
deleted file mode 100644
index b668f6c500..0000000000
--- a/docs/Help_Spanish/Topics/Command_GATHER.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- GATHER Command
-
- Commands
- Fieldsassigning new values
- GATHER command
-
-
-
- GATHER Command (FoxPro)
-
-
- Purpose
- Replaces the data in the current record of the currently selected table with data from an array, a set of variables, or an object.
- Syntax
-
- GATHER FROM ArrayName | MEMVAR | NAME ObjectName [FIELDS FieldList | FIELDS LIKE Skeleton | FIELDS EXCEPT Skeleton] [MEMO]
- Arguments
-
-
-
- FROM <ArrayName>Specifies the array whose data replaces the data in the current record. The contents of the elements of the array, starting with the first element, replace the contents of the corresponding fields of the record. The contents of the first array element replace the first field of the record; the contents of the second array element replace the second field, and so on. If the array has fewer elements than the table has fields, the additional fields are ignored. If the array has more elements than the table has fields, the additional array elements are ignored.
-
- MEMVARSpecifies the variables or array from which data is copied to the current record. Data is transferred from the variable to the field that has the same name as the variable. The contents of a field are not replaced if there does not exist a variable with the same name as the field.
-
- NAME <ObjectName>Specifies an object whose properties have the same names as fields in the table. The contents of each field are replaced by the value of the property with the same names as the fields. The contents of a field are not replaced if there does not exist a property with the same name as the field.
-
- MEMOSpecifies that the contents of memo or Blob fields are replaced with the contents or array elements or variables. If you omit MEMO, memo and Blob fields are skipped when GATHER replaces the contents of fields with the contents of an array or variable. General and picture fields are always ignored in GATHER, even if you include the MEMO keyword.
- See Also
- APPEND FROM ARRAY, COPY TO ARRAY, SCATTER
-
-
diff --git a/docs/Help_Spanish/Topics/Command_SCATTER.xml b/docs/Help_Spanish/Topics/Command_SCATTER.xml
deleted file mode 100644
index b266079eab..0000000000
--- a/docs/Help_Spanish/Topics/Command_SCATTER.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- SCATTER Command
-
- Commands
- Fieldsupdating
- SCATTER command
-
-
-
- SCATTER Command (FoxPro)
-
-
- Purpose
- Assign new values to the contents of one or more fields in the current record.
- Syntax
- SCATTER [FIELDS <idFieldList> | FIELDS LIKE <Skeleton> | FIELDS EXCEPT <Skeleton>] [MEMO] [BLANK] | TO ArrayName | MEMVAR | NAME ObjectName [ADDITIVE]
- Arguments
-
- MEMOSpecifies that the field list include one or more memo fields.
-
- BLANKInclude the BLANK keyword to create a set of empty variables or to fill the array or object with empty values. Each variable is assigned the same name, data type, and size as its field. If a field list is included, a variable is created for each field in the field list.
-
- TO <ArrayName>Specifies an array to which the record contents are copied. Starting with the first field, SCATTER copies the contents of each field into each element of the array in sequential order.
- SCATTER automatically creates a new array. The array elements have the same size and data types as the corresponding fields.
-
- MEMVARScatters the data to a set of variables instead of an array. SCATTER creates one variable for each field in the table and fills each variable with data from the corresponding field in the current record, assigning the variable the same name, size, and type as its field.
-
- NAME <ObjectName>Creates an object whose properties have the same names as fields in the table. To copy the value of each field in the table to each object property, do not include the BLANK keyword. To leave the properties empty, include the BLANK keyword
-
- ADDITIVETo update the property values of an existing and valid Visual FoxPro object specified by ObjectName. Using BLANK with ADDITIVE omits the values for existing properties that have matching field names.
-
- See Also
- GATHER, COPY TO ARRAY, APPEND FROM ARRAY
-
-
diff --git a/docs/Help_Spanish/Topics/Command_SET_ALTERNATE.xml b/docs/Help_Spanish/Topics/Command_SET_ALTERNATE.xml
deleted file mode 100644
index 2499ee90f5..0000000000
--- a/docs/Help_Spanish/Topics/Command_SET_ALTERNATE.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- SET ALTERNATE Command
-
- Commands
- SET ALTERNATE command
- Terminal Window
-
-
-
- SET ALTERNATE Command
-
-
- Purpose
- Writes screen output to a text file.
- Syntax
- SET ALTERNATE TO [<cFileName> [ADDITIVE] ]
- SET ALTERNATE ON | OFF | <lToggle>
-
- Arguments
- <cFileName>Specifies the name of the ASCII file where screen output is recorded. The name must contain the drive and path. The file name can be specified either as a literal file name or as a character expression in parentheses. When the file name is specified without a file extension, the extension ".TXT" is used by default.
- ADDITIVEThe option ADDITIVE adds the screen output to the current contents of the file <cFileName>. Without this option, the contents of the file are deleted if the file already exists. If a file with the name <cFileName> does not exist, it is created.
-
- <lToggle><lToggle> is a logical expression which must appear in parentheses. Instead of the logical expression, the option ON can be specified for the value .T. (true) or OFF for the value .F. (false). When .T. or ON is specified, screen output is recorded in the file <cFileName> .
- Description
- The command SET ALTERNATE opens an ASCII file to record screen output. Only screen output performed using commands like ? or LIST and functions like QOut() and QQOut() is written into the file. Commands containing the option TO FILE work like SET ALTERNATE. .
-
- The alternate file (the ASCII file <cFileName> ) is not tied to a single work area, but can be used from all work areas. Output to the file is turned on or off by the options ON | OFF or the logical value of <lToggle> . An alternate file is defined by including a file name in the command SET ALTERNATE. When SET ALTERNATE TO is called without a specified file name, the currently open alternate file is closed and recording screen output to a file is no longer possible. The alternate file is also closed by the commands CLOSE ALTERNATE and CLOSE ALL.
- Examples
-
-
-
-
-
- See Also
- SetAlternate(),SetAltFile(), SET CONSOLE
-
-
diff --git a/docs/Help_Spanish/Topics/Command_SET_CONSOLE.xml b/docs/Help_Spanish/Topics/Command_SET_CONSOLE.xml
deleted file mode 100644
index 69f4bf96c9..0000000000
--- a/docs/Help_Spanish/Topics/Command_SET_CONSOLE.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- SET CONSOLE Command
-
- Commands
- SET CONSOLE Command
- Terminal window
-
-
-
- SET CONSOLE Command
-
-
- Purpose
- Turns the screen display on/off.
- Syntax
- SET CONSOLE ON | off | <lToggle>
- Arguments
- <lToggle>A logical expression which must appear in parentheses. Instead of the logical expression, the option ON can be specified for the value .T. (true) or OFF for the value .F. (false). When .T. or ON is specified (the default value), all output is displayed on the screen. If the setting is set to OFF, output on the screen using commands like ? or ?? is suppressed.
- Description
- The command SET CONSOLE deactivates or activates output of characters on the screen. This includes commands like ? and functions like QOut() or QQOut(), which always begin output at the current cursor position.
-
- When SET CONSOLE is set to ON, output is displayed on the screen. There can also be parallel output to a file (command SET ALTERNATE).
- Examples
-
-
-
-
-
- See Also
- SetConsole(), SET ALTERNATE
-
-
diff --git a/docs/Help_Spanish/Topics/Command_SET_TEXTMERGE.xml b/docs/Help_Spanish/Topics/Command_SET_TEXTMERGE.xml
deleted file mode 100644
index 36832ad8ac..0000000000
--- a/docs/Help_Spanish/Topics/Command_SET_TEXTMERGE.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- SET TEXTMERGE Command
-
- Commands
- SET TEXTMERGE Command
- Terminal window
-
-
-
- SET TEXTMERGE Command
-
-
- Purpose
- Enables or disables the evaluation of fields, variables, array elements, functions, or expressions that are surrounded by text-merge delimiters, and lets you specify text-merge output.
- Syntax
- SET TEXTMERGE [ON | OFF] [TO [FileName] MEMVAR VarName [ADDITIVE]]
- [WINDOW WindowName] [SHOW | NOSHOW]
-
- Arguments
- ON Specifies that any fields, variables, array elements, functions, or expressions surrounded by the text-merge delimiters be evaluated and output when placed after \ or \\, or between TEXT and ENDTEXT.
-
- OFF(Default) Specifies that any fields, variables, array elements, functions, or expressions be literally output along with the text-merge delimiters surrounding them.
- TO [ FileName] Specifies that output from \, \\, and TEXT ... ENDTEXT be directed to a text file in addition to the main Visual FoxPro window, which is the default. You can also direct the output to a text file by including FileName. If a file with that name doesn't exist, a new file is created. If a file with the same name already exists and SET SAFETY is set to ON, you are given the option of overwriting the existing file. The text file is opened as a low-level file, and its file handle is stored to the _TEXT system variable. You can close the file by issuing SET TEXTMERGE TO without additional arguments. If the file handle of another file was previously stored in _TEXT, that file is closed.
-
- MEMVAR VarNameSpecifies a variable to contain data from TEXTMERGE output. Because SET TEXTMERGE is a global setting and can span several procedures or methods, it is possible for MEMVAR VarName to lose scope. The command will function even when the variable is out of scope, but will return no content. You can control scoping of MEMVAR VarName by declaring the variable.
-
- ADDITIVESpecifies that output from \, \\, and TEXT ... ENDTEXT be appended to an existing file or memory variable.
-
- SHOW | NOSHOW (Default) SHOW displays text-merge output. NOSHOW suppresses display of text-merge output. By default, output generated by \, \\, and TEXT ... ENDTEXT is sent to the Console window.
-
- Description
-
- Specifies that any fields, variables, array elements, functions, or expressions surrounded by the text-merge delimiters be evaluated and output when placed after \ or \\, or between TEXT and ENDTEXT.
- The following short program example demonstrates how the contents of the variable gcTodayDate and the DATE( ) and TIME( ) functions are evaluated when SET TEXTMERGE is set to ON.
-
- Examples
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Commands-by-Category.xml b/docs/Help_Spanish/Topics/Commands-by-Category.xml
deleted file mode 100644
index 426826f972..0000000000
--- a/docs/Help_Spanish/Topics/Commands-by-Category.xml
+++ /dev/null
@@ -1,184 +0,0 @@
-
-
-
- Commands and Statements
-
-
- Commands and Statements
-
- The X# language knows commands and statements. The difference between these two is:
-
-
Statements are defined by the compiler. Examples are the declarations of functions, local variables, and control structures, such as IF statements and FOR statements.
-
Commands are defined in a header file and are preprocessed by the compiler into function calls. Examples of a Command are the USE command and APPEND BLANK command.
-
-
- Statements are available in almost all dialects, with only a few exceptions.
- The available commands are very much dependent on the dialect. For example, in the Core dialect, no commands are available at all. Most commands have optional parameters and depend on the X# runtime types such as USUAL.
-
- This reference lists both the commands that are 'built-in' into the compiler and commands that are defined as default 'User Defined Commands' in STD.UDC.
- Some commands are marked with an asterisk as 'deprecated'. They may not be available in future versions of %APP%
-
-
-
-
- Built-in Statements
-
-
- Commands in header file
-
-
- Commands in header file
-
-
- Grouped by category
-
-
-
-
- #ifdef #else #endif
- #ifndef #else #endif
- ?|??
- \|\\
- _DLL
- ACCESS
- ASSIGN
- BEGIN SEQUENCE
- BREAK
- CLASS
- DECLARE
- DELEGATE
- DEFINE
- DO*
- DO CASE
- DO WHILE
- ENUM
- EXIT
- FIELD
- FOR
- FOREACH
- FUNCTION
- GLOBAL
- IF
- LOCAL
- LOOP
- MEMVAR
- METHOD
- PARAMETERS
- PRIVATE
- PROCEDURE
- PUBLIC
- REPEAT
- RETURN
- STATIC
- STRUCTURE
- TEXT
- UNION
- VOSTRUCT
-
-
- ACCEPT
- APPEND BLANK
- APPEND FROM
- AVERAGE
- CANCEL
- CLEAR ALL*
- CLEAR MEMORY*
- CLOSE
- COMMIT
- CONTINUE
- COPY FILE
- COPY STRUCTURE
- COPY STRUCTURE EXTENDED
- COPY TO
- COUNT
- CREATE
- CREATE FROM
- DEFAULT
- DELETE
- DELETE FILE
- DELETE TAG
- DIR
- ERASE
- EXTERNAL*
- FIND
- GO
- INDEX
- JOIN
- LOCATE
- NOTE
- PACK
- QUIT
- RECALL
- REINDEX
- RELEASE*
- RENAME
- REPLACE
- RESTORE*
- RUN
-
-
-
- SAVE*
- SEEK
- SELECT
- SET ANSI
- SET CENTURY
- SET COLLATION
- SET COLOR
- SET DATE
- SET DATE FORMAT
- SET DECIMALS
- SET DEFAULT
- SET DELETED
- SET DESCENDING
- SET DIGITFIXED
- SET DIGITS
- SET DRIVER
- SET EPOCH
- SET EXCLUSIVE
- SET FILTER
- SET FIXED
- SET INDEX
- SET INTERNATIONAL
- SET MEMOBLOCK
- SET OPTIMIZE
- SET ORDER
- SET PATH
- SET RELATION
- SET SCOPE
- SET SCOPEBOTTOM
- SET SCOPETOP
- SET SOFTSEEK
- SET UNIQUE
- SKIP
- SORT
- STORE
- SUM
- TOTAL
- UNLOCK
- UPDATE
- USE
- WAIT
- ZAP
-
-
- Comment
- Concurrency Control
- Database
- Date
- Entity Declaration
- Environment
- File
- Index/Order
- International
- Memory Variable
- Numeric
- Program Control
- Runtime Declaration
- Terminal Window
- Variable Declaration
-
- __CLR2__ (only for compatibility with Vulcan, x# does not implement the /clr compiler option). See comment below.
-
-
-
-
- __CLR4__
-
-
- String Literal
-
-
- __CLR4__ (only for compatibility with Vulcan, x# does not implement the /clr compiler option). See comment below.
-
-
-
-
- __CLRVERSION__
-
-
- String Literal
-
-
- "2" or "4"depending on the version. (only for compatibility with Vulcan, x# does not implement the /clr compiler option). See comment below.
-
-
-
-
- __DATE__
-
-
- String Literal
-
-
- Current date in YYYYMMDD format
-
-
-
-
- __DATETIME__
-
-
- String Literal
-
-
- Current date/time in format from regional settings
-
-
-
-
- __DIALECT__
-
-
- String
-
-
- Name of the current dialect
-
-
-
-
- __DIALECT_CORE__
-
-
- Logical
-
-
- Defined with TRUE when Core dialect is selected
-
-
-
-
- __DIALECT_FOXPRO__
-
-
- Logical
-
-
- Defined with TRUE when FoxPro dialect is selected
-
-
-
-
- __DIALECT_HARBOUR__
-
-
- Logical
-
-
- Defined with TRUE when Harbour dialect is selected
-
-
-
-
- __DIALECT_VO__
-
-
- Logical
-
-
- Defined with TRUE when VO dialect is selected
-
-
-
-
- __DIALECT_VULCAN__
-
-
- Logical
-
-
- Defined with TRUE when Vulcan dialect is selected
-
-
-
-
- __DIALECT_XBASEPP__
-
-
- Logical
-
-
- Defined with TRUE when Xbase++ dialect is selected
-
-
-
-
- __DEBUG__
-
-
- Logical Literal
-
-
- TRUE when compiling in debug mode. Undefined in Release mode
-
-
-
-
- __ENTITY__
-
-
- String Literal
-
-
- Name of current entity
-
-
-
-
- __FILE__
-
-
- String Literal
-
-
- Current source file name
-
-
-
-
- __FOX1__, __FOX2__
-
-
- Logical
-
-
- Current value of the FoxPro compatibility compiler options /fox1 and /fox2
-
-
-
-
- __FUNCTION__
-
-
- String Literal
-
-
- Current function/method name without class prefix and in original case
-
-
-
-
- __FUNCTIONS__
-
-
- String Literal
-
-
- Returns the name of the current Functions class
-
-
-
-
- __HARBOUR__
-
-
- Logic literal
-
-
- TRUE when the Harbour dialect is selected. Otherwise not defined.
-
-
-
-
- __LINE__
-
-
- String Literal
-
-
- Current source line number
-
-
-
-
- __MEMVAR__
-
-
- Logical
-
-
- TRUE when the /memvar compiler option is used
-
-
-
-
- __MODULE__
-
-
- String Literal
-
-
- Current source file name
-
-
-
-
- __SIG__
-
-
- String Literal
-
-
- Signature of current entity
-
-
-
-
- __SRCLOC__
-
-
- String Literal
-
-
- Filename and line number in the source
-
-
-
-
- __SYSDIR__
-
-
- String Literal
-
-
- Systemdir (on developers machine!)
-
-
-
-
- __TIME__
-
-
- String Literal
-
-
- Compile time in HH:mm:ss format
-
-
-
-
- __UNDECLARED__
-
-
- Logical Literal
-
-
- TRUE when the /undeclared compiler option is used
-
-
-
-
- __UNSAFE__
-
-
- Logical Literal
-
-
- TRUE when the /unsafe compiler option is used
-
-
-
-
- __UTCTIME__
-
-
- String Literal
-
-
- UTC Compile time in HH:mm:ss format
-
-
-
-
- __VERSION__
-
-
- String Literal
-
-
- Version of the compiler
-
-
-
-
- __VO__
-
-
- Logic literal
-
-
- TRUE when the VO dialect is selected. Otherwise not defined.
-
-
-
-
- __VO1__ , __VO2__ ... __VO17__
-
-
- Logical
-
-
- Current value of the matching VO compatibility compiler option, /vo1, /vo2 ... /vo17
-
-
-
-
- __VULCAN__
-
-
- Logic literal
-
-
- TRUE when the Vulcan dialect is selected. Otherwise not defined.
-
-
-
-
- __WINDIR__
-
-
- String Literal
-
-
- Windows dir (on developers machine!)
-
-
-
-
- __WINDRIVE__
-
-
- String Literal
-
-
- Windows drive (on developers machine!)
-
-
-
-
- __XPP__
-
-
- Logic literal
-
-
- TRUE when the Xbase++ dialect is selected. Otherwise not defined.
-
-
-
-
- __XPP1__
-
-
- Logical
-
-
- Current value of the /xpp1 compiler option. Only defined in the Xbase++ dialect.
-
-
-
-
- __XSHARP__
-
-
- Logical Literal
-
-
- Always TRUE
-
-
-
-
- __XSHARP_RT__
-
-
- Logical Literal
-
-
- TRUE when compiling against the X# runtime. Not defined otherwise.
-
-
-
- Note
- The CLR2 and CLR4 version is determined by the X# compiler by looking at the version of either system.dll or mscorlib.dll.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Compiler-magic-in-the-startup-code.xml b/docs/Help_Spanish/Topics/Compiler-magic-in-the-startup-code.xml
deleted file mode 100644
index 911c229841..0000000000
--- a/docs/Help_Spanish/Topics/Compiler-magic-in-the-startup-code.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- Compiler magic in the startup code
-
- $AppExit
- $AppInit
- $Exit
- $Init1
- $Init2
- $Init3
- EXIT PROCEDURE
- INIT PROCEDURE
-
-
-
- Compiler magic in the startup code
-
- The X# compiler also does some extra "tricks" in the startup code.
-
- XBase code may have so called INIT procedures, which contain code that will be executed at startup. For example inside the VO GUI Classes there is a procedure
- PROCEDURE __WCInitCriticalSections() _INIT1
- To ensure that these procedures are called at start the compiler generates one to three special methods in the functions class with the names $Init1, $Init2, $Init3 and $Exit. The VOGuiclasses assembly has two of these ($Init1 and $Init3). When you look at the contents of this method in ILSpy you see the following (using C# decompilation)
- // VOGUIClasses.Functions usingSystem.Runtime.CompilerServices;
[CompilerGenerated] publicstaticvoid$Init1() { __WCInitCriticalSections(); }
- In some assemblies you will see that the $Init1() method is there but it is empty. For example in the VOSystemClasses:
- // VOSystemClasses.Functions usingSystem.Runtime.CompilerServices;
[CompilerGenerated] publicstaticvoid$Init1() { }
- The reason why we are creating these empty initializers is the following:
- many of our VO customers are instantiating classes indirectly, by calling CreateInstance().
- To be able to do so the classes have to be available at runtime.
- The Roslyn compiler that we use is very smart. It does not include references to external assemblies into the exe when the exe does not reference any types or methods in that assembly.
- As a result if you were calling CreateInstance(#DbServer) in your app but you were never declaring variables of type DbServer (but only of type DataServer for example) then even when you include a reference to the VORDDClasses assembly at compile time you would not have a reference to the RDDClasses in your main app.
- That is why we are generating the empty $Init() methods.
-
- When building the main application, the X# compiler checks all referenced assemblies and looks for all $Init1, $Init2, $Init3 and $Exit methods and build some code to call all these methods. As a result all referenced assemblies will be loaded at startup. You will find this startup code in a special compiler generated method in the compiler generated <module> class:
-
- // <Module> usingApplication1.Exe; usingSystem; usingSystem.Runtime.CompilerServices; usingVOWin32APILibrary; usingXSharp; usingXSharp.RT;
[CompilerGenerated] internalstaticvoid$AppInit() { try { RuntimeState.AppModule=typeof(Application1.Exe.Functions).Module; RuntimeState.CompilerOptionOVF=false; RuntimeState.CompilerOptionVO11=false; RuntimeState.CompilerOptionVO13=false; RuntimeState.Dialect=XSharpDialect.VO; VOWin32APILibrary.Functions.$Init1(); XSharp.RT.Functions.$Init1(); Application1.Exe.Functions.$Init1(); } catch(ExceptioninnerException) { thrownewException("Error when executing code in INIT procedure(s)",innerException); } }
- As you can see this code not only calls several $Init1() methods, but it also sets some properties in the X# runtime. You can also see that the code above was called in the VO Dialect.
- And if you look at the generated code for the Start function this looks like this:
- // Application1.Exe.Functions usingSystem; usingXSharp.RT;
publicstaticvoidStart() { try { <Module>.$AppInit(); XSharp.RT.Functions.QOut("Function Start"); } finally { <Module>.$AppExit(); GC.Collect(); GC.WaitForPendingFinalizers(); } }
- The compiler has created a try finally block and calls $AppInit() to initialize the runtime state and call the init procedures in every referenced assembly.
- You also see that in the finally clause there is a call to $AppExit() from which EXIT procedures are called (we have added these in X#) and where the garbage collector cleans all references and waits for all finalizers to finish before your app finished.
-
- Unfortunately this does not mean that for example all open servers will be closed. If you have opened a DbServer and assigned the object to a global variable then this does not automatically close the server.
- There is some code in the runtime that takes care of this (but that is the subject of another topic)..
-
-
-
diff --git a/docs/Help_Spanish/Topics/Currency-Type.xml b/docs/Help_Spanish/Topics/Currency-Type.xml
deleted file mode 100644
index 89fc5d4a73..0000000000
--- a/docs/Help_Spanish/Topics/Currency-Type.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Currency Type
-
- CURRENCY
- XSharp.__Currency
-
-
-
- Currency Type
-
- This implements the FoxPro Currency type. The internal typename is XSharp.__Currency
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/DATE.xml b/docs/Help_Spanish/Topics/DATE.xml
deleted file mode 100644
index 011fe5eafd..0000000000
--- a/docs/Help_Spanish/Topics/DATE.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- DATE
-
- DATE
-
-
-
- DATE
-
- The DATE type is an integral type that stores a date value. The DATE is internally stored in three fields (DAY, MONTH and YEAR) that occupy a total of 32 bits in memory.
- Implementation
- The DATE type is implemented in the structure XSharp.__Date.
- The Usual type of DATE is 2.
-
-
diff --git a/docs/Help_Spanish/Topics/DECIMAL.xml b/docs/Help_Spanish/Topics/DECIMAL.xml
deleted file mode 100644
index cda289d62e..0000000000
--- a/docs/Help_Spanish/Topics/DECIMAL.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- DECIMAL
-
-
- DECIMAL
-
- The DECIMAL keyword describes the .Net System.Decimal type. The Decimal value type represents decimal numbers ranging from positive 79,228,162,514,264,337,593,543,950,335 to negative 79,228,162,514,264,337,593,543,950,335. The Decimal value type is appropriate for financial calculations that require large numbers of significant integral and fractional digits and no round-off errors. The Decimal type does not eliminate the need for rounding. Rather, it minimizes errors due to rounding. For example, the following code produces a result of 0.9999999999999999999999999999 instead of 1.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/DWORD.xml b/docs/Help_Spanish/Topics/DWORD.xml
deleted file mode 100644
index dbbec68d02..0000000000
--- a/docs/Help_Spanish/Topics/DWORD.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- DWORD
-
- DWORD
-
-
-
- DWORD
-
- The DWORD keyword denotes an integral type that stores unsigned 32-bit values with values ranging from 0 to 4,294,967,295.
-
-
diff --git a/docs/Help_Spanish/Topics/DYNAMIC.xml b/docs/Help_Spanish/Topics/DYNAMIC.xml
deleted file mode 100644
index 67706455a5..0000000000
--- a/docs/Help_Spanish/Topics/DYNAMIC.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- DYNAMIC
-
- DYNAMIC
-
-
-
- DYNAMIC
-
- The dynamic type enables the operations in which it occurs to bypass compile-time type checking. Instead, these operations are resolved at run time. The dynamic type simplifies access to COM APIs such as the Office Automation APIs, and also to dynamic APIs such as IronPython libraries, and to the HTML Document Object Model (DOM).
-
- Type dynamic behaves like type object in most circumstances. However, operations that contain expressions of type dynamic are not resolved or type checked by the compiler. The compiler bundles information about the operation, which is then used to evaluate the operation at run time. As part of the process, variables of type dynamic are compiled into variables of type object. Therefore, type dynamic exists only at compile time, not at run time.
- Please note that, to be able to use the DYNAMIC type in your app, you have to include the Microsoft.CSharp DLL at this moment, and the property names and method names are case sensitive at this moment.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Date-Type.xml b/docs/Help_Spanish/Topics/Date-Type.xml
deleted file mode 100644
index 95b3ca0c12..0000000000
--- a/docs/Help_Spanish/Topics/Date-Type.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Date Type
-
- DATE
- XSharp.__Date
-
-
-
- Date Type
-
- This structure holds year, month, day in 32 bits. For date calculations it uses the System.DateTime calculation logic. There are implicit converters between Date and DateTime. The internal type name for this type is XSharp.__Date
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/DateLiterals.xml b/docs/Help_Spanish/Topics/DateLiterals.xml
deleted file mode 100644
index 31e0b71f36..0000000000
--- a/docs/Help_Spanish/Topics/DateLiterals.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- Date Literals
-
- DATE
- Date Literals
- DATETIME
- DateTime Literals
- Literals
-
-
-
- Date and DateTime Literals
-
- Date literals are formatted
-
- YYYY.MM.DD
-
-
- or alternatively
- {^YYYY-MM-DD}
-
- DateTime Literals can be constructed with the followin syntax:
- {^YYYY-MM-DD HH:MM:SS}.
-
- Examples:
- 2000.01.01 2012.02.29 2015.09.25 // foxpro date and datetime literals {^2019.02.28} {^2020.02.29 23:59:59}
- Date and DateTime literals are supported in all dialects. In the Core dialect, both date and datetime literals will be translated to a DateTime value. In the other dialects, the Date literals are translated to a Date value.
- Of course you can also use runtime functions to construct a literal, such as STOD("20150925") or ConDate(2019,9,25), but a literal is more efficient.
-
-
diff --git a/docs/Help_Spanish/Topics/Delegates.xml b/docs/Help_Spanish/Topics/Delegates.xml
deleted file mode 100644
index 51be66f75c..0000000000
--- a/docs/Help_Spanish/Topics/Delegates.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Delegates
-
-
- Delegates
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Dialect-(in)compatibilities.xml b/docs/Help_Spanish/Topics/Dialect-(in)compatibilities.xml
deleted file mode 100644
index 36b0e4e6be..0000000000
--- a/docs/Help_Spanish/Topics/Dialect-(in)compatibilities.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Dialect (in)compatibilities
-
-
- Dialect (in)compatibilities
-
- The following pages list incompatibilties between X# and the various dialects. Please note that this list is not complete yet.
-
-
diff --git a/docs/Help_Spanish/Topics/Dialects.xml b/docs/Help_Spanish/Topics/Dialects.xml
deleted file mode 100644
index 6d03bb0dfa..0000000000
--- a/docs/Help_Spanish/Topics/Dialects.xml
+++ /dev/null
@@ -1,1070 +0,0 @@
-
-
-
- Dialects
-
-
- Dialects
-
- The X# compiler can run in different dialects. The table below shows the differences between these dialects. You can use the /dialect compiler option to select the dialect that you want to use.
- The Core dialect is default. All dialects apart from the Core dialect require a reference to the XSharp runtime DLLs
-
-
-
-
- Feature
-
-
- Core
-
-
- VO
-
-
- Vulcan
-
-
- Harbour
-
-
- Xbase++ 14
-
-
- FoxPro
-
-
-
-
- 4 Letter abbreviations of keywords
- (FUNC, WHIL etc).
-
-
- -
-
-
- Yes 11
-
-
- -
-
-
- Yes 11
-
-
- Follow the conventions of Xbase++
-
-
- Yes 11
-
-
-
-
- && as single line comment character (alternative syntax for //)
-
-
- -
-
-
- Yes
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- * at beginning of line as comment character
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- ALIAS (->) operator
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- AND, NOT, OR, XOR as alternatives for .AND., .NOT. etc
-
-
- -
-
-
- -
-
-
- -
-
-
- -
-
-
- -
-
-
- Yes
-
-
-
-
- ARRAY type, Including Array literals & NULL_ARRAY, including missing elements
-
- PSZ Type, including NULL_PSZ and (pseudo) PSZ conversion functions (String2Psz(), Cast2Psz()
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- PSZ Indexer
-
-
- n/a
-
-
- 1 based
-
-
- 0 based
-
-
- 1 based
-
-
- 1 based
-
-
- 1 based
-
-
-
-
- NULL_STRING
-
-
- Yes 9
-
-
- Yes 9
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- SYMBOL type, including Symbol literals & NULL_SYMBOL
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- Statements before the first entity in a source file
-
-
- -
-
-
- -
-
-
- -
-
-
- -
-
-
- -
-
-
- Yes
-
-
-
-
- USUAL type, including NIL literal (1,2)
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes 15
-
-
-
-
- TEXT Command
-
-
- -
-
-
- -
-
-
- -
-
-
- -
-
-
- -
-
-
- Yes
-
-
-
-
- Special features
-
-
-
-
-
-
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- VOSTRUCT and AS/IS syntax (10)
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- -
-
-
- -
-
-
- -
-
-
-
-
- UNION and AS/IS syntax (10)
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- -
-
-
- -
-
-
- -
-
-
-
-
- Untyped Literal Arrays
-
-
- -
-
-
- Yes 8
-
-
- Yes 8
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- Missing types allowed
-
-
- -
-
-
- Yes 3
-
-
- Yes 3
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- Missing arguments in function/method calls MyFunc(1,,2)
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- Pseudo functions
-
-
-
-
-
-
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- PCount(), _GetMParam(), _GetFParam(), _Args()
-
-
- -
-
-
- Yes 4
-
-
- Yes 4
-
-
- Yes 4
-
-
- Yes 4
-
-
- Yes 4
-
-
-
-
- SLen()
-
-
- -
-
-
- Yes 5
-
-
- Yes 5
-
-
- Yes 5
-
-
- Yes 5
-
-
- Yes 5
-
-
-
-
- _Chr()
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- AltD()
-
-
- -
-
-
- Yes 6
-
-
- Yes 6
-
-
- Yes 6
-
-
- Yes 6
-
-
- Yes 6
-
-
-
-
- PCall, PCallNative
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- CCall, CCallNative
-
-
- -
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
- Yes
-
-
-
-
- Other information
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Generated Function class name
-
-
- Functions X$<ModuleName>$Functions for static functions and globals
-
-
- <AssemblyName>.Functions (DLLs) <AssemblyName>.Exe.Functions (EXEs) <AssemblyName>.Exe.$<ModuleName>$.Functions for static functions and globals
-
-
-
-
-
-
-
-
Requires VulcanRT.DLL or XSharp.VO.DLL.
-
Requires VulcanRTFuncs.DLL or XSharp.VO.DLL.
-
Missing types get translated to USUAL. With the new /vo15 compiler option you can tell the compiler that you do not want to allow missing types.
-
Only supported inside functions and methods with Clipper Calling convention.
-
The Vulcan runtime does not have a SLen() function. The compiler translates this to accessing the Length property of the string.
-
This gets translated to: IF System.Diagnostics.Debugger.Attached System.Diagnostics.Debugger.Break() ENDIF.
-
In the core dialect each of the expressions is cast to OBJECT. In the other dialects the expression is cast to USUAL.
-
Untyped literal arrays in the VO/Vulcan dialect are translated to the VO Array type: {"aa", "bb", "cc"} Typed literal arrays are prefixed with <Type> like this: <STRING>{"aa", "bb", "cc"} This becomes a literal string array.
-
With the /vo2 compiler option NULL_STRING is compiled to an empty string. Otherwise to a NULL.
-
The VOSTRUCT and UNION can be replaced with a standard .NET structure. For Union, you need to use the [StructLayout(LayoutKind.Explicit)] attribute on the structure, and the [FieldOffSet()] attribute on each field, to explicitly define the location of the fields.
-
Only for VO compatible keywords, not for keywords introduced in Vulcan or XSharp.
-
The true and false expressions for an IIF() are optional in Harbour and Xbase++.
-
The macro compiler is not supported. However, when you use the RDD system in the Core dialect, the index expression will still use the macro compiler and a reference to the XSharp.RT.DLL is needed for the support of the macro compiler.
-
This requires the XSharp runtime.
-
In FoxPro, NIL is not allowed and redefined to FALSE.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Disclaimer.xml b/docs/Help_Spanish/Topics/Disclaimer.xml
deleted file mode 100644
index bb22a32ea0..0000000000
--- a/docs/Help_Spanish/Topics/Disclaimer.xml
+++ /dev/null
@@ -1,115 +0,0 @@
-
-
-
- Disclaimer
-
-
- Disclaimer
-
-
- At this moment X# supports the following Xbase dialects:
-
-
-
-
- Dialect
-
-
- Syntax
-
-
- Classes
-
-
- Functions
-
-
-
-
- Core
-
-
- Complete
-
-
- Complete
-
-
- Complete
-
-
-
-
- Visual Objects
-
-
- Complete
-
-
- Complete
-
-
- Complete
-
-
-
-
- Vulcan
-
-
- Complete
-
-
- Complete
-
-
- Complete
-
-
-
-
- Xbase++
-
-
- Complete
-
-
- Partially.
-
-
- Partially
-
-
-
-
- (Visual) FoxPro
-
-
- Partially.
-
-
- Partially.
-
-
- Partially.
-
-
-
-
- (X)Harbour
-
-
- Partially.
-
-
- Partially.
-
-
- Partially.
-
-
-
-
- For more info about the dialects see the dialects topic in this documentation
-
-
diff --git a/docs/Help_Spanish/Topics/Editor-combo-boxes.xml b/docs/Help_Spanish/Topics/Editor-combo-boxes.xml
deleted file mode 100644
index bc73a2c33b..0000000000
--- a/docs/Help_Spanish/Topics/Editor-combo-boxes.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Editor combo boxes
-
- dropdowns
- Editor combo boxes
-
-
-
- Editor combo boxes (dropdowns)
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Embedded_topics.xml b/docs/Help_Spanish/Topics/Embedded_topics.xml
deleted file mode 100644
index 28313ac2e9..0000000000
--- a/docs/Help_Spanish/Topics/Embedded_topics.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-
-
- Embedded topics
-
- Enter topic text here.
-
-
diff --git a/docs/Help_Spanish/Topics/Enumeration-Types.xml b/docs/Help_Spanish/Topics/Enumeration-Types.xml
deleted file mode 100644
index a4e6b4192b..0000000000
--- a/docs/Help_Spanish/Topics/Enumeration-Types.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Enumeration Types
-
-
- Enumeration Types
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Escape-codes.xml b/docs/Help_Spanish/Topics/Escape-codes.xml
deleted file mode 100644
index 9f71dd5b78..0000000000
--- a/docs/Help_Spanish/Topics/Escape-codes.xml
+++ /dev/null
@@ -1,151 +0,0 @@
-
-
-
- Escape codes
-
- \'
- \"
- \\
- \0
- \a
- \b
- \f
- \n
- \r
- \t
- \u
- \v
- \x
- Escape codes
- Literals
-
-
-
- Escape codes
-
- The <char> literals in the table that are marked with an asterisk (*) may contain a special escape code:
-
-
-
-
- Character
-
-
- Description
-
-
-
-
- Character that does NOT start with a backslash
-
-
- Normal character
-
-
-
-
- \\
-
-
- Backslash
-
-
-
-
- \"
-
-
- Double quote
-
-
-
-
- \'
-
-
- Single quote
-
-
-
-
- \0
-
-
- 0 character
-
-
-
-
- \a
-
-
- Alert
-
-
-
-
- \b
-
-
- Backspace
-
-
-
-
- \f
-
-
- Form feed
-
-
-
-
- \n
-
-
- Line feed
-
-
-
-
- \r
-
-
- New Line
-
-
-
-
- \t
-
-
- Tab
-
-
-
-
- \v
-
-
- Vertical tab
-
-
-
-
- \x HEXDIGIT(1-4)
-
-
- Hex number of character. 1-4 hex digits.
-
-
-
-
- \u HEXGDIGIT (4 or 8)
-
-
- Unicode number of character. 4 or 8 hex digits.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Events.xml b/docs/Help_Spanish/Topics/Events.xml
deleted file mode 100644
index 93f3dc828b..0000000000
--- a/docs/Help_Spanish/Topics/Events.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Events
-
-
- Events
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-ASYNC.xml b/docs/Help_Spanish/Topics/Ex-ASYNC.xml
deleted file mode 100644
index b9baca5593..0000000000
--- a/docs/Help_Spanish/Topics/Ex-ASYNC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- ASYNC Example
-
-
- ASYNC Example
-
- // // This example shows that you can call an async task and wait for it to finish // The result of the async task (in this case the size of the file that has been downloaded) // will be come available when the task has finished // The calling code (The Start()) function will not have to wait until the async task has // finished. That is why the line "2....." will be printed before the results from TestClass.DoTest() // The sample also shows an event and displays the thread id's. You can see that the DownloadFileTaskAsync() method // starts multiple threads to download the web document in multiple pieces.
USING System USING System.Threading.Tasks
FUNCTION Start() ASVOID ? "1. calling long process" TestClass.DoTest() ? "2. this should be printed while processing" Console.ReadKey()
CLASS TestClass STATIC PROTECT oLock AS OBJECT // To make sure we synchronize the writing to the screen STATIC CONSTRUCTOR oLock := OBJECT{}
ASYNCSTATICMETHOD DoTest() ASVOID LOCAL Size AS INT64 Size := AWAIT LoooongProcess() ? "3. returned from long process" ? Size, " Bytes downloaded"
ASYNCSTATICMETHOD LoooongProcess() AS Task<INT64> VAR WebClient := System.Net.WebClient{} VAR FileName := System.IO.Path.GetTempPath()+"temp.txt" webClient:DownloadProgressChanged += OnDownloadProgress webClient:Credentials := System.Net.CredentialCache.DefaultNetworkCredentials AWAIT webClient:DownloadFileTaskAsync("http://www.xsharp.info/index.php", FileName) VAR dirInfo := System.IO.DirectoryInfo{System.IO.Path.GetTempPath()} VAR Files := dirInfo:GetFiles("temp.txt") IF Files:Length > 0 System.IO.File.Delete(FileName) RETURN Files[1]:Length ENDIF RETURN 0
STATICMETHOD OnDownloadProgress (sender AS OBJECT, e AS System.Net.DownloadProgressChangedEventArgs) ASVOID BEGINLOCK oLock ? String.Format("{0,3} % Size: {1,8:N0} Thread {2}", 100*e:BytesReceived / e:TotalBytesToReceive , e:BytesReceived, ; System.Threading.Thread.CurrentThread:ManagedThreadId) ENDLOCK RETURN
ENDCLASS
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-ASYNC_MSHC.xml b/docs/Help_Spanish/Topics/Ex-ASYNC_MSHC.xml
deleted file mode 100644
index 7b864753cd..0000000000
--- a/docs/Help_Spanish/Topics/Ex-ASYNC_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- ASYNC Example
-
-
- ASYNC Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Anonymous-Methods.xml b/docs/Help_Spanish/Topics/Ex-Anonymous-Methods.xml
deleted file mode 100644
index 1b6407cec2..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Anonymous-Methods.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Anonymous Method Expressions
-
-
- Anonymous Method Expressions
-
- An example of an Anonymous Method Expression (AME) (note the DELEGATE keyword): Note that the body of the that you can have :
-
-
A single Expression
-
An Expression List
-
A statement List
-
- The first 2 require the expression(s) to be on the same line as the opening Curly { . Of course you can use the statement continuation character ; to tell the compiler that you have spread the statement over more than one line. The last one requires the statements in the list to be on separate lines and the closing Curly } must also be on a separate line. This is shown in the example below.
-
- USING System.Windows.Forms FUNCTION Start() ASVOID TestAnonymous() RETURN FUNCTION TestAnonymous() ASVOID LOCAL oForm AS Form oForm := Form{} oForm:Text := "Click me to activate the anonymous method" oForm:Click += DELEGATE(o AS System.Object, e AS System.EventArgs ) { System.Windows.Forms.MessageBox.Show("Click 1!") System.Windows.Forms.MessageBox.Show("Click 2!") } oForm:ShowDialog() RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Anonymous-Methods_MSHC.xml b/docs/Help_Spanish/Topics/Ex-Anonymous-Methods_MSHC.xml
deleted file mode 100644
index e330ecb198..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Anonymous-Methods_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Anonymous Method Expressions
-
-
- Anonymous Method Expressions
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Anonymous-Types.xml b/docs/Help_Spanish/Topics/Ex-Anonymous-Types.xml
deleted file mode 100644
index 5f97331dc7..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Anonymous-Types.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- Anonymous Types
-
-
- Anonymous Types
-
- Anonymous types are used a lot in relation to LINQ. See the LINQ example below. In the first LINQ statement an anonymous class is created
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Anonymous-Types_MSHC.xml b/docs/Help_Spanish/Topics/Ex-Anonymous-Types_MSHC.xml
deleted file mode 100644
index 322c065c21..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Anonymous-Types_MSHC.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- Anonymous Types
-
-
- Anonymous Types
-
- Anonymous types are used a lot in relation to LINQ. See the LINQ example below. In the first LINQ statement an anonymous class is created
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-BEGIN-UNSAFE.xml b/docs/Help_Spanish/Topics/Ex-BEGIN-UNSAFE.xml
deleted file mode 100644
index 2557a4cd22..0000000000
--- a/docs/Help_Spanish/Topics/Ex-BEGIN-UNSAFE.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- BEGIN UNSAFE Example
-
-
- BEGIN UNSAFE Example
-
- Enter topic text here.
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-BEGIN-UNSAFE_MSHC.xml b/docs/Help_Spanish/Topics/Ex-BEGIN-UNSAFE_MSHC.xml
deleted file mode 100644
index 1cc986ec8a..0000000000
--- a/docs/Help_Spanish/Topics/Ex-BEGIN-UNSAFE_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- BEGIN UNSAFE Example
-
-
- BEGIN UNSAFE Example
-
- Enter topic text here.
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-BEGIN-USING.xml b/docs/Help_Spanish/Topics/Ex-BEGIN-USING.xml
deleted file mode 100644
index 0256a50fc0..0000000000
--- a/docs/Help_Spanish/Topics/Ex-BEGIN-USING.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- BEGIN USING Example
-
-
- BEGIN USING Example
-
- // // XSharp allows you to not only use the using statement to link to namespaces // You can also link to a static class and call the methods in this class as if they are functions. // The functions WriteLine and ReadKey() in the following code are actually resolved as System.Console.WriteLine() // and System.Console.ReadKey() // Finally there is also the BEGIN USING .. END USING construct which controls the lifetime of a variable // At the end of the block the Variable will be automatically disposed. USING System USINGSTATIC System.Console
FUNCTION Start() ASVOID WriteLine("Before Using Block") WriteLine("------------------") BEGINUSINGVAR oTest := Test{} oTest:DoSomething() ENDUSING WriteLine("------------------") WriteLine("After Using Block") ReadKey()
CLASS Test IMPLEMENTS IDisposable CONSTRUCTOR() Console.WriteLine("Test:Constructor()")
ENDCLASS
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-BEGIN-USING_MSHC.xml b/docs/Help_Spanish/Topics/Ex-BEGIN-USING_MSHC.xml
deleted file mode 100644
index 2d7b9c82e4..0000000000
--- a/docs/Help_Spanish/Topics/Ex-BEGIN-USING_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- BEGIN USING Example
-
-
- BEGIN USING Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-CHECKED.xml b/docs/Help_Spanish/Topics/Ex-CHECKED.xml
deleted file mode 100644
index 5c045ff7ac..0000000000
--- a/docs/Help_Spanish/Topics/Ex-CHECKED.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- CHECKED Example
-
-
- CHECKED Example
-
- FUNCTION Start() ASVOID LOCAL d ASDWORD LOCAL n ASINT d := UInt32.MaxValue ? "Initial value of d:", d
BEGINUNCHECKED // arithmetic operations inside an UNCHECKED block will not produce // overflow exceptions on arithmetic conversions and operations, // no matter if overflow checking is enabled application-wide or not n := (INT)d ? "Value of n after conversion:", n d ++ ? "Value of d after increasing it:", d ENDUNCHECKED
d := UInt32.MaxValue BEGINCHECKED // arithmetic operations inside a CHECKED block always do // overflow checking and throw exceptions if overflow is detected TRY n := (INT)d d ++ CATCH e AS Exception ? "Exception thrown in CHECKED operation:", e:Message ENDTRY ENDCHECKED Console.ReadLine() RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-CHECKED_MSHC.xml b/docs/Help_Spanish/Topics/Ex-CHECKED_MSHC.xml
deleted file mode 100644
index 529544fece..0000000000
--- a/docs/Help_Spanish/Topics/Ex-CHECKED_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- CHECKED Example
-
-
- CHECKED Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-EVENT.xml b/docs/Help_Spanish/Topics/Ex-EVENT.xml
deleted file mode 100644
index 57e583faf2..0000000000
--- a/docs/Help_Spanish/Topics/Ex-EVENT.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- EVENT Example
-
-
- EVENT Example
-
- USING System.Collections.Generic FUNCTION Start ASVOID LOCAL e AS EventsExample e := EventsExample{} e:Event1 += TestClass.DelegateMethod e:Event1 += TestClass.DelegateMethod e:Event1 -= TestClass.DelegateMethod // added 2, removed 1, should be called once e:Event2 += TestClass.DelegateMethod e:Event2 += TestClass.DelegateMethod e:Event2 -= TestClass.DelegateMethod // added 2, removed 1, should be called once e:Event3 += TestClass.DelegateMethod e:RaiseEvent1("This is a test through a multi line event definition") e:RaiseEvent2("This is a test through a single line event definition") e:RaiseEvent3("This is a test through an old style event definition") Console.WriteLine("Press a Key") Console.ReadLine()
DELEGATE EventHandler (s ASSTRING) ASVOID
CLASS TestClass STATICMETHOD DelegateMethod(s ASSTRING ) ASVOID Console.WriteLine( s) ENDCLASS
// Multiline definition EVENT Event1 AS EventHandler ADD BEGIN LOCK eventsTable eventsTable[sEvent1] := ((EventHandler) eventsTable[sEvent1]) + value END LOCK Console.WriteLine(__ENTITY__ + " "+value:ToString()) END REMOVE BEGIN LOCK eventsTable eventsTable[sEvent1] := ((EventHandler) eventsTable[sEvent1]) - value END LOCK Console.WriteLine(__ENTITY__+ " "+value:ToString()) END ENDEVENT
// Single Line defintion on multilpe lines with semi colons, for better reading ! EVENT Event2 AS EventHandler ; ADD eventsTable[sEvent2] := ((EventHandler) eventsTable[sEvent2]) + value ; REMOVE eventsTable[sEvent2] := ((EventHandler) eventsTable[sEvent2]) - value
// Old style definition EVENT Event3 AS EventHandler
METHOD RaiseEvent1(s ASSTRING) ASVOID VAR handler := (EventHandler) eventsTable[sEvent1] IF handler != NULL handler(s) ENDIF
METHOD RaiseEvent2(s ASSTRING) ASVOID VAR handler := (EventHandler) eventsTable[sEvent2] IF handler != NULL handler(s) ENDIF
METHOD RaiseEvent3(s ASSTRING) ASVOID IFSELF:Event3 != NULL Event3(s) ENDIF ENDCLASS
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-EVENT_MSHC.xml b/docs/Help_Spanish/Topics/Ex-EVENT_MSHC.xml
deleted file mode 100644
index 539246fbe1..0000000000
--- a/docs/Help_Spanish/Topics/Ex-EVENT_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- EVENT Example
-
-
- EVENT Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Expression.xml b/docs/Help_Spanish/Topics/Ex-Expression.xml
deleted file mode 100644
index a11c460d86..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Expression.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Expression Examples
-
-
- Expression Examples
-
- // // This example shows various new expression formats // using System.Collections.Generic
Function Start() asvoid VAR oNone := Person{"No", "Parent"}
FOREACHVAR oValue in GetList() if oValue ISSTRING// Value IS Type ? (String) oValue ELSEIF oValue ISINT ? (Int) oValue ELSEIF oValue ISDateTime ? (DateTime) oValue ELSEIF oValue IS Person LOCAL oPerson as Person oPerson := (Person) oValue ? oPerson:FirstName, oPerson:LastName // Value DEFAULT Value2 . When Value IS NULL then Value2 will be used oPerson := oPerson:Parent DEFAULT oNone ? "Parent: ", oPerson:FirstName, oPerson:LastName ENDIF NEXT LOCAL oEmptyPerson as Person LOCAL sName asSTRING oEmptyPerson := GetAPerson() sName := oEmptyPerson?:FirstName // Conditional Access: This will not crash, even when Person is a NULL_OBJECT ? sName DEFAULT "None" Console.ReadLine() RETURN
FUNCTION GetList() AS List<OBJECT> VAR aList := List<OBJECT>{} aList:Add(DateTime.Now) aList:Add("abcdefg") aList:Add(123456) VAR oPerson := Person{"John", "Doe"} aList:Add(oPerson) VAR oChild := Person{"Jane", "Doe"} oChild:Parent := oPerson aList:Add(oChild) RETURN aList
CLASS Person EXPORT FirstName ASSTRING EXPORT LastName asSTRING EXPORT Parent as Person CONSTRUCTOR(First asSTRING, Last asSTRING) FirstName := First LastName := Last
ENDCLASS
FUNCTION GetAPerson() as Person RETURN NULL_OBJECT
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Expression_MSHC.xml b/docs/Help_Spanish/Topics/Ex-Expression_MSHC.xml
deleted file mode 100644
index 0c3dab8ca0..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Expression_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Expression Examples
-
-
- Expression Examples
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-FIXED.xml b/docs/Help_Spanish/Topics/Ex-FIXED.xml
deleted file mode 100644
index 844104532d..0000000000
--- a/docs/Help_Spanish/Topics/Ex-FIXED.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- FIXED Example
-
-
- FIXED Example
-
- The new FIXED modifier and BEGIN FIXED .. END FIXED keywords allow you to tell the .Net runtime that you do not want a variable to be moved by the Garbage collector.
- UNSAFEFUNCTION Start ASVOID VAR s := "SDRS" BEGINFIXEDLOCAL p := s ASCHARPTR VAR i := 0 WHILE p[i] != 0 p[i++]++ END ENDFIXED Console.WriteLine(s) Console.Read() RETURN
- As you can see the BEGIN FIXED statement requires a local variable declaration. The contents of this local (in the example above a CHAR PTR) will be excluded from garbage collection inside the block.
-
- Please note: The FIXED keyword and the example above should be used with extreme care. Strings in .Net are immutable. You normally should not manipulate strings this way !
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-FIXED_MSHC.xml b/docs/Help_Spanish/Topics/Ex-FIXED_MSHC.xml
deleted file mode 100644
index c98ccd04a4..0000000000
--- a/docs/Help_Spanish/Topics/Ex-FIXED_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- FIXED Example
-
-
- FIXED Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-GENERICs.xml b/docs/Help_Spanish/Topics/Ex-GENERICs.xml
deleted file mode 100644
index ac8d27cb43..0000000000
--- a/docs/Help_Spanish/Topics/Ex-GENERICs.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- GENERICs Example
-
-
- GENERICs Example
-
- Stack Example This example shows that we can now create generic classes with X# ! In the Stack class the T parameter will be replaced with a type at compile time.
- /* Stack Example - Written by Robert van der Hulst This example shows that we can now create generic classes with X# ! Note: Compile with the /AZ option */
USING System.Collections.Generic USINGSTATIC System.Console
FUNCTION Start ASVOID LOCAL oStack AS Stack<INT> LOCAL i ASLONG TRY oStack := Stack<INT>{25} WriteLine("Created a stack with {0} items",oStack:Capacity) WriteLine("Pushing 10 items") FOR I := 1 TO 10 oStack:Push(i) NEXT WriteLine("Popping the stack until it is empty") i := 0 WHILE oStack:Size > 0 i += 1 WriteLine(oStack:Pop()) END WriteLine("{0} Items popped from the stack",i) WriteLine("Press Enter") ReadLine() WriteLine("The next line pops from an empty stack and throws an exception") ReadLine() WriteLine(oStack:Pop()) CATCH e AS Exception WriteLine("An exception was catched: {0}", e:Message) ENDTRY WriteLine("Press Enter to Exit") ReadLine() RETURN
CLASS Stack<T> WHERE T IS STRUCT, NEW() PROTECT _Items AS T[] PROTECT _Size ASINT PROTECT _Capacity ASINT PROPERTY Size ASINTGET _Size PROPERTY Capacity ASINTGET _Capacity
PUBLICMETHOD Push( item AS T) ASVOID IF _Size >= _Capacity THROW StackOverFlowException{} ENDIF _Items[_Size] := item _Size++ RETURN
PUBLICMETHOD Pop( ) AS T _Size-- IF _Size >= 0 RETURN _Items[_Size] ELSE _Size := 0 THROW Exception{"Cannot pop from an empty stack"} ENDIF ENDCLASS
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-GENERICs_MSHC.xml b/docs/Help_Spanish/Topics/Ex-GENERICs_MSHC.xml
deleted file mode 100644
index 02588bf4c1..0000000000
--- a/docs/Help_Spanish/Topics/Ex-GENERICs_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- GENERICs Example
-
-
- GENERICs Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-LINQ.xml b/docs/Help_Spanish/Topics/Ex-LINQ.xml
deleted file mode 100644
index c92d782e2d..0000000000
--- a/docs/Help_Spanish/Topics/Ex-LINQ.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- LINQ Example
-
-
- LINQ Example
-
- The following example shows a couple of LINQ Queries in X#
- //references: //System.dll //System.Core.dll //System.Linq.dll USING System.Collections.Generic USING System.Linq USINGSTATIC System.Console
FUNCTION Start ASVOID VAR oDev := GetDevelopers() VAR oC := GetCountries() VAR oAll := FROM D IN oDev ; JOIN C IN oC ON D:Country EQUALS C:Name ; ORDERBY D:LastName ; SELECTCLASS {D:Name, D:Country, C:Region} // Anonymous class ! // The type of oAll is IOrderedEnumerable<<>f__AnonymousType0<Developer,Country>> // We prefer the VAR keyword! VAR oGreek := FROM Developer IN oDev ; WHERE Developer:Country == "Greece" ; ORDERBY Developer:LastName DESCENDING ; SELECT Developer // The type of oGreek is IOrderedEnumerable<Developer> // We prefer the VAR keyword!
VAR oCount := FROM Developer IN oDev ; GROUP Developer BY Developer:Country INTO NewGroup ; ORDERBY NewGroup:Key SELECT NewGroup // The type of oCount is IOrderedEnumerable<<IGrouping<string,Developer>> // We prefer the VAR keyword!
WriteLine(e"X# does LINQ!\n") WriteLine(e"All X# developers (country+lastname order)\n") FOREACHVAR oDeveloper IN oAll WriteLine("{0} in {1}, {2}",oDeveloper:Name, oDeveloper:Country, oDeveloper:Region) NEXT WriteLine(e"\nGreek X# Developers (descending lastname)\n") FOREACH oDeveloper AS Developer IN oGreek WriteLine(oDeveloper:Name) NEXT WriteLine(e"\nDevelopers grouped per country\n")
FOREACHVAR country IN oCount WriteLine(i"{country.Key}, {country.Count()} developer(s)") FOREACHVAR oDeveloper IN country WriteLine(" " + oDeveloper:Name) NEXT NEXT WriteLine("Enter to continue") ReadLine() RETURN
FUNCTION GetDevelopers AS IList<Developer> // This function uses a collection initializer for the List of Developers // and Object initializers for the Developer Objects VAR oList := List<Developer>{} { ; Developer{}{ FirstName := "Chris", LastName := "Pyrgas", Country := "Greece"},; Developer{}{ FirstName := "Robert", LastName := "van der Hulst", Country := "The Netherlands"},; Developer{}{ FirstName := "Fabrice", LastName := "Foray", Country := "France"},; Developer{}{ FirstName := "Nikos", LastName := "Kokkalis", Country := "Greece"} ; } RETURN oList
FUNCTION GetCountries AS IList<Country> // This function uses a collection initializer for the List of Counties // and Object initializers for the Country Objects VAR oList := List<Country>{}{ ; Country{} {Name := "Greece", Region := "South East Europe"},; Country{} {Name := "France", Region := "West Europe"},; Country{} {Name := "The Netherlands", Region := "North West Europe"} ; } RETURN oList CLASS Developer PROPERTY Name ASSTRINGGET FirstName + " " + LastName PROPERTY FirstName ASSTRING AUTO PROPERTY LastName ASSTRING AUTO PROPERTY Country ASSTRING AUTO ENDCLASS
CLASS Country PROPERTY Name ASSTRING AUTO PROPERTY Region ASSTRING AUTO ENDCLASS
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-LINQ_MSHC.xml b/docs/Help_Spanish/Topics/Ex-LINQ_MSHC.xml
deleted file mode 100644
index 49e038b611..0000000000
--- a/docs/Help_Spanish/Topics/Ex-LINQ_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- LINQ Example
-
-
- LINQ Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Lamda-Expressions.xml b/docs/Help_Spanish/Topics/Ex-Lamda-Expressions.xml
deleted file mode 100644
index df73a96773..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Lamda-Expressions.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Lamda Expressions
-
- =>
- Lamda
- Lamda Expression
-
-
-
- Lamda Expressions
-
- Lamda Expressions are very much like CodeBlocks, but the difference is that it has optional typed parameters and return values. You can also specify the parameter type in the parameter list as the 3rd example shows
DELEGATE Multiply(x ASREAL8) ASREAL8 FUNCTION Start ASVOID LOCAL del AS Multiply del := {e => e * e} ? del(1) ? del(2) ? del(3) ? del(4) Console.ReadLine() LOCAL dfunc AS System.Func<Double,Double> dfunc := {x => ? "square of", x RETURN x^2 } ? dfunc(5) LOCAL typed AS Multiply typed := {x ASREAL8 => ? "square of", x RETURN x^2 } ? typed(6) RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Lamda-Expressions_MSHC.xml b/docs/Help_Spanish/Topics/Ex-Lamda-Expressions_MSHC.xml
deleted file mode 100644
index 2a4a9c30ee..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Lamda-Expressions_MSHC.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Lamda Expressions
-
- =>
- Lamda
- Lamda Expression
-
-
-
- Lamda Expressions
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-NOP.xml b/docs/Help_Spanish/Topics/Ex-NOP.xml
deleted file mode 100644
index 0bfb22c8be..0000000000
--- a/docs/Help_Spanish/Topics/Ex-NOP.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- NOP Example
-
-
- NOP Example
-
- // The NOP keyword is an empty statement. // This tells the compiler that there is no code missing ! FUNCTION Start() ASVOID LOCAL i as LONG FOR i := 1 to 10 IF I % 2 == 0 Console.WriteLine(i) ELSE NOP // Nothing happens here. This tells the compiler that there is no code missing ! ENDIF NEXT RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-NOP_MSHC.xml b/docs/Help_Spanish/Topics/Ex-NOP_MSHC.xml
deleted file mode 100644
index e48daf97ea..0000000000
--- a/docs/Help_Spanish/Topics/Ex-NOP_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- NOP Example
-
-
- NOP Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-SWITCH.xml b/docs/Help_Spanish/Topics/Ex-SWITCH.xml
deleted file mode 100644
index dbcc9f4198..0000000000
--- a/docs/Help_Spanish/Topics/Ex-SWITCH.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- SWITCH Example
-
-
- SWITCH Example
-
- // // The SWITCH statement is a replacement for the DO CASE statement // The biggest difference is that the expression (in this case sDeveloper) is only evaluated once. // which will have a performance benefit over the DO CASE statement // Empty statement lists for a CASE are allowed. In that case the labels share the code (see CHRIS and NIKOS below) // // Please note that EXIT statements inside a switch are not allowed, however RETURN, LOOP and THROW are allowed. using System.Collections.Generic
Function Start() asvoid FOREACHVAR sDeveloper in GetDevelopers() SWITCH sDeveloper:ToUpper() CASE "FABRICE" ? sDeveloper, "France" CASE "CHRIS" CASE "NIKOS" ? sDeveloper, "Greece" CASE "ROBERT" ? sDeveloper, "The Netherlands" OTHERWISE ? sDeveloper, "Earth" END SWITCH NEXT Console.ReadKey() RETURN
FUNCTION GetDevelopers as List<String> VAR aList := List<String>{} aList:AddRange(<string>{ "Chris", "Fabrice", "Nikos", "Robert", "YourName" } ) RETURN aList
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-SWITCH_MSHC.xml b/docs/Help_Spanish/Topics/Ex-SWITCH_MSHC.xml
deleted file mode 100644
index 5af7358726..0000000000
--- a/docs/Help_Spanish/Topics/Ex-SWITCH_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- SWITCH Example
-
-
- SWITCH Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Typed-Enums.xml b/docs/Help_Spanish/Topics/Ex-Typed-Enums.xml
deleted file mode 100644
index be36ab579d..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Typed-Enums.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Typed Enums
-
- ENUM
- Typed Enums
-
-
-
- Typed Enums
-
- Enums may now be typed in X#. The type indicates the base class for the ENUM. By specifying a AS clause you can determine the size in bytes that the ENUM uses.
-
- ENUM Foo AS BYTE MEMBER One MEMBER Two ENDENUM
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Typed-Enums_MSHC.xml b/docs/Help_Spanish/Topics/Ex-Typed-Enums_MSHC.xml
deleted file mode 100644
index c8908cda3e..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Typed-Enums_MSHC.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- Typed Enums
-
- ENUM
- Typed Enums
-
-
-
- Typed Enums
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-USING.xml b/docs/Help_Spanish/Topics/Ex-USING.xml
deleted file mode 100644
index 40f1574e38..0000000000
--- a/docs/Help_Spanish/Topics/Ex-USING.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- USING Example
-
-
- USING Example
-
- // // XSharp allows you to not only use the using statement to link to namespaces // You can also link to a static class and call the methods in this class as if they are functions. // The functions WriteLine and ReadKey() in the following code are actually resolved as System.Console.WriteLine() // and System.Console.ReadKey() // Finally there is also the BEGIN USING .. END USING construct which controls the lifetime of a variable // At the end of the block the Variable will be automatically disposed. USING System USINGSTATIC System.Console
FUNCTION Start() ASVOID WriteLine("Before Using Block") WriteLine("------------------") BEGINUSINGVAR oTest := Test{} oTest:DoSomething() ENDUSING WriteLine("------------------") WriteLine("After Using Block") ReadKey()
CLASS Test IMPLEMENTS IDisposable CONSTRUCTOR() Console.WriteLine("Test:Constructor()")
ENDCLASS
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-USING_MSHC.xml b/docs/Help_Spanish/Topics/Ex-USING_MSHC.xml
deleted file mode 100644
index 5e768b3a27..0000000000
--- a/docs/Help_Spanish/Topics/Ex-USING_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- USING Example
-
-
- USING Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-VAR.xml b/docs/Help_Spanish/Topics/Ex-VAR.xml
deleted file mode 100644
index 2498667a75..0000000000
--- a/docs/Help_Spanish/Topics/Ex-VAR.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- VAR Example
-
-
- VAR Example
-
- // // The VAR keyword has been added to the language because in many situations // the result of an expression will be directly assigned to a local, and the expression // will already describe the type of the variable // VAR is a synonym for LOCAL IMPLIED using System.Collections.Generic
FUNCTION Start ASVOID // In the next line the compiler "knows" that today is a DateTime VAR today := System.DateTime.Now ? today
// In the next line the compiler "knows" that text is a String VAR text := Convert.ToString(123) ? text
// In the next line the compiler "knows" that s is a string FOREACHVAR s in GetList() ? s NEXT
Console.ReadLine()
RETURN
FUNCTION GetList AS List<String> VAR aList := List<String>{} aList:Add("abc") aList:Add("def") aList:Add("ghi") return aList
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-VAR_MSHC.xml b/docs/Help_Spanish/Topics/Ex-VAR_MSHC.xml
deleted file mode 100644
index 7d22972f99..0000000000
--- a/docs/Help_Spanish/Topics/Ex-VAR_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- VAR Example
-
-
- VAR Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-Vulcan-Runtime-Types-BYOR.xml b/docs/Help_Spanish/Topics/Ex-Vulcan-Runtime-Types-BYOR.xml
deleted file mode 100644
index 7c54577553..0000000000
--- a/docs/Help_Spanish/Topics/Ex-Vulcan-Runtime-Types-BYOR.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Vulcan Runtime(BYOR)
-
-
- Vulcan Runtime (BYOR)
-
- This "Bring Your Own Runtime" (BYOR) example shows how you can use Vulcan Datatypes and functions in X#.
The example does NOT come with the Vulcan Runtime DLLs. You need to have these installed on your machine and you may need to update the references in the example and point them to the Vulcan Runtime DLLs on your machine.
// Please read the comments in Readme.txt ! using System using System.Collections.Generic using System.Linq using System.Text
Function Start() asvoid
LOCAL startingColor AS ConsoleColor startingColor := Console.ForegroundColor
ConsoleHeading("Bring Your Own Runtime (BYOR) Sample",ConsoleColor.Magenta) Console.ForegroundColor := ConsoleColor.Gray
FUNCTION ConsoleHeading(s ASSTRING, c := ConsoleColor.Yellow AS ConsoleColor) ASVOID LOCAL originalColor AS ConsoleColor originalColor := Console.ForegroundColor
Console.ForegroundColor := c Console.WriteLine(s) Console.ForegroundColor := originalColor
FUNCTION Wait() ASVOID ConsoleHeading("Press any key to continue...",ConsoleColor.Green) Console.ReadKey()
FUNCTION DateSamples() ASVOID ConsoleHeading("Dates") LOCAL dToday := Today() ASDATE Console.WriteLine( i"Today is {dToday:d}" ) // Interpolated string, short Date Format Console.WriteLine( i"Today is {dToday:G}" ) // Interpolated string, General Date Format
LOCAL dTomorrow AS __VODATE dTomorrow := dToday + 1 // can perform VO date arithmetic Console.WriteLine( i"Tomorrow is {dTomorrow:D}") // Long date format
LOCAL dNewYear ASDATE dNewYear := 2016.01.01
Console.WriteLine("New year was " +AsString(dNewYear)+ " on a "+CDOW(dNewyear))
FUNCTION Conversion() ASVOID ConsoleHeading("Conversion") LOCAL sToday ASSTRING sToday := DTOS(Today()) // Convert date using VO function Console.WriteLine(i"Today is {sToday}") FUNCTION Strings() ASVOID ConsoleHeading("Strings") LOCAL s ASSTRING LOCAL sToday := DTOS(Today()) s := SubStr(sToday,1,4) // string manipulation Console.WriteLine(String.Format("SubStr is {0}",s))
LOCAL n ASDWORD n := At("0",s) Console.WriteLine(String.Format("At is {0}",n))
LOCAL c := "" ASSTRING Console.WriteLine(String.Format("c is {0}",IIF(Empty(c),"Empty","Not empty"))) c := "x" Console.WriteLine(String.Format("c is {0}",IIF(Empty(c),"Empty","Not empty"))) RETURN
FUNCTION Numeric() asVOID ConsoleHeading("Numeric") LOCAL r ASREAL8 r := Pow(2,3) Console.WriteLine(String.Format("Pow is {0}",r)) LOCAL f ASFLOAT f := Sqrt(10) Console.WriteLine(String.Format("The root of 10 is {0}",f)) RETURN
FUNCTION Arrays() ASVOID ConsoleHeading("Array") LOCAL a ASARRAY a := {1,2,3} Console.WriteLine(String.Format("Original Array length is {0}",ALen(a))) AAdd(a,4) AAdd(a,5) AAdd(a,6) Console.WriteLine(String.Format("Array length after adding 3 elements is {0}",ALen(a))) FORVAR i := 1 TO ALen(a) Console.Writeline(String.Format("{0} {1}", i, a[i])) NEXT ADel(a, 1) Asize(a, Alen(a) -1) Console.WriteLine(String.Format("Array length after deleting 1 elements is {0}",ALen(a))) RETURN
FUNCTION Symbols() ASVOID LOCAL s asSymbol LOCAL c asSTRING ConsoleHeading("Symbol") s := #LastName Console.WriteLine("Symbol s: "+s:ToString()) c := Symbol2String(s) Console.WriteLine("Symbol converted to string : "+c)
RETURN
FUNCTION LateBinding() ASVOID LOCAL e as Object ConsoleHeading("Late binding") e := Error{0, "Message"} Console.WriteLine("Reading property from a untype variable") Console.WriteLine( (String) e:Message)
RETURN
Function Workarea() ASVOID LOCAL cWorkDir asSTRING FIELD LASTNAME, FIRSTNAME in CUSTOMER ConsoleHeading("DBF Access") cWorkDir := "..\..\" SetPath(cWorkDir) DbUseArea(TRUE, "DBFNTX","Customer") DbSetIndex("CustNum.NTX") DbSetIndex("CustName.NTX") DbGoTop() DOWHILE ! EOF() ? Str(Recno(),3), LASTNAME, FIRSTNAME, _FIELD->CITY DbSkip(1) ENDDO DbCloseArea()
// The Yield return statement allows you to create code that returns a // collection of values without having to create the collection in memory first. // The compiler will create code that "remembers" where you were inside the // loop and returns to that spot. FUNCTION Start ASVOID FOREACH nYear ASINTIN GetAllLeapYears(1896, 2040) ? "Year", nYear, "is a leap year." NEXT Console.ReadLine() RETURN
FUNCTION GetAllLeapYears(nMin ASINT, nMax ASINT) AS IEnumerable<INT> FORLOCAL nYear := nMin ASINTUPTO nMax IF nYear % 4 == 0 .and. (nYear % 100 != 0 .or. nYear % 400 == 0) YIELDRETURN nYear ENDIF IF nYear == 2012 YIELDEXIT// Exit the loop ENDIF NEXT
-
-
diff --git a/docs/Help_Spanish/Topics/Ex-YIELD-_MSHC.xml b/docs/Help_Spanish/Topics/Ex-YIELD-_MSHC.xml
deleted file mode 100644
index 7764b215ba..0000000000
--- a/docs/Help_Spanish/Topics/Ex-YIELD-_MSHC.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- YIELD Example
-
-
- YIELD Example
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Example-1-The-VO-Explorer-Examp.xml b/docs/Help_Spanish/Topics/Example-1-The-VO-Explorer-Examp.xml
deleted file mode 100644
index fe49be205e..0000000000
--- a/docs/Help_Spanish/Topics/Example-1-The-VO-Explorer-Examp.xml
+++ /dev/null
@@ -1,499 +0,0 @@
-
-
-
- Example 1: The VO Explorer Example
-
-
- Example 1: The VO Explorer Example
-
- Please note: This example assumes that you have installed X# with the default installation options, and that the X# runtime is installed in the GAC.
- If you have not yet done this, the example won't run. Please see the chapter about runtime installation in the GAC in this documentation.
-
- The first example of XPorting VO apps is the VO Explorer example.
- Start the VO Xporter program and point it to the VO Explorer example:
-
-
-
- On my machine, the VO installation is in the C:\Cavo28SP3 folder. That may be different on your machine of course.
- I have not changed any of the xPort options. The options are:
-
-
-
- Option
-
-
- Description
-
-
-
-
- RemoveClassClause
-
-
- Remove the “Class Clause” for methods and accesses/assigns. This will group all methods inside a CLASS .. END CLASS block, eliminating the need to specify the CLASS clause at the method level.
-
-
-
-
- ChangeInitAxitToCtorDtor
-
-
- Init and Axit are reserved method names in VO. In DotNet, these names are often used by classes. Vulcan and X# have introduced new keywords CONSTRUCTOR and DESTRUCTOR. This option automatically renames the Init and Axit Methods. Example:
- METHOD Init(oOwner) CLASS MyClass
- becomes
- CONSTRUCTOR(oOwner)
-
-
-
-
- RemoveDeclareMethod
-
-
- If using strong typing in VO, it was necessary to add DECLARE METHOD statements and/or DECLARE ACCESS and DECLARE ASSIGN. The X# compiler still recognizes these statements but no longer requires them.
-
-
-
-
- RemoveExportLocalClause
-
-
- This option removes the EXPORT LOCAL clause that may be included in method declarations in VO code, but is ignored in X#.
-
-
-
-
- AllClassesArePartial
-
-
- Partial classes is a mechanism in Vulcan and X# that allows you to split a class over multiple source files. That may be convenient if your classes have become very big, or if you want to separate generated code from hand written code (like what the Windows Forms Editor in Visual Studio does). You can choose to make all Xporter classes partial. We have disabled this because there is a (small) performance penalty when you use this, especially if you have split the Accesses and Assigns from your class over separate files.
-
-
-
-
- AddMissingConstructors
-
-
- VO allows you to declare a class without Init method / Constructor. In .Net this is also allowed, but then the compiler assumes you have a class with a constructor without parameters. This option will automatically generate missing constructors. Note that also the X# compiler supports emitting missing constructors even if they are not specified in the code, when the /vo16 compatibility option is enabled. Therefore, this Xporter option is not necessary anymore and has been depreciated.
-
-
-
-
- IgnoreDuplicateDefines
-
-
- If you select this, duplicate defines will simply be ignored and not written to the output files.
-
-
-
-
- Don’tGenerateEmptyFiles
-
-
- Each module from your VO application will become a source file in X#. This option will suppress the generation of empty source files.
-
-
-
-
- AdjustCallbackFunctions
-
-
- Some (advanced) VO code contains callback functions where the address of a function is passed to another function and will get called. The Windows API uses that a lot, for example for enumerating windows or printers. That mechanism will not work in .Net. This option will change your code and will help you to get a working solution.
-
-
-
-
- ExportOnlyDefines
-
-
- This option allows you to generate a DLL with only the defines from the AEF(s) or files you have selected. That may be useful if you have ported your code before with the Vulcan Transporter and want to get rid of the header files with the defines.
-
-
-
-
- Sort Entities by name
-
-
- This will sort all entities on name, Methods will be sorted inside the CLASS.. ENDCLASS and functions will be sorted as well
-
-
-
-
- Use XSharp Runtime
-
-
- When you select this (the default), your app will be compiled against the X# runtime. Otherwise, we will use the Vulcan runtime (which is not included with our product)
-
-
-
-
- Copy Resources to Project folder
-
-
- When you select this option, all BMP, ICO, CUR, etc. resources that are used in resource entities in your app, will be copied to a Resources subfolder inside your project.
-
-
-
-
- Replace Resource Defines with Values
-
-
- This controls the way that the numeric identifiers associated with menu options and control identifiers on forms are exported to the external resource files
-
-
-
-
- Check For IVar and Property Conflicts
-
-
- In Visual Objects, it is allowed to have ACCESS/ASSIGN methods that have the same name with IVars (usually INSTANCE vars) of the same class. This is not allowed in .Net, so if this option is enabled, the Xporter will detect this and will prefix the IVar names with an underscore ("_").
-
-
-
-
- Ignore code inside #ifdef...#endif
-
-
- As a means of preparing Visual Objects code to be ported to X#, it is common practice to provide a VO version and an X# version of the same code in the VO version of the source code, surrounded by #ifdef __XSHARP__ ... #else ... #endif preprocessor directives. When this option is set, Xporter does not touch any code that is surrounded by those directives.
-
-
-
- The XPorter will allow you to select a destination folder and names for your Visual Studio solution and project files.
- After pressing xPort you will see the following folders:
- C:\XporterOutput\Examples\Explorer C:\XporterOutput\Examples\Explorer\Explorer
- C:\XporterOutput\Examples\Explorer\Explorer\Resources
- C:\XporterOutput\Examples\Explorer\Explorer\Properties
-
- The first folder is the so called “Solution” folder The subfolder contains the project and its files. If you had selected multiple AEF files then each AEF would have its own subfolder under the Solution Folder
- The solution folder contains the following files:
-
-
-
-
- File
-
-
- Contains
-
-
-
-
- Explorer.sln
-
-
- VS Solution file
-
-
-
-
- Explorer.viproj
-
-
- XIDE project file
-
-
-
-
- The project folder contains the following files:
-
-
-
- File
-
-
- Contains
-
-
-
-
- Customer Explorer.prg
-
-
- Module source code
-
-
-
-
- Data Servers.prg
-
-
- Module source code
-
-
-
-
- Explorer Shell.prg
-
-
- Module source code
-
-
-
-
- Explorer.viapp
-
-
- XIDE Application file
-
-
-
-
- Explorer.xsproj
-
-
- VS Project file
-
-
-
-
- Help About.HelpAboutDialog.rc
-
-
- Form resource used by VS
-
-
-
-
- Help About.HelpAboutDialog.xsfrm
-
-
- Form "binary" used by VS
-
-
-
-
- Help About.prg
-
-
- Module source code
-
-
-
-
- Help About.rc
-
-
- Form resource used by XIDE
-
-
-
-
- Icons.ICONONE.rc
-
-
- Icon resource used by VS
-
-
-
-
- Icons.ICONTWO.rc
-
-
- Icon resource used by VS
-
-
-
-
- Icons.prg
-
-
- Module source code
-
-
-
-
- Icons.rc
-
-
- Icon resources used by XIDE
-
-
-
-
- Menus.CustomerExplorerMenu.rc
-
-
- Menu resource used by VS
-
-
-
-
- Menus.CustomerExplorerMenu.xsmnu
-
-
- Menu "binary"
-
-
-
-
- Menus.CustomerExplorerMenu_Accelerator.rc
-
-
- Menu accelerators resource used by VS
-
-
-
-
- Menus.EMPTYSHELLMENU.rc
-
-
- Menu resource used by VS
-
-
-
-
- Menus.EMPTYSHELLMENU.xsmnu
-
-
- Menu binary
-
-
-
-
- Menus.EMPTYSHELLMENU_Accelerator.rc
-
-
- Menu accelerator resource used by VS
-
-
-
-
- Menus.OrdersListViewMenu.rc
-
-
- Menu resource used by VS
-
-
-
-
- Menus.prg
-
-
- Module source code
-
-
-
-
- Menus.rc
-
-
- Menu resources for XIDE
-
-
-
-
- Start.prg
-
-
- Module source code
-
-
-
-
- To compile and build the project, we open the file Explorer.SLN in Visual Studio. Inside Visual Studio it looks as follows:
-
-
- The arrows in front of several modules show that there are subitems in these modules. Those subitems contain the Form, Menu and Icon resources.
- Now, let’s try to build the solution inside Visual Studio (Menu option Build – Build Solution).
- This compiles the application and builds a debuggable version in the c:\XporterOutput\Explorer\Debug folder. You will see that this folder contains an EXE, PDB (debug symbols) and copies of the VO runtime libraries: Explorer.exe Explorer.pdb SDK_Defines.dll VOGUIClasses.dll VORDDClasses.dll VOSystemClasses.dll VOWin32APILibrary.dll
- XSharp.VO.dll
- XSharp.RT.dll
- XSharp.Core.dll
-
- Now, can try to run the app. This works, but as soon as we select the File/Open menu option we will get a runtime error. After some resizing, the screen looks similar to this
-
-
- The error message is clear: the app uses the splitwindow control, which requires the splitwindow support DLL.
- This DLL is located in the Redist folder of your VO installation. Copy the “Cato3spl.dll” file from your VO Redist folder to the output folder as well as the MSVCRT.DLL, and try again. You can also add the DLLs to your project (Add Existing Item, and point to the DLLs in the Redist folder). This will copy them to the project folder. Then set the build action for the 2 DLLs to None and the “Copy to Output Directory” property to “Preserve Newest”. When you now build your app, the DLL will be copied to the right folder.
- After that, the code will run just like it did in VO with no code changes!
-
- Let’s have a closer look at what the XPorter has done:
-
-
Each module in VO has become a PRG file in the X# project.
-
-
-
Source code has been grouped by class and put in a CLASS .. END CLASS construct.
-
-
-
Init methods have been renamed to CONSTRUCTOR.
-
Compiler macros such as "%CavoSamplesRootDir%\Explorer\" have been replaced with literal values: "C:\cavo28SP3\Samples\Explorer\".
-
-
-
Resources have become “children” of the source file where they were defined.
-
Locations for resources have also been changed. %CavoSamplesRootDir%\Explorer\TWO.ICO has been changed to ICONTWO Icon C:\cavo28SP3\Samples\Explorer\TWO.ICO. Also, the RESOURCE keyword has been removed.
-
The binaries for the forms and menus have not been included in this version of the XPorter (Beta 11). That will change.
-
-
-
The Start file has the biggest change. In VO, there was a method in there App:Start(). However, the App class is not defined in this application, but part of the GUI Classes. There was also no Start function in the App. VO would call the Start function in the GUI classes and would merge the App:Start() method in the application with the rest of the App class in the GUI Classes. This is not allowed in .Net. Classes cannot be spread over more than one assembly (the .Net name for of a Library, EXE or DLL). Therefore, the XPorter has created a new class (xApp) and moved the Start method to this Xapp class. It has also added a Start() function which instantiates the App class and calls the Start method inside XApp. You can also see in the example below that a TRY .. CATCH .. END TRY construct is added, which captures the errors that are not catched anywhere else and shows an error message in an ErrorBox object. This is the errorbox that was shown before because the CATO3SPL.DLL was missing.
-
Finally, the Start function is marked with an attribute (The word between the square brackets). In this case the attribute is [STAThread] which means that the main function (and therefore the whole app) needs to run in Single Threaded Appartment mode. This is important if your app uses external code such as OCX/ActiveX controls.
-
-
-
-
-
-
If you look closer to the solution explorer in Visual Studio and click on the References node in the tree, you will see that the example has references to the Vulcan runtime and the VO Class libraries, as well as the SDK defines library that was included with the XPorter.
-
-
-
If you open the project properties, you will see on the General page that the selected dialect is “Visual Object”. On the Dialect page, most VO options are set, and on the Build page the platform target is x86 (because the GUI classes are designed to run in x86 mode), and several warnings have been suppressed. These warnings are:
-
-
-
-
- Number
-
-
- Meaning
-
-
-
-
- 162
-
-
- Suppresses a warning about Unreachable code
-
-
-
-
- 618
-
-
- Suppresses a warning about the use of obsolete functions, such as CollectForced
-
-
-
-
- 649
-
-
- Suppresses a warning about unused private and/or internal fields.
-
-
-
-
- 9025
-
-
- Suppresses a warning about missing return statements
-
-
-
-
- 9032
-
-
- Suppresses a warning about return values inside ASSIGN methods and/or constructors/destructors
-
-
-
-
- 9043
-
-
- Suppresses a warning about ambiguous code, which could happen if two assemblies define a function with the same name.
-
-
-
- In this particular example, only warning 618 is generated by the compiler, because the CustomerExplorer:Close() method calls CollectForced. After commenting out that line, you can remove all “suppressed” warnings from the app, and it will compile without any warnings.
- You will find the "code before" and "code after" in the XSharp Examples folder
-
-
diff --git a/docs/Help_Spanish/Topics/Example-2-The-VOPAD-Example.xml b/docs/Help_Spanish/Topics/Example-2-The-VOPAD-Example.xml
deleted file mode 100644
index 81f6d1733e..0000000000
--- a/docs/Help_Spanish/Topics/Example-2-The-VOPAD-Example.xml
+++ /dev/null
@@ -1,315 +0,0 @@
-
-
-
- Example 2: The VOPAD Example
-
-
- Example 2: The VOPAD Example
-
- This example converts the VOPAD AEF file from the C:\cavo28SP3\Samples\Controls\Richedit folder.
- After converting it with the same options as the first example we will have a folder structure like
- C:\XporterOutput\Examples\VoPad C:\XporterOutput\Examples\VoPad\VoPad
-
-
-
-
- File
-
-
- Contains
-
-
-
-
- VoPad.sln
-
-
- VS Solution file
-
-
-
-
- VoPad.viproj
-
-
- XIDE project file
-
-
-
-
- The project folder contains the following files:
-
- Open the project in VS and compile. You will see the following errors/warnings:
-
- PadWin.prg(473,1): warning XS1030: #warning: 'The following method did not include a CLASS declaration'
- PadWin.prg(480,1): warning XS1030: #warning: 'The following method did not include a CLASS declaration'
- PadHelp About.prg(78,3): error XS9046: Cannot assign to 'font' because it is a 'method'
- PadHelp About.prg(81,8): error XS0119: 'TextControl.Font(params __Usual[])' is a method, which is not valid in the given context
- PadHelp About.prg(88,3): error XS9046: Cannot assign to 'font' because it is a 'method'
- PadHelp About.prg(91,8): error XS0119: 'TextControl.Font(params __Usual[])' is a method, which is not valid in the given context
- PadWin.prg(166,19): error XS1061: 'RichEdit' does not contain a definition for 'RTFChangeFont' and no extension method 'RTFChangeFont' accepting a first argument of type 'RichEdit' could be found (are you missing a using directive or an assembly reference?)
-
- Let's examine this by double clicking on the errors/warnings.
-
- First, the warnings. These are generated by a #warning preprocessor statement inserted by XPorter, because it found problems in your code:
-
-
There was an ACCESS FilterIndex CLASS SaveAsDialog in the source. This adds an access to a class in the GUI Classes. This is not allowed in .Net. The XPorter has created a special subclass of SaveAsDialog to hold this extra property. Fortunately, this ACCESS is no longer needed, because it has been added to the GUI Classes already. Therefore, we can completely delete that code.
-
There was a method RTFChangeFont CLASS RichEdit. This has the same problem as the SaveAsDialog:FilterIndex. In this case, the method is necessary. It has been moved to a subclass of RichEdit already. However, since the original code still points to the RichEdit class, there could be a runtime problem, because this method is not part of the richedit class. There are two possible solutions here:
-
-
-
-
Change the method to an extension method.
-
Change the code that uses the RichEdit class to use the changed class.
-
-
- Option 1 is preferable in this case, since we are not using any private or protected properties of the RichEdit class. To achieve that, change the code from
- CLASS RichEdit_external_class INHERIT RichEdit METHOD RTFChangeFont() etc
- to
- STATICCLASS RichEditExtensions STATICMETHOD RTFChangeFont( SELF oEdit as RichEdit) ASVOID LOCAL oFontDlg AS StandardFontDialog oFontDlg := StandardFontDialog{oEdit:Owner} oFontDlg:FontColor := oEdit:TextColor oFontDlg:Font := oEdit:ControlFont oFontDlg:Show() oEdit:TextColor := oFontDlg:FontColor oEdit:ControlFont := oFontDlg:Font ENDCLASS
- Note
- The Extension Method works great to enhance existing classes, but has one disadvantage: The Vulcan Runtime will not pick up these extension methods for late bound code.That is not a problem in this example, but may be a problem elsewhere.
-
- Now we have added an extension method that can be used like a normal method.
- This change also solves the error in PadWin.prg
- Then, look at the other problems: they all have to do with a Font property in the TextControl class. Unfortunately, the VO class libraries have both a Font() method and a Font() Access/Assign for the TextControl class. Having a method and a property with the same name is not allowed in .Net.
- When the VO Gui classes were ported to Vulcan, the decision was made to rename the Font property to Controlfont. Therefore, we need to make that change. Simply double click on the errors and change
- :Font
- to
- :ControlFont
- (4 times)
- After that, the code should compile and run. Clicking the Font button on the toolbar should show the font dialog (from the RTFChangeFont extension method).
-
- Some of the changes that were made to the code (omitting the ones that were also in example 1):
-
-
Manifest.prg is empty but included, because it had a dependent resource.
-
-
-
- You will find the "code before" and "code after" in the XSharp Examples folder
-
-
diff --git a/docs/Help_Spanish/Topics/Example-3-The-Pizza-Example.xml b/docs/Help_Spanish/Topics/Example-3-The-Pizza-Example.xml
deleted file mode 100644
index d9aee9bb67..0000000000
--- a/docs/Help_Spanish/Topics/Example-3-The-Pizza-Example.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-
-
-
- Example 3: The Pizza Example
-
-
- Example 3: The Pizza Example
-
- Our third migration example is the Pizza Example. You can find this in the Samples\Controls\Buttons folder in your VO Installation. I have selected the same output folder (C:\XporterOutput\Examples\) and the XPorter will create a Pizza subfolder with the contents of the AEF and a Pizza solution in the Examples folder.
- There is no real need to list the files again, as the concept is already clear.
- After opening Pizza.sln inside Visual Studio and compiling it, you will find the following problems:
-
-
-
- The problem is:
-
-
The original VO program had an output name 'PIZZA.EXE'.
-
The X# compiler uses the same logic as the Vulcan compiler and creates a static class called Pizza.Exe.Functions, holding the functions in the application, the globals and (new for X#) the defines.
-
The application also has an image, called 'PIZZA'.
-
When we compile this app, a conflict occurs between the class named PIZZA and the namespace Pizza (from the class Pizza.Exe.Functions).
-
This is something that is not recommended by the DotNet standard. Vulcan ignores this and allows both a class Pizza and a namespace Pizza. X# follows the .Net guidelines more closely.
-
There are 2 solutions to this problem:
-
-
Rename the image class Pizza (inside Images.prg);
-
Rename the output filename. To rename the output filename, open the Project Settings (from the Project menu) and set the Assembly Name on the "General" page. You could rename the assembly to PizzaApp and it will solve the problem.
-
-
-
-
In this case, I choose to rename the PIZZA image. Therefore, open Images.PRG and rename
-
- CLASS PIZZA INHERIT Bitmap
- to
- CLASS ImgPIZZA INHERIT Bitmap
-
-
Next, recompile again. This leaves just one remaining issue:
-
- C:\XporterOutput\Examples\Pizza\Order Dialog.prg(165,25): error XS0246: The type or namespace name 'PIZZA' could not be found (are you missing a using directive or an assembly reference?)
-
-
-
This is the place where the Pizza image is used in the example app. To change this, open the Order Dialog window (Order Dialog.ORDERDIALOG.xsfrm). Select the button on the bottom left and update the "Image" text in the property window from Pizza to ImgPizza. Save the form, and the code will be automatically regenerated.
-
After making these changes, if you check at the order dialog rc file, you will notice that the file has been marked with a header indicating that the code was auto-generated. Additionally, #defines have been added for all windows styles used in the form. This makes the resource "self contained", meaning it no longer has dependencies on any external files within the resource file.
-
Recompile and the program compiles.
-
When we run the program, we see that it works as expected:
-
-
-
- You will find the "code before" and "code after" in the XSharp Examples folder
-
-
diff --git a/docs/Help_Spanish/Topics/Example-4-Ole-Automation.xml b/docs/Help_Spanish/Topics/Example-4-Ole-Automation.xml
deleted file mode 100644
index dddf8071e2..0000000000
--- a/docs/Help_Spanish/Topics/Example-4-Ole-Automation.xml
+++ /dev/null
@@ -1,100 +0,0 @@
-
-
-
- Example 4: Ole Automation - Excel
-
-
- Example 4: Ole Automation - Excel
-
- For the fourth example, instead of using a standard example from Visual Objects, we will create a new sample application in VO to remote control Excel and write data to an Excel Sheet.
- I adapted a script found in the Comp.Lang.Clipper.Visual-Objects newsgroup to fit our example.
-
-
Start by creating a new terminal application in Visual Objects, then copy and paste the code below into the application.
-
Open the application Properties and add the Ole Library.
-
Rename the app to "ExcelTest".
-
Now, open the start module and copy the code.
-
Compile and run, and you will find an xls file in the C:\ExcelTest folder.
-
-
- FUNCTION Start() LOCAL oExcel AS OBJECT LOCAL oWorkBooks AS OBJECT LOCAL oWorksheet AS OBJECT LOCAL oRange AS OBJECT LOCAL cFile ASSTRING cFile := "C:\ExcelTest\example.xls" DirMake("C:\ExcelTest") oExcel:=OLEAutoObject{"Excel.Application"} oExcel:Visible:=FALSE // Don't show the EXCEL execute oExcel:DisplayAlerts:=FALSE // Don't show messages oWorkBooks:=oExcel:Workbooks oWorkBooks:add() //open a new worksheet oWorkSheet:=oExcel:ActiveSheet // active the first sheet oRange:=oWorkSheet:[Range,"A1","A1"] // A1 cell oRange:SELECT() oRange:FormulaR1C1:="Hello my text" oExcel:ActiveWorkBook:SaveAs(cFile,56,"","",; FALSE,FALSE) //"56" save the file in work book of EXCEL 97-2003 (Excel 8)
oWorkBooks:Close() oExcel:Quit() WAIT
RETURN NIL
-
-
-
Export the AEF to "C:\ExcelTest\ExcelTest.AEF"
-
Run the VOExporter and export the code.
-
After opening the solution inside Visual Studio, you will also get an application with a single source file (Start.prg). The source is almost identical except for one difference. The line :
-
- oRange:=oWorkSheet:[Range,"A1","A1"] // A1 cell
-
- has been changed to
- oRange:=oWorkSheet:Range["A1","A1"] // A1 cell
-
-
-
Note that the name Range is now in front of the Square brackets. Range is a so-called "Indexed property" of the worksheet. Visual Objects uses a "funny" syntax for this. X# uses the same syntax that most other languages do. The property looks like an array (the square brackets) .
-
-
-
Now, compile the app in X#. You will get the following errors:
-
-
- Let's look at these errors:
-
-
The last errors in the list indicate that the Start method is incorrect. This is because the Start function in .Net has to either be a VOID function or a function that returns an INT. In this case, no return type has been declared, making X# think that you want to create a function that returns a USUAL. Change the prototype of the start function to:
-
- FUNCTION Start() ASVOID
- and remove the NIL return value from the RETURN statement.
-
-
Now, two errors remain. These indicate that X# does not know how to convert the array index from string to int. This is in line with the range assignment. The code above uses 'Late Binding', so the types are not known at compile time. X# does not know whether the Range property from the Worksheet object is an indexed property or returns an array. It assumes that it returns an array and wants to specify the array index which is numeric (and subtract one because Visual Objects uses 1 based arrays where .Net uses 0 based arrays).
-
The best way to fix this is to use strong typing and use the Generated Class wrappers for Excel. In Visual Objects you would use the 'Automation Server' tool to generate such a class wrapper. In .Net there is a similar tool. The easiest way to achieve this is to add a reference to Excel to the references of the application:
-
Right Click on "References" in the solution Explorer and Choose "Add Reference"
-
In the 'Add Reference' dialog, choose the COM tabpage
-
Locate the "Microsoft Excel nn.m Object Library". On my machine, that is Excel 16.0.
-
-
-
-
Click Ok.
-
This will add an entry to your References list with the name "Microsoft.Office.Interop.Excel". This is a generated type library that contains class definitions for all types inside Excel.
-
Now go into your code, add a Using statement for the namespace of the Excel classes, and change "AS OBJECT" to the right types:
-
- USING Microsoft.Office.Interop.Excel FUNCTION Start() ASVOID LOCAL oExcel AS Application LOCAL oWorkBooks AS Workbooks LOCAL oWorksheet AS Worksheet LOCAL oRange AS Range
-
-
-
Also, change the call to create the Main Excel object:
-
- oExcel:=ApplicationClass{}
-
-
Your code is now strongly typed, so you should also get intellisense if you try to select a member from one of these objects, such as oExcel:Workbooks.
-
-
-
Compile and run the code. It works as expected.
-
You may want to change the value 56 in the SaveAs line to the appropriate enum value: xlFileFormat.xlExcel8
-
Now run the app again and everything works as expected.
-
If you look in the folder where the EXE is generated you will see both ExcelTest.Exe and Microsoft.Office.Interop.Excel.dll, the type library.
-
- Note 1
- If you are wondering why we declare oExcel as Application but use ApplicationClass to instantiate the object, here is the reason:
- Application is the interface, ApplicationClass is the actual class that implements the Application interface. This is a model that you will see for most Automation Servers.
- Note 2
- Many people have asked for a way to implement OLE Events. With the X# code and the generated type library this is very easy.
- Add the following code to the start method to define a BeforeSave and AfterSave event:
- oExcel:WorkbookBeforeSave += OnBeforeSave oExcel:WorkbookAfterSave += OnAfterSave
-
- Then, add the following functions:
- FUNCTION OnBeforeSave (oWb AS Workbook, SaveAsUI AS LOGIC, Cancel REF Logic) ASVOID ? "OnBeforeSave", oWb:Path, oWb:Name, SaveAsUI RETURN
FUNCTION OnAfterSave (oWb AS Workbook, Success AS LOGIC) ASVOID ? "OnAfterSave", oWb:Path, oWb:Name, Success RETURN
- If you then run the example again, you will see that both functions are called. Before the save, the path and name are not set properly, while afterwards, they are set to the values specified in the code Some versions of Excel do not support the WorkbookAfterSave event. In that case you will get a compile time error
-
- Note: If you run this code through the debugger and set a break point in the OnBeforeSaveAs, you will see that the callstack in these events is a little bit weird: there is no Start() function inside this callstack (I have disabled the 'Just My code option', otherwise you would only see the line with OnBeforeSave())
-
-
-
- The reason is that these events are called on a separate threat. If you look at the Threads window in VS (Debug - Windows - Threads) you will see that:
-
-
- Note 3
- If you look closely in the Add References dialog, you may also find other occurrences of the Excel library (on the .Net tab). On my machine these are:
-
-
-
- These are so called "Primary Interop Assemblies" (PIAs), pre-compiled assemblies, for different Excel versions. You can use these as well. These assemblies are installed with the Office Developers Tools for Visual Studio. On my machine, they are located in subfolders of "c:\Program Files (x86)\Microsoft Visual Studio 14.0\Visual Studio Tools for Office\PIA" .
-
- You will find the "code before" and "code after" in the XSharp Examples folder.
-
-
diff --git a/docs/Help_Spanish/Topics/Example-4-The-Email-Client-Exa.xml b/docs/Help_Spanish/Topics/Example-4-The-Email-Client-Exa.xml
deleted file mode 100644
index 1bcc6a2bc5..0000000000
--- a/docs/Help_Spanish/Topics/Example-4-The-Email-Client-Exa.xml
+++ /dev/null
@@ -1,141 +0,0 @@
-
-
-
- Example 5: OCX - The Email Client Example
-
-
- Example 5: OCX - The Email Client Example
-
- This example shows how to migrate an application that uses an ActiveX/OCX Control. We are using the Email example from Visual Objects that you can find in the Examples folder, subfolder Email.
- The problem that we can expect here is that the X# Runtime (and also Vulcan rumtime) does not support ActiveX controls.
- So let's try to solve this.
-
-
-
First, run VOXporter and create a Visual Studio solution from the AEF.
-
Compile and run in Visual Studio.
-
We will get 2 messages:
-
-
- The first message shows the biggest problem in this example. The second message was inserted by the Xporter to warn us that the original code was adding a method to a class that exists inside the VO Gui classes.
-
- Let's fix these problems quickly so that we can compile the app. We will add the OCX later:
-
-
Click on the warning. You will see that the XPorter has added a CLASS ToolBar_external_classthat inherits from Toolbar. The original code was trying to add the ShowButtonmenu method to the existing Toolbar class.
-
We can solve this problem, which we have also seen in the VOPAD example, by either adding an Extension Method, or by sub-classing the Toolbar class.
-
Just like in the VOPAD example, I prefer the extension method.
-
Change the class name and method declaration. We will create two overloads, because the symTb parameter is optional:
-
- STATICCLASS ToolBarExtensions STATICMETHOD ShowButtonMenu(SELF tbSelf as Toolbar, nButtonID as LONG, oButtonMenu as Menu) ASVOID tbSelf:ShowButtonMenu(nButtonID, oButtonMenu, #MAINTOOLBAR) RETURN STATICMETHOD ShowButtonMenu(SELF tbSelf as Toolbar, nButtonID as LONG, oButtonMenu as Menu,symTb as Symbol) ASVOID
-
-
Remove the Default() line and replace SELF in the body of the original ShowButtonMenu with tbSelf.
-
We will also have to make some changes to the code calling this method. This is due to the fact that the code calls ShowButtonMenu on the Toolbar access from the window class. This Toolbar access is untyped and therefore returns a USUAL.. To do this, locate the two lines with SELF:ToolBar:ShowButtonMenuand change that to ((Toolbar) SELF:ToolBar):ShowButtonMenu. You cannot use the oToolbar field of the Window class, because the DataWindow class will return the Toolbar from its framewindow in stead of its own toolbar. In the improved VO SDK that we will include with our X# runtime, we will solve this problem by strongly typing properties such as Window:Toolbar. You may be tempted to add the Extension methods to the USUAL type, to avoid having to add the casts to the code that calls ShowButtonMenu. Although that will compile, it will unfortunately produce a problem at runtime. The X# compiler (like the Vulcan and VO Compilers) knows that the USUAL type is special and will not try to emit a method call, but will produce code that calls Send() on the usual to call its method. And the Vulcan Runtime does not handle extension methods inside the Send() function.
-
We can confirm that this works later when we press the "Reply" button on the toolbar. That should bring up the menu with "Reply to Sender" and "Reply to All".
-
-
- Now, it is time to fix the ActiveX/OCX problem
-
-
Click on the error about OleControl.
-
As a quick workaround, we will change the code and let webbrowser inherit from MultiLineEdit. This gives us a control that will certainly work. We will implement the OCX later. To do so, go to the Class Webbrowser.PRG and change the INHERIT clause. It says INHERIT OleControl now. Change that to INHERIT MultiLineEdit.
-
Compile again and now some other errors will be shown. Two of these mention the type cOleMethod. Go to this code by double clicking the error.
-
You will see the Quit method of the Webbrowser class. This code uses an internal class and internal methods from the VO OLE Classes. Comment out the contents of this method for now.
-
Compile again, and you will see that only a few errors are left. Some of these are the same as the error in the VOPAD Example and require that we change the Font property to ControlFont. Correct that.
-
One error points to an incorrect '+' operator: in the line
-
- cTemp += +"; "+ cEntry
-
-
This is an obvious error in the original VO code that was never picked up by the VO Compiler. Remove the + before the double quote.
-
The last error comes from the constructor of the Webbrowser class. It is calling the CreateEmbedding method from the OleControl. This method does not exist in the MultiLineEdit class, so we comment it out for now. We will deal with the Webbrowser later.
-
The rest of the code should compile without problems, after commenting out the call to SELF:CreateEmbedding().
-
You should be able to run the application now.
-
There will be a runtime error if you try to open the Address Book, because it uses the Databrowser control which depends on Cato3Cnt.dll. Fix this by copying the cato3*.dll and msvcrt.dll from the Cavo28\Redist folder to your output folder.
-
Recompile and run the example. It will now produce an error inside the Display method of the Webbrowser class (DisplayHtml if you have used the Email example from VO 2.8 SP4). This method takes the content of the email, writes it to disk and calls the Navigate method of the Webbrowser control (late bound, using the Send() function of VO). This will not work. Since we have changed the webbrowser control and made it a multi-line edit, we can change this behavior. Instead of writing the email text to disk, we can simply assign it to the TextValue property of the MultiLineEdit. In order to do this, comment out the body of the Display method (do not throw the code away as we will need it later), and replace it with:
-
- SELF:TextValue := cText
-
-
After that, the sample should run without problems. You can also display the emails. Of course it will not show HTML properly but that is the next step.
-
- How to add the ActiveX to the code
- The VO compatible GUI classes inside Vulcan do not support ActiveX Controls. However, Windows Forms has great support for ActiveX Controls.
- We will use the ActiveX support from Windows Forms to add the ActiveX control to the example.
- There are two possibilities here:
-
-
Replace the entire Email Display window with a Windows Forms window;
-
Use a trick to use Windows Forms to show the ActiveX control and merge that control into our VO GUI app.
-
- The first solution is much easier to understand, but requires creating a whole new window and changing the calling code as well.
- It is up to you to make the choice for your own apps.
- In this example, we will the choose the second approach.
- Create a Windows Forms Window to display the email
- For this method, we use a Windows.Forms.Form window as "Host" for the ActiveX control. We will instantiate that window, grab the windows handle to the control, and link that windows handle with our VO GUI window.
- To do this, you must take the following steps:
-
-
Right Click on the project icon in the solution explorer and select "Add New Item"
-
This brings up a list of possible new items. Choose the icon for Windows Forms Form, give it a meaningful name (such as "EmailDisplayForm.prg"), and click Add.
-
This will open the Form Designer window.
-
Open the ToolBox. The webbrowser control will not be in there.
-
Right click on an empty area in the toolbox and select "Choose Items...". This will bring up a dialog where you can control the contents of the ToolBox.
-
Select the "COM Components" Tab and scroll down until you see the Microsoft Web Browser control:
-
Tick the checkbox in front of the control and press Ok. This should add the ActiveX to the toolbox:
-
-
-
-
You can drag the control to a different place in the Toolbox if you are not happy with where it landed.
-
Now, drag the Control from the ToolBox to the form. There is no need to size or move the control.
-
Visual Studio will add two references to our project. These are:
-
-
AxSHDocVw, a type library that contains that code for the actual ActiveX control;
-
SHDocVw, a type library that contains code for the supporting automation server interfaces and classes.
-
-
-
-
The form editor will add a field named axWebBrowser1 to the form. This field is of the type AxSHDocVw.AxWebBrowser.
-
Go to the property window and change the Modifiers Field to change it from Private to it Public (Export). That will make the field accessible outside of the webBrowserHost class.
-
-
-
Save the code, and close the form.
-
Now go to the Webbrowser class.
-
Add the following using clauses to the top of the file:
-
- using Email using AxShDocVw using ShDocVw
-
- The first using is the namespace where the webBrowserHost window is generated, the second is the namespace of the generated ActiveX and the third is that of the other types that we need, such as enums and events.
-
-
Add the following two fields (no need to elaborate I think):
-
- EXPORT oHost as webBrowserHost EXPORT oWebBrowser as AxWebBrowser
-
-
Go to the constructor of the Webbrowser class and add the following lines of code (in stead of the CreateEmbedding() that we commented out before)
-
- SELF:oHost := webBrowserHost{} // Create the host window, do not show ! SELF:oWebBrowser := SELF:oHost:axWebBrowser1 // Get the ActiveX on the form SetParent(oWebBrowser:Handle, self:Handle()) // Using Windows API "steal" its handle and link to the MLE SELF:oWebBrowser:Visible := TRUE // make the webbrowser visible SELF:Okay := TRUE
-
-
Then, add the following methods to make sure that the ActiveX has the same width and height as the MultiLineEdit that is its owner, and to make sure it is properly destroyed:
-
- METHOD Resize(oEvent) LOCAL oDim as Dimension SUPER:Resize(oEvent) oDim := SELF:Size IF oDim:Width > 0 SELF:oWebBrowser:SuspendLayout() SELF:oWebBrowser:Location := System.Drawing.Point{0,0} SELF:oWebBrowser:Size := System.Drawing.Size{oDim:Width,oDim:Height} SELF:oWebBrowser:ResumeLayout() ENDIF RETURN NIL
We also need to "restore" the old behavior to display the HTML in the browser window, that we commented out before. To do this, go to the WebBrowser:Display() method (DisplayHtml for VO 2.8 SP4) and restore the old code and change
-
- Send(SELF, #Navigate, cFileName)
- into
- SELF:oWebBrowser:Navigate(cFileName)
- so you change this into an early bound method call.
-
-
To finish our work, browse through the source of the webbrowser class and find lines that call Navigate, such as
-
- Send( SELF, #Navigate, "#top" )
- and change these to early bound method calls:
- SELF:oWebBrowser:Navigate("#top" )
- Also, look for lines like:
- Send( SELF, #ExecWB, OLECMDID_PRINT, OLECMDEXECOPT_DODEFAULT, NIL, NIL )
- and change these to early bound method calls using enums in the type library. Additionally, remove the NIL values:
- SELF:oWebBrowser:ExecWB(OLECMDID.OLECMDID_PRINT, OLECMDEXECOPT.OLECMDEXECOPT_DODEFAULT )
-
-
That wraps it up. Everything works now, including the PrintPreview and Print functionality.
-
Of course, you can now also use the activeX events and respond to them. You have to do that the .Net way. Something like this:
-
- SELF:oWebBrowser:NavigateComplete2 += NavigateComplete2
-
- and then the implementation
- METHOD NavigateComplete2(sender AS OBJECT, e AS DWebBrowserEvents2_NavigateComplete2Event) ASVOID SELF:Owner:StatusBar:SetText("Showing file:" +e:uRL:ToString())
- You will find the "code before" and "code after" in the XSharp Examples folder.
-
-
diff --git a/docs/Help_Spanish/Topics/Exceptions-and-Exception-Handl.xml b/docs/Help_Spanish/Topics/Exceptions-and-Exception-Handl.xml
deleted file mode 100644
index f45df38331..0000000000
--- a/docs/Help_Spanish/Topics/Exceptions-and-Exception-Handl.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Exceptions and Exception Handling
-
-
- Exceptions and Exception Handling
-
- In X#, errors in the program at run time are propagated through the program through a mechanism called exceptions. Exceptions are thrown by code that encounters an error and caught by code that can correct the error. Exceptions can be thrown by the .NET Framework common language runtime (CLR) or by code in a program. Once an exception is thrown, it propagates up the call stack until a catch statement for the exception is found. Uncaught exceptions are handled by a generic exception handler provided by the system that displays a dialog box.
-
- Exceptions are represented by classes derived from Exception. This class identifies the type of exception and contains properties that have details about the exception. Throwing an exception involves creating an instance of an exception-derived class, optionally configuring properties of the exception, and then throwing the object by using the throw keyword. For example:
- CLASS CustomException INHERIT Exception
CONSTRUCTOR(message ASSTRING) SUPER(message)
ENDCLASS
FUNCTION TestThrow asVOID LOCAL ex AS CustomException ex := CustomException{"Custom exception in TestThrow()} THROW ex RETURN
- After an exception is thrown, the runtime checks the current statement to see whether it is within a try block. If it is, any catch blocks associated with the try block are checked to see whether they can catch the exception. Catch blocks typically specify exception types; if the type of the catch block is the same type as the exception, or a base class of the exception, the catch block can handle the method. For example:
- FUNCTION TestCatch asVOID
TRY TestThrow() CATCH ex AS CustomException System.Console.WriteLine(ex.ToString()) ENDTRY RETURN
- If the statement that throws an exception is not within a try block or if the try block that encloses it has no matching catch block, the runtime checks the calling method for a try statement and catch blocks. The runtime continues up the calling stack, searching for a compatible catch block. After the catch block is found and executed, control is passed to the next statement after that catch block.
-
- A try statement can contain multiple catch blocks. The first catch statement that can handle the exception is executed; any following catch statements, even if they are compatible, are ignored. Therefore, catch blocks should always be ordered from most specific (or most-derived) to least specific.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Expressions.xml b/docs/Help_Spanish/Topics/Expressions.xml
deleted file mode 100644
index af54aa5b96..0000000000
--- a/docs/Help_Spanish/Topics/Expressions.xml
+++ /dev/null
@@ -1,243 +0,0 @@
-
-
-
- Expressions
-
-
- Expressions
-
- Expressions are an important element of the language. There are many types of expressions. The expression rule in the compiler is the biggest rule
- The table below lists the various expression types in the order they are recognized by the compiler. Some expression types are covered in a separate topic.
- As you can see, most expression types are recursive. They contain one or more references to sub-expressions
- Expressions
-
-
-
- Expression type
-
-
- Syntax
-
-
-
-
- Member Access
-
-
- expression? (.|:) identifier
-
-
-
-
- Member Access with Ampersand (resolved at runtime)
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/FLOAT.xml b/docs/Help_Spanish/Topics/FLOAT.xml
deleted file mode 100644
index 23ed81f661..0000000000
--- a/docs/Help_Spanish/Topics/FLOAT.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- FLOAT
-
- FLOAT
-
-
-
- FLOAT
-
- The FLOAT type is a type that stores a 64-bit floating point value, along with formatting information. The precision and range of a FLOAT are the same as that from a REAL8, since the value of the float is stored in a REAL8.
- Implementation
- The FLOAT type is implemented in the structure XSharp.__Float.
- The Usual type of FLOAT is 3.
-
-
diff --git a/docs/Help_Spanish/Topics/File-System-and-the-Registry.xml b/docs/Help_Spanish/Topics/File-System-and-the-Registry.xml
deleted file mode 100644
index 6ac123a0fe..0000000000
--- a/docs/Help_Spanish/Topics/File-System-and-the-Registry.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- File System and the Registry
-
-
- File System and the Registry
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Float-Type.xml b/docs/Help_Spanish/Topics/Float-Type.xml
deleted file mode 100644
index 8e5edc769e..0000000000
--- a/docs/Help_Spanish/Topics/Float-Type.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Float Type
-
- FLOAT
- XSharp.__Float
-
-
-
- Float Type
-
- This structure is a combination of a REAL8 (System.Double) and a width and # of decimals.
- It is not a reference type like in VO.
- The internal type name for this type is XSharp.__Float
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Forms.xml b/docs/Help_Spanish/Topics/Forms.xml
deleted file mode 100644
index 15a1344fc6..0000000000
--- a/docs/Help_Spanish/Topics/Forms.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Forms
-
-
- Forms
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Generics.xml b/docs/Help_Spanish/Topics/Generics.xml
deleted file mode 100644
index 6f91f38bb7..0000000000
--- a/docs/Help_Spanish/Topics/Generics.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Generics
-
-
- Generics
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Highlight-words.xml b/docs/Help_Spanish/Topics/Highlight-words.xml
deleted file mode 100644
index 3df31db8d6..0000000000
--- a/docs/Help_Spanish/Topics/Highlight-words.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Highlight Identifiers
-
- Highlight words
-
-
-
- Highlight Identifiers
-
- When you select a specific word, it shows you all occurrences of that word, this is case sensitive.
-
-
-
- The color for the highlights can be set in the Tools/Options dialog under the Environment/Fonts and Colors node. The X# specific colors all start with the text "X#"
-
-
diff --git a/docs/Help_Spanish/Topics/INT.xml b/docs/Help_Spanish/Topics/INT.xml
deleted file mode 100644
index 48c5acad6c..0000000000
--- a/docs/Help_Spanish/Topics/INT.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- INT
-
- INT
- LONG
- LONGINT
-
-
-
- INT / LONG / LONGINT
-
- The INT or LONG keyword denotes an integral type that stores signed 32-bit values with values that range from negative 2,147,483,648 (which is represented by the Int32.MinValue constant) through positive 2,147,483,647 (which is represented by the Int32.MaxValue constant) The .NET Framework also includes an unsigned 32-bit integer value type, UInt32 or DWORD, which represents values that range from 0 to 4,294,967,295.
-
-
-
diff --git a/docs/Help_Spanish/Topics/INT64.xml b/docs/Help_Spanish/Topics/INT64.xml
deleted file mode 100644
index 46b2a8dd90..0000000000
--- a/docs/Help_Spanish/Topics/INT64.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- INT64
-
- INT64
-
-
-
- INT64
-
- The INT64 keyword denotes an integral type that stores signed 64-bit values, with a range from negative 9,223,372,036,854,775,808 to positive 9,223,372,036,854,775,807
-
-
diff --git a/docs/Help_Spanish/Topics/Identifiers.xml b/docs/Help_Spanish/Topics/Identifiers.xml
deleted file mode 100644
index 3818b2a255..0000000000
--- a/docs/Help_Spanish/Topics/Identifiers.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Identifiers
-
-
- Identifiers
-
- Identifiers in X# appear on many places in the language. They consist of a character followed by one or more characters, numbers or digits. The lexer definition for identifiers is below. As you can see, we also allow 'special characters' and 'unicode characters', but in general, that is not recommended.
- New keywords that are introduced in Vulcan and X# (see the keyword table) can also be used as Identifier.
- When an identifier must be used that has the same value as a keyword, then you can prefix the identifier with a double @@ sign, like in the following example.
- This is not recommended. But it can happen that code in an external DLL has properties or method names that are keywords in X#. In that case using the @@ prefix can work too.
-
- LOCAL @@Class as STRING LOCAL @@Local as LOGIC
- ID : IDStartChar IDChar* ;
The initializer which is also delimited by curly braces immediately follows the closing curly brace of the constructor call.
-
-
- An example of an object initializer:
- VAR oPerson := Person{}{FirstName := "John", LastName := "Smith"} VAR oPerson := Person{"John", "Smith"} {Age := 35 }
- An example of a collection initializer:
- oList := List<Int>{} {1,2,3,4,5}
- And combined:
- Var oPeople := List<Person> {} {; Person{}{FirstName := "John", LastName := "Smith"}, ; Person{}{FirstName := "Jane", LastName := "Doe"} ; }
- The LINQ example topic shows different initializers in action.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Installation.xml b/docs/Help_Spanish/Topics/Installation.xml
deleted file mode 100644
index 25e3d9434c..0000000000
--- a/docs/Help_Spanish/Topics/Installation.xml
+++ /dev/null
@@ -1,361 +0,0 @@
-
-
-
- Installation
-
- component
- folders
- Installation
-
-
-
- Installation
-
- When you install XSharp, you will find the following folders on your machine:
-
-
-
-
- Folder
-
-
- Setup component
-
-
- Contents
-
-
-
-
- C:\Program Files (x86)\XSharp
-
-
- Main
-
-
- Main installation folder
-
-
-
-
- Assemblies
-
-
- Main
-
-
- The runtime assemblies that are selectable in the Add Reference dialog inside Visual Studio. Please note that this is a subset of the folders in the Redist Folder. For deploying your apps, please use the files in the Redist folder. In a future version, this folder may contain so called reference assemblies (assemblies with only meta data and no code).
-
-
-
-
- Bin
-
-
- main
-
-
- The command line compiler, the Script interpreter and Vulcan XPorter.
-
-
-
-
- Debug
-
-
- main
-
-
- Debug versions of the runtime DLLs and SDK DLLs (FOX only).
-
-
-
-
- Extension
-
-
- main
-
-
- The components that must be installed inside Visual Studio for the X# project system and Language support.
- If you want to reinstall the project systems you should run the deployvs<num>.cmd files in the Uninst folder. These files were created at install time and match your specific configuration of Visual Studio versions.
-
-
-
-
- Help
-
-
- main
-
-
- The PDF, CHM help files and the Visual Studio help.
-
-
-
-
- Images
-
-
- main
-
-
- Some images.
-
-
-
-
- Include
-
-
- main
-
-
- XSharpDefs.xh and other header files needed by X#.
-
-
-
-
- MsBuild
-
-
- main
-
-
- The MsBuild integration for XsProj files.
-
-
-
-
- NetCore
-
-
- main\netcore
-
-
- A version of the X# compiler and script engine for .Net Core 3.1 (FOX only).
-
-
-
-
- Nuget
-
-
- main\nuget
-
-
- The XSharp Nuget packages
-
-
-
-
- Redist
-
-
- main
-
-
- Files that you may want to include with your application compiled with X#.
-
-
-
-
- Templates
-
-
- main\dotnet
-
-
- Contains the templates for the VO Compatible editors for Windows, Servers and Menus.
-
-
-
-
- Tools
-
-
- main
-
-
- Tools that are used during installation.
-
-
-
-
- Uninst
-
-
- main
-
-
- The uninstaller and some cmd files generated during installation to register your X# Extension inside Visual Studio. It also contains cmd files created at install time to help generating native images for the X# compiler. The cmd files with the numbers 1-6 are used to install into different versions of Visual Studio.
-
-
-
-
- VFPXporter
-
-
- main
-
-
- The VFP Exporter
-
-
-
-
- VOXPorter
-
-
- main
-
-
- The VOXPorter.
-
-
-
-
- XIDE
-
-
- xIde
-
-
- The XIDE installer.
-
-
-
-
- <Global Assembly Cache>
-
-
- main\gac
-
-
- X# runtime files will be installed in the GAC when this component is selected.
-
-
-
-
- <Global Assembly Cache>\NativeImages
-
-
- main\ngen
-
-
- The X# compiler files will be precompiled when the option "Optimize performance by generating native images" is selected.
-
-
-
-
- <Common Documents\XSharp\Examples
-
-
- main\examples
-
-
- The X# examples will be installed in the common documents folder when this option is selected.
-
-
-
-
- Visual Studio folders
-
-
- main\vs..
-
-
- X# will be integrated into Visual Studio when this is selected.
-
-
-
-
- Visual Studio 2019 Assuming you have installed (one of) these in the default location:
- c:\Program Files (x86)\Microsoft Visual Studio\<number>\<Version>
- then X# will be in the subfolder
-
-
Common7\IDE\Extensions\XSharp
-
-
-
- main\vs1 .. main\vs6
-
-
-
-
<number> is 2017 or 2019.
-
<Version> can be one of Professional, Community, Enterprise or Buildtools. There can be more than one edition of VS2017/VS2019 on your machine. The installer will show all instances that are detected.
-
-
-
-
-
- Visual Studio 2022 & 2026
- Assuming you have installed VS 2022 in the default location: c:\Program Files\Microsoft Visual Studio\2022\<Version>
- then X# will be in the subfolder
-
-
Common7\IDE\Extensions\XSharp
-
-
-
- main\vs1 .. main\vs6
-
-
-
-
<Version> can be one of Professional, Community, Enterprise or Buildtools. There can be more than one edition of VS2017/VS2019 on your machine. The installer will show all instances that are detected.
-
-
-
-
-
- Registry
- The installer will also write some changes to the registry:
-
-
- Environment variables
- The installer creates / modifies the following environment variables
- XSHARPPATH
- XSHARPMSBUILDDIR
-
-
-
-
-
-
-
-
- User Folders The XSharp installer will register your nuget packages in the folder c:\Users\yournamet\AppData\Roaming\NuGet
-
-
-
-
- The installer will add a section to the NuGet.Config file with the package source "XSharp Offline Packages" and will map the packages with the name "xsharp.*" to this package source.
-
-
-
-
-
- See the topic Building XSharp apps with Visual Studio and/or MsBuild for a description how the various registry settings and folders are involved with the build process with MsBuild and Visual Studio.
-
-
diff --git a/docs/Help_Spanish/Topics/Installer-Command-Line-options.xml b/docs/Help_Spanish/Topics/Installer-Command-Line-options.xml
deleted file mode 100644
index 6c480aeb1b..0000000000
--- a/docs/Help_Spanish/Topics/Installer-Command-Line-options.xml
+++ /dev/null
@@ -1,346 +0,0 @@
-
-
-
- Installer Command Line options
-
- /closeapplications
- /components
- /dir
- /forcecloseapplications
- /group
- /help
- /loadinf
- /log
- /nocancel
- /nocloseapplications
- /noforcecloseapplications
- /noicons
- /norestart
- /norestartapplications
- /nouninstall
- /restartapplications
- /restartexitcode
- /saveinf
- /silent
- /suppressmsgboxes
- /type
- /verysilent
- setup component
- setup type
-
-
-
- Installer Command Line options
-
- Our installer was created with the product Inno Setup. We are supporting the "normal" Inno Setup command line options and the following extra options. Some options are not installed because these are not relevant for our installer, such as /lang and /password.
- Custom Setup command line options
-
-
-
-
- Option
-
-
- Description
-
-
-
-
- /nouninstall
-
-
- This option exists since X# 2.4. This suppresses uninstalling the previous version. When you choose this you can install 2 different versions of X# side by side, assuming you choose different installation folders. Please note that if both versions install into the same Visual Studio version then the latest installation "wins". If you want to switch to another version of the VS integration or MsBuild support files you should run the "deployvs<num>".cmd files in the Uninst folder of the installation that you want to activate.
-
-
-
- Standard Inno Setup command line options
-
-
-
-
- Option
-
-
- Description
-
-
-
-
- /help, /?
-
-
- Shows a summary of this information. Ignored if the UseSetupLdr [Setup] section directive was set to no.
-
-
-
-
- /silent, /verysilent
-
-
- Instructs Setup to be silent or very silent. When Setup is silent, the wizard and the background window are not displayed, but the installation progress window is. When a setup is very silent, this installation progress window is not displayed. Everything else is normal, so for example, error messages during installation are displayed, as well as the startup prompt (if you have not disabled it with DisableStartupPrompt or the '/SP-' command line option explained above).
- If a restart is necessary and the '/norestart command is not used (see below) and Setup is silent, it will display a Reboot now? message box. If it is very silent, it will reboot without asking.
-
-
-
-
- /suppressmsgboxes
-
-
- Instructs Setup to suppress message boxes. Only has an effect when combined with '/silent or '/verysilent.
- The default response in situations where there's a choice is:
-
-
Yes in a 'Keep newer file?' situation.
-
No in a 'File exists, confirm overwrite.' situation.
-
Abort in Abort/Retry situations.
-
Cancel in Retry/Cancel situations.
-
Yes (=continue) in a DiskSpaceWarning/DirExists/DirDoesntExist/NoUninstallWarning/ExitSetupMessage/ConfirmUninstall situation.
-
Yes (=restart) in a FinishedRestartMessage/UninstalledAndNeedsRestart situation.
-
The recommended choice in a PrivilegesRequiredOverridesAllowed=dialog situation.
-
- Five message boxes are not suppressible:
-
-
The About Setup message box.
-
The Exit Setup? message box.
-
The FileNotInDir2 message box displayed when Setup requires a new disk to be inserted and the disk was not found.
-
Any (error) message box displayed before Setup (or Uninstall) could read the command line parameters.
-
Any task dialog or message box displayed by [Code] support functions TaskDialogMsgBox and MsgBox.
-
-
-
-
-
- /log="filename"
-
-
- This allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Setup will abort with an error message. If you do not specify this command line option, the installer will log to a file with the name "Setup Log <date>#<number>.txt" in the current users TEMP folder.
-
-
-
-
- /nocancel
-
-
- Prevents the user from canceling during the installation process, by disabling the Cancel button and ignoring clicks on the close button. Useful along with '/silent or '/verysilent.
-
-
-
-
- /norestart
-
-
- Prevents Setup from restarting the system following a successful installation, or after a Preparing to Install failure that requests a restart. Typically used along with /silent or /verysilent.
-
-
-
-
- /restartexitcode=exit code
-
-
- Specifies a custom exit code that Setup is to return when the system needs to be restarted following a successful installation. (By default, 0 is returned in this case.) Typically used along with /norestart.
-
-
-
-
- /closeapplications
-
-
- Instructs Setup to close applications using files that need to be updated by Setup if possible.
-
-
-
-
- /nocloseapplications
-
-
- Prevents Setup from closing applications using files that need to be updated by Setup. If /closeapplications was also used, this command line parameter is ignored.
-
-
-
-
- /forcecloseapplications
-
-
- Instructs Setup to force close when closing applications.
-
-
-
-
- /noforcecloseapplications
-
-
- Prevents Setup from force closing when closing applications. If /forcecloseapplications was also used, this command line parameter is ignored.
-
-
-
-
- /restartapplications
-
-
- Instructs Setup to restart applications if possible. Only has an effect when combined with '/closeapplications.
-
-
-
-
- /norestartapplications
-
-
- Prevents Setup from restarting applications. If /restartapplications was also used, this command line parameter is ignored.
-
-
-
-
- /loadinf="filename"
-
-
- Instructs Setup to load the settings from the specified file after having checked the command line. This file can be prepared using the '/saveinf=' command as explained below. Do not forget to use quotes if the file name contains spaces.
-
-
-
-
- /saveinf="filename"
-
-
- Instructs Setup to save installation settings to the specified file. Do not forget to use quotes if the file name contains spaces.
-
-
-
-
- /dir="x:\dirname"
-
-
- Overrides the default directory name displayed on the Select Destination Location wizard page. A fully qualified path name must be specified. May include an "expand:" prefix which instructs Setup to expand any constants in the name. For example: '/dir=expand:{autopf}\My Program'.
-
-
-
-
- /group="folder name"
-
-
- Overrides the default folder name displayed on the Select Start Menu Folder wizard page. May include an "expand:" prefix, see '/dir='. If the [Setup] section directive DisableProgramGroupPage was set to yes, this command line parameter is ignored.
-
-
-
-
- /noicons
-
-
- Instructs Setup to initially check the Don't create a Start Menu folder check box on the Select Start Menu Folder wizard page.
-
-
-
-
- /type=type name
-
-
- Overrides the default setup type.
- If the specified type exists and is not a custom type, then any /components parameter will be ignored.
- The types in the X# installer are: full, compact, custom
-
-
-
-
- /components= "comma separated list of component names"
-
-
- Overrides the default component settings. Using this command line parameter causes Setup to automatically select a custom type. If no custom type is defined, this parameter is ignored.
- Only the specified components will be selected; the rest will be deselected.
- If a component name is prefixed with a "*" character, any child components will be selected as well (except for those that include the dontinheritcheck flag). If a component name is prefixed with a "!" character, the component will be deselected.
- This parameter does not change the state of components that include the fixed flag.
- Example: Deselect all components, then select the "help" and "plugins" components: /components="help,plugins"
- Example: Deselect all components, then select a parent component and all of its children with the exception of one: /components="*parent,!parent\child"
The components in the X# installer are:
-
-
-
- Component
-
-
- Description
-
-
-
-
- main
-
-
- The XSharp Compiler and Build System
-
-
-
-
- main\script
-
-
- Register .prgx as X# Script extension
-
-
-
-
- main\ngen
-
-
- Optimize performance by generating native images
-
-
-
-
- main\gac
-
-
- Register runtime DLLs in the GAC (recommended !)
-
-
-
-
- main\examples
-
-
- Install the Xsharp Examples
-
-
-
-
- main\debug
-
-
- Install debug versions of the runtime
-
-
-
-
- main\netcore
-
-
- Install the .Net Core version of the compiler
-
-
-
-
- vs
-
-
- Visual Studio Integration
-
-
-
-
- vs\1 thru vs\6
-
-
- The detected versions of Visual Studio
-
-
-
-
- xide
-
-
- Include the XIDE installer
-
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/IntegerLiterals.xml b/docs/Help_Spanish/Topics/IntegerLiterals.xml
deleted file mode 100644
index cd5acd6ea9..0000000000
--- a/docs/Help_Spanish/Topics/IntegerLiterals.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
- Integer Literals
-
- Integer Literals
- Literals
- Numeric Literals
-
-
-
- Integer Literals
-
- Literal INT values may be specified in decimal, hexadecimal, or binary notation:
-
- 12345 0x1234ABCD 0b010010101
-
- Integer literals may have one of the following suffixes:
-
-
-
-
- Suffix
-
-
-
-
-
-
- L or l
-
-
- Signed 32 bits integer
-
-
-
-
- U or u
-
-
- Unsigned integer
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Interfaces.xml b/docs/Help_Spanish/Topics/Interfaces.xml
deleted file mode 100644
index 2a124bb116..0000000000
--- a/docs/Help_Spanish/Topics/Interfaces.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Interfaces
-
-
- Interfaces
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Interoperability.xml b/docs/Help_Spanish/Topics/Interoperability.xml
deleted file mode 100644
index ec91b443a1..0000000000
--- a/docs/Help_Spanish/Topics/Interoperability.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Interoperability
-
-
- Interoperability
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Introduction.xml b/docs/Help_Spanish/Topics/Introduction.xml
deleted file mode 100644
index 81c3b746eb..0000000000
--- a/docs/Help_Spanish/Topics/Introduction.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- Getting Started with X#
-
-
- Getting Started with X#
-
-
-
- Click here for the version history
- Click here for the list of known issues
-
-
diff --git a/docs/Help_Spanish/Topics/Item-Templates.xml b/docs/Help_Spanish/Topics/Item-Templates.xml
deleted file mode 100644
index 29c834e7c1..0000000000
--- a/docs/Help_Spanish/Topics/Item-Templates.xml
+++ /dev/null
@@ -1,491 +0,0 @@
-
-
-
- Item Templates
-
- item templates
- templates
-
-
-
- Item Templates
-
- The X# Visual Studio integration comes with the following item templates:
-
-
-
-
-
-
- Template
-
-
- Description
-
-
- Required Framework version
-
-
-
-
-
-
- Category: Code
-
-
-
-
-
-
-
-
-
-
-
- Class
-
-
- An empty class definition
-
-
- 2.0
-
-
-
-
-
-
-
- CodeFile
-
-
- An empty Code File
-
-
- 2.0
-
-
-
-
-
-
-
- Header
-
-
- An empty Header File
-
-
- n/a
-
-
-
-
-
-
-
- TextFile
-
-
- An empty text file
-
-
- n/a
-
-
-
-
-
-
- Category: Forms
-
-
-
-
-
-
-
-
-
-
-
- Windows Forms Form
-
-
- A Windows form with separate designer.prg
-
-
- 2.0
-
-
-
-
-
-
-
- Windows Forms Simple Form
-
-
- A simple Windows Forms Form without designer.prg
-
-
- 2.0
-
-
-
-
-
-
-
- Windows Forms User Control
-
-
- Windows Forms User Control
-
-
- 2.0
-
-
-
-
-
-
- Category: Internal
-
-
-
-
-
-
-
-
-
-
- AppConfigInternal
-
-
- A hidden app.config
-
-
- 2.0
-
-
-
-
-
-
- AppManifestInternal
-
-
- A hidden app.manifest
-
-
- 2.0
-
-
-
-
-
-
- AssemblyInfoInternal
-
-
- A hidden assemblyinfo prg
-
-
- 2.0
-
-
-
-
-
-
- Managed Resource Internal
-
-
- A hidden resource file
-
-
- 2.0
-
-
-
-
-
-
- Settings Internal
-
-
- A hidden settings file
-
-
- 2.0
-
-
-
-
-
-
- Category: Resources
-
-
-
-
-
-
-
-
-
-
-
- Native Resource File (.rc)
-
-
- A file in which native resources can be defined
-
-
- n/a
-
-
-
-
-
-
-
- Bitmap
-
-
- A Bitmap file
-
-
- n/a
-
-
-
-
-
-
-
- Cursor
-
-
- A Cursor file
-
-
- n/a
-
-
-
-
-
-
-
- Icon
-
-
- An Icon file
-
-
- n/a
-
-
-
-
-
-
-
- Managed resource file (.resx)
-
-
- A file to store managed resources
-
-
- 2.0
-
-
-
-
-
-
- Category: VO
-
-
-
-
-
-
-
-
-
-
- VODBServer
-
-
- An empty DBServer
-
-
- n/a
-
-
-
-
-
-
- VOFieldSpec
-
-
- An empty FieldSpec container file
-
-
- n/a
-
-
-
-
-
-
- VOMenu
-
-
- An empty VO Menu
-
-
- n/a
-
-
-
-
-
-
- VOWindow
-
-
- An empty VO Window
-
-
- n/a
-
-
-
-
-
-
- Category: WCF
-
-
-
-
-
-
-
-
-
-
-
- WCF Service
-
-
- A WCF Service
-
-
- 3.0
-
-
-
-
-
-
- Category: WPF
-
-
-
-
-
-
-
-
-
-
-
- WPF Flow Document
-
-
- Dynamically formatted XAML document
-
-
- 3.0
-
-
-
-
-
-
-
- WPF Page
-
-
- Windows Presentation Foundation page
-
-
- 3.0
-
-
-
-
-
-
-
- WPF Page Function
-
-
- Windows Presentation Foundation page function
-
-
- 3.0
-
-
-
-
-
-
-
- WPF Resource Dictionary
-
-
- XAML Resource Dictionary
-
-
- 3.0
-
-
-
-
-
-
-
- WPF UserControl
-
-
- Windows Presentation Foundation user control
-
-
- 3.0
-
-
-
-
-
-
-
- WPF Window
-
-
- Windows Presentation Foundation window
-
-
- 3.0
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Keyword-Matching.xml b/docs/Help_Spanish/Topics/Keyword-Matching.xml
deleted file mode 100644
index 968080f7ed..0000000000
--- a/docs/Help_Spanish/Topics/Keyword-Matching.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Highlight Keywords
-
-
- Highlight Keywords
-
- The keyword matching feature will highlight keyword pairs in the editor as you can see in the image below.
-
-
- The TRY, CATCH and END TRY keywords are highlighted so you can see that they belong to each other.
-
- If the cursor is located on a RETURN statement, the matching FUNCTION or METHOD will be highlighted.
-
-
-
- The color for the highlights can be set in the Tools/Options dialog under the Environment/Fonts and Colors node. The X# specific colors all start with the text "X#".
-
-
diff --git a/docs/Help_Spanish/Topics/Keywords.xml b/docs/Help_Spanish/Topics/Keywords.xml
deleted file mode 100644
index 13d066f125..0000000000
--- a/docs/Help_Spanish/Topics/Keywords.xml
+++ /dev/null
@@ -1,6196 +0,0 @@
-
-
-
- Keywords
-
- Entities
- Keywords
- Parameters
-
-
-
- Keywords
-
- The table below has the keywords that are available in the X# language.
-
-
The Keywords in the VO column find their origin in the Visual Objects language. When the compiler dialect is set to VO, these keywords may be abbreviated (4 letter minimum).
-
The Keywords in the VN column were introduced in Vulcan.NET. These keywords may never be abbreviated, and most of these keywords are positional, so are only recognized in certain positions in the language. That also means that these keywords may be used as Variable Names or Method names.
-
The Keywords in the X# column were introduced in X#. Just like the VN keywords, they may never be abbreviated and they are also positional.
-
The Keywords in the VFP column are FoxPro specific. Please note that many FoxPro commands are implemented as "User Defined Commands" and their tokens are not strictly Keywords inside X#.
-
The Keywords in the Xb++ column are Xbase++ specific. Please note that many FoxPro commands are implemented as "User Defined Commands" and their tokens are not strictly Keywords inside X#.
-
Keywords that are listed in the Id column may also be used as an identifier. These are so called "context sensitive" keywords. You may see in the Visual Studio editor that these keywords will change color depending on the position in the source. For example, if you start typing PROPERTY, the word will be shown in the IDENTIFIER color:
-
-
- However, as soon as you continue to complete the PROPERTY definition, it will get the KEYWORD color:
-
-
-
-
- Keyword
-
-
- VO
-
-
- VN
-
-
- X#
-
-
- VFP
-
-
- Xb++
-
-
- Id
-
-
-
-
- ABSTRACT
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- ACCESS
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ADD
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- ALIGN
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- AND
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- ANNOUNCE
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
- Y
-
-
-
-
- ANSI
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- ARRAY
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- AS
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ASCENDING
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- ASPEN
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- ASSEMBLY
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- ASSIGN
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ASSIGNMENT
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- ASYNC
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- AUTO
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- AWAIT
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- BEGIN
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- BREAK
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- BY
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- BYTE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- CALLBACK
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- CASE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- CATCH
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- CCALL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- CCALLNATIVE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- CHAR
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- CHECKED
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- CLASS
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- CLIPPER
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- CODEBLOCK
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- CONST
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- CONSTRUCTOR
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- DATE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- DECLARE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- DEFAULT
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- DEFERRED
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- DEFINE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- DELEGATE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- DESCENDING
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- DESTRUCTOR
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- DIM
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- DIMENSION
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- DLLEXPORT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- DO
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- DOWNTO
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- DWORD
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- DYNAMIC
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- EACH
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- ELSE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ELSEIF
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- END
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ENDCASE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ENDDO
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ENDCLASS
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- ENDDEFINE
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- ENDIF
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ENDFOR
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
- Y2
-
-
- Y
-
-
-
-
- ENDFUNC
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
-
-
-
- Y
-
-
-
-
- ENDPROC
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
-
-
-
- Y
-
-
-
-
- ENDSCAN
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
-
-
-
- Y
-
-
-
-
- ENDSEQUENCE
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
- Y
-
-
-
-
- ENDTRY
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
-
-
-
- Y
-
-
-
-
- ENDWITH
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
-
-
-
- Y
-
-
-
-
- ENUM
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- EQUALS
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- EVENT
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- EXIT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- EXCLUDE
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- EXPLICIT
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- EXPORT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- EXPORTED
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- EXTERN
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- FALSE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FASTCALL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- FIELD
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- FINAL
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- FINALLY
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FIXED
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- FLOAT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FOR
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FOREACH
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- FOR EACH
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
- Y2
-
-
- Y
-
-
-
-
- FREEZE
-
-
-
-
-
- `
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- FROM
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- FUNC
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- FUNCTION
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- GET
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- GLOBAL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- GROUP
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- HELPSTRING
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- HIDDEN
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- IF
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- IIF
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- IMPLEMENTS
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- IMPLICIT
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- IMPLIED
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- IN
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- INHERIT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- INITONLY
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- INLINE
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- INSTANCE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- INT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- INT64
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- INTERFACE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- INTO
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- INTERNAL
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- INTRODUCE
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- IS
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- JOIN
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- LET
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- LOCAL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- LOCK
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- LONG
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- LONGINT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- LOOP
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- LPARAMETERS
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- MEMBER
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- MEMVAR
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- METHOD
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- MODULE
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- NAMEOF
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- NAMESPACE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- NEW
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- NEXT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NIL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NOINIT
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- NOP
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- NOSAVE
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- NOT
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- NULL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NULL_ARRAY
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NULL_CODEBLOCK
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NULL_DATE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NULL_OBJECT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NULL_PSZ
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NULL_PTR
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NULL_STRING
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NULL_SYMBOL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- OBJECT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- OFF
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- OLEPUBLIC
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- ON
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- OPERATOR
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- OPTIONS
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- OR
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- ORDERBY
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- OTHERWISE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- OVERRIDE
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- OUT
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- PARAMETERS
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PARAMS
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- PARTIAL
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- PASCAL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- PCALL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PCALLNATIVE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PCOUNT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- POP
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PRIVATE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PROC
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- PROCEDURE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PROPERTY
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- PROTECTED
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PSZ
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- PTR
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- PUBLIC
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PUSH
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REAL4
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- REAL8
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- RECOVER
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REF
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REMOVE
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- REPEAT
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REQUEST
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y2
-
-
- Y
-
-
-
-
- RETURN
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- SCOPE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- SEALED
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- SELECT
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- SELF
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- SEQUENCE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- SET
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- SHARED
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- SHARING
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- SHORT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- SHORTINT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- SIZEOF
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- STATIC
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- STEP
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- STRICT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- STRING
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- STRUCT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- STRUCTURE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- SUPER
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- SWITCH
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- SYMBOL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- SYNC
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
- Y
-
-
-
-
- THEN
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- THISCALL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- TO
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- THROW
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- TRUE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- TRY
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- TUPLE
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- TYPEOF
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- UINT64
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- UNCHECKED
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- UNICODE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- UNION
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- UNSAFE
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- UNTIL
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- UPTO
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- USING
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- USUAL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- VALUE
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- VAR
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- VIRTUAL
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- VOID
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- VOLATILE
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- VOSTRUCT
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- WARNINGS
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _WINCALL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- WHEN
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- WHERE
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- WHILE
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- WORD
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Y1
-
-
-
-
- XOR
-
-
-
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
- Y
-
-
-
-
- YIELD
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
- Y
-
-
-
-
- __ARGLIST
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
- _AND
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _CAST
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _CODEBLOCK
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _DLL
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _FIELD
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _GETFPARAM
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _GETMPARAM
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _INIT1, _INIT2, _INIT3
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _NOT
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _OR
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _SIZEOF
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _TYPEOF
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- _XOR
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- .AND.
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- .F.
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- .NOT.
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- .OR.
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- .T.
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- .XOR.
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ...
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #command
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #define
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #else
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #endif
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #endregion
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #ifdef
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #ifndef
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #include
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #line
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #pragma
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #region
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #translate
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #undef
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #using
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #warning
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #xcommand
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #xtranslate
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #ycommand
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
- #ytranslate
-
-
-
-
-
-
-
-
- Y
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1These type names can only be used as identifiers when the dialect is not Core, VO or Vulcan.
- 2This keyword is actually defined by a preprocessor command.
-
-
diff --git a/docs/Help_Spanish/Topics/Known-Issues-in-XSharp-3.xml b/docs/Help_Spanish/Topics/Known-Issues-in-XSharp-3.xml
deleted file mode 100644
index 2e29241439..0000000000
--- a/docs/Help_Spanish/Topics/Known-Issues-in-XSharp-3.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Known Issues in XSharp 3
-
-
- Known Issues in XSharp 3
-
- Known issues
-
-
Renaming an item in a SDK project also sometimes fails.
-
There is no dialog yet in Visual Studio to declare GLOBAL USINGs at the project file level
-
Projects that are Multi-Targeting (that have a TargetFrameworks property are supported, but only one Framework is built when opened inside Visual Studio. The project system renames the node to XTargetFrameworks, and adds a TargetFramework property with the active framework. When saving this is reversed and the last selected active target framework is stored in the project file as ActiveTargetFramework, so it can be restored the next time that the project is opened.
-
We have occasionally seen that switching a single targeting project from one version to another may cause Visual Studio to hang.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Known-Issues.xml b/docs/Help_Spanish/Topics/Known-Issues.xml
deleted file mode 100644
index dcdac5591b..0000000000
--- a/docs/Help_Spanish/Topics/Known-Issues.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- Known Issues
-
-
- Known Issues
-
- Below is the complete (but short) list of things that are not supported yet or are known problems in the current build of X#.
- Compiler
-
-
Some parser errors need improvements, compiler errors may be cryptic every now and then
-
Sometimes you may see a "Include file not found" error, where the file DOES exist. This seems to be a side effect of the codepage that was used to save the include files. When you save the file as UTF8 (File Advanced Save Options in Visual Studio), this problem almost always disappears.
-
- RDD System
-
-
Query Optimization (Rushmore) is not supported yet.
-
-
- Runtime
-
-
Some runtime functions are not supported yet.
-
-
-
diff --git a/docs/Help_Spanish/Topics/LINQ-Query-Expressions.xml b/docs/Help_Spanish/Topics/LINQ-Query-Expressions.xml
deleted file mode 100644
index 48ae0c610c..0000000000
--- a/docs/Help_Spanish/Topics/LINQ-Query-Expressions.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- LINQ Query Expressions
-
-
- LINQ Query Expressions
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/LINQ.xml b/docs/Help_Spanish/Topics/LINQ.xml
deleted file mode 100644
index 53c0d5b726..0000000000
--- a/docs/Help_Spanish/Topics/LINQ.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- LINQ Expressions
-
- AS
- ASCENDING
- BY
- DESCENDING
- EQUALS
- FROM
- GROUP
- IN
- INTO
- JOIN
- LET
- ON
- ORDERBY
- SELECT
- WHERE
-
-
-
- LINQ Expressions
-
- The LINQ expression rule is:
-
- linqquery : fromClause queryBody ;
fromClause : FROM identifier (AS typeName)? IN expression ;
queryBodyClause : fromClause | LET identifier ASSIGN_OP expression | WHERE expression | JOIN identifier (AS typeName)? IN expression ON expression EQUALS expression joinIntoClause? | ORDERBY ordering (, ordering)* ;
joinIntoClause : INTO identifier ;
ordering : expression (ASCENDING|DESCENDING)? ;
selectOrGroupclause : SELECT expression | GROUP expression BY expression ;
queryContinuation : INTO identifier queryBody
- An example of a LINQ Query:
- VAR oAll := FROM D IN oDev ; JOIN C IN oC ON D:Country EQUALS C:Name ; ORDERBY D:LastName ; SELECTCLASS {D:Name, D:Country, C:Region}
- In this example you will see
- fromclause: FROM D in oDev querybody 1: JOIN C IN oC ON D:Country EQUALS C:Name querybody 2: ORDERBY D:LastName selectOrGroupClause: SELECT CLASS {...}
- Other examples can be found in the LINQ Example topic.
-
-
diff --git a/docs/Help_Spanish/Topics/LOGIC.xml b/docs/Help_Spanish/Topics/LOGIC.xml
deleted file mode 100644
index e1c3582d7e..0000000000
--- a/docs/Help_Spanish/Topics/LOGIC.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- LOGIC
-
- LOGIC
-
-
-
- LOGIC
-
- The LOGIC keyword represents the .Net Boolean type. This type can have either of two values: true, or false.
-
- If you have members of type LOGIC in VOSTRUCT or UNION types, these will not be represented with .Net Boolean types. This is because a .Net Boolean occupies 1 byte, whereas in the Windows API, LOGIC values are represented using 4 bytes. Therefore, the compiler replaces them with a special type, __WinBool, which occupies 4 bytes and includes implicit converters between Logic and __WinBool.
-
-
diff --git a/docs/Help_Spanish/Topics/Lamda-Expressions.xml b/docs/Help_Spanish/Topics/Lamda-Expressions.xml
deleted file mode 100644
index 72b8f9d3d7..0000000000
--- a/docs/Help_Spanish/Topics/Lamda-Expressions.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- Lamda Expressions
-
- =>
- Lamda Expressions
-
-
-
- Lamda Expressions
-
- Lambda Expressions are a bit like a codeblock. it is a block of code with optional parameters and a return value. They are used to create anonymous functions. Unlike a codeblock, they do NOT inherit from a common class. They also cannot be stored inside the USUAL type.
-
- Code that expects a lambda expression often declares a delegate that describes the parameter types and return value of the lambda expression. Lambda expressions can also be used to declare an event handler.
-
- The return value of the lambda expression is the last expression in the expression list, or the value returned by the return statement in the statement list.
- { [pars] => expression [, expressionlist] }
- or
- { [pars] => statements // these are NOT separated with semi colons! }
- parsComma separated list of arguments. They can optionally be typed.
-
- Some examples:
- // single expression, untyped parameters { a, b => a * b}
// single expression, typed parameters { a asint, b asint => a / b}
// typed parameters, expression list, last expression is return value { a asint, b asint => a := iif(a == 0, 1, a), b / a}
// statement list, no semi colons needed, return statement is return value { a asint, b asint => if a == 0 a := 1 endif return b / a }
// Register a click event handler. No need to type the args // The signature is derived from the signature of the Click Event btnOk:Click += { sender, args => SELF:Close() }
-
-
diff --git a/docs/Help_Spanish/Topics/Licenses.xml b/docs/Help_Spanish/Topics/Licenses.xml
deleted file mode 100644
index dc92e72b1b..0000000000
--- a/docs/Help_Spanish/Topics/Licenses.xml
+++ /dev/null
@@ -1,73 +0,0 @@
-
-
-
- Licensing
-
-
- Licensing
-
- XSharp is FREE Software. Of course that does not mean that you can do with it whatever you want. We have set a couple of rules that determine what you can and cannot do with our software, so our software is released under a license.
- In an ideal world we would have published all of our source code and binaries under a very open license agreement, such as the Apache License, just like how the Roslyn code is published. However the reality is that there are people on this world that would like to take our source code and binaries and release this with minimal changes under their own name. To prevent that from happening we have been forced to set some limitations to how you can use our product. For any "normal" developer that uses XSharp to develop applications for end users this should present no problems.
- The simplified version of the limitations means that :
-
-
You can only redistribute the 'runtime' components that are listed in the documentation. You can not redistribute our compiler. However when needed, you can ask your customer to download our compiler from this website
-
You (when you are a FOX subscriber) have access to the compiler source code and may change and rebuild the compiler for internal use inside your company. However you are not allowed to publish or redistribute the (changed) compiler to your customers
-
- We are convinced that you will find our license agreements fair and easy to work with. If you have any questions about the licenses, please contact us at info@xsharp.eu
-
-
-
-
- Component & Name
-
-
- Short summary of the license
-
-
-
-
- The compiler binaries and runtime binaries XSharp Open Software License Agreement 1.0
-
-
- This can be downloaded for free from our website. All you have to do is to create an account on this website.
-
-
You can download the components from our website
-
You can use the components for free both for commercial and personal use
-
You can only deploy the runtime components to your customers
-
OEM Licensing of the compiler binaries is only allowed when you have a separate agreement with XSharp BV
-
-
-
-
-
- The source code to the runtime, visual studio integration and tools Apache License version 2.0
-
-
- Everybody can access this public source code in our public repository on GitHub
-
-
You can download the source from our GitHub project
-
You can make adjustments to the source code both for internal use and also to redistribute the changed runtime binaries to your customers
-
If you have a contribution that you want to see included in a future version of XSharp you can send us a pull request on GitHub
-
XSharp BV decides which changes will be included in the main branch and which not.
-
-
-
-
-
- The Roslyn part of the Compiler Source code Apache License version 2.0
-
-
- This license applies to the Roslyn code that we have used and that you can also find on GitHub
-
-
-
-
- The Antlr part of the Compiler Source code Antlr BSD License
-
-
- This license applies to the Antlr 4 source code that we have used and that you can find on GitHub
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Literals.xml b/docs/Help_Spanish/Topics/Literals.xml
deleted file mode 100644
index 03d9a95a52..0000000000
--- a/docs/Help_Spanish/Topics/Literals.xml
+++ /dev/null
@@ -1,82 +0,0 @@
-
-
-
- Literals
-
-
- Literals
-
- The X# language knows the following literal types:
-
-
-
-
- Keyword
-
-
- Description
-
-
-
-
- Char Literals
-
-
-
-
-
-
- Date Literals
-
-
-
-
-
-
- Logic Literals
-
-
-
-
-
-
- Macros
-
-
-
-
-
-
- NULL Literals
-
-
-
-
-
-
- Numeric Literals
-
-
-
-
-
-
- String Literals
-
-
-
-
-
-
- Symbol Literals
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Logic-Ttype.xml b/docs/Help_Spanish/Topics/Logic-Ttype.xml
deleted file mode 100644
index cc3b7ef0ef..0000000000
--- a/docs/Help_Spanish/Topics/Logic-Ttype.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Logic Ttype
-
- LOGIC
- XSharp.__WinBool
-
-
-
- Logic Ttype
-
- For normal use the logic type is mapped to System.Boolean.
- Inside VOSTRUCT and UNION, the XSharp.__WinBool is used, because this is a 4 byte value just like the Win32 api expects.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/LogicLiterals.xml b/docs/Help_Spanish/Topics/LogicLiterals.xml
deleted file mode 100644
index 24098db328..0000000000
--- a/docs/Help_Spanish/Topics/LogicLiterals.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- Logic Literals
-
- .F.
- .N.
- .T.
- .Y.
- FALSE
- Literals
- LOGIC
- Logic Literals
- TRUE
-
-
-
- Logic Literals
-
- X# uses the following Logical literals:
-
-
- Returns TRUE when both operands are TRUE, otherwise FALSE.
-
-
-
-
- .OR.
-
-
- x .OR. y
-
-
- Returns TRUE with one or both operands are TRUE. Only when both operands are FALSE then FALSE is returned.
-
-
-
-
- .NOT. or !
-
-
- .NOT. x
-
-
- Reverses TRUE and FALSE.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Macros.xml b/docs/Help_Spanish/Topics/Macros.xml
deleted file mode 100644
index 3fd3dca4a1..0000000000
--- a/docs/Help_Spanish/Topics/Macros.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- Macros
-
- Macros
-
-
-
- Macros
-
-
- & Command
-
-
diff --git a/docs/Help_Spanish/Topics/Managed-Resources.xml b/docs/Help_Spanish/Topics/Managed-Resources.xml
deleted file mode 100644
index d28478a09d..0000000000
--- a/docs/Help_Spanish/Topics/Managed-Resources.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Managed Resources
-
-
- Managed Resources
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Memory-Variables.xml b/docs/Help_Spanish/Topics/Memory-Variables.xml
deleted file mode 100644
index 2ff5eaed1d..0000000000
--- a/docs/Help_Spanish/Topics/Memory-Variables.xml
+++ /dev/null
@@ -1,121 +0,0 @@
-
-
-
- Memory Variables
-
-
- Memory Variables
-
- X# provides support for dynamically scoped variables that are created and maintained completely at runtime. The term dynamically scoped refers to the fact that the scope of these variables is not limited by the entity in which the variable is created.
- Warning! Dynamically scoped variables are NOT supported in the Core and Vulcan dialects. In other dialects they are supported only if the -memvar compiler option is enabled.
-
-
-
-
- Variable Type
-
-
- Lifetime
-
-
- Visibility
-
-
-
-
- PRIVATE
-
-
- Until creator returns or until released
-
-
- Creator and called routines
-
-
-
-
- PUBLIC
-
-
- Application or until released
-
-
- Application
-
-
-
-
- The data type of a dynamically scoped variable changes according to the contents of the variable. For this reason, they are often described as dynamic or polymorphic.
- Dynamically scoped variables are provided mainly for Clipper/Xbase compatibility; however, they are very useful in certain circumstances. For instance, they let you develop rapid prototypes and have certain inheritance properties that you may find hard to resist.
- You must be aware, however, that using them comes at a cost. Consider these points:
-
-
Because they are not resolved at compile time, these variables require overhead in the form of run-time code, making your application larger and slower than necessary.
-
No compile time checking for type compatibility is possible with these variables.
-
Using the inheritance properties of these variables defies one of the basic tenets of modular programming and may lead to maintenance and debugging problems down the line. Furthermore, this practice will make the transition to lexically scoped and typed variables more difficult.
-
- This section explores dynamically scoped variables fully, but X# has several options for variable declarations that you will want to explore before deciding to use this variable class. The next two sections in this chapter introduce you to Lexically Scoped Variables and Strongly Typed Variables, which you may find useful.
- Important! For the sake of illustration, some of the examples in this section use unorthodox programming practices. Using the inheritance properties of public and private variables instead of passing arguments and returning values is not recommended.
- Private
- Private is one of the two types of dynamically scoped variables, and there are several ways to create a private variable:
-
-
List the variable name as part of a PRIVATE statement. If you do not make an assignment at this time, the variable takes on the NIL value and data type; otherwise, it takes on the data type of its assigned value. You can assign a new value (with a new datatype) to a variable at any time: PRIVATE X := 10, y This creates x as a numeric variable and y as an untyped variable with the value NIL. You can later change the values and their types by assigning other values to them: X := "X# Is great" Y := Today()
-
-
-
List the variable name as part of a PARAMETERS statement within a FUNCTION, PROCEDURE or METHOD definition. The variable takes on the data type of its associated argument when the routine is called, or NIL if the argument is omitted. You can assign a new value (and a new data type) to the variable at any time.
-
-
-
Assign a value to a non-existent variable name (for example, x := 10). The variable takes on the data type of its assigned value until you assign a new value to it. (x is numeric, but the assignment x := "Ms. Jones" changes it to a string.) This will only work if you have used both the -undeclared and the -memvar commandline options.
-
- Private variables have these properties:
-
-
You can access them within the creating routine and any routines called by the creator. In other words, private variables are automatically inherited by called routines without having to pass them as arguments.
-
You can hide them from a called routine by explicitly creating a private (using PRIVATE or PARAMETERS) or declaring a local (using LOCAL) variable with the same name in the called routine.
-
They are automatically released from memory when the creator returns to its calling routine, or you can release them explicitly using RELEASE, CLEAR ALL, or CLEAR MEMORY.
-
- In this example, the function Volume() expects three arguments, or parameters, to be passed. When the function is called, it creates three private variables, nLength, nWidth, and nHeight to accept the arguments. Because they are created with the PARAMETERS statement, any higher-level variables (either public or private) created with these names are temporarily hidden, preventing their values from being overwritten in memory:
- FUNCTION Volume() PARAMETERS nLength, nWidth, nHeight RETURN nLength * nWidth * nHeight
- In the next example, a modified version of Volume() creates a private variable (assuming no other variable name nVolume is visible) to store its return value. If the variable nVolume exists prior to calling Volume() and is visible to Volume() (for example, nVolume may be public or private to the routine that called Volume()), its value is overwritten in memory and will remain changed when the function returns to its calling routine:
- FUNCTION Volume() PARAMETERS nLength, nWidth, nHeight nVolume := nLength * nWidth * nHeight RETURN nVolume
- In this version, Volume() specifies the nVolume variable as PRIVATE. Doing this temporarily hides any higher-level variable (either public or private) with the same name, preventing its value from being overwritten in memory:
- FUNCTION Volume() PARAMETERS nLength, nWidth, nHeight PRIVATE nVolume := nLength * nWidth * nHeight RETURN nVolume
- Public
- The second category of undeclared variable is public. Public variables have application-wide lifetime and visibility, and you can define them in only one way:
-
-
List the variable name as part of a PUBLIC statement. If you do not make an assignment at this time, the variable takes on a value of FALSE (or NIL for array elements); otherwise, it takes on the data type of its assigned value. You can assign a new value (and a new data type) to the variable at any time.
-
- Public variables have these properties:
-
-
Once they are created, you can access them anywhere in the application. In other words, public variables are automatically inherited by all routines in the application without having to pass them as arguments or post them as return values.
-
You can hide them from a routine by explicitly creating a private (using PRIVATE or PARAMETERS) or declaring a local (using LOCAL) variable with the same name.
-
They are not released from memory until you explicitly release them using RELEASE, CLEAR ALL, or CLEAR MEMORY.
-
- In this example, the function Volume() is defined without arguments. Instead, the calling routine, Compute(), creates three public variables, nLength, nWidth, and nHeight that are automatically visible to Volume():
- PROCEDURE Compute() PUBLIC nLength := 5, nWidth := 2, nHeight := 4 ? Volume() // Result: 40
FUNCTION Volume() RETURN nLength * nWidth * nHeight
- In the next example, a modified version of Volume() creates a public variable to store the computed volume, getting around having to return a value to the calling routine. Since nVolume is public, it is not released from memory when Volume() returns:
- PROCEDURE Compute() PUBLIC nLength := 5, nWidth := 2, nHeight := 4 Volume() ? nVolume // Result: 40 , this will only compile with -undeclared RETURN
PROCEDURE Volume() PUBLIC nVolume nVolume := nLength * nWidth * nHeight RETURN
- A better solution for the use of the nVolume variable from the last example that will not require the -undeclared commandline option is:
- PROCEDURE Compute() PUBLIC nLength := 5, nWidth := 2, nHeight := 4 MEMVAR nVolume // tell the compiler that nVolume is a Public or private Volume() ? nVolume // Result: 40 RETURN
- or
- PROCEDURE Compute() PUBLIC nLength := 5, nWidth := 2, nHeight := 4 Volume() ? _MEMVAR->nVolume // Result: 40 RETURN
- Please note that this kind of programming is NOT recommended.
- Variable References
- Once a public or private variable is created as demonstrated in the previous two sections, you obtain its value by referring to its name. You might display the value of a variable using a built-in command or function:
- ? nVolume QOut(nVolume)
- or use its value as part of an expression:
- Str(nVolume, 10, 2) + " cubic feet"
- For dynamically scoped variables, you can use the _MEMVAR alias to qualify a variable reference. In some cases, you may have to do this in order to help the compiler resolve what might otherwise be an ambiguous reference (for example, if you have a field variable with the same name as a memory variable and want to use the memory variable in an expression).
- Note: MEMVAR is an abbreviation for memory variable, a term that is synonymous with dynamically scoped variable. Assuming that the database file Measures has fields named nLength, nWidth, and
- nHeight, this example calls Volume() using the field variable values:
- FUNCTION Calculate() PRIVATE nLength := 5, nWidth := 2, nHeight := 3 USE measures ? Volume(nLength, nWidth, nHeight) ...
- To force the function to use the private variables instead of the field variables, you could use the _MEMVAR-> (or, more simply, M->) alias to qualify the variable names:
- FUNCTION Calculate() PRIVATE nLength := 5, nWidth := 2, nHeight := 3 USE measures ? Volume(_MEMVAR->nLength, _MEMVAR->nWidth, _MEMVAR->nHeight) ...
- Of course, it is better to avoid ambiguous situations like the one described above by ensuring that field and variable names are unique. However, the point is that the compiler follows certain default rules for handling ambiguous references. If you do not want to be at the mercy of those defaults, it is best to qualify variable names in all cases.
- MEMVAR Declarations
- Although you may hear them referred to as such, the statements mentioned so far in the discussion of dynamically scoped variables are not declarations. The term declaration refers to a statement whose purpose is to inform the compiler of something—PRIVATE, PARAMETERS, and PUBLIC are statements that generate memory variables at runtime.
- In fact, you never have to declare a dynamically scoped variable to the compiler, which is the reason for their inefficiency. Because they are not created using compile-time declaration statements, the compiler has to generate runtime code for handling such issues as type translation, memory management, and resolving ambiguous references to variable names, since it is possible for several variables with the same name to be visible at one time.
- You can, however, declare dynamically scoped variables with the MEMVAR statement and they will be created as PRIVATE variables:
- FUNCTION Calculate() MEMVAR nLength, nWidth, nHeight nLength := 5 nWidth := 2 nHeight := 3 USE measures ? Volume(nLength, nWidth, nHeight)
- In this case, the MEMVAR statement causes memory variables to take precedence over field variables with the same names, causing Volume() to be called with the private variables.
- Using MEMVAR to declare dynamically scoped variable names to the compiler may make your programs slightly more efficient (especially if you have lots of ambiguous references); however, it will not eliminate the runtime overhead of these variables.
-
-
diff --git a/docs/Help_Spanish/Topics/MigratingappsfromVOtoX.xml b/docs/Help_Spanish/Topics/MigratingappsfromVOtoX.xml
deleted file mode 100644
index c757e60ec1..0000000000
--- a/docs/Help_Spanish/Topics/MigratingappsfromVOtoX.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Migrating apps from VO to X#
-
-
- Migrating apps from VO to X#
-
- In this topic, we will discuss how to migrate applications from Visual Objects (VO) to X#, using the VO XPorter tool from X#.
- When you want to do this, we strongly recommend you to start small. Therefore, we will start with a few VO example programs and describe the steps to take and the necessary adjustments after the conversion.
- The examples
- The examples on the following pages provide a step-by-step introduction to migrating your apps.
- Each example is included with the X# installer and comes with separate "before" and "after" folders to illustrate the changes made during the migration process.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Modifiers.xml b/docs/Help_Spanish/Topics/Modifiers.xml
deleted file mode 100644
index 8b0e87328f..0000000000
--- a/docs/Help_Spanish/Topics/Modifiers.xml
+++ /dev/null
@@ -1,78 +0,0 @@
-
-
-
- Modifiers
-
- ABSTRACT
- DEFERRED
- EXPORT
- FINAL
- FREEZE
- HIDDEN
- INSTANCE
- INTERNAL
- INTRODUCE
- NEW
- OVERRIDE
- PARTIAL
- PRIVATE
- PROTECT
- PROTECTED
- PUBLIC
- SEALED
- STATIC
- SYNC
- VIRTUAL
- Visibility Modifiers
-
-
-
- Modifiers
-
- Modifiers are language keywords that are used to modify the visibility of a program element (function, global, class, property etc), or the way they operate within a type hierarchy.
- There are several groups of modifiers that will be discussed in these subtopics.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Modifiers_Async_Await.xml b/docs/Help_Spanish/Topics/Modifiers_Async_Await.xml
deleted file mode 100644
index 4e29ffa578..0000000000
--- a/docs/Help_Spanish/Topics/Modifiers_Async_Await.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- ASYNC/AWAIT
-
-
- ASYNC/AWAIT
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Modifiers_ClassHierarchy.xml b/docs/Help_Spanish/Topics/Modifiers_ClassHierarchy.xml
deleted file mode 100644
index eb3ca9f7a5..0000000000
--- a/docs/Help_Spanish/Topics/Modifiers_ClassHierarchy.xml
+++ /dev/null
@@ -1,79 +0,0 @@
-
-
-
- Class hierarchy modifiers
-
- /cs
- /vo3
- ABSTRACT
- DEFERRED
- FINAL
- FREEZE
- INTRODUCE
- NEW
- OVERRIDE
- SEALED
- SYNC
- VIRTUAL
-
-
-
- Class hierarchy modifiers
-
- Hierarchy modifiers control the way elements of a class behave within their class hierarchy.
- VIRTUAL/OVERRIDE/NEW
- By default, all methods in .Net are non-VIRTUAL, meaning they cannot be overridden by methods with the same name (and signature - parameter and return types) in descendant classes. In the following example, calling a method from code inside the Parent class, results in calling the version of the method defined in this particular class in the class hierarchy, not the method with the same name and signature defined in the Child class (even though the object we are testing is an instance of the Child class):
- FUNCTION Start() ASVOID LOCAL oTest AS Child oTest := Child{} oTest:DoTest()
CLASS Parent METHOD SomeMethod() ASVOID ? "Parent method was called" METHOD DoTest() ASVOID SELF:SomeMethod() // calls the method of this Parent class, not the same named one defined in the Child class RETURN ENDCLASS
CLASS Child INHERIT Parent METHOD SomeMethod() ASVOID ? "Child method was called" ENDCLASS
- This behavior is different from that of Visual Objects, FoxPro and Xbase++, where ALL methods are always considered VIRTUAL. In order to make a method overridable from descendant classes, it needs to be defined as VIRTUAL. In the following code, calling a VIRTUAL method from code in the Parent class, results in calling the version of the method defined in the Child class, since it has overridden the parent method:
- CLASS Parent METHOD NonVirtualMethod() ASVOID// cannot be overridden in child class ? "Parent non virtual method was called" VIRTUALMETHOD VirtualMethod() ASVOID// can be overridden ? "Parent virtual method was called" METHOD DoTest() ASVOID SELF:NonVirtualMethod() // calls method in parent SELF:VirtualMethod() // calls method in child RETURN ENDCLASS
CLASS Child INHERIT Parent METHOD NonVirtualMethod() ASVOID// this is completely different method to the parent one, even though it has the same name ? "Child non virtual method was called" OVERRIDEMETHOD VirtualMethod() ASVOID// overrides the same named method of the parent class ? "Child virtual method was called" ENDCLASS
- Note that VirtualMethod() in the child class is declared with the OVERRIDE modifier; this tells the compiler that we have intentionally overridden a parent method with the same name. The OVERRIDE modifier is not mandatory in X# and can be omitted, but using it makes the code more self-explanatory and allows the compiler to make additional compile time checks. If OVERRIDE is used on a method to override a parent method that is not VIRTUAL, or it does not even exist (or is spelled with a different name or has a different signature in the parent class), then a compiler error will be reported. For this reason, it is recommended to explicitly declare methods overriding parent methods with the OVERRIDE keyword. It is also possible to enforce the use of the OVERRIDE keyword in the compiler, by enabling the compiler option "Enforce OVERRIDE" (/enforceoverride).
-
- In the above code, the compiler does report a warning on the NonVirtualMethod() defined in the child class: "warning XS0108: 'Child.NonVirtualMethod()' hides inherited member 'Parent.NonVirtualMethod()', use the new keyword if hiding was intended". This issues a warning about the definition of a method in the child class that has the same name as a non-virtual method in the parent class, as this may have been done by accident (either accidentally using the same name, or forgetting to define the base method as virtual). In order to tell the compiler that the use of the same name in a child method was intentional (and prevent the warning), the NEW modifier keyword can be used, which explicitly marks the method as one that does override the base one:
- CLASS Child INHERIT Parent NEWMETHOD NonVirtualMethod() ASVOID// explicitly mark the method as new one, different to the parent method ? "Child non virtual method was called" OVERRIDEMETHOD VirtualMethod() ASVOID// overrides the same named method of the parent class ? "Child virtual method was called" ENDCLASS
- For already existing code ported from older systems like Visual Objects where methods are always VIRTUAL, it can be tedious to manually add the VIRTUAL modifier keyword to all the methods that need it. For this reason, you can instruct the compiler to automatically treat ALL methods as virtual, by using the "All instance methods virtual" (/vo3) compiler option. However, it is highly recommended to instead review the code and manually add the VIRTUAL modifier only where it is truly needed.
-
- Note that a method in a child class can override a parent class method only if it has the exact same signature with it, meaning it has the exact same name (even the exact same casing of the name, if the Case sensitive type names (/cs) compiler option is enabled), parameter count and types and return type with the base method. If the two methods are different on any of those aspects, then they are considered as completely different methods, and one cannot override the other:
- CLASS Parent VIRTUALMETHOD VirtualMethod(n ASINT) ASVOID// child class has same named method but with different signature ENDCLASS
CLASS Child INHERIT Parent OVERRIDEMETHOD VirtualMethod(c ASSTRING) ASINT// compiler error XS0115: 'VirtualMethod': no suitable method found to override RETURN 0 ENDCLASS
The VIRTUAL/OVERRIDE/NEW modifiers do not apply to methods only, but also to properties or ACCESS/ASSIGN pairs (and also to events, but it makes little sense in declaring/overriding virtual events):
METHOD DoTest() ASVOID ? SELF:TestProp // child, because the property is overridden in the child class ? SELF:TestAccess // parent, because the access is not virtual RETURN ENDCLASS
CLASS Child INHERIT Parent OVERRIDEPROPERTY TestProp ASSTRINGGET "child" NEWACCESS TestAccess ASSTRING RETURN "child" ENDCLASS
- Finally, also class fields can be declared as NEW (but not as VIRTUAL), in order to differentiate them from fields with the same name in a parent class:
- FUNCTION Start() ASVOID Child{}
CLASS Parent EXPORT cField := "parent" ASSTRING CONSTRUCTOR() ? SELF:cField // parent, refers to the filed defined in the parent class ENDCLASS
CLASS Child INHERIT Parent NEWEXPORT cField := "child" ASSTRING CONSTRUCTOR() SUPER() ? SELF:cField // child, refers to the filed defined in the parent class ENDCLASS
- Please note that the XBase++ dialect also has the modifiers:
-
-
-
- DEFERRED
-
-
- Synonym for ABSTRACT
-
-
-
-
- INTRODUCE
-
-
- Synonym for NEW
-
-
-
-
- SYNC
-
-
- Code inside the method is protected from running simultaneously in different threads
-
-
-
- ABSTRACT/SEALED
- Using the SEALED modifier on a class, prevents it from being inherited by a child class.
- This can be useful in order to prevent users of a class/library to alter its functionality in a subclass and possibly introduce problems in it.
- It also allows the compiler to emit more efficient code, because it knows that there will be no subclasses of a type.
- SEALEDCLASS Parent ENDCLASS
CLASS Child INHERIT Parent // compiler error XS0509: cannot derive from sealed type 'Parent' ENDCLASS
- SEALED can also be used on specific (virtual) methods/properties to prevent overriding only them in a subclass:
- FUNCTION Start() ASVOID Child{}:DoTest()
CLASS Base VIRTUALMETHOD VirtualMethod() ASVOID ? "base" METHOD DoTest() ASVOID SELF:VirtualMethod() // parent, because method is overridden in the parent class, but cannot be overridden in the subclass of parent ENDCLASS
CLASS Parent INHERIT Base SEALEDOVERRIDEMETHOD VirtualMethod() ASVOID ? "parent" ENDCLASS
CLASS Child INHERIT Parent // compiler error // OVERRIDE METHOD VirtualMethod() AS VOID // compiler error XS0239: cannot override method because it is sealed NEWMETHOD VirtualMethod() ASVOID// can only define a NEW method with the same name and signature, which does not override the parent method ? "child" ENDCLASS
- The ABSTRACT modifier can be used on a class in order to prevent it from being accidentally directly instantiated. Only classes inheriting (and implementing additional functionality) from an abstract class can be instantiated. This is useful for classes that implement base functionality, but for which it does not make sense to create an instance of them directly (like the Control class in System.Windows.Forms or the same named class in the VOSDK):
- FUNCTION Start() ASVOID LOCAL o ASOBJECT o := Child{} // OK o := Parent{} // Compiler error XS0144: cannot create an instance of the abstract type ABSTRACTCLASS Parent ENDCLASS
CLASS Child INHERIT Parent ENDCLASS
- Abstract classes can also define abstract methods or properties, which dictates that it is mandatory to implement them in classes inheriting from the abstract class. Abstract methods are implicitly virtual so they can be overridden, and it is a compiler error not providing an implementation in a child class:
- ABSTRACTCLASS Parent METHOD BasicFunctionality() ASVOID// does not need to be overriden in subclass ABSTRACTMETHOD MustImplementInChild() ASVOID// implementation must be defined in subclasses ENDCLASS
CLASS Child INHERIT Parent // Omitting this would result to a compiler error that Child class does not implement inherited abstract method OVERRIDEMETHOD MustImplementInChild() ASVOID ENDCLASS
- Please note that XBase++ dialect used the modifier FINAL, which is equivalent to SEALED. The FREEZE modifier is not supported by X#.
-
-
diff --git a/docs/Help_Spanish/Topics/Modifiers_Others.xml b/docs/Help_Spanish/Topics/Modifiers_Others.xml
deleted file mode 100644
index 0dcb5711b4..0000000000
--- a/docs/Help_Spanish/Topics/Modifiers_Others.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- Other modifiers
-
- EXTERN
- PARTIAL
- UNSAFE
-
-
-
- Other modifiers
-
- PARTIAL
- Using the PARTIAL modifier on a class declaration, instructs the compiler that the class definition and its members (methods, properties etc) may span in multiple program files in the current application/library. By default (when not using the PARTIAL modifier), all members of a class are expected to be defined in a single file, and if they span in multiple files, all of the CLASS...END CLASS definitions of that class need to be marked as PARTIAL:
- // file code1.prg PARTIALCLASS ClassSpanningInMultipleFiles // omitting PARTIAL would result to compiler error on missing partial modifier on declaration of type METHOD MethodInFile1() ASVOID ENDCLASS
// file code2.prg PARTIALCLASS ClassSpanningInMultipleFiles PROPERTY PropertyInFile2() ASLOGIC GET RETURN TRUE ENDGET ENDPROPERTY ENDCLASS
- Note that all members of a partial class need to be defined in the same assembly. It is NOT possible to use the PARTIAL modifier to define members of a class in separate assemblies/libraries.
-
- EXTERN
- The EXTERN modifier tells the compiler that a method is implemented externally, so it has no body in the code itself. Most commonly, EXTERN is used together with the DllImport attribute (System.Runtime.InteropServices.DllImportAttribute), which specifies exactly where the method is implemented (usually in a Win32 API dll) and how it needs to be called. When using that, the method needs to be declared also as static:
- USING System.Runtime.InteropServices FUNCTION Start() ASVOID WinAPICalls.MessageBox(IntPtr.Zero, "Calling unmanaged code through an EXTERN method", "EXTERN modifier sample", 0)
STATICCLASS WinAPICalls [DllImport("user32.dll", CharSet := CharSet.Unicode)]; STATICEXTERNMETHOD MessageBox(hWnd AS IntPtr, text ASSTRING , caption ASSTRING , type ASDWORD ) ASINT ENDCLASS
- Note that it is a compiler error for an EXTERN method to directly return a value, since its complete implementation is provided externally.
- UNSAFE
- The UNSAFE modifier on a method specifies that its entire body will run in an unsafe context, meaning it can use pointers to data and manipulate memory directly. The unsafe modifier can be used only when the compiler option Allow unsafe code (/unsafe) is enabled:
- FUNCTION Start() ASVOID ? UnsafeMethods.GetByte2of4(0x10203040) // 32 (hex 20)
CLASS UnsafeMethods UNSAFESTATICMETHOD GetByte2of4(d ASDWORD) ASBYTE LOCAL p ASBYTEPTR p := (BYTEPTR) @d // get direct pointer to the data RETURN p[3] ENDCLASS
- When only a small part of the method body involves pointers or other potentially unsafe operations, it is more common to declare a BEGIN UNSAFE block for it, instead of marking the whole method as unsafe:
- CLASS UnsafeMethods STATICMETHOD GetByte2of4(d ASDWORD) ASBYTE LOCAL b ASBYTE ? "Begin of unsafe possibly code executing" BEGINUNSAFE// code inside this block uses pointer operations LOCAL p ASBYTEPTR p := (BYTEPTR) @d // get direct pointer to the data b := p[3] ENDUNSAFE ? "End of unsafe code"
RETURN b ENDCLASS
- Note that writing code that uses pointers is strongly discouraged (as the code cannot be verified by the .Net runtime for correct usage and can destabilize the running application) and needs to be used with extreme caution and only when it is absolutely necessary to do so.
-
-
diff --git a/docs/Help_Spanish/Topics/Modifiers_Static.xml b/docs/Help_Spanish/Topics/Modifiers_Static.xml
deleted file mode 100644
index 908efec04a..0000000000
--- a/docs/Help_Spanish/Topics/Modifiers_Static.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- STATIC modifier
-
- STATIC
-
-
-
- STATIC modifier
-
- The STATIC modifier has a different meaning depending on whether it is used on a class or its members, on a FUNCTION/GLOBAL or on a LOCAL variable.
- Static classes and members
- Static members
- The STATIC modifier on a member of a class (method, constructor, property, field, event) declares a member which belongs to the class itself, instead of to an instance of the class. Normal (instance) methods and other members can be called by using an instance of the class (for example through SELF, or a local variable holding such an instantiated object) with the colon (":") operator (also with the dot "." operator if the compiler option /allowdot is enabled), while static members can be accessed directly through the class itself, using the dot operator:
- FUNCTION Start() ASVOID LOCAL oInstance AS TestClass oInstance := TestClass{} ? oInstance:instance_field ? oInstance:InstanceMethod() ? oInstance:InstanceProperty ? TestClass.static_field ? TestClass.StaticMethod() ? TestClass.StaticProperty
- CLASS TestClass EXPORT instance_field := "instance field" ASSTRING STATICEXPORT static_field := "static field" ASSTRING METHOD InstanceMethod() ASSTRING RETURN "Instance method" PROPERTY InstanceProperty() ASSTRINGGET "Instance property" STATICMETHOD StaticMethod() ASSTRING RETURN "Static method" STATICPROPERTY StaticProperty() ASSTRINGGET "Instance property" ENDCLASS
- A static method is very similar to a common function and can be used in the same way, but it has the advantage that it is encapsulated within a class that may contain other related static or non-static members. Like functions, static methods cannot use instance members of the class with SELF; but they can access other static members. Methods with related functionality can be grouped together under the same class, offering much better intellisense support in the editor (typing a dot after a class name will show a list of all its static members) and makes the code more structured. For example, the System.Math class offers a lot of mathematical functions, all grouped together under a single class, making it easier to find and use, rather than having several standalone functions offering the same functionality. Similarly, a static field can be regarded as a GLOBAL, but again structured under a class. Any method of a class that is not using SELF in its body (so is not accessing any instance members) is a good candidate to be declared as static.
- Static constructor
- It is also possible to define a single static constructor per class, which is guaranteed to be called automatically just before any static member (method, field, etc.) of the class is accessed for the first time. A static constructor must have no parameters and cannot be overloaded. Typical use of a static constructor is to initialize static fields:
- FUNCTION Start() ASVOID ? TestClass.static_field // adjusted by static constructor
CLASS TestClass STATICEXPORT static_field := "initial value" ASSTRING STATICCONSTRUCTOR() ? TestClass.static_field // initial value TestClass.static_field := "adjusted by static constructor" ENDCLASS
- Note that it is not allowed to define a static destructor. If you need to clean up data stored inside a static class, it is recommended to register a ProcessExit event handler in the AppDomain class.This will be called when the application ends.
- FUNCTION Start() ASVOID
CLASS TestClass STATICCONSTRUCTOR() AppDomain.CurrentDomain:ProcessExit += EventHandler{CurrentDomain_ProcessExit}
staticmethod CurrentDomain_ProcessExit(sender asobject, e as EventArgs) asvoid // clean up return ENDCLASS
- Static class
- When a class is designed to hold only static members, it can be declared as being static itself. Doing so allows the compiler to check every member of the class and ensure that none are accidentally declared as non-static:
- STATICCLASS StaticClass STATICEXPORT static_field ASSTRING EXPORT accidental_instance ASSTRING// compiler error XS0708: cannot declare instance members in a static class
STATICMETHOD Static_method() ASVOID METHOD Accidental_Instance_method() ASVOID// compiler error XS0708: cannot declare instance members in a static class ENDCLASS
- Static functions and globals
- Declaring a function or global as static, restricts its visibility to the code file where it is declared only. This allows multiple files to declare functions and globals with the same name, with each being visible only within its respective file:
- STATICGLOBAL GlobalVisibleOnlyInThisFile ASINT STATICFUNCTION FunctionVisibleOnlyInThisFile() ASVOID
- Static local
- Declaring a LOCAL variable as STATIC, causes it to be initialized with a value only once, being the first time that the method, function or other entity where it is declared is called. The local variable retains its previous value on subsequent times the code is called:
- FUNCTION Start() ASVOID ? TestStaticLocal() // 2 ? TestStaticLocal() // 3 ? TestStaticLocal() // 4
FUNCTION TestStaticLocal() ASINT STATICLOCAL nStaticLocal := 1 ASINT// gets initialized to 1 only the first time the function is called nStaticLocal ++ // the current value will be retained the next time the function is called RETURN nStaticLocal
-
-
diff --git a/docs/Help_Spanish/Topics/Modifiers_Visibility.xml b/docs/Help_Spanish/Topics/Modifiers_Visibility.xml
deleted file mode 100644
index 7fa7a90778..0000000000
--- a/docs/Help_Spanish/Topics/Modifiers_Visibility.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- Access/Visibility modifiers
-
- EXPORT
- HIDDEN
- INTERNAL
- PRIVATE
- PROTECT
- PROTECTED
- PUBLIC
- STATIC
-
-
-
- Access/Visibility modifiers
-
- Access / Visibility modifiers
- Access modifiers restrict the visibility of program elements:
-
-
-
PUBLIC/EXPORT: A public function, global, type (class, structure, delegate etc) or type member (field, method, property, event etc) is visible to all code within the same assembly (exe or dll) where it is declared and assemblies referenced by the declaring assembly. This is the default in X#.
-
PROTECT/PROTECTED: The PROTECT(ED) keyword can be applied only to type members and restrict their visibility to code within the same type and classes that inherit from that type
-
INSTANCE: A unique modifier keyword to X# (and Visual Objects), very similar to PROTECT, but applies only to class fields and has different semantics to PROTECT, on the way it is used by code within the same class (see sample below).
-
PRIVATE/HIDDEN: Also applies to type members and is more restrictive than PROTECT, as it limits the member visibility to only code within the type where it is declared (not to classes inheriting from that type). If you declare a field or method as PRIVATE then the compiler may produce a compiler warning xs0169 when it detects that that field or method is never called inside the class.
-
INTERNAL: Restricts the visibility of a type or member only to code from the same assembly (dll or exe). An internal member is not visible to any code outside the defining assembly, not even to classes inheriting from this class declared in other assemblies. Can be combined with PROTECTED, so that an INTERNAL PROTECTED member can be seen only from within the same class and also from inheriting classes that are defined in the same assembly, but not from inheriting classes that are defined in other assemblies.
-
The XBase++ dialect also has the modifier STATIC, which means that the class is only visible in the source file where it is used.
-
-
- Note: It is still possible to explicitly specify certain assemblies where internal types and members of an assembly are visible, by using the InternalsVisibleTo attribute. See documentation for System.Runtime.CompilerServices.InternalsVisibleToAttribute for more information.
- INTERNALPROCEDURE InternalProc() // procedure accessible only from within the same assembly INTERNALGLOBAL InternalGlobal ASINT// global accessible only from within the same assembly
PUBLICCLASS TestClass // accessible from everywhere EXPORT Export_field ASINT// accessible from everywhere PROTECT Protected_field ASINT// accessible to this class and classes inherited from it INTERNALPROTECT Internal_Protected_field ASINT// accessible to this class and classes inherited from it, defined in this same assembly only PRIVATEMETHOD Private_Method() ASVOID// accessible only from code inside this particular class ENDCLASS
- PROTECTED vs HIDDEN
- A compatibility feature for code derived from Visual Objects, INSTANCE applies to fields and is similar to PROTECT, but has different semantics when a property (or ACCESS) is defined with the same name. When a PROTECT field is used and an ACCESS/ASSIGN pair (or PROPERTY) is defined with the same name in the type, then any code within that class that tries to access this member, always refers to the field. But when the member is declared with the INSTANCE keyword, the compiler binds the name to the ACCESS instead:
- FUNCTION Start() ASVOID TestClass{}:DoTest()
CLASS TestClass PROTECT Protected_member := "field" ASSTRING INSTANCE Instance_member := "field" ASSTRING ACCESS Protected_member ASSTRING RETURN "access" ACCESS Instance_member ASSTRING RETURN "access" METHOD DoTest() ASVOID ? SELF:Protected_member // field ? SELF:Instance_member // access, because the field is defined with the INSTANCE keyword ENDCLASS
- This feature is a leftover from old Visual Objects versions that were emitting INSTANCE members for every control in the Window Editor and is depreciated in X#, but still available for compatibility reasons.
-
-
diff --git a/docs/Help_Spanish/Topics/Namespaces2.xml b/docs/Help_Spanish/Topics/Namespaces2.xml
deleted file mode 100644
index 97f025068d..0000000000
--- a/docs/Help_Spanish/Topics/Namespaces2.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- Namespaces
-
-
- Namespaces
-
- A Namespace is a prefix to item names that provides a logical grouping of types and other .Net elements, making it easier to structure together items that have a common purpose and avoid naming conflicts. Due to the vast amount of libraries and classes available in .Net (in System and third-party libraries and in every application written in .Net), using simple small names without a namespace would have led to a lot of naming conflicts, making it impossible to distinguish between each other. For example, there's a type named "Button" (representing a Button control) in the Windows Forms system library, another for WPF, another one in the VOSDK GUI classes, and of course the new typed VOSDK GUI classes library has one, too. Furthermore, it's very likely that dozens of other custom control libraries include a same named type as well! In order to distinguish among all them, an additional prefix name (namespace) has been added to each version of the type:
-
-
-
System.Windows.Forms.Button // Windows forms
-
System.Windows.Controls.Button // WPF
-
VO.Button // VOGUI library
-
XSharp.VO.Button // Typed SDK GUI library
-
-
- For the full class name System.Windows.Forms.Button, everything before the final dot (System.Windows.Forms) is called the namespace of the class, while the rest is called the short class name. Note that a namespace is not something concrete, and it does not exist as a separate entity in .Net assemblies. It is only a convention to use a descriptive name prefix for all class names and is not mandatory. Using the dot as name part separator is also a convention in .Net, even though it would have been equally valid to choose another character, such as an underscore, for the same purpose, resulting in the name System_Windows_Forms_Button for the winforms class name, where "System_Windows_Forms" would have been the namespace part of the name.
-
- Also by convention, namespace and type names are usually structured in the following format:
- <Company name>.<Library name>.<Optional further group names>.<Short type name>
- This has been applied in the name XSharp.VO.Button, where "XSharp" is the company name, "VO" represents the library and "Button" is the actual class (short) name. The optional additional group names provide further better structuring of the type names, often used in large libraries where it is important to logically group together the large amount of available items.
- Specifying namespaces to type names
- In X#, there are several ways to provide a namespace to types/classes defined in the code. The most common way is to use the BEGIN...END NAMESPACE block statement:
- BEGINNAMESPACE OurCompany.CommonLibrary CLASS GeneralUseType // ... ENDCLASS ENDNAMESPACE
- Every type defined inside the block will automatically have its name prefixed by the compiler with the provided namespace, so the class in the example above would become OurCompany.CommonLibrary.GeneralUseType. Additionally, BEGIN NAMESPACE blocks can be nested (to any level), and the above could have been equally been written as follows:
- BEGINNAMESPACE OurCompany BEGINNAMESPACE CommonLibrary CLASS GeneralUseType // ... ENDCLASS ENDNAMESPACE ENDNAMESPACE
- Another option is to provide the namespace part of the name in the class declaration directly:
- CLASS OurCompany.CommonLibrary.GeneralUseType // ... ENDCLASS
- Finally, it is possible to define a Default Namespace in the project properties (which maps to the -ns compiler option). When defining this, all class names in the code that have not been explicitly assigned a namespace, automatically get the one provided in the project option. This is particularly useful for applications and libraries ported from Visual Objects or other systems not supporting the concept of namespaces, so all types in them used simple class names. To avoid having to explicitly provide namespace names in a large number of code files, the project option can be used instead.
- Using types with namespaces
- Typically, in order to use a type in code, its full class name (including the namespace part) needs to be used:
- FUNCTION Start() ASVOID LOCAL oUse AS OurCompany.CommonLibrary.GeneralUseType oUse := OurCompany.CommonLibrary.GeneralUseType{}
- If the namespace part was not included, the compiler would not be able to resolve the class name. However, since always using such long names can be tedious and may lead to code bloat, it is common practice to specify commonly used namespaces at the beginning of each code file in USING statements:
- USING OurCompany.CommonLibrary
FUNCTION Start() ASVOID LOCAL oUse AS GeneralUseType oUse := GeneralUseType{}
- The USING statement instructs the compiler every time it finds a class name that it cannot resolve, to try resolving it by prefixing it with all the namespace names provided in USING statements in the given file. Of course, if multiple types used in the code have the same short name with different namespaces, it is not possible to have a USING statement for each one of them, as that would lead to a name conflict, making it impossible for the compiler to distinguish which exact class is used in each case.
-
- Also note that any code between a BEGIN...END NAMESPACE statement, additionally automatically resolves short type names defined in it to full type names using the namespace provided in the statement. Therefore, it is not necessary to provide a namespace in the class name in this code:
- BEGINNAMESPACE OurCompany.CommonLibrary CLASS GeneralUseType ENDCLASS CLASS AnotherClass METHOD Test() ASVOID LOCAL oUse AS GeneralUseType // not necessary to provide the namespace oUse := GeneralUseType{} ENDCLASS ENDNAMESPACE
- Implicit namespace lookup
- Especially for libraries with the Default namespace option (see above) provided, it is possible for applications that reference them to use their classes with their short names without needing to provide USING statements. This can be done by enabling the Enable Implicit Namespace lookup project option (which maps to the /ins compiler option). Every such library includes its default namespace as information in an assembly attribute and when that option is used, the compiler automatically resolves type names also by using that default namespace in the library. This is used in the VOSDK classes for example, so that all classes defined in those libraries can be used without the need to provide USING VO statements, in all files of the applications that reference those libraries.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Native-Types.xml b/docs/Help_Spanish/Topics/Native-Types.xml
deleted file mode 100644
index 657cc2be8d..0000000000
--- a/docs/Help_Spanish/Topics/Native-Types.xml
+++ /dev/null
@@ -1,298 +0,0 @@
-
-
-
- Simple (Native) Types
-
-
- Simple (Native) Types
-
- By simple data types, we mean data types that are not primarily used to hold other data, e.g. Objects, Structures, Arrays, that we will see later.
-
- Most data types are identical across all .Net languages, which makes it easier to use assemblies written in different .Net languages within one application - one of the main benefits of the framework. The simple data types are divided in various categories, with some categories containing multiple types. The following table groups data types by category:
-
-
-
-
-
- Type
-
-
- Category
-
-
- .Net Name
-
-
- Size in Bits
-
-
-
-
- BYTE
-
-
- Unsigned Integer
-
-
- Byte
-
-
- 8
-
-
-
-
- CHAR
-
-
- Character
-
-
- Char
-
-
- 16
-
-
-
-
- DWORD
-
-
- Unsigned Integer
-
-
- UInt32
-
-
- 32
-
-
-
-
- DECIMAL
-
-
- Numeric
-
-
- Decimal
-
-
- 96
-
-
-
-
- DYNAMIC
-
-
- Multi purpose
-
-
- Dynamic
-
-
- Reference (32 or 64 bits)
-
-
-
-
- INT
-
-
- Signed Integer
-
-
- Int32
-
-
- 32
-
-
-
-
- INT64
-
-
- Signed Integer
-
-
- Int64
-
-
- 64
-
-
-
-
- LOGIC
-
-
- Logic
-
-
- Boolean
-
-
- 8
-
-
-
-
- LONGINT
-
-
- Signed Integer
-
-
- Int32
-
-
- 32
-
-
-
-
- OBJECT
-
-
- Multi purpose
-
-
- Object
-
-
- Reference (32 or 64 bits)
-
-
-
-
- PTR
-
-
- Multi purpose
-
-
- Intptr
-
-
- Reference (32 or 64 bits)
-
-
-
-
- REAL4
-
-
- Floating Point
-
-
- Single
-
-
- 32
-
-
-
-
- REAL8
-
-
- Floating Point
-
-
- Double
-
-
- 64
-
-
-
-
- SBYTE
-
-
- Signed Integer
-
-
- SByte
-
-
- 8
-
-
-
-
- SHORT
-
-
- Signed Integer
-
-
- Int16
-
-
- 16
-
-
-
-
- STRING
-
-
- String
-
-
- String
-
-
- Reference (32 or 64 bits)
-
-
-
-
- UINT64
-
-
- Unsigned Integer
-
-
- Uint64
-
-
- 64
-
-
-
-
- VOID
-
-
- Not a type
-
-
- Void
-
-
- 0
-
-
-
-
- WORD
-
-
- Unsigned Integer
-
-
- UInt16
-
-
- 16
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/New-features.xml b/docs/Help_Spanish/Topics/New-features.xml
deleted file mode 100644
index ffe1245fdb..0000000000
--- a/docs/Help_Spanish/Topics/New-features.xml
+++ /dev/null
@@ -1,165 +0,0 @@
-
-
-
- New language features
-
-
- New language features
-
-
- Below is a list of some of the most visible new language features in the Core language of X#, compared to Visual Objects and Vulcan.
- As you can see many new keywords were introduced, but these are positional: they will also be recognized as Identifiers on other places, so there is very little chance that you will have to make changes to avoid naming conflicts.
-
-
-
-
- FEATURE
-
-
- Description
-
-
-
-
- DEFINE <id> := <Expression>
-
-
- The VO Define is back again in X#. It will be compiled into a constant of the Globals class, the same class in which all Functions and Methods are implemented. The biggest advantage of a DEFINE over the preprocessor DEFINEs in Vulcan.NET is that there is no longer a chance that a DEFINE with the same name as a Method, Property or Variable will lead to incomprehensible compiler errors.
-
-
-
-
- USING STATIC <Name>
-
-
- The STATIC modifier for USING (note that the # sign is no longer needed) allows you to name a static class. When you do so, you can then use the methods of this class as functions. For example: USINGSTATIC System.Console FUNCTION Start asVOID WriteLine("X# is cool!") RETURN
-
-
-
-
- BEGIN USING <Var> <Statements> END [USING]
-
-
- The USING block allows you to control the lifetime of a variable. If <Var> has a destructor, it will be automatically destructed once the block has finished.
-
-
-
-
- SWITCH <Expression> CASE <Const> <Statements> CASE <Const2> CASE <Const3> <Statements> OTHERWISE <Statements> END [SWITCH]
-
-
- The SWITCH statement generates a more efficient jump structure than the DO CASE command. Also, the expression is only evaluated once.
-
-
-
-
- BEGIN UNSAFE <Statements> END [UNSAFE]
-
-
- Allows unsafe code in the context of this block, regardless of the compiler setting for the project as a whole.
-
-
-
-
- BEGIN CHECKED <Statements> END [CHECKED]
- Also allowed as expression
- x := CHECKED(y)
-
-
- The statements inside the block will have checked conversions, regardless of the compiler setting for the project as a whole.
-
-
-
-
- BEGIN UNCHECKED <Statements> END [UNCHECKED]
- Also allowed as expression
- x := UNCHECKED(y)
-
-
- The statements inside the block will have unchecked conversions, regardless of the compiler setting for the project as a whole.
-
-
-
-
- VAR <Identifier> := <Expression>
-
-
- This is a synonym for LOCAL IMPLIED
-
-
-
-
- CLASS <Id> < <ParamName> > WHERE <TypeConstraints> <Classmembers> END [CLASS]
-
-
- Creating Generic classes is now supported in X#, with all the features that C# also has For example: CLASS MyList<T> WHERE T ISCLASS .. ENDCLASS or CLASS MyList<T> WHERE T IS ICustomer, NEW() .. ENDCLASS
-
-
-
-
- ASYNC - AWAIT
-
-
- The ASYNC AWAIT infratructure is fully available inside X#.
-
-
-
-
- <Expression> IS <Type>
-
-
- Allows to check an expression for a type. Can be used instead of IsInstanceOf() and will perform better.
-
- Conditional access for properties, methods etc. For example: nCount := MyList?:Count This translates to something like: VAR temp := MyList IF temp != NULL nCount := temp:Count ENDIF The expression on the left-hand side of the question mark will be evaluated only once!
-
-
-
-
- <Expression> DEFAULT <Expression>
-
-
- The default operator allows you to inline a check for NULL: lResult := Foo() DEFAULT Bar() This translates to the same as: lResult := Foo() IF lResult == NULL lResult := Bar() ENDIF Foo() will be evaluated only once. Bar() will only be evaluated when the result is NULL.
-
-
-
-
- y := CHECKED(x)
-
-
- Tells the compiler to generate code that checks for overflow.
-
-
-
-
- y := UNCHECKED(x)
-
-
- Tells the compiler to generate code that does NOT check for overflow.
-
-
-
-
- LINQ Query expressions are now supported: VAR CustQuery = FROM Cust in Customers ; WHERE Cust.City = "Athens" ; ORDER BY Cust.Zipcode Select Cust
-
-
- The full LINQ feature set will be supported by X#: FROMLETWHEREJOINORDERBYEQUALSINTO
-
-
-
-
- YIELD RETURN <Value>
-
-
- Can be used in a method declared as Enumerator of a type. This will instruct the compiler to automatically generate a class that implemented an enumerator and return to the calling code directly on the YIELD RETURN line. The next time the Iterator is called, the code will remember where the code was the previous time it was executed, and it will continue on the next statement after the YIELD RETURN line.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Nuget-Packages.xml b/docs/Help_Spanish/Topics/Nuget-Packages.xml
deleted file mode 100644
index de6e51bf72..0000000000
--- a/docs/Help_Spanish/Topics/Nuget-Packages.xml
+++ /dev/null
@@ -1,119 +0,0 @@
-
-
-
- Nuget Packages
-
-
- Nuget Packages
-
- XSharp 3 comes with nuget packages for the runtime. These packages contain assemblies and support files for both .Net Framework 4.6 and .Net 8.0
- There are the following packages:
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/OBJECT.xml b/docs/Help_Spanish/Topics/OBJECT.xml
deleted file mode 100644
index ff1b0a5b28..0000000000
--- a/docs/Help_Spanish/Topics/OBJECT.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- OBJECT
-
- OBJECT
-
-
-
- OBJECT
-
- The OBJECT keyword is a generic type from which all objects in .Net automatically inherit.
-
- X# does not require a class to declare inheritance from Object because the inheritance is implicit.
-
- Because all classes in the .NET Framework are derived from Object, every method defined in the Object class is available in all objects in the system. Derived classes can and do override some of these methods, including:
-
-
-
Equals - Supports comparisons between objects.
-
-
-
-
Finalize - Performs cleanup operations before an object is automatically reclaimed.
-
-
-
-
GetHashCode - Generates a number corresponding to the value of the object to support the use of a hash table.
-
-
-
-
ToString - Manufactures a human-readable text string that describes an instance of the class.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Operator_NameOf.xml b/docs/Help_Spanish/Topics/Operator_NameOf.xml
deleted file mode 100644
index 66a3899362..0000000000
--- a/docs/Help_Spanish/Topics/Operator_NameOf.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- NameOf Operator
-
-
- NameOf Operator
-
- A nameof expression produces the name of a variable, type, or member as the string constant:
-
- You can use a nameof expression to make the argument-checking code more maintainable:
-
- Syntax
- NameOf( identifier )
-
- FUNCTION Test(cName asSTRING) IF cName == null thrownew ArgumentNullException(nameof(cName), i"{nameof(cName)} cannot be null"); endif
-
-
diff --git a/docs/Help_Spanish/Topics/Operator_SizeOf.xml b/docs/Help_Spanish/Topics/Operator_SizeOf.xml
deleted file mode 100644
index 4053b46a7f..0000000000
--- a/docs/Help_Spanish/Topics/Operator_SizeOf.xml
+++ /dev/null
@@ -1,135 +0,0 @@
-
-
-
- SizeOf Operator
-
-
- SizeOf Operator
-
- The sizeof operator returns the number of bytes occupied by a variable of a given type. The argument to the sizeof operator must be the name of an unmanaged type or a type parameter that is constrained to be an unmanaged type.
-
- Syntax
- SizeOf( type )
-
-
-
-
- Expression
-
-
- Constant value
-
-
-
-
- sizeof(sbyte)
-
-
- 1
-
-
-
-
- sizeof(byte)
-
-
- 1
-
-
-
-
- sizeof(short)
-
-
- 2
-
-
-
-
- sizeof(word)
-
-
- 2
-
-
-
-
- sizeof(int)
-
-
- 4
-
-
-
-
- sizeof(dword)
-
-
- 4
-
-
-
-
- sizeof(int64)
-
-
- 8
-
-
-
-
- sizeof(uint64)
-
-
- 8
-
-
-
-
- sizeof(char)
-
-
- 2
-
-
-
-
- sizeof(real4)
-
-
- 4
-
-
-
-
- sizeof(real8)
-
-
- 8
-
-
-
-
- sizeof(decimal)
-
-
- 16
-
-
-
-
- sizeof(logic)
-
-
- 1
-
-
-
-
-
- For some types, the size depends on how the program is running, e.g. in 32 bits mode or 64 bits mode. In that case, you may see an error message that the SizeOf operator requires the /unsafe compiler option.
- Note
- _sizeof() (with a leading underscore and parenthesis) is also supported for compatibility with Visual Objects and is synonymous with sizeof.
-
-
-
diff --git a/docs/Help_Spanish/Topics/Operator_Typeof.xml b/docs/Help_Spanish/Topics/Operator_Typeof.xml
deleted file mode 100644
index 12820b25fa..0000000000
--- a/docs/Help_Spanish/Topics/Operator_Typeof.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- TypeOf operator
-
-
- TypeOf operator
-
-
- In .Net, all types are inherited from the System.Type.
-
- Syntax
- TypeOf( type )
-
- The TypeOf operator gets the System.Type of a type.
- This code sample shows the use case of typeof operator using C#.
-
- Console.WriteLine(typeof(String)) Console.WriteLine(typeof(USUAL))
- The following example demonstrates several ways to obtain a type
- Example
- FUNCTION Start() ASVOID LOCAL t1 AS Type LOCAL t2 AS Type LOCAL t3 AS Type LOCAL t4 AS Type LOCAL s ASSTRING s := "Live long and prosper!" t1 := s:GetType() t2 := typeof(System.String) t3 := typeof(STRING) t4 := Type.GetType( "System.String" ) ? "Type objects are equal:", t1 == t2 .and. t1 == t3 .and. t1 == t4 ? t1:Name ? t1:FullName ? t1:AssemblyQualifiedName RETURN
- Note
- _typeof() (with a leading underscore and parenthesis) is also supported for compatibility with Visual Objects and is synonymous with sizeof.
-
-
diff --git a/docs/Help_Spanish/Topics/Operators.xml b/docs/Help_Spanish/Topics/Operators.xml
deleted file mode 100644
index 1b63f4fe84..0000000000
--- a/docs/Help_Spanish/Topics/Operators.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- Operators
-
-
- Operators
-
- X# has many operators. These are:
-
-
-
-
- The Tools/Options dialog contains some settings that are used by these custom editors:
-
-
-
- There is a second page with some settings for the other editor and for some other relevant settings:
-
-
-
- The values for the settings are stored in the file XSharp\ProjectSystemSettings.json in your roaming profile folder.
-
-
-
diff --git a/docs/Help_Spanish/Topics/PSZ-Type.xml b/docs/Help_Spanish/Topics/PSZ-Type.xml
deleted file mode 100644
index 4a6320584c..0000000000
--- a/docs/Help_Spanish/Topics/PSZ-Type.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- PSZ Type
-
- PSZ
- XSharp.__Psz
-
-
-
- PSZ Type
-
- This structure contains a pointer to a memory block with an Ansi string. When created with String2Psz() and Cast2Psz(), the compiler will take care of releasing these memory blocks. When created with other runtime functions, such as StringAlloc(), you are responsible of releasing the memory yourself.
- The internal type name for this type is XSharp.__Psz
-
- Note
- Please do not use the PSZ type for new code. It is only included for backward compatibility.
- Even new code that calls the windows API can use a better alternative, for example using the [DllImportAttribute] from the framework.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/PSZ.xml b/docs/Help_Spanish/Topics/PSZ.xml
deleted file mode 100644
index 9a2f54cfad..0000000000
--- a/docs/Help_Spanish/Topics/PSZ.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- PSZ
-
- PSZ
-
-
-
- PSZ
-
- The PSZ type is a pointer type that points to a null terminated sequence of zero or more bytes, typically representing a printable character string. This type is for backward compatibility only. Don't use this type in new code unless you have to.
- Implementation
- The PSZ type is implemented in the class XSharp.__Psz.
- The Usual type of PSZ is 17.
-
-
diff --git a/docs/Help_Spanish/Topics/PTR2.xml b/docs/Help_Spanish/Topics/PTR2.xml
deleted file mode 100644
index 7d2431fda1..0000000000
--- a/docs/Help_Spanish/Topics/PTR2.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- PTR
-
- PTR
-
-
-
- PTR
-
- The PTR keyword denotes an integral type that stores a pointer to a memory location. It is usually compiled to the System.IntPtr .Net Type. Please note that the size of the PTR depends on the underlying operating system and it will also be different when your application runs in x86 or x64 mode. In Visual Objects PTR is always 32 bits. Many people have written code that CAST INT values to PTR and back. This works because both values are 32 bit in VO. Safe code in .Net cannot do this, since the size of PTR is not fixed.
-
-
diff --git a/docs/Help_Spanish/Topics/Primary-Expressions.xml b/docs/Help_Spanish/Topics/Primary-Expressions.xml
deleted file mode 100644
index 56d196dd5d..0000000000
--- a/docs/Help_Spanish/Topics/Primary-Expressions.xml
+++ /dev/null
@@ -1,289 +0,0 @@
-
-
-
- Primary Expressions
-
- _AND
- _ARGLIST
- _CAST
- _NOT
- _OR
- _sizeof
- _typeof
- _XOR
- CHECKED
- CLASS
- DEFAULT
- FIELD
- IF
- IIF
- NAMEOF
- nativetype
- PTR
- SELF
- SIZEOF
- SUPER
- TUPLE
- TYPEOF
- UNCHECKED
-
-
-
- Primary Expressions
-
- Primary Expressions are the simplest building blocks in the expression rule in X#.
-
-
Select the <Myprojectname> Properties option from the Project Menu;
-
Choose the context menu option "Properties" on the project icons in the Solution Explorer;
-
Choose the context menu option "Open" on the Properties folder below the Project Icon in the Solution Explorer.
-
-
- All these options open the same project properties dialog. This dialog has several pages.
-
-
Application
-
Language
-
Dialect
-
Build
-
Build Events
-
Debug
-
Resources
-
Settings
-
-
- A description of each of these pages will follow in the next chapters.
-
-
diff --git a/docs/Help_Spanish/Topics/Project-System.xml b/docs/Help_Spanish/Topics/Project-System.xml
deleted file mode 100644
index 8693cf3162..0000000000
--- a/docs/Help_Spanish/Topics/Project-System.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Project System
-
- .xsproj
- MsBuild
-
-
-
- Project System
-
- The X# Visual Studio project system allows you to create X# projects with Visual Studio. It has support for a special kind of project file format for X# (the .xsproj files), and also recognizes various X# specific file types, such as PRG files and several "binary" files for VO compatible Form, Server, Menu and FieldSpec definitions.
-
- Part of this project system is the MsBuild support, which uses the .xsproj files and creates command lines for the X# compiler based on properties and values in the .xsproj files.
- The following chapters will briefly discuss solutions and projects and will describe the various project property pages for X# inside Visual Studio.
-
-
diff --git a/docs/Help_Spanish/Topics/Project-Templates.xml b/docs/Help_Spanish/Topics/Project-Templates.xml
deleted file mode 100644
index 4be4e36628..0000000000
--- a/docs/Help_Spanish/Topics/Project-Templates.xml
+++ /dev/null
@@ -1,428 +0,0 @@
-
-
-
- Project Templates
-
- ClassLibrary
- Console Application
- NUnit
- project templates
- templates
- Test Library
- VO MDI Application
- VO SDI Application
- Vulcan Console Application
- Windows Forms Application
- WPF Application
- XUnit
-
-
-
- Project Templates
-
- The X# Visual Studio integration comes with the following project templates:
-
-
-
-
-
-
- Template
-
-
- Description
-
-
- Required Framework version
-
-
- Default Dialect
-
-
- References
-
-
-
-
-
-
-
- ClassLibrary
-
-
- A project for creating an X# class library (.dll) for the Core dialect with no dependencies on the runtime
-
-
- 2.0
-
-
- Core
-
-
- System, and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- Core ClassLibrary
-
-
- A project for creating an X# class library (.dll) for the Core dialect with a dependency on XSharp.Core
-
-
- 2.0
-
-
- Core
-
-
- System, X# Core and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- FoxPro ClassLibrary
-
-
- A project for creating an X# class library (.dll) for the FoxPro Dialect
-
-
- 2.0
-
-
- FoxPro
-
-
- System, X# Core, VFP and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- VO ClassLibrary
-
-
- A project for creating an X# class library (.dll) for the VO Dialect
-
-
- 2.0
-
-
- Visual Objects
-
-
- System, X# Core, VO and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- Vulcan ClassLibrary
-
-
- A project for creating an X# class library (.dll) for the Vulcan Dialect
-
-
- 2.0
-
-
- Vulcan
-
-
- System, X# Core, Vulcan and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- XPP ClassLibrary
-
-
- A project for creating an X# class library (.dll) for the Xbase++ Dialect
-
-
- 2.0
-
-
- Xbase++
-
-
- System, X# Core, XPP and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- Console Application
-
-
- A project for creating an X# command line application in the core dialect.
-
-
- 2.0
-
-
- Core
-
-
- System, and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- FoxPro Console Application
-
-
- A project for creating an X# command line application in the FoxPro Dialect.
-
-
- 2.0
-
-
- FoxPro
-
-
- System, VFP, and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- VO Console Application
-
-
- A project for creating an X# command line application in the VO Dialect.
-
-
- 2.0
-
-
- Visual Objects
-
-
- System, VO, and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- Vulcan Console Application
-
-
- A project for creating an X# command line application in the Vulcan dialect with Vulcan Runtime Assemblies (BYOR = Bring Your Own Runtime).
-
-
- 2.0
-
-
- Vulcan
-
-
- System, Vulcan, and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- XPP Console Application
-
-
- A project for creating an X# class library (.dll) for the Xbase++ Dialect
-
-
- 2.0
-
-
- Xbase++
-
-
- System, XPP, and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- Windows Forms Application
-
-
- A project for creating an application with a Windows Forms user interface.
-
-
- 2.0
-
-
- Core
-
-
- System, and some extensions for frameworks > 3.5 System.Drawing System.Windows.Forms
-
-
-
-
-
-
-
- WPF Application
-
-
- Windows Presentation Foundation client application.
-
-
- 3.0
-
-
- Core
-
-
- System, and some extensions for frameworks > 3.5 WindowsBase, PresentationCore, PresentationFramework
-
-
-
-
-
-
-
- VO MDI Application
-
-
- A project for creating a VO MDI application in the VO Dialect.
-
-
- 4.6
-
-
- Visual Objects
-
-
- System and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
-
- VO SDI Application
-
-
- A project for creating a VO SDI application in the VO Dialect.
-
-
- 4.6
-
-
- Visual Objects
-
-
- System and some extensions for frameworks > 3.5
-
-
-
-
-
-
-
- Vulcan Console Application
-
-
- A project for creating a Vulcan command line application.
-
-
- 2.0
-
-
- Vulcan
-
-
- System, and some extensions for frameworks > 3.5 VulcanRT and VulcanRTFuncs
-
-
-
-
-
-
-
- Ms Test Library
-
-
- A Library with test support using the MsTest Framework
-
-
- 2.0
-
-
- Core
-
-
- System and several MsTest related assemblies
-
-
-
-
-
-
-
- NUnit Test Library
-
-
- A library with test support using the open source NUnit Framework
-
-
- 2.0
-
-
- Core
-
-
- System and several NUnit related assemblies. The template uses a NuGet package to retrieve the correct assemblies
-
-
-
-
-
-
-
- XUnit Test Library
-
-
- A library with test support using the open source XUnit Framework
-
-
- 2.0
-
-
- Core
-
-
- System and several XUnit related assemblies. The template uses a NuGet package to retrieve the correct assemblies
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Projects.xml b/docs/Help_Spanish/Topics/Projects.xml
deleted file mode 100644
index 5d7644a31a..0000000000
--- a/docs/Help_Spanish/Topics/Projects.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- Projects
-
- ItemGroup
- PropertyGroup
-
-
-
- Projects
-
- Project properties in Visual Studio are stored in the project files. The file names for X# projects end with the .xsproj extension.
- Project files are a special kind of XML files.
- These XML files contains various groups of information.
- Properties at the project level are stored in <PropertyGroup> nodes.
- Some of these properties are "Global" and some of these properties have a condition through which they are only active when a certain "configuration" is selected, such as "Debug" or "Release".
- Properties like the dialect and the output filename are global.
- Properties such as the optimization, PDB generation and output folders are configuration-specific.
-
- The project files also contain the list of references to external assemblies, other projects and COM components and the list of files.
- The build system inside Visual Studio uses the contents of the project files and constructs a command line that is passed to the X# compiler to produce the output for the project.
- We have developed a set of dialogs that allows you to set the various properties for a project. The following chapters will show you these dialogs and will discuss the various options that you can set on each page.
- Tip: Since the project file is an XML file, you can also directly edit the project file if you want. For example, you can add <Import> lines to import common properties from "include" files. We use that internally for our assemblies, so common properties are declared at one location. When doing that, you must be careful when using the project property dialogs inside Visual Studio. These dialogs will not understand that some values were read from an imported file and will change the values in the xsproj file, even when they were imported from an external file. Additionally, the order of the various property groups is important: The PropertyGroups with the Pre and PostBuild events are expected to be at the end of the XML file.
-
- The lists of external references and lists of items inside a project are stored in <ItemGroup> nodes.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/PropPage-Application.xml b/docs/Help_Spanish/Topics/PropPage-Application.xml
deleted file mode 100644
index c029e1d6ed..0000000000
--- a/docs/Help_Spanish/Topics/PropPage-Application.xml
+++ /dev/null
@@ -1,194 +0,0 @@
-
-
-
- Application
-
- Application Icon
- Assembly Name
- Default Namespace
- Dialect
- -main
- -nowin32manifest
- Output File
- Output Type
- Prefer native resource
- Prefer native resource over managed resource
- Project File
- Project Folder
- -rootnamespace
- Startup Object
- Suppress default Win32
- Suppress default Win32 manifest
- Target Framework Moniker
- -usenativeversion
- Vulcan Compatible Managed Resources
- -win32icon
-
-
-
- Application
-
- The Application page contains the most important settings for your Visual Studio project.
-
-
-
-
-
-
- Item
-
-
- Description
-
-
- Command item
-
-
-
-
- Default Namespace
-
-
- Specifies the default namespace for added items, such as classes, that are added via the Add New Item Dialog Box.
-
-
- This is not a commandline option for the compiler but used by Visual Studio.
-
-
-
-
- Dialect
-
-
- Select the compiler dialect to use when compiling this project. Changing the dialect may also change the 'Allow NamedArguments' setting on the Language page."
-
-
- -dialect
-
-
-
-
- Output Type
-
-
- The type of application to build.
-
-
-
-
-
-
- Startup Object
-
-
- The name of the class that contains the Start method that you want called when you launch your application.
- The default for X# applications is the Start function inside the compiler generated Functions class.
- You can override this setting by specifying another classname here.
-
-
- -main:
-
-
-
-
- Target Framework Moniker
-
-
- The version of the Common Language Runtime to use for output assembly.
-
-
- This is not a command line option for the compiler, but it controls the location from which reference assemblies are loaded.
-
-
-
-
- Assembly Name
-
-
- The name of the output file that will hold assembly metadata.
-
-
- -out
-
-
-
-
- Output File
-
-
- The name of the project's primary output file.
-
-
- This is derived from the assembly name.
-
-
-
-
- Project File
-
-
- The name of the file containing build, configuration, and other information about the project.
-
-
- This is the name from the current project.
-
-
-
-
- Project Folder
-
-
- The absolute location of the project.
-
-
- This is the location from the current project.
-
-
-
-
- Application Icon
-
-
- Sets the .ico file to use as your application icon. Please note that if your application contains native resources, this value will be ignored.
-
-
- -win32icon
-
-
-
-
- Prefer native resource over managed resource
-
-
- When your application includes a native resource, use this native resource and do not generate a resource based on the global assembly properties such as AssemblyTitle, AssemblyVersion, etc.
-
-
- -usenativeversion
-
-
-
-
- Suppress default Win32 manifest
-
-
- Suppress default Win32 manifest. You will have to supply your own Win32 manifest if you suppress the default one.
-
-
- -nowin32manifest
-
-
-
-
- Vulcan Compatible Managed Resources
-
-
- Use Vulcan Compatible Managed Resources. (When 'True', resource files are included in the assembly without namespace prefix. When 'False', the resource files are prefixed with the namespace of the app, just like in other .Net languages, such as C#.)
-
-
- -resource
-
-
-
- .
-
-
diff --git a/docs/Help_Spanish/Topics/PropPage-Build.xml b/docs/Help_Spanish/Topics/PropPage-Build.xml
deleted file mode 100644
index ba348fd6a8..0000000000
--- a/docs/Help_Spanish/Topics/PropPage-Build.xml
+++ /dev/null
@@ -1,257 +0,0 @@
-
-
-
- Build
-
- Code Signing KeyFile
- -d
- Defines
- Defines for the preprocessor
- Delayed sign only
- -delaysign
- Extra Command Line Options
- Generate preprocessor output
- Generate XML doc comments file
- Intermediate Output Path
- -keyfile
- -nowarn
- Optimize
- Output Path
- Platform Target
- -ppo
- Prefer 32 Bit
- Preprocessor
- Preprocessor output
- Register for COM interop
- Shared Compiler
- -sign
- Sign the output assembly
- Suppress Specific Warnings
- Use Shared Compiler
- -warn
- -warnaserror
- Warning Level
- Warnings As Errors
- XML doc comments file name
-
-
-
- Build
-
- The Build properties page contains Configuration Specific properties, so properties can differ for a Debug and a Release configuration. Please read the Build Configuration topic for more information about build configurations.
-
-
-
-
-
-
- Item
-
-
- Description
-
-
- Command item
-
-
-
-
- Platform Target
-
-
- Select the platform target when compiling this project. This should be AnyCPU, X86, x64,Arm or Itanium.
-
-
- -platform
-
-
-
-
- Prefer 32 Bit
-
-
- Prefer 32 bit when AnyCpu platform is selected.
-
-
- -platform
-
-
-
-
- Intermediate Output Path
-
-
- Intermediate Output Path (macros are allowed).
-
-
- Used by Visual Studio/MsBuild.
-
-
-
-
- Output Path
-
-
- Output Path (macros are allowed).
-
-
- Used by Visual Studio/MsBuild.
-
-
-
-
- Code Signing KeyFile
-
-
- Choose a code signing key file.
-
-
- -keyfile
-
-
-
-
- Delayed sign only
-
-
- Delayed signing.
-
-
- -delaysign
-
-
-
-
- Sign the output assembly
-
-
- Sign the assembly.
-
-
- -keyfile
-
-
-
-
- Extra Command Line Options
-
-
- User-Defined Command Line options.
-
-
- You can specify additional command line options here.
-
-
-
-
- Optimize
-
-
- Should compiler optimize output?
-
-
- -optimize
-
-
-
-
- Register for COM Interop
-
-
- Register the output assembly for COM Interop (requires administrator rights).
-
-
- This will run a tool after the build process to register the assembly for COM Interop.
-
-
-
-
- Use Shared Compiler
-
-
- Should the shared compiler be used to compile the project? (Faster, but may hide some compiler errors.)
-
-
- -shared
-
-
-
-
- Defines for the preprocessor
-
-
- Defines for the preprocessor.
-
-
- -define
-
-
-
-
- Generate preprocessor output
-
-
- Save the output from the preprocessor to .ppo files.
-
-
- -ppo
-
-
-
-
- Suppress Specific Warnings
-
-
- Specify a list of warnings to suppress.
-
-
- -nowarn
-
-
-
-
- Warning Level
-
-
- Set the warning level to a value between 0 and 4.
-
-
- -warn
-
-
-
-
- Warnings As Errors
-
-
- Treat warnings as errors.
-
-
- -warnaserror
-
-
-
-
- Generate XML doc comments file
-
-
- Generate XML doc comments file.
-
-
- -doc
-
-
-
-
- XML doc comments file name
-
-
- XML doc comments file name.
-
-
- -doc
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/PropPage-BuildEvents.xml b/docs/Help_Spanish/Topics/PropPage-BuildEvents.xml
deleted file mode 100644
index 2fd7b34f8b..0000000000
--- a/docs/Help_Spanish/Topics/PropPage-BuildEvents.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- Build Events
-
-
- Build Events
-
- On the Build Events property page you can specify command lines that need to be run before or after the build process.
- You can use this, for example, to run a tool that generates source code, or to copy the output DLLs to another folder.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/PropPage-Debug.xml b/docs/Help_Spanish/Topics/PropPage-Debug.xml
deleted file mode 100644
index ce8f0c66ba..0000000000
--- a/docs/Help_Spanish/Topics/PropPage-Debug.xml
+++ /dev/null
@@ -1,83 +0,0 @@
-
-
-
- Debug
-
- Command
- Command Arguments
- Debug Information
- Enable unmanaged debugging
- Generate Debug Information
- unmanaged debugging
- Working Directory
-
-
-
- Debug
-
-
-
-
-
- Item
-
-
- Description
-
-
- Command item
-
-
-
-
- Command
-
-
- The debug command to execute.
-
-
-
-
-
-
- Command Arguments
-
-
- The command line arguments to pass to the application.
-
-
-
-
-
-
- Generate Debug Information
-
-
- Generate Debug Information (none, full, pdbonly).
-
-
-
-
-
-
- Working Directory
-
-
- The application's working directory. By default, the directory containing the project file.
-
-
-
-
-
-
- Enable unmanaged debugging
-
-
- Enable unmanaged debugging.
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/PropPage-Dialect.xml b/docs/Help_Spanish/Topics/PropPage-Dialect.xml
deleted file mode 100644
index 2caa8be8f9..0000000000
--- a/docs/Help_Spanish/Topics/PropPage-Dialect.xml
+++ /dev/null
@@ -1,259 +0,0 @@
-
-
-
- Dialect
-
- -fox1
- -fox2
- -vo1
- -vo10
- -vo11
- -vo12
- -vo13
- -vo14
- -vo15
- -vo16
- -vo2
- -vo3
- -vo4
- -vo5
- -vo6
- -vo7
- -vo8
- -vo9
- -xpp1
-
-
-
- Dialect
-
- The Dialect page contains some additional language settings. Some of these settings apply to all dialects, while others only apply to the given dialect and are only enabled when the appropriate dialect is chosen.
-
-
-
-
-
-
- Item
-
-
- Description
-
-
- Command item
-
-
-
-
- All instance methods virtual
-
-
- Add the virtual modifier to all methods by default (which is the normal Visual Objects behavior).
-
-
- -vo3
-
-
-
-
- Allow Init() and Axit() as aliases for Constructor/Destructor
-
-
- Allow Init() and Axit() as aliases for Constructor/Destructor.
-
-
- -vo1
-
-
-
-
- Compatible IIF Behavior
-
-
- Compatible IIF Behavior, allow different types of return values in TRUE and FALSE expression.
-
-
- -vo10
-
-
-
-
- Compatible preprocessor
-
-
- Makes the preprocessor case-insensitive, and controls how #ifdef inspects #defines.
-
-
- -vo8
-
-
-
-
- Handle problems with incorrect or missing return statements
-
-
- Allow missing return statements, or allow return statements with incorrect return values.
-
-
- -vo9
-
-
-
-
- Implicit numeric conversions
-
-
- Implicit numeric integer conversions.
-
-
- -vo4
-
-
-
-
- Initialize strings
-
-
- Initialize strings to empty string (String.Empty).
- Please note that in .NET a NULL_STRING is different than a string with length 0. When enabled, this will initialize local string variables, regardless of the setting of 'initialize locals' setting from the Language page.
-
-
- -vo2
-
-
-
-
- Clipper Compatible intiger divisions
-
-
- Compatible integer divisions, integer divisions may return a float.
-
-
- -vo12
-
-
-
-
- Compatible numeric conversions
-
-
- Compatible arithmetic conversions.
-
-
- -vo11
-
-
-
-
- Compatible string comparisons
-
-
- Compatible string comparisons, respects SetExact and collation table.
-
-
- -vo13
-
-
-
-
- Generate Clipper constructors
-
-
- Automatically create clipper calling convention constructors for classes without constructor where the parent class has a Clipper Calling convention constructor.
-
-
- -vo16
-
-
-
-
- Implicit casts and conversions
-
-
- Compatible implicit casts and Conversions.
-
-
- -vo7
-
-
-
-
- Implicit Clipper calling convention
-
-
- Methods without parameters and calling convention are compiled as Clipper calling convention.
- Please note that without this switch, all methods without parameters will be seen as STRICT. Methods with untyped parameters are always seen as CLIPPER calling convention.
-
-
- -vo5
-
-
-
-
- Implicit pointer conversions
-
-
- Implicit conversions between typed function PTR and PTR.
-
-
- -vo6
-
-
-
-
- Treat missing types as USUAL
-
-
- Missing type clauses for locals, instance variable, and parameters are treated as USUAL (VO and Vulcan dialect). The default = TRUE for the VO dialect and FALSE for the other dialects. We strongly recommend to set this to FALSE, as this will help you find problems in your code and non-optimal code. If you have to use the USUAL type, we recommend to explicitly declare variables and parameters as USUAL.
-
-
- -vo15
-
-
-
-
- Use FLOAT literals
-
-
- Store floating point literals as FLOAT and not as System.Double (REAL8).
-
-
- -vo14
-
-
-
-
- Compatible BEGIN SEQUENCE .. END
-
-
- Generate code to fully implement the VO compatible BEGIN SEQUENCE .. END SEQUENCE. The compiler generates calls to the runtime functions _SequenceError and _SequenceRecover that you may override in your own code.
-
-
- -vo17
-
-
-
-
- Compatible Array Handling
-
-
- FoxPro compatible array handling (Allows parenthesized arrays and assigning a single value to an array to fill all elements). WARNING: Allowing parenthesized arrays may slow down the execution of your program!(/fox2)
-
-
- -fox2
-
-
-
-
- Inherit from Abstract class
-
-
- All classes without parent class inherit from the XPP Abstract class.
-
-
- -xpp1
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/PropPage-Language.xml b/docs/Help_Spanish/Topics/PropPage-Language.xml
deleted file mode 100644
index 2e4db845fb..0000000000
--- a/docs/Help_Spanish/Topics/PropPage-Language.xml
+++ /dev/null
@@ -1,280 +0,0 @@
-
-
-
- Language
-
- Additional Include paths
- Allow Late Binding
- Allow Named Arguments
- Allow Unsafe Code
- Alternate standard header file
- -az
- Case Sensitive
- -cs
- Enable Implicit Namespace lookup
- Enable Memvar support
- Enable Undeclared variables support
- -i
- Implicit Namespace lookup
- Include paths
- Initialize Local variables
- -initlocals
- -ins
- -lb
- Local variables
- -memvar
- Memvar support
- -namedargs
- NAMESPACE
- Namespace lookup
- -nostddef
- ns
- -ns:<Namespace>
- Overflow Exceptions
- -ovf
- Prefix classes
- Prefix classes with default Namespace
- standard header file
- -stddefs
- Suppress standard header file
- -undeclared
- Undeclared variables support
- -unsafe
- Unsafe Code
- Use Zero Based Arrays
- Zero Based Arrays
-
-
-
- Language
-
- The Language page contains some settings that control X# Language specific options. These settings apply to all dialects.
-
-
-
-
-
-
- Item
-
-
- Description
-
-
- Command item
-
-
-
-
- Allow Late Binding
-
-
- Allow property access and method calls on expressions of type OBJECT and USUAL.
-
-
- /lb
-
-
-
-
- Allow Named Arguments
-
-
- Allow named arguments (Default = TRUE for the Core dialect and FALSE for the other dialects). Changing the dialect may also automatically change this setting.
-
-
- /namedargs
-
-
-
-
- Allow Unsafe Code
-
-
- Allow Unsafe code inside this assembly.
-
-
- /unsafe
-
-
-
-
- Case Sensitive
-
-
- Enable/Disable case sensitivity.
-
-
- /cs
-
-
-
-
- Initialize Local variables
-
-
- Automatically initialize local variables without initialization expression. Please note that for locals of type string, the initial value will depend on the 'Initialize strings' setting from the Dialect page.
-
-
- /initlocals
-
-
-
-
- Overflow Exceptions
-
-
- Check for Overflow and Underflow for numeric expressions, like the CHECKED keyword.
-
-
- /ovf
-
-
-
-
- Use Zero Based Arrays
-
-
- Use Zero Based Arrays.
-
-
- /az
-
-
-
-
- Enforce SELF
-
-
- When checked, all references to methods and fields/properties inside a class should be prefixed with SELF (or SUPER).
-
-
- /enforceself
-
-
-
-
- Allow DOT for instance members
-
-
- When checked, you can also use the DOT (.) operator to access instance fields, properties and methods. Otherwise, the COLON (:) operator is needed.
-
-
- /allowdot
-
-
-
-
- Enforce VIRTUAL/OVERRIDE
-
-
- When checked, you MUST prefix methods with VIRTUAL and/or OVERRIDE when overriding methods in a parent class, or when defining a new method that can be overridden.
-
-
- /enforceoverride
-
-
-
-
- Allow Old Style assignments
-
-
- When checked, allow the use of the single equals operator (=) for assignments. Otherwise, the Colon Equals (:=) operator is mandatory.
-
-
- /allowoldstyleassignments
-
-
-
-
- Modern Syntax
-
-
- This options disables some old style features, such as certain comment characters.
-
-
- /modernsyntax
-
-
-
-
- Enable Memvar support
-
-
- Enable support for memory variables (MEMVAR, PUBLIC, PRIVATE & PARAMETERS).
- Please note that this is NOT supported for the Core and Vulcan dialects.
-
-
- /memvar
-
-
-
-
- Enable Undeclared variables support
-
-
- Enable support for undeclared variables (these are resolved to MEMVARs).
- Please note that this requires /memvar to be enabled as well.
-
-
- /undeclared
-
-
-
-
- Enable Implicit Namespace lookup
-
-
- Enable the implicit lookup of classes defined in assemblies with an Implicit Namespace attribute.
-
-
- /ins
-
-
-
-
- Prefix classes with default Namespace
-
-
- Prefix all classes that do not have a namespace prefix and are not in a begin namespace ... end namespace block with the namespace of the assembly.
-
-
- /ns:<Namespace>
-
-
-
-
- Additional Include paths
-
-
- Additional include paths for the preprocessor. (It also looks through the folders set with the include environment variable.)
-
-
- /i
-
-
-
-
- Alternate standard header file
-
-
- Name of an alternative standard header file (alternative for XSharpDefs.xh).
-
-
- /stddefs
-
-
-
-
- Suppress standard header file
-
-
- Suppress inclusion of the standard header file (XSharpDefs.xh) in every file.
-
-
- /nostddef
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/PropPage-Resources.xml b/docs/Help_Spanish/Topics/PropPage-Resources.xml
deleted file mode 100644
index a8d066ba09..0000000000
--- a/docs/Help_Spanish/Topics/PropPage-Resources.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- Resources
-
- Custom tool
- resource editor
-
-
-
- Resources
-
- The Resources Property page allows you to open up a resources editor for project wide resources. These resources can be files, strings, images, etc.
- The Resource editor is the normal Visual Studio resource editor.
-
-
-
- This resource editor will generate a Resources.Resx file in the Properties folder of the project.
- The "Access Modifier" combobox at the top of the screen allows you to control the code generation for these resources:
-
-
Using (Custom), no code will be generated;
-
Using "Internal", X# code will be generated with internal visibility;
-
Using "Public", X# code will be generated with public visibility.
-
-
- The value of the Access Modifier also sets the "Custom tool" in the properties dialog for the Resources.Resx file.
-
-
diff --git a/docs/Help_Spanish/Topics/PropPage-Settings.xml b/docs/Help_Spanish/Topics/PropPage-Settings.xml
deleted file mode 100644
index fd52a70dcb..0000000000
--- a/docs/Help_Spanish/Topics/PropPage-Settings.xml
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
- Settings
-
- app.config
- Custom Tool
- Settings
- settings editor
-
-
-
- Settings
-
- Application settings enable you to store application information dynamically.
-
-
- Settings allow you to store information on the client computer that should not be included in the application code (for example a connection string), user preferences, and other information you need at run time.
- Each application setting must have a unique name. The name can be any combination of letters, numbers, or an underscore, as long as it does not start with a number and it cannot have spaces. The name is changed through the Name property.
-
- Application settings can be stored as any data type that is serialized to XML or has a TypeConverter that implements ToString/FromString. The most common types are String, Integer, and Boolean, but you can also store values such as Color, Object, or as a connection string.
-
- Application settings also hold a value. The value is set with the Value property and must match the data type of the setting.
-
- In addition, application settings can be bound to a property of a form or control at design time.
-
- There are two types of application settings, based on scope:
-
-
Application-scoped settings can be used for information such as a URL for a web service or a database connection string. These values are associated with the application. Therefore, users cannot change them at run time.
-
User-scoped settings can be used for information such as persisting the last position of a form or a font preference. Users can change these values at run time.
-
-
- You can change the type of a setting by using the Scope property.
-
- The project system stores application settings in two XML files:
-
-
-
an app.config file, which is created at design time when you create the first application setting;
-
a user.config file, which is created at run time when the user who runs the application changes the value of any user setting.
-
-
- Notice that changes in user settings are not written to disk unless the application specifically calls a method to do this.
-
- The Settings Property page allows you to open up a settings editor for project settings. The definition for these settings will be stored in the Properties folder of your project.
- The values of these settings will be stored in an app.config file in the root folder of your project.
-
- Just like in the resource editor, you can also choose the visibility of the generated code (the IDE generates a file called Settings.Designer.prg). This also changes the "Custom Tool" property of the Settings file.
-
-
-
- When you compile your project, MsBuild will generate a copy of app.config and will rename it to <yourapp>.exe.config in the output folder of your project.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Pseudo-Functions.xml b/docs/Help_Spanish/Topics/Pseudo-Functions.xml
deleted file mode 100644
index caf810b922..0000000000
--- a/docs/Help_Spanish/Topics/Pseudo-Functions.xml
+++ /dev/null
@@ -1,129 +0,0 @@
-
-
-
- Pseudo Functions
-
- _ARGS
- _Chr
- _GETFPARAM
- _GetInst
- _GETMPARAM
- ALTD
- ARGCOUNT
- CCALL
- CCallNative
- Chr
- PCALL
- PCallNative
- PCOUNT
- SLen
-
-
-
- Pseudo Functions
-
- The following pseudo functions are supported by the X# compiler:
-
-
-
-
- Function
-
-
- Description
-
-
-
-
- PCOUNT()
-
-
- This pseudo function is only available in methods or functions with a CLIPPER calling convention. It returns the number of argument passed to the function. The function does not expect and does not allow any arguments. Not available in Core.
-
-
-
-
- ARGCOUNT()
-
-
- This pseudo function returns the number of arguments defined for the current method or function.
-
-
-
-
- _GETMPARAM() and _GETFPARAM()
-
-
- These pseudo functions are only available in methods or functions with a CLIPPER calling convention. You can use them to retrieve a function parameter by position. You must pass a numeric expression to these functions. If you pass a number that is larger than the actual number of parameters at runtime then you will get an array access exception. Not available in Core.
-
-
-
-
- String2Psz() and Cast2Psz()
-
-
- These pseudo functions are used to convert DotNet strings to unmanaged Ansi PSZ strings. Not only is a PSZ created, but the functions also change the code generation and set up code to clear the allocated PSZ variable on exit of the function in which they are created. Not available in Core.
-
-
-
-
- ALTD()
-
-
- This function will insert a call to System.Diagnostics.Debugger.Break inside a check to see if the debugger is attached (System.Diagnostics.Debugger.IsAttached).
-
-
-
-
- _GetInst()
-
-
- This function will return the module handle for the current module. Behind the scenes this is translated to System.Runtime.InteropServices.Marshal.GetHINSTANCE(TypeOf(FunctionsClass):Module).
-
-
-
-
- PCALL() and CCALL()
-
-
- The methods are used to call an API function for a strongly typed PTR. The function expects a first parameter of type PTR and the other parameters must match the parameters defined in the function to which the typed PTR points. The compiler creates a delegate with the proper prototype and uses Marshal.GetDelegateForFunctionPointer() to call the function.
-
-
-
-
- PCallNative<Type>() and CCallNative<Type>()
-
-
- The methods are used to call an API function for an untyped PTR.
- The function expects a generic type parameter which indicates the return type and a first parameter of type PTR. Other parameters are allowed and must not point to managed memory.
- The compiler creates a delegate with the proper prototype and uses Marshal.GetDelegateForFunctionPointer() to call the function.
-
-
-
-
- _ARGS()
-
-
- This pseudo function returns is replaced by the compiler to a reference to the generated array of parameters for functions/methods with clipper calling convention.
-
-
-
-
- SLen()
-
-
- This function is translated by the compiler to a call of the Length property of the string, with a built-in check for NULL.
-
-
-
-
- Chr(), _Chr()
-
-
- When the numeric parameter of this function is a literal number between 0 and 127, then the compiler replaces the function call with a literal string with a character of that value. Larger values are not converted at compile time but at runtime because these numbers are codepage dependent. So an expression like "Hello world"+Chr(13)+Chr(10) will be translated into a literal string containing "Hello world" followed by the CRLF characters (the compiler concatenates the strings at compile time).
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Quick-Start.xml b/docs/Help_Spanish/Topics/Quick-Start.xml
deleted file mode 100644
index 02f387d0ce..0000000000
--- a/docs/Help_Spanish/Topics/Quick-Start.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Quick Start
-
-
- Quick Start
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/REAL4.xml b/docs/Help_Spanish/Topics/REAL4.xml
deleted file mode 100644
index a4a84f976e..0000000000
--- a/docs/Help_Spanish/Topics/REAL4.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- REAL4
-
- REAL4
-
-
-
- REAL4
-
- The REAL4 keyword denotes a single precision 32 bit number with values ranging from negative 3.402823e38 to positive 3.402823e38, as well as positive or negative zero, PositiveInfinity, NegativeInfinity, and not a number ( NaN). It is intended to represent values that are extremely large (such as distances between planets or galaxies) or extremely small (such as the molecular mass of a substance in kilograms) and that are often imprecise (such as the distance from earth to another solar system). The REAL4 type complies with the IEC 60559:1989 (IEEE 754) standard for binary floating-point arithmetic.
-
-
-
diff --git a/docs/Help_Spanish/Topics/REAL8.xml b/docs/Help_Spanish/Topics/REAL8.xml
deleted file mode 100644
index ca3d84e9dd..0000000000
--- a/docs/Help_Spanish/Topics/REAL8.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- REAL8
-
- REAL8
-
-
-
- REAL8
-
- The REAL8 keyword denotes an double precision 64-bit number with values ranging from negative 1.79769313486232e308 to positive 1.79769313486232e308, as well as positive or negative zero, PositiveInfinity, NegativeInfinity, and not a number ( NaN). It is intended to represent values that are extremely large (such as distances between planets or galaxies) or extremely small (the molecular mass of a substance in kilograms) and that are often imprecise (such as the distance from earth to another solar system), The Double type complies with the IEC 60559:1989 (IEEE 754) standard for binary floating-point arithmetic.
-
-
-
diff --git a/docs/Help_Spanish/Topics/RECORD-statement.xml b/docs/Help_Spanish/Topics/RECORD-statement.xml
deleted file mode 100644
index 9304246c2b..0000000000
--- a/docs/Help_Spanish/Topics/RECORD-statement.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- RECORD modifier
-
-
- RECORD modifier
-
- Purpose
- The RECORD modifier for both classes and stryuctures instruct the compiler to create special versions of these entities that have value equality. These are often used to represent data models.
- Two objects of a Record class or a Record structure are considered equal when all the members have the same
- To achieve this, the compiler generates a special Equals() operator for the type that compares all fields in the type.
-
-
diff --git a/docs/Help_Spanish/Topics/RealLiterals.xml b/docs/Help_Spanish/Topics/RealLiterals.xml
deleted file mode 100644
index 603d2b27e2..0000000000
--- a/docs/Help_Spanish/Topics/RealLiterals.xml
+++ /dev/null
@@ -1,75 +0,0 @@
-
-
-
- Floating point Literals
-
- Currency
- Currency Literal
- Floating point Literals
- Literals
- Numeric Literals
-
-
-
- Floating point Literals
-
- Single or double precision literals may be used to store numeric values in your code.
-
- 123.456 123.0 0.123 .123 123.456e+7 123.456e-7 $123.45
- Real literals may have one of the following suffixes:
-
-
-
-
- Suffix
-
-
-
-
-
-
- S or s
-
-
- Single precision (REAL4)
-
-
-
-
- D or d
-
-
- Double precision (REAL8)
-
-
-
-
- M or m
-
-
- Decimal
-
-
-
-
- Floating point literals without suffix are stored as REAL8, unless you have specified the /vo14 compiler option, in which case they are stored as FLOAT literals.
-
-
-
-
- Prefix
-
-
-
-
-
-
- $
-
-
- Currency Literal
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Redistributing-X.xml b/docs/Help_Spanish/Topics/Redistributing-X.xml
deleted file mode 100644
index 230415ed1d..0000000000
--- a/docs/Help_Spanish/Topics/Redistributing-X.xml
+++ /dev/null
@@ -1,326 +0,0 @@
-
-
-
- Redistributing X#
-
-
- Redistributing X#
-
- With your projects, you are allowed to distribute the XSharp DLLs listed below.
- You are also allowed to distribute the PDB files that come with these DLLs.
- These PDB files may help in locating the line numbers where an error occurs.
- These files can be found in the <Program Files>\XSharp\Redist folder on your machine.
- XSharp.Runtime
-
-
-
- Name
-
-
- Needed for
-
-
-
-
- XSharp.CodeAnalysis.dll
-
-
- Full macro compiler & Scripting
-
-
-
-
- XSharp.Core.dll
-
-
- All dialects
-
-
-
-
- XSharp.Data.dll
-
-
- All dialects
-
-
-
-
- XSharp.MacroCompiler.dll
-
-
- Macro compiler
-
-
-
-
- XSharp.MacroCompiler.Full.dll
-
-
- Full Macro compiler
-
-
-
-
- XSharp.RT.dll
-
-
- All dialects
-
-
-
-
- XSharp.RT.Debugger.dll
-
-
- All dialects
-
-
-
-
- XSharp.RDD.dll
-
-
- All dialects
-
-
-
-
- XSharp.Scripting.dll
-
-
- Full Macro compiler & Scripting
-
-
-
-
- XSharp.VFP.dll
-
-
- FoxPro dialect
-
-
-
-
- XSharp.VFP.UI.dll
-
-
- FoxPro dialect
-
-
-
-
- XSharp.VO.dll
-
-
- VO and Vulcan dialect
-
-
-
-
- XSharp.XPP.dll
-
-
- Xbase++ Dialect
-
-
-
- VO Compatible SDK
-
-
-
- Name
-
-
-
-
- VOConsoleClasses.dll
-
-
-
-
- VORDDClasses.dll
-
-
-
-
- VOSQLClasses.dll
-
-
-
-
- VOGUIClasses.dll
-
-
-
-
- VOReportClasses.dll
-
-
-
-
- VOSystemClasses.dll
-
-
-
-
- VOWin32APILibrary.dll
-
-
-
- Strongly Typed version of the VO SDK
-
-
-
- Name
-
-
-
-
- XSharp.VOConsoleClasses.dll
-
-
-
-
- XSharp.VOGUIClasses.dll
-
-
-
-
- XSharp.VORDDClasses.dll
-
-
-
-
- XSharp.VOSQLClasses.dll
-
-
-
-
- XSharp.VOSystemClasses.dll
-
-
-
-
- The following files are needed by VOGUIClasses.dll when you use the DataBrowser or Splitwindow:
-
-
-
-
- Name
-
-
-
-
- CATO3CNT.DLL
-
-
-
-
- CATO3DAT.DLL
-
-
-
-
- CATO3MSK.DLL
-
-
-
-
- CATO3NBR.DLL
-
-
-
-
- CATO3SBR.DLL
-
-
-
-
- CATO3TBR.DLL
-
-
-
-
- CATO3TIM.DLL
-
-
-
-
- CATO3SPL.DLL
-
-
-
-
- MSVCRT.DLL
-
-
-
-
-
-
-
-
- The following file is needed for image support in VOGUIClasses.DLL
-
-
-
-
- CAPAINT.DLL
-
-
-
- XSharp Scripting
-
-
-
- Name
-
-
-
-
- Xsi.exe
-
-
-
-
- XSharp.Scripting.dll
-
-
-
-
- XSharp.CodeAnalysis.dll
-
-
-
-
- These scripting files can all be found in the <Program Files>\XSharp\Bin folder.
- Support files
-
-
-
- Name
-
-
-
-
- Microsoft.DiaSymReader.Native.amd64.dll
-
-
-
-
- Microsoft.DiaSymReader.Native.x86.dll
-
-
-
-
- System.*.dll
-
-
-
-
- These support files can all be found in the <Program Files>\XSharp\Bin folder.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/References.xml b/docs/Help_Spanish/Topics/References.xml
deleted file mode 100644
index 781249e701..0000000000
--- a/docs/Help_Spanish/Topics/References.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- References
-
- References to External .Net Assemblies
- References to External COM components
- References to other Visual Studio projects
- References to unmanaged code
-
-
-
- References
-
- XSharp projects inside Visual studio work with source code items and may contain references to code defined in external libraries.
- Inside Visual Studio you can set these references through the References dialog.
- In short, there are 3 kinds of references:
-
-
External .Net assemblies
-
External COM components
-
Other projects inside the same Visual Studio solution.
-
- References to unmanaged code
- You cannot add references to unmanaged code using the Project References.
- To call unmanaged code you will have to declare either functions or procedures with the _DLL prefix, or you declare static methods or functions and add a special [DllImport()] attribute to them.
-
-
diff --git a/docs/Help_Spanish/Topics/Relational_Operators.xml b/docs/Help_Spanish/Topics/Relational_Operators.xml
deleted file mode 100644
index 3a169fce0a..0000000000
--- a/docs/Help_Spanish/Topics/Relational_Operators.xml
+++ /dev/null
@@ -1,199 +0,0 @@
-
-
-
- Relational
-
- <
- <=
- >
- >=
- Clipper collation
- 'compatible string comparions
- operator
- Ordinal collation
- relational operator
- SetCollation
- Unicode collation
- -vo13
- Windows collation
-
-
-
- Relational
-
- X# uses the following Logical operators:
-
-
-
-
- Operator
-
-
- Example
-
-
- Meaning
-
-
-
-
- <
-
-
- x < y
-
-
- less than (true if x is less than y). See below for string comparisons.
-
-
-
-
- <=
-
-
- x <= y
-
-
- less than or equal to (true if x is less than or equal to y). See below for string comparisons.
-
-
-
-
- >
-
-
- x > y
-
-
- greater than (true if x is greater than y). See below for string comparisons.
-
-
-
-
- >=
-
-
- x >= y
-
-
- greater than or equals to (true if x is greater than or equal to y). See below for string comparisons.
-
-
-
-
- =
-
-
- x = y
-
-
- equality. . Note that there is a difference between = and == for strings only. See below.
-
-
-
-
- ==
-
-
- x == y
-
-
- exact equality. Note that there is a difference between = and == for strings only. See below.
-
-
-
-
- <>, #, !=
-
-
- x <> y, x # y, x != y
-
-
- not equal. Note that for strings this follows the same rules as the single = operator.
-
-
-
-
- $
-
-
- x $ y
-
-
- Is substring of. Returns true if the first string is a substring of the second (case sensitive!).
-
-
-
-
- IS
-
-
- x IS y
-
-
- Type compatibility. Returns true if the evaluated left operand can be cast to the type specified in the right operand (a static type).
-
-
-
-
- ASTYPE
-
-
- x ASTYPE y
-
-
- Type conversion. Returns the left operand cast to the type specified by the right operand (a static type), but as returns null where (T)x would throw an exception.
-
-
-
- String comparisons
- The '=' and '==' operators behave differently for strings, and the behavior of the single equals also depends on a runtime setting.
-
- If you call SetExact(FALSE) then ‘=’ equates the characters up to the length of the string on the right-hand side of the operator ignoring the remaining characters on the left. This is the default setting. If you call SetExact(TRUE) then = and == have the same meaning for strings.
- The <, <=, > and >= operators for strings have a behavior that depends on a compiler option and a runtime setting. The -vo13 compiler option 'compatible string comparions' tells the compiler that it needs to use a runtime function for string comparisons. The behavior of this runtime function depends on the setting of SetCollation(). There are four possible values for SetCollation():
-
-
-
-
- Setting
-
-
- Description
-
-
-
-
- Clipper
-
-
- This setting will convert both strings to OEM strings using the current DOS codepage. After that, the strings will be compared using the string comparison / weight tables that are defined with SetNatDLL(). The default comparison uses a wight based on the byte number. Other comparisons available are for example GERMAN, DUTCH, FRENCH, RUSSIAN, SPANISH, SLOV852 etc. This setting should be used if your application needs to share files with CLIPPER programs.
-
-
-
-
- Windows
-
-
- This setting will convert both strings to ANSI using the current ANSI codepage. After that, the strings will be compared using the normal windows ANSI CompareString() code. This setting should be used when your application shares files with VO programs.
-
-
-
-
- Unicode
-
-
- This setting will NOT convert strings and will do a normal Unicode string comparison using the String.Compare() method from the .Net.
-
-
-
-
- Ordinal
-
-
- This setting will NOT convert strings and will do a normal Ordinal string comparison using the String.CompareOrdinal() method from the .Net. This is the fastest.
-
-
-
- The >= and <= operators for strings also take into account the setting for SetExact(). The 'equalness' of the 2 strings is determined by the same rules as the '=' operator.
-
-
diff --git a/docs/Help_Spanish/Topics/Resources.xml b/docs/Help_Spanish/Topics/Resources.xml
deleted file mode 100644
index 9bbfd07d29..0000000000
--- a/docs/Help_Spanish/Topics/Resources.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Native Resources
-
-
- Native Resources
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Runtime-Scripting.xml b/docs/Help_Spanish/Topics/Runtime-Scripting.xml
deleted file mode 100644
index 8b97b862f7..0000000000
--- a/docs/Help_Spanish/Topics/Runtime-Scripting.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- Runtime Scripting
-
- ExecScript
-
-
-
- Runtime Scripting
-
- XSharp 2.8 adds support for Runtime scripting through the ExecScript() function.
- Scripting was added for the FoxPro dialect but also works for other dialects.
- Inside scripts you will have the full X# language at your disposal.
- The first time a script runs, it will be compiled. If you run the same script a second time, the script compiler can reuse the already compiled version of the first script.
-
- An example (FoxPro dialect, MessageBox() is a FoxPro functon)
-
- VAR cScript := 'MessageBox("Hello ExecScript")' ExecScript(cScript)
- Of course scripts can also be multiple lines and can call any function in the runtime and in your code.
- PUBLIC and PRIVATE variables that are visible when your script is started are accessible by the script.
- You can also declare new local variables in the script and use any statement and user defined command that you would normally use.
-
- We did an online session about scripting in Jan 2021 that shows several example scripts. See https://www.youtube.com/watch?v=88crZsEiAOg&t=5s for the recording.
- One sample script from that demo is
-
- LPARAMETERS oForm USE employees.dbf PrintOut(oForm, 'private',MyPrivate, Used(), Alias()) GOTOP DOWHILE ! Eof() PrintOut(oForm, RecNo(), FieldGet(1), FieldGet(2), FieldGet(3)) SKIP ENDDO USE
- That script calls a PrintOut function and passes it the form that was received as parameter. The PrintOut function then adds a line of text to the terminal window that was passed to the script. The USE, GO TOP and SKIP commands are all UDCs that are handled by the script compiler without problems.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/RuntimeInstallationintheGAC.xml b/docs/Help_Spanish/Topics/RuntimeInstallationintheGAC.xml
deleted file mode 100644
index 4409b6f413..0000000000
--- a/docs/Help_Spanish/Topics/RuntimeInstallationintheGAC.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-
- Runtime Installation in the GAC
-
- GAC
- Installation
- Runtime
-
-
-
- Runtime Installation in the GAC
-
- The default behavior of the X# installer is to register the X# runtime in the GAC. The following files are registered there
-
-
-
XSharp.Core.DLL
-
XSharp.Data.DLL
-
XSharp.RT.DLL
-
XSharp.VO.DLL
-
XSharp.XPP.DLL
-
XSharp.VFP.DLL
-
XSharp.RDD.DLL
-
XSharp.Macrocompiler.DLL
-
VOConsoleClasses.dll
-
VOGUIClasses.dll
-
VOInternetClasses.dll
-
VORDDClasses.dll
-
VOReportClasses.dll
-
VOSQLClasses.dll
-
VOSystemClasses.dll
-
VOWin32APILibrary.dll
-
-
- Some components are dynamically loaded at runtime and do not have to be added as references to your application:
-
-
XSharp.RDD.DLL
-
XSharp.Macrocompiler.DLL
-
-
- The X# runtime tries to locate these assemblies in the GAC and in the directory where the application is installed.
- If you are not installing the runtime to the GAC, then you must make sure that these two DLLs are available in your application folder. Otherwise, you will get a runtime error when these DLLs are needed.
-
-
-
diff --git a/docs/Help_Spanish/Topics/SBYTE.xml b/docs/Help_Spanish/Topics/SBYTE.xml
deleted file mode 100644
index d3b2aa3b84..0000000000
--- a/docs/Help_Spanish/Topics/SBYTE.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- SBYTE
-
-
- SBYTE
-
- The SBYTE keyword denotes an integral type that stores signed 8-bit values with values ranging from negative 128 to positive 127.
-
-
-
diff --git a/docs/Help_Spanish/Topics/SCAN-Command.xml b/docs/Help_Spanish/Topics/SCAN-Command.xml
deleted file mode 100644
index 63950eb5b8..0000000000
--- a/docs/Help_Spanish/Topics/SCAN-Command.xml
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-
- SCAN .. ENDSCAN Command
-
- ENDSCAN
- EXIT statement
- LOOP statement
- SCAN
-
-
-
- SCAN ... ENDSCAN Command
-
-
- Purpose
- Moves the record pointer through the currently selected table and executes a block of commands for each record that meets the specified conditions.
-
- SCAN [NOOPTIMIZE] [Scope] [FOR lExpression1] [WHILE lExpression2] [Commands] [LOOP] [EXIT] ENDSCAN
- Arguments
- NOOPTIMIZE Prevents Rushmore Query Optimization of SCAN. For more information, see SET OPTIMIZE Command and Using Rushmore Query Optimization to Speed Data Access.
-
- Scope Specifies a range of records to be scanned. Only the records within the range are scanned. The scope clauses are: ALL, NEXT nRecords, RECORD nRecordNumber, and REST. For more information on scope clauses, see the Scope Clauses online topic. The default scope for SCAN is all records (ALL).
- FOR lExpression1 Executes commands only for records for which lExpression1 evaluates to true (.T.). Including the FOR clause lets you filter out records you don't want scanned. Rushmore optimizes a query created with SCAN ... FOR if lExpression1 is an optimizable expression. For best performance, use an optimizable expression in the FOR clause. For more information, see SET OPTIMIZE Command and Using Rushmore Query Optimization to Speed Data Access.
-
- WHILE lExpression2 Specifies a condition whereby the commands are executed for as long as lExpression2 evaluates to true (.T.).
-
- Commands Specifies the Visual FoxPro commands to be executed.
-
- LOOP Returns control directly back to SCAN. LOOP can be placed anywhere between SCAN and ENDSCAN.
-
- EXIT Transfers program control from within the SCAN ... ENDSCAN loop to the first command following ENDSCAN. EXIT can be placed anywhere between SCAN and ENDSCAN.
-
- ENDSCAN Indicates the end of the SCAN procedure.
- Remarks
- SCAN automatically advances the record pointer to the next record that meets the specified conditions and executes the block of commands.
- You can place comments after ENDSCAN on the same line. The comments are ignored during program compilation and execution.
-
- SCAN ... ENDSCAN ensures that, upon reaching ENDSCAN, Visual FoxPro reselects the table that was current when the SCAN ... ENDSCAN loop began.
-
- Example
- The following example uses a SCAN ... ENDSCAN loop to display all the companies in Sweden.
- USE customer && Opens Customer table CLEAR SCANFOR UPPER(country) = 'SWEDEN' ? contact, company, city ENDSCAN
-
- See Also
- DO CASE Statement
- DO WHILE Statement
- FOR Statement
- FOREACH Statement
- SWITCH Statement
-
-
diff --git a/docs/Help_Spanish/Topics/SHORT.xml b/docs/Help_Spanish/Topics/SHORT.xml
deleted file mode 100644
index 2eac702287..0000000000
--- a/docs/Help_Spanish/Topics/SHORT.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- SHORT
-
- SHORT
- SHORTINT
-
-
-
- SHORT
-
- The SHORT keyword denotes an integral type that stores signed 16-bit values with values ranging from negative 32768 through positive 32767.
-
-
-
diff --git a/docs/Help_Spanish/Topics/STACKALLOC.xml b/docs/Help_Spanish/Topics/STACKALLOC.xml
deleted file mode 100644
index 2cf38b11f5..0000000000
--- a/docs/Help_Spanish/Topics/STACKALLOC.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- STACKALLOC
-
- STACKALLOC
-
-
-
- STACKALLOC Modifier
-
- The STACKALLOC keyword allows you allocate a block of memory on the stack of the current function or method.
- The syntax to use STACKALLOC is:
-
- VAR x := StackAlloc <dword>{1,2,3,4,5,6,7,8,9,10} VAR y := StackAlloc int[]{10}
- or more generic:
- VAR x := StackAlloc <typed Literal array> VAR y := StackAlloc <typed array>
-
- The compiler will generate variables of the type "Typed PTR". So in the first example, x will be of type DWORD PTR, and y will be of type INT PTR.
-
- You can also declare the variables with a normal LOCAL keyword. In that case, the type must be <Type> PTR.
-
- LOCAL x := StackAlloc <dword>{1,2,3,4,5,6,7,8,9,10} AS DWORD PTR LOCAL y := StackAlloc INT[]{10} AS INT PTR
-
- You can also use STACKALLOC for an expression that is not a variable declaration. In that case, the compiler will resolve the STACKALLOC expression to an allocation of an object of type System.Span<T>. This type is not available in the .Net Framework, but only in .Net 5 and later.
-
-
diff --git a/docs/Help_Spanish/Topics/STRING.xml b/docs/Help_Spanish/Topics/STRING.xml
deleted file mode 100644
index e67272082d..0000000000
--- a/docs/Help_Spanish/Topics/STRING.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- STRING
-
- STRING
-
-
-
- STRING
-
- A STRING is a sequential collection of Unicode characters that is used to represent text. A String object is a sequential collection of System.Char objects that represent a string. The value of the String object is the content of the sequential collection, and that value is immutable (that is, it is read-only). For more information about the immutability of strings, see the Immutability and the StringBuilder class section later in this topic. The maximum size of a String object in memory is 2 GB, or about 1 billion characters.
-
- Please note that you cannot CAST strings to PSZ like you can in Visual Objects. The PSZ type consists of 8 bits per character, while the STRING type has 16 bits per character.
-
-
diff --git a/docs/Help_Spanish/Topics/SYMBOL.xml b/docs/Help_Spanish/Topics/SYMBOL.xml
deleted file mode 100644
index b6318421d6..0000000000
--- a/docs/Help_Spanish/Topics/SYMBOL.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- SYMBOL
-
- SYMBOL
-
-
-
- SYMBOL
-
- The SYMBOL type is a 32-bit integer that represents an index into an array of strings.
-
- Since a SYMBOL represents a string, there is a built-in implicit conversion from SYMBOL to STRING, and from STRING to SYMBOL.
-
- Since the underlying value of a SYMBOL is an integer, there is a built-in explicit conversion from SYMBOL to DWORD and from DWORD to SYMBOL. A cast is necessary in order to perform explicit conversions.
-
- Unlike with Visual Objects, the number of symbols is not limited by available memory or symbols that are declared in another library.
- Literal symbols consist of the '#' character followed by one or more alphanumeric characters. The first character must be a letter or an underscore.
-
- Some examples of literal symbols are shown below:
- #XSharp #XSHARP
-
- Note that although literal symbols can be specified with lower or upper case letters, the strings they represent are converted to uppercase at compile time, for compatibility with Visual Objects. It is not possible to specify a literal symbol that contains lower case letters; the StringToAtom() function must be used.
-
- The compiler-defined constant NULL_SYMBOL can be used to express a null symbol, i.e. a symbol that has no associated string value.
- Implementation
- The SYMBOL type is implemented in the structure XSharp.__Symbol.
- The Usual type of SYMBOL is 10.
-
-
diff --git a/docs/Help_Spanish/Topics/Settings.xml b/docs/Help_Spanish/Topics/Settings.xml
deleted file mode 100644
index 9ddd089fb0..0000000000
--- a/docs/Help_Spanish/Topics/Settings.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Settings
-
-
- Settings
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Shift_Operators.xml b/docs/Help_Spanish/Topics/Shift_Operators.xml
deleted file mode 100644
index f2ac946901..0000000000
--- a/docs/Help_Spanish/Topics/Shift_Operators.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- Shift
-
- <<
- >>
- operator
- shift operator
-
-
-
- Shift
-
- X# uses the following shift operators:
-
-
-
-
- Operator
-
-
- Example
-
-
- Meaning
-
-
-
-
- >>
-
-
- x >> y
-
-
- shift bits right. If the left operand is signed, then left bits are filled with the sign bit. If the left operand is unsigned, then left bits are filled with zero.
-
-
-
-
- <<
-
-
- x << y
-
-
- shift bits left and fill with zero on the right.
-
-
-
-
- Note that shift operators are only supported on integral numeric types.
-
-
diff --git a/docs/Help_Spanish/Topics/Solution.xml b/docs/Help_Spanish/Topics/Solution.xml
deleted file mode 100644
index d8f3634fe1..0000000000
--- a/docs/Help_Spanish/Topics/Solution.xml
+++ /dev/null
@@ -1,77 +0,0 @@
-
-
-
- Solution
-
-
- Solution
-
- Visual Studio organizes your source code in Solutions and in one or more projects.
-
- A solution is a container for one or more related projects, along with build information, Visual Studio window settings, and any miscellaneous files that are not associated with a particular project.
- A solution is described by a text file (extension .sln) with its own unique format; it is not intended to be edited by hand.
- Visual Studio uses two file types (.sln and .suo) to store settings for solutions:
-
-
-
-
- Extension
-
-
- Name
-
-
- Description
-
-
-
-
- .sln
-
-
- Visual Studio Solution
-
-
- Organizes projects, project items, and solution items in the solution.
-
-
-
-
- .suo
-
-
- Solution User Options
-
-
- Stores user-level settings and customizations, such as breakpoints.
-
-
-
-
- Different projects in Visual Studio may target different development languages.
-
- It is very well possible to use C# and X# projects next to each other in the same solutions.
- You can also set dependency relations between projects for different development languages without problems.
- Visual Studio will automatically determine the order in which projects must be build.
-
- If you want, you can control this order by opening the Solution Properties dialog (right click on the Solution node in the Solution Explorer and choose "Properties").
- The image below shows the Solution Properties dialog for the X# runtime solution.
- On this dialog you can also specify which project should be the "start-up project" when you start debugging inside Visual Studio.
- Additionally, as shown, you can launch multiple projects simultaneously.
- The "Action" combo allows you to choose whether to Start a program or to start Debugging a program when launching the debugger inside Visual Studio.
-
-
-
- On the "Project Dependencies" tab page, you can define the dependencies between projects.
-
-
-
- In this dialog, you can see that two projects are already marked with a checkboxes. These projects are listed as references in the XSharp.VO project.
- Other projects have a gray checkbox, which means that they depend on XSharp.VO, so you cannot make XSharp.VO dependent on them, as that would create a circular dependency. Projects with a white checkbox can be added to the "Depends on:" list for XSharp.VO if desired, which would mean that Visual Studio would always build them before building XSharp.VO.
-
- From this dialog, you can also open the "Configuration Manager" to maintain the various Configurations (typically Debug and Release) and different "Platforms". By default, there is only one Platform called "AnyCpu", but if your project contains C++ code, you may also have x86 and x64 platforms. The configuration manager can also be accessed through the Visual Studio Build menu.
- Refer to the next chapter for more information about build configurations.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Source-Code-Editor.xml b/docs/Help_Spanish/Topics/Source-Code-Editor.xml
deleted file mode 100644
index 0cfa93a22a..0000000000
--- a/docs/Help_Spanish/Topics/Source-Code-Editor.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Source Code Editor
-
-
- Source Code Editor
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Source-code-Items.xml b/docs/Help_Spanish/Topics/Source-code-Items.xml
deleted file mode 100644
index ff5885d209..0000000000
--- a/docs/Help_Spanish/Topics/Source-code-Items.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Source code Items
-
-
- Source code Items
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Special-classes-generated-by-t.xml b/docs/Help_Spanish/Topics/Special-classes-generated-by-t.xml
deleted file mode 100644
index 8bfdc9a8f8..0000000000
--- a/docs/Help_Spanish/Topics/Special-classes-generated-by-t.xml
+++ /dev/null
@@ -1,211 +0,0 @@
-
-
-
- Special classes and code generated by the compiler
-
- $AppExit()
- $AppInit()
- $Exit
- $Init1
- $Init2
- $Init3
- $PCall$<FunctionName>$<suffix>
- $PCallNative$<FunctionName>$<suffix
- _CAST
- <>ClassName
- <AssemblyName>.Functions
- Clipper calling convention
- Functions$<ModuleName>$
- PSZ
- RunInitProcs()
- String2Psz
- Xs$Args
- Xs$PSZLiteralsTable
- Xs$SymbolTable
-
-
-
- Special classes and code generated by the compiler
-
- The compiler may generate some special classes for optimization. Some of these classes are generated by Roslyn (such as the classes for Lambda expressions or the state machines for asynchronous code). Others are generated by the X# compiler.
- Below are some examples of these classes (that you can see if you open a X# compiler assembly with a tool such as IlSpy)
-
-
-
-
-
- Class
-
-
- Purpose
-
-
-
-
- Xs$PSZLiteralsTable
-
-
- This class is generated by the compiler if you have code in your application that looks like this:
- LoadLibrary(PSZ(_CAST, "RICHED20.DLL")) // inside GUI classes
-
- Since we cannot "know" at compile time what the lifetime of the PSZ must be we create a static field in this class and assign the generated PSZ value (a value type) to this field. As a result this PSZ will be "alive" during the whole lifetime of your application.
- If you know that the PSZ will not be needed after the call to the WIN32 api then you are better off replacing the PSZ(_CAST with a String2Psz(). This will ensure that the PSZ value is destroyed when the function that creates it finishes. The following code:
- FUNCTION TestMe() ASVOID LoadLibrary(PSZ(_CAST, "RICHED20.DLL")) RETURN
- generates the following
- publicunsafestaticvoidTestMe() { VOWin32APILibrary.Functions.LoadLibrary((IntPtr)(void*)Xs$PSZLiteralsTable._$psz_$0); }
- and the following PSZ table:
- internalstaticclassXs$PSZLiteralsTable { internalstaticreadonly__Psz_$psz_$0=new__Psz("RICHED20.DLL"); }
- As you can see the PSZ value is stored in the table. Please note that every PSZ variable contains a pointer to static memory allocated with the String2Mem function in the runtime. So these static memory blocks are allocated for the whole lifetime of your application.
-
- If you change the code to use String2Psz() instead
- FUNCTION TestMe() ASVOID LoadLibrary(String2Psz("RICHED20.DLL")) RETURN
- then the result will be:
-
- publicunsafestaticvoidTestMe() { List<IntPtr>pszList=newList<IntPtr>(); try { VOWin32APILibrary.Functions.LoadLibrary((IntPtr)(void*)new__Psz(CompilerServices.String2Psz("RICHED20.DLL",pszList))); } finally { CompilerServices.String2PszRelease(pszList); } }
- as you can see the compiler has now generated a local variable (a list of IntPtr) which is passed to a runtime function at the end that takes care of deleting the allocated memory when the function finishes. To ensure that a try .. finally was added.
-
-
-
-
- Xs$SymbolTable
-
-
- This class is generated by the compiler if you are using literal symbols in your code. For each symbol in your app there will be a field in the class. Inside the System classes there are 21 literal symbols as you can see when you decompile its code:
- internal static class Xs$SymbolTable
- { internalstaticreadonly__Symbol_init=new__Symbol("INIT"); internalstaticreadonly__Symbol_concurrencycontrol=new__Symbol("CONCURRENCYCONTROL"); internalstaticreadonly__Symbol_notify=new__Symbol("NOTIFY"); . . internalstaticreadonly__Symbol_unknown=new__Symbol("UNKNOWN"); internalstaticreadonly__Symbol_resourcestring=new__Symbol("RESOURCESTRING"); }
- This is very similar to the way how symbols are handed in Visual Objects. When the first symbol in an assembly is used then all the symbols are created and after that using literal symbols is very fast. Symbols are stored in a static table in the runtime and the symbol value contains only the offset in this table. Comparing 2 symbols is like comparing 2 numbers and therefore very fast.
-
-
-
-
- <AssemblyName>.Functions
-
-
- Dotnet does not know the concept of functions or global variables. The X# compiler is therefore creating a static class in each assembly that contains static methods for each of the functions or procedures in your code.
- The name of this class is derived from the name of your output assembly:
- MyFile.DLL will contain a class MyFile.Functions
- MyFile.EXE will contain a class MyFile.Exe.Functions
- If your output assembly name contains embedded dots then these dots will be replaced with underscore characters in the functions class name:
- MyApp.Main.EXE will contain a classname MyApp_Main.EXE.Functions
-
-
-
-
- Functions$<ModuleName>$
-
-
- Whenever your code uses STATIC FUNCTION, STATIC DEFINE, STATIC GLOBAL (whose visibility is within the same file only) then the compiler generates a separate class for each modulde (PRG file) where the name of the PRG file is used for the <Modulename>, so the file Start.Prg in Application1.exe will result in a class name
- Application1.Exe.Functions$Start$
-
-
-
-
- $PCall$<FunctionName>$<suffix>
-
-
- If your code contains PCALL() constructs then the compiler will generate a special delegate with a name based on the method/function name and will make this delegate a nested object inside the type where the PCALL() is used. So a PCALL() inside a function will result in a nested delegate inside the Functions class and a PCALL() in a method of the Window class will result in a nested delegate inside the Windows class.
- The return type and parameter names and types of the delegates are derived from the function declaration for the typed pointer that you are passing to PCall().
- For example The VOGUIClasses assembly contain a $PCall$DeleteTrayIcon$430inside the Window class and a $PCall$__InitFunctionPointer$28 inside the Functions class. If you look at the original code in the __InitFunctionPointer procedure then it looks like this:
- IF !PCALL(gpfnInitCommonControlsEx, @icex)
- The resulting code looks like this:
-
- if(!$PCallGetDelegate<$PCall$__InitFunctionPointer$28>(gpfnInitCommonControlsEx)(&icex))
-
- The $PCallGetDelegate function is a special compiler generated function that looks like this:
- [CompilerGenerated] internalstaticT$PCallGetDelegate<T>(IntPtrp) { return(T)(object)Marshal.GetDelegateForFunctionPointer(p,typeof(T)); }
- In short: it takes a function pointer (p) and Gets a delegate of type T. This delegate is then used to call the API function.
- Please don't worry if you don't get this. It took us a while to create this ourselves too !
-
-
-
-
-
- $PCallNative$<FunctionName>$<suffix>
-
-
- This is a delegate generated for PCallNative constructs. The return type is the type of the generic argument and the parameter types are derived from the types of the arguments. The parameter names are $param1, $param2 etc.
- So the following code inside a Test function
- LOCAL p AS IntPtr P := GetProcAddress(hDLL, "MyFunc") PCallNative<INT> (p,1,2,3)
- Will generate a delegate like this:
- [CompilerGenerated] internaldelegateint$PCallNative$Test$0(int$param1,int$param2,int$param3);
-
- These special methods inside the function class are generated to call Init and Exit procedures. See the topic about startup code for more information about this
-
-
-
-
- <Module>.RunInitProcs()
-
-
- This special method inside the <Module> class is generated by the compiler and will be called at runtime when you are dynamically loading assemblies using the XSharpLoadLibrary() function. This takes care of calling all init procedures when a DLL is loaded dynamically.
-
-
-
-
- <>ClassName
-
-
- Special classes that start with a <> prefix are generated by the Roslyn compiler for lambda expressions and codeblocks.
- If you look at the VORDDClasses assembly you will find many examples of these. You may have to set ILSpy to show IL instead of C# or XSharp code, because otherwise these classes will be hidden by the tool.
- If you look at the RDD classes in C# mode it will looks like this:
-
-
- If you switch ILSpy to IL mode it looks like this:
-
-
-
- As you can see there are now quite some nested classes inside the DbServer class. The <>c class contains codeblocks that do not need to access local variables from functions or methods. In the DbServer class this class has some 25 methods, each of which is a codeblock.
- The classes with the name <>c_DisplayClass<nn> contain codeblocks that need access to local variables from the function or method where they are defined.
- The compiler has detected this and has moved the local variables out of the function/method and made them fields in a compiler generated class, so the codeblocks can access them. In Clipper and VO these were called "detached locals".
-
- For example DisplayClass56_0 has the variables for the Average function:
- .classnestedprivateautoansisealedbeforefieldinit'<>c__DisplayClass56_0' extends[mscorlib]System.Object { .custominstancevoid[mscorlib]System.Runtime.CompilerServices.CompilerGeneratedAttribute::.ctor()=( 01000000 ) // Fields .fieldpublicint32iCount .fieldpublicclass[XSharp.RT]XSharp.__ArrayacbExpr .fieldpublicclass[XSharp.RT]XSharp.__ArrayaResults .fieldpublicvaluetype[XSharp.RT]XSharp.__UsualcbKey .fieldpublicvaluetype[XSharp.RT]XSharp.__UsualuValue
}// end of class <>c__DisplayClass56_0
- The codeblocks inside the Average method apparently access 5 locals variables (iCount, acbExpr, aResults, cbKey and uValue).
-
- If you look inside the Average() method of DbServer you will see a codeblock such as
- SELF:__DBServerEval( { || iCount += 1, __IterateForSum( acbExpr, aResults ) }.......)
-
-
- If you look in the decompiled code for Average() (in C# mode) you will see something like this:
- __DbServerEval(new { Cb$Eval$=(<>F<__Usual>)delegate { iCount++; VORDDClasses.Functions.__IterateForSum(acbExpr,aResults); returndefault(__Usual); }, Cb$Src$="{ || iCount += 1, __IterateForSum( acbExpr, aResults ) }" },...........................)
- The whole {} after the new is an anonymous codeblock expression The Cb$Eval$ field in this expression is a delegate that contains the code for the codeblock.
- The CB$Src field in this expression includes the source for the codeblock so at runtime you will be able to see the source of the compiler time codeblock (this was introduced in build 2.3.0)
-
- The actual body of the codeblock (the part from iCount++ until return default(__Usual)) is in reality stored as a method of <>c__DisplayClass56_0. And all the variables that are needed inside this codeblock are not really stored as variables inside Average() but they are stored as fields of <>c__DisplayClass56_0.
-
- Please don't worry if you don't get this. It took us a while to understand and create this ourselves too !
-
-
-
-
- Xs$Args
-
-
- Whenever your code contains functions or methods with the so called CLIPPER calling convention, then X# compiler will create code that handles the parameters in a special way: For example the function Str() in the runtime. This is declared with the following parameters:
FUNCTION Str(nNumber,nLength,nDecimals) ASSTRING
-
- The compiler sees this as CLIPPER calling convention because all 3 of the parameters are optional.
-
- The C# version of the IL code generated for this function is:
-
- [ClipperCallingConvention(newstring[] {"nNumber", "nLength", "nDecimals" })] publicstaticstringStr([CompilerGenerated]params__Usual[]Xs$Args) { intnum=(Xs$Args!=null)?Xs$Args.Length:0; __UsualnNumber=(num>=1)?Xs$Args[0]:__Usual._NIL; __UsualnLength=(num>=2)?Xs$Args[1]:__Usual._NIL; __UsualnDecimals=(num>=3)?Xs$Args[2]:__Usual._NIL;
- As you can see the function now has a single argument, an array of usuals. The parameter names are stored in an attribute of type ClipperCallingConvention. This attribute is used by the intellisense inside Visual Studio and XIDE so the parameter names can be shown.
- Inside the body of the generated method the compiler now declares a variable that has the length of the array (the number of arguments passed, which you can also request at runtime with PCount()). The compiler also generates a local variable with the same name as the parameter and initializes each variable with either the value passed (0 based array elements) or with NIL.
- In the body of the method you will see a try finally. In the finally clause there is the following code:
- finally { if(num>=2) { Xs$Args[1]=nLength; } }
- The reason for this code is that somewhere inside Str() nLength has been assigned. Str() does not know if the variable was passed by value or by reference. If the value was passed by reference then the array element inside Xs$Args must be updated, which is exactly what happens here.
- The code that calls Str() is now responsible for assigning back the value from the array to its local, when that value is passed by reference
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Statements_-Expressions-and-Op.xml b/docs/Help_Spanish/Topics/Statements_-Expressions-and-Op.xml
deleted file mode 100644
index 8dcc3ca69a..0000000000
--- a/docs/Help_Spanish/Topics/Statements_-Expressions-and-Op.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Statements, Expressions and Operators
-
-
- Statements, Expressions and Operators
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/StringLiterals.xml b/docs/Help_Spanish/Topics/StringLiterals.xml
deleted file mode 100644
index 61dc0a8554..0000000000
--- a/docs/Help_Spanish/Topics/StringLiterals.xml
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-
- String Literals
-
- Extended
- interpolated
- Literals
- STRING
- String Literals
-
-
-
- String Literals
-
- There are a couple of different string types inside X#. For normal strings, the notation can be different for different dialects:
-
-
-
-
- Literal
-
-
- VO, FoxPro & Harbour
-
-
- Vulcan & Core
-
-
-
-
- '<char>'
-
-
- String literal
-
-
- Char literal*
-
-
-
-
- '<char>...<char>'
-
-
- String literal
-
-
- Not Supported
-
-
-
-
- "<char>...<char>"
-
-
- String literal
-
-
- String literal
-
-
-
-
- e"<char>...<char>"
-
-
- Extended string literal*
-
-
- Extended string literal*
-
-
-
-
- i"<char>.. <char>{expression}"
-
-
- Interpolated string literal
-
-
- Interpolated string literal
-
-
-
-
- ei"<char>.. <char>{expression}" or
- ie"<char>.. <char>{expression}"
-
-
- Extended interpolated string literal*
-
-
- Extended interpolated string literal*
-
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Strings.xml b/docs/Help_Spanish/Topics/Strings.xml
deleted file mode 100644
index 64b1ca1528..0000000000
--- a/docs/Help_Spanish/Topics/Strings.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Strings
-
-
- Strings
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Strong-Typing.xml b/docs/Help_Spanish/Topics/Strong-Typing.xml
deleted file mode 100644
index 9436d67ab8..0000000000
--- a/docs/Help_Spanish/Topics/Strong-Typing.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Strong Typing
-
-
- Strong Typing
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Stylesheet-for-Style-Test.xml b/docs/Help_Spanish/Topics/Stylesheet-for-Style-Test.xml
deleted file mode 100644
index 3b4509d94e..0000000000
--- a/docs/Help_Spanish/Topics/Stylesheet-for-Style-Test.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- Stylesheet for Style Test
-
-
- This is Heading1
-
- This reference topic is a showcase of the styles contained in this help project template. Once you are familiar with styles, you can simply delete this topic (select "Stylesheet for Style Test" in the TOC, then p
- DEL).
The predefined styles in this project should help you get started more quickly. You can change, extend and customize these styles here: iVBORw0KGgoAAAANSUhEUgAAAYsAAAClCAIAAAAiU0YuAAAAAXNSR0IArs4c6QAAMV9JREFUeNrtnQdAFMcagOcqh4AgvaogqFixAioaW1QsEXsJGk3sJr4UEzVRY0uMJaYZk2g00VgSNRq7sUVBBCtiAQEBBaT3fvXN3t7t7fV+t8B8j9zbm52dndu7/fxnbm6GJhKJAAKBQFASGjIUAoGgLMhQCASCuiBDIRAI6oIMhUAgqAsyFAKBoC7IUAgEgrogQyEQCOqCDIVAIKgLMhQCgaAutLi4OGvXAYFAIFSDYigEAkFd9DbUrVu3wsPDrV1thIE0irevUVSy6UHNy44M1bxoFG9fo6hk04Oal12nfihyvan5MhA6ovD2HbiSbe0aSYge6qeukgjLQM3LThMKhZpzxMfHI0M1GZChEOqg5mVHhmpeIEMh1EHNy44M1bxAhkKog5qXHRnKlISNXhx/9kfqlKMMMpQxOL62Qt2uiv82W7t2xkLNy94UDDVg5t+xBydYuxaNgyZmqIOHYzRnCGznGNjOx9HRkclkGl9JaKiJ/hcc/F+vLHzJbOk8cMEXbI5dXWr8stVnkaGMKV/w7rvqjjKxoeKSCnYcTFoyMfC1vv7me6lkoJ4EgoZbR6YDceih6YWYISohnxGWr6ECms9uqnK00vQM1f31CKFAxS4aHTTU1T+LvWNnWx0aGuLu7s5gMIysJDTUlH7nKxucuLZ8XgODyWnDsxNW1d99+F9UczNUdn7V3uNPEpPz+3b1WLlAp6MoYajJn1wqcwlNObUlJ3YjfDrmrTV4ukgk4vP4ODw+TygQmtAXIeO+Szz1nqlKa9oYZihRYZ0gsQgfOccI96A5sOEnh0YzZcUMNlS3YRJDYfWhw7oCkVDytLa2rqE8Nyclz862sl+/Pq6urnQ63ZhKQkMdGvcVowVgOwAhB9TwQEENyGsAX//1iWZD7Z0UvPUJAJ2Xnz82t60pL5sp0f2yV1ZzF2+4Ulpeu2nZgB2/xe/f8oaR5VvOUP/dznzzg193rZ86dkhXc15MGVBPdbVFDQ3lWTHfW+aMZF6V8B5l1Oz8p+DUxg5AYxCn2chR614sjHTs0pbj48YxphytGGYo3uFUm6xafh2Py+XTXvNkDPOlMxg0QDehpAw2VMjwCKgkGgs0VPN4VYU0JsfGwZnJpgn5QCgSleak9e4aeOrvmw521eHhvV1cXIyRFDTU7xP+beVE6xJQ2Mo+7xTr7uSfeuC73rfdj2989tnEli1bKB16bVXwzkAq+0nny15Tx1u14+bdx6/WLA4bMSDAJOVLDPXNN9jj//4n2RDTFPqhrAJ00+Oshl1nSgS8+l3L2hhpFljawh0ZvPqqRePcenRwmTz3Y8PK0YohhuKL6NuTAkL92LbskqzSFyl54JOuLBZb3GiSKKq2nvc4o8DD2a61h5NYW3qry2BD9R4ZweeLihK2u3H3twDpzJbdylnTKm3DXNqHCbiAX1XYvZ1rJY9++liMU8vasLDezs7OBod/0FAwViqqFVRVVxUWp0fs6oOnf7J80ldbjx1e8KCTS8hvOw6sXTvFzs5G/tCmY6jIBScqquqEAqw55OTsCVP6hbivW9KntKJ+2caLLTjg5w1v6Fu+akPBDcJQK1euJB/w5ZdfEttWMdSKFXJfmmzerDaEHjDzb/j48dzgcUODLXNGHBj1YFeWVw+1wm2ogo/w79aBmfqeV7kcfkPNyR1R7i4ck19VYJChBPeLXB9VeXV0FwlFAq4g8WqyaGobdpALg8mi0yTxyM2kF2VVtSWVdTOGdmEwmTSa3uGVwYYKHR2R8+8Hbbk7BCJQSe/AEha2bt2qlPVOrqCva+eh9oIaN3tmPU9QzWNcu3Db2akuLKyPk5OTYZKChrr45+a8YlBWCSqqgYgLKipBQTHv11T2xysmbNn895WluX0DPNd8enDduqm2tmzSoYShxBs/Rp5bjDX7on5Mnp85aRS2KWsCwhyLT4gPgru/GIxtZO3FM3Vevrz91nMS00kTSflUo+NnW8fL/vVvd4+efzptdMfpozvDUHrB59fLK6sPbhl5Oym3qrruzOXHh7+bqW/52g0FSJIi6wlYr6ecuKxaZfE0vXDGB0cST71nZE+57mcE0hhqx+EUqJX9a8LVxVA6hjywtOjPY6GePoru3trdfuGHqw0rRysGGIr7fVIbb2cnb8fc1HyvAPeMhBdl7iLmlCA2y4ZGZ8A7XSAU/XExcc7oHqdvJAd4Owb6ujJYTEJeOmKwobr0cKPd7CoAzNp2h1oFR3FrKqvuLQ92vV7f8p3n5UF09z75OellpaUAiFo6thJUMTzduX369GnZsqUBVw8a6s/9mwuKQHU1qK0FdXWikjJRTS396PEVtV2/Gj+v18nd927Mev6qJDfhataWLdGkQ8mGWnwCtxFpU6wlIC8auUPwfWIpgeWE6XBVXVs1KXO+5vBMl8+2jpd93mfnE5Nf7d8yLridG3z69e/3j19M6dzO6Yc1I9gsTd9FGGsoIJaUgp6AVXvK4WXVUU+Hvp7WKdBda4EmOSOZ3KL6O49zvtqbgEdPBhtq6LvX3p/WoXtgSz8Pe2PK0Yq+hhJVcJm/JAf0bVNTVpOZk9+1c7vS7LLnT1+yVoWwW7QQf4VPe/Q8v4HHD+kYVFSSdyPxxfj+QUyWDV0sL90x2FD+re7ZZbxf0/pTn6EbhQ3YV3h8Aci7+l6w8wWu47yEdE/g1JvfUIl97vg8Op/5IjNm8uTJQUFBBlw9DeOhxIYKPbk74fFHPB69ev/3p9UbimjuqdmWBVFifYG9kz4C2yQGkmYDRAAlRksUhaH1s63LZa+oahj21h8ujqwLe2fhKUmpRfM+PePnwTn2w3TNx1KiH6q59ZQ3OvQ1FP/iS+ccrndH9/RHL8tedwm43WDf0j4pPgW87m3T15vFhGEU7cCFxKhBnV9V2LbzFP1x9vbQnq09XR1hG1CvlpTBhmprf9U293PQZY97n7cFdVgigwVKiqozT7/5Wo9nZcw5cZmqi/L2tgvu4O3s7Mxms3U5l0o+/vjAjjrJvRoZ3e/cAcnv8N+33W+goTD1pC+RBExiM6k1FJ7NZOhy2S/ceL5y+8U3hrT/fNkwPCUtq3TuiuMlJeUnfp7dIcDdsPJ1jaFUgnrKNdDkx0NxN9xp3dHT0bPlw1c5vFGebn8X+Xi6Pb+bWc7hcpZ0Z7NtXhZW3X/2auzAkJspvBB/dlrW85Ly6sE927JgG1Cf3ijDW3mBlbTUD2tZoc5hG+3d/ARcQGeAsqKqh/GJ3qy/e3hfKRDOrPJdaGPnKJJ+0mGGkqKinMQUBr2qb5+Ofn5+LBbLsOsJDfXllmjOu7T+UzuV19SlF2c1xIvqvxet/PiAgYbKlKZhLbpzkZpaeYtTTTp6QZfL/tmOy6cuPf5t6+SenX0Wrbu0Yl7flOeFJWXVG7+/NHVMSHjPtrF3MtZ/MFLf8puyofCecmLQJkIzehlKmFHBPpUd0MO3pqwuxauO3tmlxbXiANCyNK8s4/lLznshNu4tz9xKq63nvzGoy61Uhpsj09+19s/LDycNDHKwt8PbgDpWzGBDDRkT8ezIIB9PYQk3xC1slb2zl0gAykqq7sclBvXrz785vKNP5lPWHscOQ0Q8yVF0Oigvr2BxS9If5QJRWf9+3Xx9fQ0bdI4bCm5ASbHCabxbmJ54QrBmhZyhSOOh/H/R0sojesWjokBq4Da5dp+annKdWnn6fjZUMnDazwy68NqhRXB74rvHewa7rFg4SCAQzl959N7jnHFDO63/cBSDTtO3fMsZyvJjyiHh0w7/unFop0B3iowpN+BEpipHK3oZincw1bkaeHf0eJ6aUzbBg2nLYVUJPS4WczicpPtP6WEe9f18j994BnMO6tm6nOslEDFCgxhXE5Kc7dm9Ovow2Wzdx0wZbKjIyRHFL9Oyz4zwa+tdwu/tE7HW3qVV7uOEwsvDOJ7hXJtunZnbk9nfu4UvFXJlB3J5fHpNfpf2vkcOx9BEJRERvby8vAyQFDTU+i+jOQwgEEsK6okuAvUCsHaVQgxlIrJM37jT/bI/ePpq5rI/Fs4Mf++tCNOW38THlJ+6krz8y0PPLm8wVYFNGD0MxRXwvrzn28HL0cOh+GUJt56HvYsiwGIxnVwcUxJTKwV1iWPbpGaX2rdgOdlz/HwCavgOfq5MYX3utXsZM4YF29hwyGOmNGOwoUZNiKDRQWlO2stz47x9WlbQInwHbSpJOcFKme7TGjxJpre0E1Z1+KdV8DghT3YgXyhsxaj2cW0JzQIlxWTASKqnp6envpLCYyg+XwQDB1gNmgheNhGTQVv1iZyhgoMlQ2GSk5ONeftM37QjoeGyL1l3pqKixsfd/klq/tEfZ8F/qkxbftMfU37ip3dN8l2ekTSluQ0EdwvYNwoCQvyAEAj5QpFAJBKK4CMQ//YlLyf/WXHeue6taDTRuHD/0/GZvYL9G+i+LAatiw/35LUHPYJcgvzcGSyWjsMODDbU2InYiE2mDa0sNz3j1Bgvb/s61gCBy5j0f9/r2T7Z2wvcf2RnO/iuS7uOvAYAG4AMJqbMhtp6Rn1JRUV5dXU1y9YhO62EzSof0L+3vj/f+/hj1bGSunSDMHVzTg0aLvui1Sdj76T36uK74YORft5OJi8fsmnTJpXpjb4fCqEXuhuq7psHrmxb7/YeucmvyvLLoJ2EADoK+//23YLodNrvr549a23Xwc8xvJPnjaR8vhC4eXcGNLa/mygjK/VFXllURBCLzdFx2IHBhnpjMmYouI1JKuf58zNRrq1gsMTl1+TmZze08Qc+fuDpy84Cv0+YFZdEvBqm5xiO73ABq1Vu9ouK8tKa6mo+r4EDowJuC0eHin79+jk7O+t+PaGJ1O0ySyvPnFhxbgMNIEM1L3Q0lKi4XvDTY992HkwOM72upCHSk/zFnPO5Yg8bx8/5mfU0ENW/rZODbXkN/3xCRqcOnZgcNzsbuotN0akbjyL7+us+7MBgQ02YIjEUwMYZ0OoqyzNjd1Rm/UUT1QCXEdyq4gCHk15e4OEDTFVOjsDGISCHO7OUM9w5MIJXXysUCoRCEYzzkmIfPk+7NnXq1A4dOlj7XbIOyFAI66OjobjnMzlJFW27+ZaXVmWOdmAwmEzstywM3DU2ZfyiuIIjwiIfV7thPb1ZLA6TxT72X7KDg4OnN9a693dpiLmbxGKKhvb0Z7F1GnZgsKEmTZUZCmAjCWj4wOY/D8cMmRhRX9Xw5Ld+7T3ue/mAxEd2NiH7RIVH23s+rrZ9p0jQ07Pba3j3OZMJrvwTc/f237Nnzw4JCbH2u2QdkKEQ1kdHQ9V8Hufq7OTi2yrfiVfWyx5aBv7RaQwRTewCoej46aQCfsPwnj4+7i3ZbBtoqOc5JXFJLzt3CWeyOK3sQGVxeuzDjGlDOra0t2PoMOzAYENNnS5nKAg27QIAfx2JGR4VUVValn28C7fylZ8f8PUFTwtedx1+seC/ecHu12vt5uXzQnxChgu4mKEuI0NR01BoNapmhS6G4qeV0U5keLi34jjYPhvIBrZMNtuW/FO77MKKf24kOzlw3ghvzWSyobxghAXbSnvP3PPzDbCzc4Y6CnQXXoxLDPJx7B3siw8911wxgw01AxpKoMJQhw/HjJwUUZyVVnO9a63Au1rYzRP8U8Xo4T/lLp1Fzzw7t73z5TqHhSW03r4hr4sE4NJJZChKGsr4FT1NMk8j+QOKMB+6GKp2/2N6amVDXb1opBcj1IPN5ij8zu7szWeZeWURXb0DfRxZLBvpuCfR7SfZT7PKXD2C4eeqjTuruDgrPbvwzeGd2TY2WocdGGyomdMjBEJ5Q4ltiA2VmhRR9upl3tkIezd/m67f8Spf2HsEO7gHwtw8Hsi+NK+dy41y5kyB23iPwG5n/0KGQoZSDzKUZdDFUEKRUMDj8/gNQqGQQWdAPTGYDCKAqqiuP3AhEW64uqnoUS4rSXVy6wU32ExaeEdwLuZ+v86eQa3dyVO1qMQYQ6nbNXoSDK9A8t+zvJ1yywS9/QatsrFz5NeLoCqhb3l8kH0xur3XveeV0W0Hrzx3HBkKGUo9yFCWQbd+KJFAIBQKBHCDRqcrTKd5/UHWo+f5Gk7B4di1cukCNzq34WS8SC6vrJg4qIPW2Q6MiqEEcn2pDAYd3zVuUgTcUVOS/ezvSG8fxwpRWJuBK21bugh4ktEJeSkJjKQwhvt4+95/XTwbjwyFDKUWZCjLoPN4KOxzAf+HNd5EstECDTzB3jP34Ean1k492rnAHVgHk4gmacCJQOyTvBeFVT4+wY4OTvYcuntL3un/EsaEBWgddmCOtV4mTIng8UQMNq2i4EXqyTFeXvYVotA2A5Y7uPrwG0QsDi3nSSztYYTQLsR92P2zp2KRoZCh1NIMDfWqhLfkh1c7l3p7uxj4w3oDMHKtl9tPc+BfkK9T/84eUE4MBhObxI6UAX6cjlxNpjMd2rbtBJ92ac2JvZ/EENYO7R2gediBYYZKT0+/ePEifFTe1bvvhEnTMEPBbSabVvIyJfWfUV4+rjXMQT593nfy8qkur3t5dZ6H4GCOcGbI1D+OHdavlZefl/8gMSnp4aOamlpbW9suXTv16tXD29vLPO+bJdBw2bf/elavoj58e7Re5WsAGcpq/HuveteZkkVjXF7vpXrWOgIT/gLGGENV1XKP/JvEEwpGh7Z1dcS6z5ni3iXJEAQpz7IKrie+7Nihr42NrYsDowWLe+a/2HH92nm4OGoYdmCYoaqrq/Pz8+Gj8q4nyVVTp0sMBYEBXNGLJ8/+Ge3m6cCl+bPt3esKbjrRUioErX1HXHP3CTiss6F4PN7JE6dTU9P79Q/zb9vaxdWloqIyM/PFzdhb/gFtJ0wYZ/BcLtZFs6FUSkcl76xav+eLNXqV3zCCRju+WzRxHv5oc1H2iUKGsg54AIVPT77nky74JMIWwBhDnY9PK6+sraytnzm0AxPKia36h8E8Pn/v2fvOrbzbtmkPI6aurW3O33xUX1sSNbADi8VWF0aZfM1hfCACjzRUismklbxKz7ixilYdx6/MZdvSGM4D3Xpt8w7sDWt0SDdD8Xj8PXv2waBpyJCBdXV133zzvYODU0VF6apVKxwc7C9dulpQULRo0TuNUVJaDfWqqBZun716S2Hv6CGyo7zdWhhgKG71HtGu4zbLLzRsHUlbNJFt/w6xy8SGOnL4KHmXSCgQCPhCAQ8+CgRcEZ8vfsoXiYRLPpBbu0HBUKPf+VrHcjTHF1Qrh+DinfKd/xTgqye8O8Fv/OBAYpf5pgAGRhjqeW7J1bsZ3bqGPnycMHVQIMeGw7KxUfP1nOjY1SeF5bW9ew6CIvNuxeDxuef/u96vs1eHNh7isekqFGUOQ82cHsFXGogAE0pzk2tKX3Ba+rj4doHVEQhFTDrtoG6GOvrX8cKiouHDh8DA7fr1Gzeux9bWVXE49qNGDR87diyHw7lw/pJQKIyeNUP+OPEMT0o/+yXNSKf51ZCn1sSntTPy8qhAq6Gy86vg9oXrt+dNHYqnw0u36au9cGPOnCl4ip+ng2ExlM1F+P88AFgNI8D5GZ8JBfAew36RhGIo6zDus2e7lrWZtf7W/jXhkz44bsAiMYZhgKEKSqrvJOfkFFf26BaWkcutr0hswWG39nAI7dSajn1rJqeb4vKatOyS+6l58HPl4e7t5OjMYtLdHdl3nqTVVFd6urQYN6AjDL+Uz2ImQ6n6eMsMie0TZ4BJuhgqOzvnhx92TZ8++enTZ76+3t7eXtu37cBmxKODNWs/y8p6kZubFxbW56ef9syZM8vfvy3pUEwxqZ1B5DayXPCJ6XRZ59MSi1lpNVTmqwq4fTnmLjTU2f8kky3cuxX/v2Wzv/n29+jZk+BTf29H42MoUUWt7N0yXwwl4HP5vAY+nyvEHhugEhXiJjIqDUWOXJRL0zeyMKY0k8dQOAPnnbqxexy+Tdl+qNtPcx6kvnJoga0zLB6EIGqAr1sgZLPob0WG0BmyoVIpL4ou33muoSgogohuPt2CfJV3mclQeuXXaqijR/+uqqp0dHS8cOEivAJvvjk9OLgjbLcymYwnT57u//2gQMifMmUyj8crKy17a84s0qGYYoBs0kxp2iUQdSJVB/VQwlDp2aVYVeIeQEPB6Al+EvgC0bYdv5XzcmH64jlL4WOgn7Px/VBg77d4OryhUAxlTcKjDxoZPem7zJ9BrTyReOJBqHK+eAoWLGyCtyUUE4PFYjFZdFlvFDaQSsDn8QU8zGRCISB3oovEhzEYdnYqVoIyh6H0PUSroVas+GzkyOHXr8fevZMAaPTJkye99tpALpdrZ2dXUFhAEwdnNhxbe3u7bVu/2bFjK+lQXDFL0kddGi5bA+8jsA2m7FS7/p2KZfJkqlKxrJ7qOuv6CdFqqGcviuD2jfikuZOHXLjxlNjbq1u7LT9sWTAbmxq4Qxs3Awz1z/7VI4e6KSRiE5IJBagfyjr9UBrQtx9Kr2X+DDMU1h8A/xPJDYzEBkFhwmEQnd/iIVTiKAubRkr15wrexSyWjXK6yQ2lYSCCOgIDA0eMGAEf1WV488231q799M8/j96+ndCrV6/58+fV1tZt/3rHpi/WJ2bGH7/xe1ZRelu3oIkRs0syayZNmEg6VGIW/1+CJYqSrORCTFuuvP5dppZl8uRL1hBe6fgJ0WqomEdYrJTyNGX2hMEweuILRTy+EP7Bt3rrzi1RUW/DvRFdfQww1InfPo0c7kFOwfUEUAzVNNB9mT/DesrFnxH8P7lPC03Sp0PTmlP+EEv0lGsYiKAOe3t7T09P+Kguw9Kly6KjZ3p6erRo0aK8vKKwsLB9+6AW9i22n/j0Zt4Zez+77l7hD1/FVb2s6W43ZNP8H9hMwsWkrm7x0lJQP2JVqV//bn6mikWo2qpfVq+tppemyydEq6Hik7HfEjxKejLzjdeuxacQe3t2bQcNNWXyfLgdFuxpgKGO7l45LlI2lIzQk+lbeagfSq9aRa17cWJtG3ybsv1QlsHkhjIHO3Z826pVqyFDXkt8mLRv7+9cbsO3332dXvJo+40P/Yc4+9b0XhPx0/qYhTl2dzIulX0x4be+QQOlh5KXcvkILIk8txO3j/r177L2ajKU8rJ6bY19dVoNdT+tEG7fu/9o6thBRPSEAw315vSFcKNnkLsBhjq86+MJ4yS9k2Q9oX4oK0M2lGVAhjKG5OTkjRs3b9q07sCBQ3FxcampyTGxMRuPvZ/lcD+sHfYFPDTU5zfmZZSnFBXn9WIO3zhrl/RQxdhHGvbILX0uv0iCxsXQVSyrZ+yr02qoR5klcDv+duKEURHx99OIvXgMNSd6Cdzu6u9igKEOfP/RlAmtgZKezBtDAdQPpR7opp1LvRfuyPjp/YDoz2OvfC/7t5Oa46HMTaMwFHzXv/hiM5/Pnzv3re3bv0lLS93z6+53fhoVPjwcuomcE0ZSSTFJx1YRk6+Re4ugVH7xP4aHS6R05QUTVCyTp3FZPePQaqiU7DK4HRN3f+zw/gragIaaPwdbr6WjXysDDPXbjvenT/FX1hPqh7Ia5BGb70/rMKa/t2XOiwxlDPBmqamp+fDD5e7ubosWLUxNTevSpdOav5Y85cUP6RkJxDEUdBPcuHrvXH/nyE2zfjL2lBZEq6Ey8rDxUFdu3M1LTS8XFSjkWTpvGXwM8DJkPNSere+9OT1AWU+oH8pq/VC5RfXvfPUY6glK6uDGIX4e9qgfSl0lKYVQKKyurv76628SEx+OGDF85KgRj/Nub/33IxtPENFpNG6omOSz9blg3cRdQ7qNsXZ99cCKv8v75at34x7KRtLV1tbX1NTBv9raOhRDWY1TN15sO/Dwo+ju4wZarisKGcoYoJtgE6+qqqqhoSEtLe3KlavPnqVOnDLhZv4/yZW3BUwwasiY81fPMPhgaMeoVVO22rAs9HNLk6DZUMnP7+lelL6GgixbNBXf4PH4ZWWVZeWV2GNZJTKU1cguqJ66/PSfW8fCAMpiJ0WGMjl5+XnFZYWZ5ckXHhzLzE8N8u7UL+j17n5hrVo6e3p6Wrt2eoDmh9JEMzSUVdDDUI+2fvHzJfHW8Mk/LA/SUnD86aX7Xdf8GG7ows9GGEppyKKWr7cs8QuSxggylCaQoSyDroYqPPrr+qyBuJgKj94qmBzeVbODqGQoE+dvLiBDaQIZyjLoaigYQJ1ru/CTyaQFwpGhmjjIUJpAhrIMOrfyoHHWFI7f9/YwH+LpI3xP6LzBr3YXR/47tqv4qcRlfjcJQ2Hx127xd9F48zD31ldzronP03WB9CglTGoo+RHYy9tv3YqPKlIxSPKExp/dNiuarKEQjQh9esolZpFqhRQlQSslRqyKDoOpaQdeTwmBGYi9ctl+LZjxtschIrMGzGYoqYNkI7TxvdvARwo/M2nuIEMhrI/e3+WJAyL3BWQHAbGtYjpi8VH86a+y+2ONQeleQARQYkLXrxqRDVOALBxTjRljKMkuucTUzk+AmaaqbLQgQyGsjwGjDUovL/4pb9aqaEDuaYKJJ8CnUWATfBSrh2woaRe7QiEn063TylNhqMWpnTs/aY8iKDmQoRDWR+ee8qO3PCaLZYS19Z72ghFQtlxfOIyt9mW5g0zXOURURbTyyB1YMnCpqYukLBxD4VM1oQ5zMhQ11C9HLuNb44b29HBtZdRpZPM/a7Se1mymKgehhF495dKu8fVEl9PRBPmnYL20g4nUBiwkNfRg5pAYXcZVGWcoyTxJQNIdnqmLoSQ/vgXLk4/N1fFMS75XvFzYTLhCbGI/vgCbX5QvFPEFkqeQk+s6mul9NAeaL/ueo//hG1XV1VVVVZXV1XV1dds+XWDLsTFJ+eqQxFC7/7xy7WbsjjXvaZWUFkNJ56VX3qkYrEkzm7EcILUYUpgUE44pl/aRm6ZijWJM+TtfZ3XtKPels0Ao4vEwJfH4kgkn8fWvYHrGy9wmZqjZUYPwbXg/wRc4ZdHKvdtWujk7maR82Yn27PkvJq6i+6e1NQ08kUBmKM/WQYcP79MqKV0MpRM6GMrYcoBOcZZeZ5u14MP9P2/X5VHXEvXnk82nS0rraup45ZUNQvnVli4eeFvzsSYzFNbKA1FyA6aMwmBDBQcHK6QkJyebqFKKjF+bolf+JmkoXE/wb/qSVdBQy7eeBNgPqgW8hnoet47Pazj8/UcqAyutb2t5efnseUvYw7/i1vGqrnw2KgKbMB4zFPyU/3r06pihoXfTSqGkDn231sCXoTH2IYNp0dAYSo9yiNKkuTVkaSxhFtRT4pNClbu06gmYxlD4KITAwUaMz1SmUcRQOw+cWxIdSTy9Entv6IBe5KeDwntiM7QLAXwcFLXg9rk9+C65hqgYNRP3qhxNaqEhppov+459Z5ZGjx4/Zzn+9PBPm2e++yk0lH0L2+raOnJOqCeYqG/5kGHjo+2HbuDx+K8JTixfLjkRDTae4T/D+45dfZqaXlCEzUNsvKF0wiIxFO44YreC8IgGo+4nVI6PdEkxIdPfPVhaXk88xa00IvpXXfQE0C+HjUODoeBddC3ufkRYD1xP8G/whIWEoaRodQ11DbX+u8MrFk3Doyeh+HHWss9MGEPBxt3fZa8J+ALX5M0H9+8j0mmw5UxYH/7N+3iTmWIo6/RDkbNJj1c4tBEFUJDRc/bx+bI1V5ChLIk6Q8FbCP4zf/3W/QF9e0imXxOCoZOalKE++mL3hg/fJvQEX+Nb/1ttwhhq7IQZ1SGfCgB/Wef0iRNly+TQGngCQk/wsi5YYZyhcIz/Ls+kMZTkbESiVHMGdKObKobSd507gvkrjr7IrSSeIkNZEmiojv4eOmZe+cUurYZSWvNOnOHHyHOL8WXyFH6mo2pNPVUY9unSfNmXrP7uZW6uQqIJY6iwsQsZvRYIBPwLHwY5Ocl632n1DQJCT/Bx0covDDeUqTBhT7lyZhySoYCVvuvTa507gk82n378rJgIo5ChLIlyDDW4X08YPeGtkNjbD8J6d8fvI/iJen3KIp1jKPmf6eBmks0ho3opKvGaem3VVdWAT5fmy15X36AQKwFxuMSg000SQ/UdOx90f0cgENz7Ui4P7ZNdWSoP2LxQ9cSPjctQyu1EWVaDtGTa7/J0X+eODPFdXml5PTKUJVE2FLlrPO5OYt+e3XE9wabQyGmLtRtKcc07uQzXtK6pp3FMvL6fLuuOhxo0elpVl3ehofbNsO/ZsyeRrnpMee8ZZ+8eGm3AaUyDab/LU1m+9HjzvhAzQ4jJKobav1luoOOsFXuNeS2NzlDKXePxdx/27tEN1xMMrCKnazNUlvKadwpLwuC71a+pZ1KsOx5q69at+/P6QEPN8b1PfJEHofWfg13E+ZPCfjkWjyfF7n3bSEPpZBaNx5sxhsIzGyopq3+XR8a6hgIkSRmpJ9B4DGXKfqhrymvekVbNk/lLw5p6psS646HKy8v7vfUt3zvULv3Itb++IbqisBhq/7knUE9QTAPm/gpVNSuyM5VjKAO/y1N5FmmJ5n05ZsPqhgJiSRmvJ9B4DAVjKDxEgkFTTPyDfn1CiD7cuw+SenTrKu2WEo19c6m2Vp7ymndYBhAFTpzAGnPSZpzGNfVMh9XHQ129enXRjqsNnn19Xu7f8MniIUOGANxQUExQT/AJoSpzxFB6/ETZfD3lysdKK6fjESiGMhONxVCLZo5S1zV+LzGpe9euuJ5gnjeilQ1Faaw4HmrPnj2/H/035uJfMJLavXv3N4/9OQW3n1/YAohWHgH1YygCWXvNmCBIT0mFTdykS7b445+a9xKJQYayMNBQC2aMUtc1/iDpUdcuXXA9QciGUv5pDjDnr3MMw4rjoaChNtxyE0LPCQXwBELxGM3UH0fBtp5Zesp1MovG44msJsimFX2GRSFDmYnGYqj/Ym+XlpVVVdfokr8pxVDGj4fSADTU2hgnodRNQnFD+u5X/eEuWq/pZ1QeY80YCmE2kKEQ6jD3eCjDQDPYNS+QoRDqoOZlR4ZqXiBDIdRBzcuODNW8QIZCqIOalx0ZqnmBDIVQBzUvOzJU80Lh7YNPrV0jBEIFxKcUGap5oWwo9G4iqAb5Y4kM1bxQePsEDhHWrhECoRpGVQxAhmpuIEMhGgvIUM0RZChEY4FXdInBYCBDNS/UGerZk3PWrhoCgdGhs2QGruqcMywWq1EYKnHvgl0Jkm2f8evWjPK07PkVK3PKy8p1MBxkKATFIQxVnH6Mw+FIDKUw9TpQP72xlQwlkUL++fVr7/Sxqh+oaCiD3z5kKATVIAyV++RgixYtZIYyyYIQ5oEsBasLwuoVUIHBbx8yFIJqEIZ6fu9XBweHRmwoWdsvdNHPc0PwXSAUJCT4wudAcS8QB2Anc7GG4njfk3fEhWg+RHyuRX3u7MKPwmugMtHKNAZDPTq/YR+xpnjHyV+P6qiw96Lzoo9CweUDuxLbww1XNcWk/LHj6H3xVs+xq98M1H5ScbGuANFYIAw1baRn6NvbFQ2lvKEA9Vp5xF5MWTmKypDbC8TmEZsKjNftkARcQrITkxJlRVoZg98+yxpKgyyU96rKXwz9lR+Oi6n4ckLxsNCO+haLoDqEoZ7G/ejo6KgihtK80pa1e8pDZUaQJRPCILW/FPaC8+t/AfMlO8kOUn+I/F745H5PeG5KNTklGPz2NTJDwQDqhufs+cOcDS8WQXUaqaGURIAFNXnjJCER7h5SNuW9Wg2luUDZbmQow1AXE50rBsB1cKTrtUTxXjzbiNJd0iZhlznvR3UlFbKvePAn0QM8iKfSbJH9is6VDpQ2HiUu80ggTio9l7R5WJDwy1dxBdhzpSYnwpqobuURkL8VorShiDS59pc0m+q9Klt5Wg6RtAFl/qKioQj0ffus1A+FOwJLAWI7lMZu+/0a6CczFHlDoRyJWaRaIWWDVkrujuss/cQHacEwg6rSUv44UDw82vUSkRlBKQhD3djS7YzdXL3HQ1kDlSIg+r1DQ0GOl6qQR36vrBGn0FOu/hCiHx2bnlnavKS0ofTFmjEUDGr+BqMlTTZllWhsoIkDItfJZAfhhTwMwt33S0EoVjK5Ax4PoMTAuCyiAKYAWTiGoAqkGGr429vfahSGMjWygEgzjV5AWmmshgLisKtoxPtRgJwNJp4F0aPBAfgoVg/ZUNIudoVCrr1CrTxKobofqlmh8gs8NRmRoUyFyr5wPVt5KZcTXIeJU7C2XmonGAEVymXDrJfvCvKdJxBRFVEauQNLBi41Ujm6KhJhJpqtoaSNOIxQ3YYIIEOZELnxUK64LKSDm5R6yjEvpJ/44PRjFT3lCj3oCtmwp4A4hGSZYlJDD2YOfig/rkrvIA5hJpqtoRAqaHpjyqV95NauB8JQkKEQMixmqB0bPlBIeX/116Y/jVzfFqJRomiouLg4a1cJYTX6vv4xvtH4Yyh8FIJ3P9Qua+QQhjq8a4G9vT2KoZo1Ta+Vh2jsoFYeQgYyFIJqKBrq6NGj1q4SwmpEzfkW30CGQlAEwlDfrouSzQ+FaJ6gecoRlIWKrbynT5926tTJ2rVoRiBDISgLMhQCGQpBXZChEGjlHgQVgR9LgUDgKAYZqlmDDIWgIMhQCAnIUAgKggyFkIAMhaAgyFAICchQCAqCDIWQgAyFoCDIUAgJFjdU/rl1q0/kiDd9ozasjTTj1FuJe+btlCx/uGT3O1rnU90z7x9vrRXCyzR5zbVXVbfqKYNd7zt9zHuhTY8lDPXDDz8cOXJk2rRpS5cuVZeiDDKUhbGoocR28iFuwfxz5/IjI/Vea1C3exU716s38FNJTqT5QF2KxUQCdLCd/pdFoaqGvmpDMlMRC8VQZCXpoieADGVxLGgo8o1oDDoHO4q5TGIoM9z5OpXajA3Vv39/cWLQokP7ZrYG4OXBOTN2pQFSmixFkkcpQS24mNq3b5+amqpVTwAZyuJYzlBqBYXdTuIFdcTRlawVKGnvyDeAAPFMsl8pP6nYnbmy1lgi6cCoqNwTsqpIbmfvM8RdrbpMWQniRl6+mmoTx4jLXdLnzk4sHSaOeSXJotRGVKgqcbnIdSBJR0X1yElLwE7yJQKqDpSvZJTPiRMJwPzNbt1RFUPFbhhwbXDsarBhwAqwOXb1ALGq1oJ1+9r8Lt4BEyQp68DaGRlvi1NiN2wAq8W71DN37lyoJyipvXv3aq0ZMpSFsaihfgYLVNwB5PuTdB8m7ln3agwpO7GLHCBoyA+IO1LubiTOc7c3kSreVFW+2jooV1va+pP1+4iNht/0pE01LUVNVRXXIV999YBSV5PKS6S+koQDzdCENQw5Q73Vv78sYoL2wawkDotkPpKGVBgjNscOvjZgxUVsQ4ubAIqhKA9FYijlf+QxZHcOKXbx1JZfxXnxzi+F+xZXFCEh6V6goUw1cpR/aUrKU3+guqp6KtcBqK0eFpspXFhVpwN6VdLKyBnqjxciSeMO+ujtjBm/BhxSMBThLDlg0KXFU6gfivpQoB9K7a0ufxARg2nMr+nEgHwH4sUtAD9LAzvVd7LaqprDUERJGqQDNFwijfVsvIZ6IRJJep8uDzuEtemkipK18qTtPpyXBzfERKwm5VDZEYW+y2sUWPS7PFKTAkPFV2xKPTLETrmGifr8snOdO+cZKU4mjsyXuwMxRb3yAbneC1S0hlSXCTRIh9yAwkWgs6FUV1WhDhqql29QK09DJTVsWOiToqKnPGjECJARgNkGj41wFHvK8RTMWRdJ+01YM2QoC2Pp8VDkdpmsY0ZeHESGUFKDxzc0VGoTSbNPsadcuUUm36cO5A9UHDugpvGoSytPrtpEd7PuMZSKqirVAWisnuJ4KtIrVXmg5kpSzFBqRxtI+s619jWZEmQoC9Ocx5STussR1EKToUghlE594aYFGcrCWMxQ8+bNU5m+e/du67xytd8tIqwP+tULQkKzjKHw1g51Rv8gFEGGQkholoZCUB1kKIQEZCgEBUGGQkhAhkJQEGQohARkKAQFkTMUWnO4OePj44MMhaAa0FBXrlxpIYZaMRTCwqAYCkFBqNvKQ1gYZCgEBUGGQkhAhkJQEGQohARkKAQFQYZCSECGQlAQZCiEBGQoBAVBhlLF+QW0yF+wjX7fpN1cFmjt6lgGZCgEBUGG0gQ01cnxop9HWbseFsGChiLNgqTbCnbyx5pofiJzLKKHMDVaDEWjaddWU80DQPq3/WeD3zUFUVSrszF5LGso0kIG+k3abyJTmGURPYTpQYZSA7RT0P/i5p/THEFRq86N0VB63/kmMoVZFtFDmB4KtfJ0i2ssivYgyoKY+/pYLYYibnyVC8NJl5nzVVqlSlUrTWkBOUssoqf2HAjjoZChKMj5BbSNnZpLX7l1+qFCVc0OLlsYTrq2nOrVE4D8gRrXETDfInrQXWgKYbOBDKUCvIWHbaHv8syCqmWR8tUvDOcpOUZx0SSF5fNUr85k/kX0xCsIAzRNp3lAhkJIsEorTzZFuJa13ojdynaTlqHT+nEqMMkiergMUSvP5CBDISRYu6c8UdXCcNIU5WXd8pXbdipbeZZbRE9qynyrr+DUlECGQkiwkqGAvGEUF4YDoSAhIQcA5d6ifOXl81SMcbLAInq97yqtUIcMZTKQoRASqDem3Mo3NlpEjwogQyEkWHe9PFWL5VnVUGgRPWqADIWQgGIoKWgRPQqBDIWQQD1DIRDIUAgpyFAICoIMhZCADIWgIMhQCAnIUAgKImeogKlbrF0fhNX4Y9kAZCgE1YCGmrT6DzqLA/+QoZo1yFAICoIMhZAADWXtKiAQKpj8+Z90JpvOtEGGQkgQCXhCPhc+ivhcIXwU8KxdI0QzhcZg0RksGpMNN5ChEBJEAr5IyJc+8kRCgbVrhGim0OgMzE10Jo3BRIZCSMCUJBLCR2wDPoqE1q4RoplCo9EBlJT47//3mk5KYG9SCQAAAABJRU5ErkJggg==
-
- Text + paragraph styles in this project template:
-
- This is Heading1 Black
- This is Heading2
- This is Heading3
- This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal. This is Normal.
- This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text. This is Body Text.
- This is Callouts.
- This is Code Example.
- This is Image Caption.
- This is Notes.
- This is NotesBox.
- This is PopupBox.
- This is See Also.
- This is Tip Body.
-
- Text-only styles in this project template:
-
- T_Code | T_Emphasis | T_Entry | T_Entry 10pt | T_Menu | T_Menu 10pt
-
-
diff --git a/docs/Help_Spanish/Topics/Subsystems-of-the-X-Runtime.xml b/docs/Help_Spanish/Topics/Subsystems-of-the-X-Runtime.xml
deleted file mode 100644
index 9ceb235668..0000000000
--- a/docs/Help_Spanish/Topics/Subsystems-of-the-X-Runtime.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- Subsystems of the X# Runtime
-
-
- Subsystems of the X# Runtime
-
- Description of Various Subsystems
-
-
-
-
- Subsystem
-
-
- Remarks
-
-
-
-
- Low Level File IO
-
-
- These functions are implemented in XSharp.Core. There is an important difference between the implementation in XSharp.Core when compared to VO. In VO, the file handles returned from functions such as FCreate() and FOpen() are OS file handles. That means that you can also pass them directly to Win32 API Functions. In the X# Runtime, this is no longer possible. We use .Net FileStream objects for the File IO. The File handler returned (which is of the IntPtr type) is a unique key into a table where we are storing these File IO objects. The keys are generated from random numbering. You can't and shouldn't rely on the values of these keys.
-
-
-
-
- Static Memory IO
-
-
- The static memory subsystem allocates memory using the Marshal.AllocHGlobal functionality. Each memory block has two guard blocks that contain information about the group number, size and a magic number. We have also implemented memory groups. Unlike in VO, you cannot release all blocks in a group by simply closing the Memory Group. If you want to enumerate allocated blocks you should first call MemTrace(TRUE) to enable block tracing. Then, create a function with the following prototype
- FUNCTION MyMemWalker(pMem AS IntPtr, nSize AS DWORD) AS LOGIC
- Then call MemWalk and pass your function as parameter. The runtime will call your function and will pass in all memory blocks that have been allocated and not released yet.
-
-
-
-
-
- Late Binding Support
-
-
- The Runtime fully supports late binding. The late binding support still needs some optimizations. We recommend to only use this when necessary. New code should either use the DYNAMIC type or try to use early bound code as much as possible.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Symbol-Type.xml b/docs/Help_Spanish/Topics/Symbol-Type.xml
deleted file mode 100644
index 1c5a6bd3fd..0000000000
--- a/docs/Help_Spanish/Topics/Symbol-Type.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Symbol Type
-
- SYMBOL
- XSharp.__Symbol
-
-
-
- Symbol Type
-
- This structure holds just a number. This number is a reference to a string table that contains the actual string representation of the symbol.
- The internal type name for this type is XSharp.__Symbol
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/SymbolLiterals.xml b/docs/Help_Spanish/Topics/SymbolLiterals.xml
deleted file mode 100644
index f8b6d1d66c..0000000000
--- a/docs/Help_Spanish/Topics/SymbolLiterals.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Symbol Literals
-
- Literals
- SYMBOL
- Symbol Literals
-
-
-
- Symbol Literals
-
- Symbol literals consist of the '#' character, followed by one of more alphanumeric characters:
- #XSharp #AnExample
- Even though the examples above are written in mixed case, the compiler will treat them as all uppercase.
- Symbol literals are compiled only once by the X# compiler, for performance reasons. Each .Net assembly created by the X# compiler will have a special, compiler-generated class, that contains all the literal symbols found in that assembly. These literals are initialized at startup and stored in the symbol table in the runtime.
-
-
diff --git a/docs/Help_Spanish/Topics/TEXT-Command-(Core).xml b/docs/Help_Spanish/Topics/TEXT-Command-(Core).xml
deleted file mode 100644
index b8e27ad624..0000000000
--- a/docs/Help_Spanish/Topics/TEXT-Command-(Core).xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- TEXT Command (Core)
-
-
- TEXT Command (Core)
-
- Syntax
-
- TEXTTO <VariableName> [ADDITIVE] TextLines ENDTEXT
- Arguments
- TextLines Specifies text to assign to the variable VarName.
-
- TO <VariableName>Specifies the variable name to use for passing the contents of the TEXT...ENDTEXT. This variable should be of type string, or should allow that a string can be added to it. It does not have to be a local variable, it can also be a field in the current class or an expression (someVar:SomeField).
-
- ADDITIVE Determines whether the contents of the TO variable are overwritten or added to existing contents.
-
- Example
-
- FUNCTION Start() ASVOID LOCAL cValue ASSTRING TEXTTO cValue Line 1 Line 2 Line 3 ENDTEXT ? cValue TEXTTO cValue ADDITIVE Line 4 Line 5 ENDTEXT ? cValue RETURN
- The first time, the variable will contain three lines of text delimited with CR/LF. The second time, there will be five lines.
- The code produced by the compiler will somewhat look like this:
- FUNCTION Start() ASVOID LOCAL cValue ASSTRING cValue := "" cValue += "Line 1" + chr(13)+chr(10) cValue += "Line 2" + chr(13)+chr(10) cValue += "Line 3" + chr(13)+chr(10)
? cValue RETURN
-
-
- See also
- #text directive
- #endtext directive
-
-
diff --git a/docs/Help_Spanish/Topics/TEXT-Command-(FoxPro).xml b/docs/Help_Spanish/Topics/TEXT-Command-(FoxPro).xml
deleted file mode 100644
index 28495b3457..0000000000
--- a/docs/Help_Spanish/Topics/TEXT-Command-(FoxPro).xml
+++ /dev/null
@@ -1,157 +0,0 @@
-
-
-
- TEXT Command (FoxPro)
-
-
- TEXT Command (FoxPro)
-
- Syntax
- TEXT [TO <VariableName> [ADDITIVE] [TEXTMERGE] [NOSHOW] [FLAGS nValue] [PRETEXT eExpression]] TextLines ENDTEXT
- Arguments
- TextLines Specifies text to send to the current output device. TextLines can consist of text, memory variables, array elements, expressions, functions, or any combination of these. Note X# evaluates expressions, functions, memory variables, and array elements specified with TextLines only if you set SET TEXTMERGE to ON and enclose them with the delimiters specified by SET TEXTMERGE DELIMITERS. If SET TEXTMERGE is OFF, Visual FoxPro outputs expressions, functions, memory variables, and array elements as string literals along with their delimiters.
For example, X# evaluates and outputs the current date when you specify the DATE( ) function as TextLines only if SET TEXTMERGE is ON, and TextLines contains the function and the appropriate delimiters, such as <<DATE( )>>. If SET TEXTMERGE is OFF, X#outputs <<DATE( )>> as a string literal.
- If you place comments within TEXT...ENDTEXT or after the single backslash character (\) or double backslash characters (\\), X# outputs the comments.
-
- TO <VariableName>Specifies the memory variable name to use for passing the contents of the TEXT...ENDTEXT. This variable can already exist.
-
- If the variable has not yet been declared, X# automatically creates it as a private variable. The TO clause operates regardless of how SET TEXTMERGE is set. If SET TEXTMERGE is set to a file, and the TO statement is included, Visual FoxPro outputs both the file and variable.
-
- ADDITIVE Determines whether the contents of the TO variable are overwritten or added to existing contents.
If the contents of TO VarName is not a string, X# always overwrites the contents in VarName.
-
-
- TEXTMERGE Enables evaluation of contents surrounded by delimiters without setting SET TEXTMERGE to ON.
-
- NOSHOW Disables display of the text merge to the screen.
-
- FLAGS nValueSpecifies a numerical value that determines if output is suppressed to an output file, or if blank lines preceding any text are included in the output.
-
-
-
-
-
-
- Value (additive)
-
-
-
-
-
-
- 1
-
-
- Suppresses output to the file specified with the _TEXT System Variable.
-
-
-
-
- 2
-
-
- When the NOSHOW clause is included, preserves blank lines preceding text that appears within TEXT...ENDTEXT. Setting nValue to 2 will separate current TEXT...ENDTEXT output from previous TEXT...ENDTEXT output with a line feed.
-
- Combining an nValue setting of 2 and PRETEXT of 4 will separate current TEXT…ENDTEXT output from previous TEXT…ENDTEXT output with a line feed while removing empty lines in the TEXT...ENDTEXT output.
-
-
-
-
-
-
-
-
-
- PRETEXT eExpressionSpecifies a character string to insert before each line of the text merge contents between TEXT...ENDTEXT or a numeric expression.
-
- The following table describes behaviors of the PRETEXT clause depending on the expression specified by eExpression.
-
- eExpressionPRETEXT behavior
-
- Character expression Insert the expression before each line of the text merge contents appearing between the TEXT...ENDTEXT statement. When using PRETEXT with TEXT...ENDTEXT, eExpression is limited to a maximum length of 255 characters.
- eExpression overrides the contents of the _PRETEXT system variable. When eExpression contains an expression that needs to be evaluated, for example, a user-defined function (UDF), Visual FoxPro evaluates it only once when the TEXT command first appears.
-
- Numeric expression Specify additive flag values to determine behavior for the text merge contents appearing between the TEXT...ENDTEXT statement.
- For example, a value of 7 specifies that Visual FoxPro eliminate all white space including spaces, tabs, and carriage returns. A value falling outside of the range of 0-15 produces an error.
-
- Note
- Specifying a value of zero does not eliminate white space.
-
- When eExpression is a numeric expression, you can use the _PRETEXT system variable to insert additional text after Visual FoxPro eliminates white space. The following table lists numeric additive flags that you can use in eExpression to specify additional behavior.
-
-
-
-
-
-
- Value (Additive)
-
-
- Description
-
-
-
-
- 1
-
-
- Eliminate spaces before each line.
-
-
-
-
- 2
-
-
- Eliminate tabs before each line
-
-
-
-
- 4
-
-
- Eliminate carriage returns, for example, blank lines, before each line.
-
-
-
-
- 8
-
-
- Eliminate line feeds.
-
-
-
-
-
-
- Note Unlike the _PRETEXT system variable, the PRETEXT clause does not have global scope and applies only to the TEXT...ENDTEXT statement in which it appears.
Characters removed using the PRETEXT clause apply only to text within the TEXT...ENDTEXT statement and not to evaluated text merged from cExpression. In the following example, the spaces in the memory variable, myvar, are not removed when merged with the text in TEXT...ENDTEXT:
- myvar = " AAA" TEXT TO x NOSHOW ADDITIVE TEXTMERGE PRETEXT 7 Start Line <<myvar>> BBB CCC ENDTEXT
-
- By default, TEXT ... ENDTEXT sends output to the terminal window. To suppress output to the terminal window, issue SET CONSOLE OFF. To send output to a printer or a text file, use SET PRINTER. To send output from TEXT ... ENDTEXT to a low-level file that you created or opened using FCREATE( ) or FOPEN( ), store the file handle returned by FCREATE( ) or FOPEN( ) to the _TEXT system variable, which you can use to direct output to the corresponding low-level file.
-
- The text merge process usually includes any white space that might appear before each line in a TEXT...ENDTEXT statement. However, the inclusion of white space might cause the text merge to fail, for example, when XML is used in a Web browser. You must remove such white space to avoid incorrectly formatted XML.
-
- Nesting TEXT...ENDTEXT statements is not recommended, especially if using the PRETEXT clause because the nested statements can affect the format of the outer statements.
- Example 1
-
- The following example demonstrates creating a low-level file called myNamesFile.txt and storing its file handle in the _TEXT system variable. The program exits if the myNamesFile.txt file cannot be created.
-
- The code opens the customer table and outputs the names of the first ten contacts to CotactList.txt.
- The code outputs the text and results of the functions to the text file.
-
-
- Example 2
-
- The following example shows a custom procedure that uses TEXT...ENDTEXT to store an XML DataSet to a variable. In the example, all spaces, tabs, and carriage returns are eliminated.
-
- PROCEDURE myProcedure DOCASE CASE nValue = 1 TEXTTO myVar NOSHOWTEXTPRETEXT 7 <?xml version="1.0" encoding="utf-8"?> <DataSet xmlns="http://tempuri.org"> <<ALLTRIM(STRCONV(leRetVal.item(0).xml,9))>> </DataSet> ENDTEXT OTHERWISE ENDCASE ENDPROC
- See Also
- FOPEN( ) Function
- _PRETEXT System Variable
- SET TEXTMERGE Command
- SET TEXTMERGE DELIMITERS Command
- _TEXT System Variable
- #text directive
- #endtext directive
-
-
diff --git a/docs/Help_Spanish/Topics/TEXT-Command-(Non-Core).xml b/docs/Help_Spanish/Topics/TEXT-Command-(Non-Core).xml
deleted file mode 100644
index f2a40be067..0000000000
--- a/docs/Help_Spanish/Topics/TEXT-Command-(Non-Core).xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- TEXT Command (Non-Core)
-
- ENDTEXT
- TEXT
- TRIMMED
- WRAP
-
-
-
- TEXT Command (Non-Core)
-
- Syntax
- TEXT [INTO <VariableName> [TRIMMED]] | [INTO <VariableName> WRAP] | [INTO <VariableName> WRAP <cLineBreak> [TRIMMED]] TextLines ENDTEXT
- or
- TEXT [TOPRINTER] | [TOFILE <cFilename>] TextLines ENDTEXT
-
- Arguments
- TextLines Specifies text to assign to the variable VarName
-
- INTO <VariableName>Specifies the variable name to use for passing the contents of the TEXT...ENDTEXT. This variable should be of type string, or should allow that a string can be added to it. It does not have to be a local variable, it can also be a field in the current class or an expression (someVar:SomeField)
-
- WRAP <cLineBreak>The optional parameter <cLineBreak> specifies a character string that is used to wrap lines. The default value is CHR(13)+CHR(10) (carriage return and line feed). If WRAP is not specified, no line breaks will be inserted.
-
- TRIMMEDThis optional parameter tells the preprocessor to remove all spaces from the beginning of the line if TEXT INTO .. is used.
-
- TO FILE <cFilename><cFilename> indicates the name of a file where the text <Text> is optionally written. The name must contain the drive and path, if necessary. The file name can be specified either as a literal file name or as a character expression in parentheses. When the file name is specified without file extension, ".TXT" is used by default.
-
- TO PRINTERIndicates that the text should be sent to the printer instead of to a file.
-
-
-
-
-
- See also
- #text directive
- #endtext directive
-
-
diff --git a/docs/Help_Spanish/Topics/Templates.xml b/docs/Help_Spanish/Topics/Templates.xml
deleted file mode 100644
index dea403418e..0000000000
--- a/docs/Help_Spanish/Topics/Templates.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Templates
-
- templates
-
-
-
- Templates
-
- The Visual Studio integrations comes with a couple of predefined templates.
- There are templates for:
-
-
Projects
-
Items
-
-
-
diff --git a/docs/Help_Spanish/Topics/Text-Editor-Options.xml b/docs/Help_Spanish/Topics/Text-Editor-Options.xml
deleted file mode 100644
index 44f912a078..0000000000
--- a/docs/Help_Spanish/Topics/Text-Editor-Options.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- Text Editor Options
-
- EditorSettings.json
- settings
- Tools/Options
-
-
-
- Text Editor Options
-
- The various settings for the Visual Studio editors can be controlled from the Tools/Options menu.
- The values for the settings are stored in the file XSharp\EditorSettings.json in your roaming profile folder.
- If you have multiple Visual Studio installations, the settings will be shared across all of them.
- When you open this menu, you will see a window like this:
-
-
-
- Tools Options dialog
- On the left-hand side, there is a tree-view in which you can select the category of the options you are interested in. This dialog contains a large number of options.
- To make navigation easier, you can use the edit control on top to filter.
- All X# options can be found by typing "X#" in this control. This will display the categories related to X#.
-
-
- Tools Options filtered on X#
- The Text Editor category (which was also visible on the first image) contains settings for all languages supported by Visual Studio or by extensions installed inside Visual Studio (such as the X# Visual Studio extension).
- Under the Debugging category, there is an entry for settings used by the X# expression evaluator in the debugger.
- The last category includes settings for the VO-compatible form editor and some of the other X#-specific editors.
-
-
diff --git a/docs/Help_Spanish/Topics/The-X-Runtime.xml b/docs/Help_Spanish/Topics/The-X-Runtime.xml
deleted file mode 100644
index 08c1a284a4..0000000000
--- a/docs/Help_Spanish/Topics/The-X-Runtime.xml
+++ /dev/null
@@ -1,233 +0,0 @@
-
-
-
- The X# Runtime
-
-
- The X# Runtime
-
- In X# version 2 - Bandol we have introduced the X# runtime.
-
- In this chapter, we would like to give you an overview of the design decisions that we made, what the run time looks like, where you can find which types and functions, etc.
- We will also list the features that are not supported yet here.
- Introduction
- When we designed the X# compile and X# Runtime, we had a few focus points in mind:
-
-
The language and runtime should be VO compatible whenever possible. We know that the Vulcan devteam made some decisions not to support certain features from VO, but we decided that we would like to be as compatible as technically possible.
-
-
-
We want our runtime to be fully Unicode and AnyCPU. It should run on any platform and also both in x86 and x64 mode. This has caused some challenges, as VO is Ansi (and not Unicode) and also X86. In VO you can cast a LONG to a PTR. That will not work in X64 mode because a LONG is 32 bits and a PTR 64 bits
-
We want the code to compile in "Safe" mode, and avoid unsafe code except when strictly needed. The biggest problem/challenge here is the PTR type. With a PTR you can access memory directly and read/write from memory, even if you don't "own" that memory. However, the same PTR type is also used as "unique identifier", for example in the low level file i/o, and in the GUI classes for Window and Control handles. These PTR values are never used to read or write memory, but are like object references. We have decided to use the .Net IntPtr type for these types of handles. Of course the compiler can transparently convert between PTR and IntPtr.
-
We want to prove that the X# language is a first class .Net development language, which is why we decided to write the X# runtime in X#. By doing that, we also create a large codebase to test the compiler, making it a win-win situation.
-
We want the runtime to be thread safe. Each thread has its own "global" state and its own list of open work areas. When a new thread is started, it inherits the state of the main thread, but it not the main thread's work areas.
-
At this moment, the X# Runtime is compiled against .Net Framework 4.6.
-
- Assemblies in the X# Runtime
-
- If you want to know in which Assembly a function or type is defined, your "best friend" is the documentation. We are using a tool to generate the documentation, so this is always correct. Some subsystems have functions in XSharp.Core DLL and in XSharp.VO.DLL as well.
-
-
-
-
- Component
-
-
- Description
-
-
- Dialect used
-
-
- Framework Version
-
-
-
-
- XSharp.Core.DLL
-
-
- This is the base DLL of the X# Runtime.
-
-
- X# Core
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.Data.DLL
-
-
- This DLL contains support code for .Net SQL based data access and for SQL based cursors.
-
-
- X# Core
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.RT.DLL
-
-
- This DLL is required for all dialects apart from Core.
-
-
- X# non - core
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.RT.Debugger.DLL
-
-
- This DLL contains the functions and windows for the Runtime Debugger.
-
-
- X# core
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.VO.DLL
-
-
- This DLL adds features to the runtime that are needed for the VO and Vulcan dialects.
-
-
- X# VO and X# Vulcan
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.XPP.DLL
-
-
- This DLL adds features to the runtime that are needed for the Xbase++ dialect.
-
-
- X# XPP
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.VFP.DLL
-
-
- This DLL adds features to the runtime that are needed for the FoxPro dialect.
-
-
- X# FoxPro
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.Macrocompiler.DLL
-
-
- This DLL is the X# "fast" macro compiler.
-
-
- X# Core
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.MacroCompiler.Full.DLL
-
-
- This DLL is the X# "full" macro compiler.
-
-
- X# Core
-
-
- 4.6 / 8.0
-
-
-
-
- XSharp.RDD.DLL
-
-
- This DLL contains the various RDDs implemented for X#.
-
- These DLLs represent the class libraries from Visual Objects.
-
-
- X# VO and X# Vulcan
-
-
- 4.6
-
-
-
- Missing or incomplete Features
-
-
-
-
- Feature
-
-
- Description
-
-
- Expected when
-
-
-
-
- Some runtime functions are not supported yet: Crypt functions (Crypt(), CryptA()) Encoding functions (B64Enc.., UUEnc.., GetChunkBase64 etc)
-
-
- These functions will most likely be added in one of the next betas. For now, they will throw a notimplementedexception when you use them.
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-Completion.xml b/docs/Help_Spanish/Topics/Tools-Options-Completion.xml
deleted file mode 100644
index 587b4d8184..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-Completion.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Settings Completion
-
- Options
- Settings Completion
- Tools Options
-
-
-
- Settings Completion
-
- This page contains X#-specific settings related to code completion.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-Formatting.xml b/docs/Help_Spanish/Topics/Tools-Options-Formatting.xml
deleted file mode 100644
index afd2f36f3b..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-Formatting.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Formatting
-
- Formatting
- Options
- Tools Options
-
-
-
- Formatting
-
- This page contains X#-specific settings with respect to source code formatting.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-General.xml b/docs/Help_Spanish/Topics/Tools-Options-General.xml
deleted file mode 100644
index bcb973ed83..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-General.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- General Options
-
- General Options
- Options
- Tools Options
-
-
-
- General Options
-
- This page contains generic editor settings for the X# language.
- The page may change between different versions of Visual Studio.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-Generator.xml b/docs/Help_Spanish/Topics/Tools-Options-Generator.xml
deleted file mode 100644
index ff9758b3f2..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-Generator.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Generator
-
- Generator
- Options
- Tools Options
-
-
-
- Generator
-
- This page contains X#-specific settings with respect to source code generating inside VS. This applies to the source code generated by the Windows Forms editor, but also to the source code generated when you choose "Go to Definition" for a member that is defined in an external assembly.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-Indentation.xml b/docs/Help_Spanish/Topics/Tools-Options-Indentation.xml
deleted file mode 100644
index 3e2c852487..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-Indentation.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- Indentation
-
- Indentation
- Options
- Tools Options
-
-
-
- Indentation
-
- This page contains X#-specific settings related to source indentation. This setting is used by the editor when choosing the option to indent "Smart" on the "Tabs" page.
-
-
-
-
- The listview on top shows the options that you can choose from. The edit control on the bottom shows the result of the setting.
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-Intellisense.xml b/docs/Help_Spanish/Topics/Tools-Options-Intellisense.xml
deleted file mode 100644
index 365c23a069..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-Intellisense.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Intellisense
-
- Intellisense
- Options
- Tools Options
-
-
-
- Intellisense
-
- This page contains X#-specific settings with respect to code completion and the dropdowns in the editor.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-Options.xml b/docs/Help_Spanish/Topics/Tools-Options-Options.xml
deleted file mode 100644
index 0a95e4f008..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-Options.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Options
-
- Options
- Tools Options
-
-
-
- Options
-
- This page contains X#-specific switches that allow you to control features inside the X# source code editor.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-ScrollBars.xml b/docs/Help_Spanish/Topics/Tools-Options-ScrollBars.xml
deleted file mode 100644
index 0f89b92d2e..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-ScrollBars.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Scroll Bars
-
- Options
- Scroll Bars
- Tools Options
-
-
-
- Scroll Bars
-
- This page contains generic settings with respect to scroll bars.
- The page may change between different versions of Visual Studio.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tools-Options-Tabs.xml b/docs/Help_Spanish/Topics/Tools-Options-Tabs.xml
deleted file mode 100644
index 3004c18b25..0000000000
--- a/docs/Help_Spanish/Topics/Tools-Options-Tabs.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Tabs
-
- Options
- Tabs
- Tools Options
-
-
-
- Tabs
-
- This page contains generic settings with respect to tabs.
- The page may change between different versions of Visual Studio.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Tuples.xml b/docs/Help_Spanish/Topics/Tuples.xml
deleted file mode 100644
index 9be7d18301..0000000000
--- a/docs/Help_Spanish/Topics/Tuples.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- Codeblock, Lambda and Anonymous Method Expressions
-
- Tuple
-
-
-
- Tuples
-
- Tuple generic data type
-
- A tuple is a data structure that groups multiple data elements in a lightweight data structure. Tuples can be used as an easy way to represent multiple data elements, pass them as argument(s) or receive them as a return value, without needing to declare a complete new class or structure for holding the data set.
-
- For example, the following code uses the generic System.Collections.Generic.Tuple type to receive multiple values from a function, without the need to declare multiple REF/OUT parameters or to create a new dedicated type for holding them:
- USING System.Collections.Generic
FUNCTION GetCustomerData() AS Tuple<STRING, INT, LOGIC> LOCAL oCustomer AS Tuple<STRING, INT, LOGIC> oCustomer := Tuple<STRING, INT, LOGIC>{"Nikos", 47, TRUE} RETURN oCustomer
FUNCTION Start() ASVOID LOCAL oCustomer AS Tuple<STRING, INT, LOGIC> oCustomer := GetCustomerData() ? "Customer name:", oCustomer:Item1 ? "Age:", oCustomer:Item2 ? "Is active:", oCustomer:Item3
- TUPLE keyword
-
- X# also supports the dedicated keyword TUPLE, which offers an easier syntax for declaring and working with tuples. The above code can be written in a simpler way with the TUPLE keyword syntax:
-
- FUNCTION GetCustomerData() ASTUPLE(STRING, INT, LOGIC) LOCAL oCustomer ASTUPLE(STRING, INT, LOGIC) // defining the tuple // tuple item types must match the types in the Tuple definition oCustomer := TUPLE{"Nikos", 47, TRUE} RETURN oCustomer
- FUNCTION Start() ASVOID LOCAL oCustomer AS (STRING, INT, LOGIC) // the TUPLE keyword in the tuple definition can even be omitted! oCustomer := GetCustomerData() ? "Customer name:", oCustomer:Item1 ? "Age:", oCustomer:Item2 ? "Is active:", oCustomer:Item3
- Note that when using the TUPLE keyword, the compiler internally uses the type System.ValueTuple, instead of the generic type System.Collections.Generic.Tuple. Also, when defining the tuple, the TUPLE keyword can be omitted, thus using the more c#-like syntax (type1, type2, ...).
- Named tuples
- The dedicated TUPLE keyword syntax also supports specifying custom names for the tuple items, instead of using the generic names Item1, Item2, etc. This way, the code can become much more readable and close to what it would be like if using a separate new class for the data:
- FUNCTION Start() ASVOID LOCAL oCustomer ASTUPLE(Name ASSTRING, Age ASINT, IsActive ASLOGIC) // provide names for each item of the tuple oCustomer := GetCustomerData() ? "Customer name:", oCustomer:Name ? "Age:", oCustomer:Age ? "Is active:", oCustomer:IsActive
- To make code even more self-explanatory, a named tuple can also be instantiated by using named arguments:
- FUNCTION GetCustomerData() ASTuple(STRING, INT, LOGIC) // defining the named tuple with custom item names LOCAL oCustomer ASTuple(Name ASSTRING, Age ASINT, IsActive ASLOGIC) // including tuple item names in the tuple instantiation oCustomer := TUPLE{Name := "Nikos", Age := 47, IsActive := TRUE} RETURN oCustomer
- Defining tuples with VAR
- Tuples can also be defined and instantiated at the same time using the VAR keyword:
-
- FUNCTION Start() ASVOID VAR oTuple := TUPLE{"Nikos", 47, FALSE} ? oTuple:Item1, oTuple:Item2, oTuple:Item3 // "Nikos", 47, FALSE
-
- In this case, the data type of each tuple item is inferred from the item types supplied in the code. In the above sample, the item types are (STRING, INT, LOGIC).
-
- Tuples with the same item types can be assigned to each other (thus copying the item values from the source tuple to the destination tuple), and the same can be done for tuples defined with either LOCAL or VAR:
- FUNCTION Start() ASVOID VAR oTuple := TUPLE{"Nikos", 47, FALSE} LOCAL oNew ASTUPLE(STRING, INT, LOGIC)
oNew := oTuple ? oNew:Item1, oNew:Item2, oNew:Item3 // "Nikos", 47, FALSE
- When defining a tuple with the VAR keyword, item names can be provided as well:
- FUNCTION Start() ASVOID VAR oTuple := TUPLE{Name := "Nikos", Age := 47, IsActive := FALSE} ? oTuple:Name, oTuple:Age, oTuple:IsActive // "Nikos", 47, FALSE
- Finally, when defining a tuple with VAR by using identifiers for the item values, instead of using literal values, then each item automatically gets a name by the identifier name used for it:
- CLASS CustomerInfo EXPORT Description := "Customer description" ASSTRING ENDCLASS
FUNCTION Start() ASVOID LOCAL name := "Unknown Customer" ASSTRING LOCAL oInfo := CustomerInfo{} AS CustomerInfo
VAR oTuple := TUPLE{name, oInfo:Description} ? oTuple:name // "Unknown Customer" ? oTuple:description // "Customer description"
- Tuple deconstruction
- A tuple can be deconstructed to multiple plain variables in one line of code, using the (var1, var2, ...) syntax:
- FUNCTION Start() ASVOID LOCAL oCustomer ASTUPLE(Name ASSTRING, Age ASINT) oCustomer := TUPLE{"Nikos", 47}
LOCAL name ASSTRING LOCAL age ASINT (name, age) := oCustomer ? name, age // "Nikos", 47
- The local variables can also be defined and assigned to the tuple item values in a single line, with a special LOCAL syntax for tuples:
- FUNCTION Start() ASVOID LOCAL oCustomer ASTUPLE(Name ASSTRING, Age ASINT) oCustomer := TUPLE{"Nikos", 47}
LOCAL (name ASSTRING, age ASINT) := oCustomer ? name, age // "Nikos", 47 // You can also deconstruct into existing local variables without the LOCAL keyword: (name, age) := oCustomer
- Additionally, the VAR keyword can be used for the tuple deconstruction, in which case the variable types are inferred from the tuple item types:
- FUNCTION Start() ASVOID LOCAL oCustomer ASTUPLE(Name ASSTRING, Age ASINT) oCustomer := TUPLE{"Nikos", 47}
VAR (name, age) := oCustomer ? name, age // "Nikos", 47
-
-
diff --git a/docs/Help_Spanish/Topics/Types.xml b/docs/Help_Spanish/Topics/Types.xml
deleted file mode 100644
index 5f7285605e..0000000000
--- a/docs/Help_Spanish/Topics/Types.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Types
-
-
- Types
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/UDC-Tester.xml b/docs/Help_Spanish/Topics/UDC-Tester.xml
deleted file mode 100644
index c6e9283ba9..0000000000
--- a/docs/Help_Spanish/Topics/UDC-Tester.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- UDC Tester
-
- UDC Tester
-
-
-
- UDC Tester
-
- Enter topic text here.
-
-
diff --git a/docs/Help_Spanish/Topics/UINT64.xml b/docs/Help_Spanish/Topics/UINT64.xml
deleted file mode 100644
index fc2a798804..0000000000
--- a/docs/Help_Spanish/Topics/UINT64.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- UINT64
-
- UNIT64
-
-
-
- UINT64
-
- The UINT64 keyword denotes an integral type that stores unsigned 64-bit values with values ranging from 0 to 18,446,744,073,709,551,615.
-
-
diff --git a/docs/Help_Spanish/Topics/USING.xml b/docs/Help_Spanish/Topics/USING.xml
deleted file mode 100644
index 1e8ba986fe..0000000000
--- a/docs/Help_Spanish/Topics/USING.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- USING
-
- #USING
- STATIC
- USING
-
-
-
- USING statement
-
- The USING statement allows the types in a namespace to be used without having to specify the fully-qualified type name.
-
- using namespaceName using alias := namespaceName using static typeName
- Arguments
- namespaceName Specifies a fully-qualified namespace name that the compiler will use when attempting to resolve type names.
- aliasAn alias for the namespace.
- typeNameSpecifies the name of the type whose static members and nested types can be referenced without specifying a type namespace.
-
- All types in .NET have fully-qualified names consisting of a namespace name and a type name. For example, "System.Windows.Forms.MessageBox" refers to a type named "MessageBox" (a class, in this case) in the "System.Windows.Forms" namespace.
-
- The use of namespaces in .NET helps prevent naming conflicts between class libraries. However, it can be cumbersome to type the fully qualified name. The using statement instructs the compiler to treat the specified namespace as if it were part of the current namespace, for purposes of type resolution. This allows you to specify partial type names in your source code, rather than fully-qualified names. You can, of course, always use a fully-qualified name regardless of any using statements present.
-
- Note that the using statement only imports the type names in the specified namespace; it does not import names in nested or parent namespaces.
-
- Also note that every source file has an implied using System and using XSharp directive, since the System and XSharp namespace contain classes that virtually every application will use. Explicitly specifying using System or using XSharp is allowed, but unnecessary.
- Examples
- USING System.Windows.Forms FUNCTION Start() ASVOID LOCAL dlg1 AS OpenFileDialog // error, without the using statement LOCAL dlg2 AS System.Windows.Forms.OpenFileDialog // always ok, but cumbersome to type dlg1 := OpenFileDialog{} // error, without the using statement dlg2 := System.Windows.Forms.OpenFileDialog{} // always ok, but cumbersome to type ... RETURN
- or
- USING SWF := System.Windows.Forms
FUNCTION Start() ASVOID LOCAL dlg1 AS SWF.OpenFileDialog // use the alias in stead of the full name dlg1 := SWF.OpenFileDialog{} ... RETURN
- or
- USINGSTATIC System.Console FUNCTION Start asVOID WriteLine("Hello world") // this calls System.Console.WriteLine() ReadLine() // this calls System.Console.ReadLine() RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/USUAL.xml b/docs/Help_Spanish/Topics/USUAL.xml
deleted file mode 100644
index 8229042dfa..0000000000
--- a/docs/Help_Spanish/Topics/USUAL.xml
+++ /dev/null
@@ -1,174 +0,0 @@
-
-
-
- USUAL
-
- USUAL
-
-
-
- USUAL
-
- The USUAL type is a datatype that can contain any data type. It consists internally of a type flag and a value. This type can store any value.
- The compiler treats this type in a special way. The compiler will not warn you when you assign a value of type USUAL to another type, but will automatically generate the necessary conversion operation.
-
- USUAL is provided primarily for compatibility with untyped code. It is not recommended for use in new code because the compiler cannot perform any type checking on expressions where one or more operands are USUAL. Any data type errors will only be discovered at runtime.
-
- Locals, parameters and fields declared as USUAL also incur considerably more runtime overhead than strongly typed variables.
-
- The literal value NIL may be assigned into any storage location typed as USUAL. The value NIL indicates the absence of any other data type or value, and is conceptually equivalent to storing NULL into a reference type. NIL is the default value for a local USUAL variable that has not been initialized.
-
- When the left operand of the ':' operator is a USUAL, the compiler will generate a late bound call to the method, field or property specified as the right operand. This call may fail if the value contained in the USUAL at runtime does not have such a member, the member type is incorrect or inaccessible, or if the name evaluates to a method and the number of parameters or their types is incorrect. The /lb compiler option must be enabled in order to use a USUAL as the left operand of the ':' operator; otherwise, a compile-time error will be raised.
-
- Numeric operations and USUAL variables of mixed types.
- When you combine two USUAL variables in a numeric operation then the type of the result is derived from the types of operands. The leading principle has been that we try not to loose decimals.
-
- The generic rule is:
-
-
When the Left Hand Side (LHS) is fractional, then the result is also fractional of the type of the LHS.
-
When the LHS is NOT fractional and the Right Hand Side (RHS) is fractional, then the result is the type of the RHS.
-
When both sides are integral, then the result has the type of the largest of the two.
-
-
-
-
-
-
- LHS
-
-
- \ RHS
-
-
- LONG
-
-
- INT64
-
-
- FLOAT
-
-
- CURRENCY
-
-
- DECIMAL
-
-
-
-
- LONG
-
-
-
-
- LONG
-
-
- INT64
-
-
- FLOAT
-
-
- CURRENCY
-
-
- DECIMAL
-
-
-
-
- INT64
-
-
-
-
- INT64
-
-
- INT64
-
-
- FLOAT
-
-
- CURRENCY
-
-
- DECIMAL
-
-
-
-
- FLOAT
-
-
-
-
- FLOAT
-
-
- FLOAT
-
-
- FLOAT
-
-
- FLOAT
-
-
- FLOAT
-
-
-
-
- CURRENCY
-
-
-
-
- CURRENCY
-
-
- CURRENCY
-
-
- CURRENCY
-
-
- CURRENCY
-
-
- CURRENCY
-
-
-
-
- DECIMAL
-
-
-
-
- DECIMAL
-
-
- DECIMAL
-
-
- DECIMAL
-
-
- DECIMAL
-
-
- DECIMAL
-
-
-
-
- Implementation
- The USUAL type is implemented in the structure XSharp.__Usual.
-
-
-
diff --git a/docs/Help_Spanish/Topics/UnInstaller-Command-Line-optio.xml b/docs/Help_Spanish/Topics/UnInstaller-Command-Line-optio.xml
deleted file mode 100644
index 5b2e0a8089..0000000000
--- a/docs/Help_Spanish/Topics/UnInstaller-Command-Line-optio.xml
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
- UnInstaller Command Line options
-
- /log
- /norestart
- /silent
- /suppressmsgboxes
- /verysilent
-
-
-
- UnInstaller Command Line options
-
- The Uninstaller (which can be found in the <Installdir>\Uninst folder) has the following command line options:
-
-
-
-
- Option
-
-
- Description
-
-
-
-
- /silent, /verysilent
-
-
- When specified, the uninstaller will not ask the user for startup confirmation or display a message stating that uninstall is complete. Shared files that are no longer in use are deleted automatically without prompting. Any critical error messages will still be shown on the screen. When '/verysilent is specified, the uninstallation progress window is not displayed.
- If a restart is necessary and the '/norestart command isn't used (see below) and '/verysilent is specified, the uninstaller will reboot without asking.
-
-
-
-
- /suppressmsgboxes
-
-
- Instructs the uninstaller to suppress message boxes. Only has an effect when combined with '/silent and '/verysilent.
-
-
-
-
- /log
-
-
- Causes Uninstall to create a log file in the user's TEMP directory detailing file uninstallation and actions taken during the uninstallation process. This can be a helpful debugging aid. The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)
- The information contained in the log file is technical in nature and therefore not intended to be understandable for end users, nor is it designed to be machine-parsable; the format of the file is subject to change without notice.
-
-
-
-
- /log="filename"
-
-
- Same as /log, except it allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists, it will be overwritten. If the file cannot be created, Uninstall will abort with an error message.
-
-
-
-
- /norestart
-
-
- Instructs the uninstaller not to reboot, even if it is necessary.
-
- prefix increment. Returns the value of x after updating the storage location with the value of x that is one greater (typically adds the integer 1).
-
-
-
-
- -- (prefix)
-
-
- --x
-
-
- prefix decrement. Returns the value of x after updating the storage location with the value of x that is one greater (typically adds the integer 1).
-
-
-
-
- ~
-
-
- ~x
-
-
- bitwise complement
-
-
-
-
- ++ (postfix)
-
-
- x++
-
-
- postfix increment. Returns the value of x and then updates the storage location with the value of x that is one greater (typically adds the integer 1).
-
-
-
-
- -- (postfix)
-
-
- x--
-
-
- postfix decrement. Returns the value of x and then updates the storage location with the value of x that is one less (typically subtracts the integer 1).
-
-
-
-
- Note that shift operators are only supported on integral numeric types.
-
-
diff --git a/docs/Help_Spanish/Topics/Unsafe-Code-and-Pointers.xml b/docs/Help_Spanish/Topics/Unsafe-Code-and-Pointers.xml
deleted file mode 100644
index 455f1b49ba..0000000000
--- a/docs/Help_Spanish/Topics/Unsafe-Code-and-Pointers.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Unsafe Code and Pointers
-
-
- Unsafe Code and Pointers
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/User-defined-Types.xml b/docs/Help_Spanish/Topics/User-defined-Types.xml
deleted file mode 100644
index c956444824..0000000000
--- a/docs/Help_Spanish/Topics/User-defined-Types.xml
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
- User-defined Types
-
- CLASS
- CLASS (FoxPro syntax)
- CLASS (Xbase++ syntax)
- DELEGATE
- ENUM
- INTERFACE
- STRUCTURE
- UNION
- VOSTRUCT
-
-
-
- User-defined Types
-
- The X# language allows you to define your own types (in fact the XBase Specific types have all been defined that way).
- The language has the following keywords that define User-defined Types.
-
-
-
-
- Type
-
-
- Description
-
-
-
-
- CLASS
-
-
- Defines a class, using a generic syntax that is available in all dialect.
-
-
-
-
- CLASS (FoxPro syntax)
-
-
- Defines a class, using the FoxPro specific syntax.
-
-
-
-
- CLASS (Xbase++ syntax)
-
-
- Defines a class, using the Xbase++ specific syntax.
-
-
-
-
- DELEGATE
-
-
- Defines a delegate, a description of a method or a function.
-
-
-
-
- ENUM
-
-
- Defines an enum, a list of possible options.
-
-
-
-
- INTERFACE
-
-
- Defines an interface.
-
-
-
-
- RECORD
-
-
- A record is a special form of a class or structure for working with data models. Records provide support frp value equality.
-
-
-
-
- STRUCTURE
-
-
- Defines a structure, a value type
-
-
-
-
- TUPLE
-
-
- Tuple type
-
-
-
-
- UNION
-
-
- Defines a Union, a special kind of structure. Only available in the VO and Vulcan dialects.
-
-
-
-
- VOSTRUCT
-
-
- Defines a VOStruct, a special kind of structure. Only available in the VO and Vulcan dialects.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Usual-Type.xml b/docs/Help_Spanish/Topics/Usual-Type.xml
deleted file mode 100644
index 368d09ddfb..0000000000
--- a/docs/Help_Spanish/Topics/Usual-Type.xml
+++ /dev/null
@@ -1,258 +0,0 @@
-
-
-
- Usual Type
-
- USUAL
- XSharp.__Usual
-
-
-
- Usual Type
-
- The USUAL type in X# is implemented as a .Net structure. It contains a type flag and a value. The value can be one of the following types:
- NIL, Long, Date, Float, Array, Object, String, Logic, Codeblock, Symbol, Ptr, Int64, DateTime, Decimal, DateTime.
- The internal type name for this type is XSharp.__Usual
-
-
-
- Type
-
-
- Usual Type Number
-
-
-
-
- NIL
-
-
- 0
-
-
-
-
- Long
-
-
- 1
-
-
-
-
- Date
-
-
- 2
-
-
-
-
- Float
-
-
- 3
-
-
-
-
- Array
-
-
- 5
-
-
-
-
- Object
-
-
- 6
-
-
-
-
- String
-
-
- 7
-
-
-
-
- Logic
-
-
- 8
-
-
-
-
- Codeblock
-
-
- 9
-
-
-
-
- Symbol
-
-
- 10
-
-
-
-
- Ptr
-
-
- 18
-
-
-
-
- Int64
-
-
- 22
-
-
-
-
- DateTime
-
-
- 26
-
-
-
-
- Decimal
-
-
- 27
-
-
-
-
- Currency
-
-
- 28
-
-
-
-
- Binary
-
-
- 29
-
-
-
-
- Note that some Usual Type numbers are not included in this table. There are defines in the compiler for these numbers, but they are never stored inside a USUAL. So you can write UsualType(uValue) == REAL8 but that will NEVER be true.
- You can assign values of these other types to a USUAL but the values will be converted to a type listed in the first table. For example if you assign a DWORD to a USUAL then the runtime will look at the value of the DWORD and if it is smaller or equal to MAX_LONG then it will store the value as a LONG. Otherwise it will store it as a FLOAT. Please note that although we support the Int64 type the DWORD conversion does not use this to be compatible with VO. Also if you assign a PSZ to a USUAL then it will be stored as a STRING. So the runtime will automatically call Psz2String() to get the string representation.
-
-
-
- Name
-
-
- Usual Type Number
-
-
-
-
- Byte
-
-
- 11
-
-
-
-
- Short
-
-
- 12
-
-
-
-
- Word
-
-
- 13
-
-
-
-
- DWord
-
-
- 14
-
-
-
-
- Real4
-
-
- 15
-
-
-
-
- Real8
-
-
- 16
-
-
-
-
- PSZ
-
-
- 17
-
-
-
-
- Usual By Ref
-
-
- 19
-
-
-
-
- UInt64
-
-
- 23
-
-
-
-
- Char
-
-
- 24
-
-
-
-
- Dynamic
-
-
- 25
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/VFPXporter.xml b/docs/Help_Spanish/Topics/VFPXporter.xml
deleted file mode 100644
index 31284a7219..0000000000
--- a/docs/Help_Spanish/Topics/VFPXporter.xml
+++ /dev/null
@@ -1,164 +0,0 @@
-
-
-
- VFPXporter
-
- export
- PropRules.json
- Statements.json
- VFP
- VFP2WinForms.json
- VFPXporter
- Visual FoxPro
-
-
-
- VFPXporter
-
- The VFPXporter tool is created to ease the move of your Visual FoxPro (VFP) Application in .NET, using a language you already know, with help of XSharp.
- 1. Minimum changes to your code during export.
- 2. Keep the original code as comment if any change is made.
- 3. Move VFP Forms to Windows Forms, using an adaptation layer/library called XSharp.VFP.UI.Dll.
- 4. Move VCX libraries as external projects containing Forms/Controls.
- 5. Create real Windows Forms solution/project so you can use any existing third party for .NET in your application.
- Start & Settings
- First, open the Settings dialog box:
-
- Folders settings
-
-
-
Default VFP item Folder: The folder where VFPXPorter will start to search for elements to export per default.
-
Default Output Folder: The folder where the VFPXPorter will create the generated export content.
-
Default exporter resources Folder: The folder where the VFPXPorter will look for extra templates, Libraries, Tools, etc.
-
-
- You can then:
-
-
Reset Settings to their default values.
-
Open Settings Folder where the .json settings file is stored (e.g., for backup).
-
- Export settings
-
- Check or Uncheck the export settings. Usually, the default values are the best choice.
-
-
-
Default Fields modifiers: When exporting a CLASS, set the default Field visibility.
-
- Project settings
-
-
-
Ignore export Errors: Allows to continue the export process in case of errors. All errors are logged in the destination folder.
-
If needed, you can specify your own name for the Folders where elements are exported.
-
Each ClassLibrary is in a SubFolder: If your application is using libraries, it is a good practice to export them separately.
-
Empty the destination folder: Each time you export an element, the destination folder is emptied
-
- Exporting
- Project
-
-
-
Input Project: Search for the .PJX file to export.
-
Output Folder: Indicate where the VFPXPorter will write the generated files.
-
Analyze: Allow to look at the content that the VFPXPorter has detected in the Project.
-
Export: Export the project
-
Open: Open the folder where the files where written.
-
-
- The generated folder should contain several folders (One per Library if you have checked the setting, One for detected FreeTables, One for XSharp Tools, etc.).
-
- You will find a file with the same name as the exported project with .SLN as extension. This is the MS Visual Studio solution file that will group all exported top-level items (Project, Libraries, etc.).
- This is the file you should open first.
- How does the VFPXPorter work?
- The VFPXPorter will read your project and its elements. It will identify their type and generate some X# code.
- In order to generate that code, it will look into the Data folder.
- There, we will find several .JSON files that are used as conversion Rules.
- The documentation for these rules is available in VFPXPorter repository on GitHub.
- Then, to generate the files, it will use some templates; one per type of file. You can find these templates on GitHub: Templates.
- Converting from VFP
- Common problems
- Please find here a list of the common troubles we will face when converting your VFP GUI code to X# and WinForms.
- Events & Methods naming
- When converting your Application from VFP to X# and WinForms, it's important to remember that these two "worlds" use a different point of view to your Form.
- In VFP, events are routed to the Controls.
- For example, each button on the Form has its own class that INHERITs from the base-class CommandButton, and is an instance of that particular class. This structure allows you to override Events and Methods at that level, providing extensive control over what's happening there.
-
- In WinForms, events are routed to the Owner of the Controls: The Form
- Therefore, the convention is to prefix the EventHandlers and Methods with the name of the Control.
- For instance, if button1 raises a click event, the name of the handler is button1_click.
- Similarly, if a Form is raising an event, since the Form itself is the class, the name will be nameOfTheForm_Event.
- This behavior can be changed through an exporter setting:
-
-
-
Prefix Event methods with FORM name
-
- Start() Function
- The generated code contains a Start() Function, which is the Startup Object of the generated application. If you are also using a Start() Function in your VFP Code, you will have to rename it after export.
- Init() Method
- With VFP, the Init() method is called when an object is created.
- With X#, calling the Constructor() of a class (with the MyClass{} syntax), won't automatically called the Init() Method.
- This process is emulated by the InitType.prg template that is used during export.
- With Controls, the Init() Method is called when the Handle is created. This code is generated by the InitType.prg template used during export.
- Colors
- Unfortunately, these cannot be handled automatically, as that would break the Windows Forms designer in Visual Studio.
- Setting a BackColor or ForeColor with an RGB, like :
- this.Label1.ForeColor = RGB(255,0,0)
- Should be converted to :
- this.Label1.ForeColor = System.Drawing.Color.FromARGB( 255,0,0) )
- BUT.... If you had a function called RGB() that returns a System.Drawing.Color in a PRG file, in the Tools folder of the Exporter, it will be part of your Exported Solution, and it will supersede the XSharp Runtime definition, which will do the trick!
- Method Call without parenthesis
- In X#, a Property holds a Value that is set/get with the equal sign, while a Method contains code that is executed when called : And you can make the difference, because Method call ends with parenthesis.
- While this is allowed in VFP, you will have to correct that in X#:
- this.Refresh
- Should be corrected as
- this.Refresh()
- These can be corrected at export time, if you check the "Convert Statement to Call" in settings.
- The handled statements are in the Statements.json file.
- Form Properties casing
- To modify a Form with the Windows Form Designer in Visual Studio, the Properties must respect the WinForm casing. Therefore, you may need to add some properties to the PropRules.json in order to automatically convert them.
- That's why ShowInTaskBar appears in the rules as ShowInTaskbar. (Note the lowercase "b").
- The following points have been addressed with the VFP2WinForms.json Rules
- Access to Parent
- The Parent Property is already defined in Windows Forms, and is strongly typed to a System.Windows.Forms.Control object. To avoid problems, and ease the port of applications, the support library contains a property called _Parent that accesses the Control's parent, but as a weakly typed Object.
- This will force X# to a late-bound call, and could help in resolving access to ported code.
- The call to _Parent is automatically generated by the XPorter.
- Calling an Object Event in Your Code
- In object with Parent, you may sometimes directly call Event handlers in your VFP code.
- This might be problematic, and for example, a direct call to the Click event of a button will fail.
- This.Parent.cmd_prec.Click
- During export, the This will be turned to ThisObject, the parent.
- Array access
- In X#, array elements are accessed using brackets [].
- In VFP, however, it is possible to use parenthesis ().
- This can create issues when accessing a .Net typed-array.
- To simplify the porting of VFP-applications, some array access operations have been converted to method calls in the XSharp.VFP.UI, the Control layer that eases access to .NET Controls using VFP syntax.
- x = __screen.FormCount __screen.Forms(x-1).Release() // Here, Forms array will be replaced by Forms Method call.
- Access Fields in the current Area/Cursor
- In VFP, it is possible to reference the current WorkArea/Cursor using its name, and to point to specific fields by specifying their name after a Dot selector, like with :
- ? movie.title
- Unfortunately, in X# the Dot selector is used for Objects, so you will have to use an arrow as selector, like with:
- ? movie->title
- Undeclared Vars
- You can use an undeclared var anywhere in your code. This is something that X# will recognize and support.
- In such case, X# will silently create a MemVar: a local, untyped, var.
- But there are some cases, where this will not work. For example:
- IF SQLExec(nHandle,"SELECT * FROM employees ORDER BY id ASC LIMIT 1","CurResult") <=0 THEN &&& validate error first. Aerror(laErr) Messagebox("Check the following error: " + Chr(13) + laErr[2],'Alert',3000) RETURN .F. ENDIF
- In the previous code, the var laErr has never been declared at this level, but it is used as a REF var by the AError() function.
- This type of construction is not supported by X#. You will have to create a local variable laErr first.
- Unsupported Functions
- When building your VFP App, you may call some functions that are not (yet) supported by X#.
- The compiler will express a warning (XS0618), but will generate an Exe, that will certainly crash at Runtime.
- To avoid that, indicate these warnings as Errors.
- To do so, with MS Visual Studio, follow these steps:
-
-
Open the Properties of the Project;
-
Go To Build;
-
In section Treat Warning as Errors, enter the Specific Warning : XS0618.
-
- XSharp.VFP.UI.Dll: adaptation layer
- VFP GUI Control library is very different from .NET Windows Forms: Properties, Methods and Event Handling are very different.
- In order to offer GUI export, VFPXPorter is using an adaptation layer, XSharp.VFP.GUI
- That library contains some controls that micmics the way VFP is behaving. It exposes the originals properties of VFP and converts them to their .NET Windows Forms counterparts.
-
- Some controls might be missing, as well as some Properties/Methods/Event. Please report your troubles in the XSharp Forums.
-
-
-
diff --git a/docs/Help_Spanish/Topics/VOID.xml b/docs/Help_Spanish/Topics/VOID.xml
deleted file mode 100644
index 016f64ad86..0000000000
--- a/docs/Help_Spanish/Topics/VOID.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- VOID
-
- VOID
-
-
-
- VOID
-
- VOID specifies a return value type for a function or method that does not return a value. Procedures implicitly define a return type of VOID.
-
-
diff --git a/docs/Help_Spanish/Topics/VOXporter.xml b/docs/Help_Spanish/Topics/VOXporter.xml
deleted file mode 100644
index a4ce6fb872..0000000000
--- a/docs/Help_Spanish/Topics/VOXporter.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- VOXporter
-
- VOXporter
-
-
-
- VOXporter
-
- Enter topic text here.
-
-
diff --git a/docs/Help_Spanish/Topics/VersionHistory.xml b/docs/Help_Spanish/Topics/VersionHistory.xml
deleted file mode 100644
index 5b258b43bb..0000000000
--- a/docs/Help_Spanish/Topics/VersionHistory.xml
+++ /dev/null
@@ -1,64 +0,0 @@
-
-
-
- Version History
-
- Changes
- Runtime chapter
- String Literals
- Version History
- XSharp 3
-
-
-
- Version History
-
- Note: When an item has a matching GitHub ticket, the ticket number is behind the item in parentheses prefixed with #. You can find these tickets by going to: https://github.com/X-Sharp/XSharpPublic/issues/nnn , where nnn is the ticket number. If you find an issue in X#, we recommend that you report it on GitHub. You will be notified of the progress on the work on your issue
- Changes in 3.0.0.0
- XSharp 3 is a MAJOR update from XSharp 2. All elements of the product have been touched during the last couple of months. X# 3 has some breaking changes, so you should take the time to recompile and test all your existing projects and solutions.
- Breaking changes
- Compiler
-
-
The compiler no longer supports "Bring Your Own Runtime". If you want to compile in the VO or Vulcan dialect you will HAVE to include references to XSharp.Core and XShar\p.RT. That does not mean that you can't link your program against the Vulcan runtime DLLs, but we no longer map our Xbase types to the types in these DLLs. So USUAL will not be mapped to Vulcan.__Usual. You can still use the types, functions and classes on these DLLs, but they will no longer be treated specially. If you want to call a function from the Vulcan Runtime yuou will have to use the syntax for static methods
-
- Runtime
-
-
The signature for several functions and methods in the X# Runtime has been changed. We have used the new IN keyword for many that use parameters defined AS USUAL. The new IN USUAL tells the compiler to pass the variable by reference, which should make the code slightly faster. It also tells the compiler that the parameter will not be changed by the code in the function / method
-
We have also moved several functions and types between Runtime DLLs, because they were not in the best possible location.
-
X# 3 comes with runtime DLLs for both .net 46 and .net 8. Not all VOSDK Dlls have been ported to .Net 8 because they contain code that does not work in a AnyCPU environment.
-
- Compiler New Features
-
-
GLOBAL USING
-
File wide NAMESPACE
-
RECORD modifier for classes and structures
-
- Bug fixes
- Build System New Features
-
-
The Build system now supports the new SDK style projects
-
We have added a task to generate source code for GLOBAL USING values declared in the project files. Please note that the VS integration does not have a page to declare the GLOBAL USING values for a project. That will follow.
-
The XAML files in the Rules subfolder of the MsBuild folder are no longer used and have been deleted. Also the references to these files in the .props and .targets files have been removed
-
The builds system no longer automarically picks up the include folder from your Vulcan installation
-
There are many changes in the .props and .targets files to support SDK style projects and .Net 10. One of these changes automatically sets dependency relations between files, such as between VOBinary files and the module that they belong to.
-
- Bug fixes
- Runtime New Features
-
-
We are now including .Net 8 versions of most of our runtime DLLs.
-
The Runtime is now delivered in both DLL format as well as Nuget Packages. See the separate topic about the Runtime in this help file for a description of these packages and DLLs
-
Several functions in the FoxPro Runtime have been added
-
- Bug fixes
- Visual Studio Integration New Features
-
-
We are now supporting SDK style projects. To do so many changes were made all over the Visual Studio support code
-
We are now fully supporting Visual Studio 2026
-
We are no longer supporting Visual Studio 2017.
-
We are still supporting Visual Studio 2019 but no new features will be implemented for this version of VS.
-
- Bug fixes
- Tools New Features
- Bug fixes
-
-
diff --git a/docs/Help_Spanish/Topics/VersionHistoryXSharp1.xml b/docs/Help_Spanish/Topics/VersionHistoryXSharp1.xml
deleted file mode 100644
index 2a0137ef23..0000000000
--- a/docs/Help_Spanish/Topics/VersionHistoryXSharp1.xml
+++ /dev/null
@@ -1,1178 +0,0 @@
-
-
-
- History XSharp 1 and older
-
- Changes
- Runtime chapter
- String Literals
- Version History
- XSharp 1
-
-
-
- History XSharp 1 and older
-
- Changes in 1.2.1
- Compiler
-
-
Fixed a problem where a compilation error resulted in the message "Failed to emit module" without further information
-
Fixed a problem with ++, -- += and similar operations in aliased expressions (like CUSTOMER->CUSTNO++)
-
Constructor initializers and Collection initializers were not working after a constructor with parameters. That has been fixed.
-
Fixed an issue with negative literal values stored in a USUAL when overflow checking was enabled.
-
For the CATCH clause now both the ID and the TypeName are optional. This means that there are 4 variations. You can only have one catch clause without type, since this defaults to the System.Exception type. However, you can have many catch clauses without ID.
-
- CATCH ID AS ExceptionType CATCH ID // defaults to Exception type CATCHAS ExceptionType CATCH// defaults to Exception type
- Visual Studio Integration
-
-
Improved the speed of the background code scanning
-
Improved the speed of the background parser inside the editor
-
Fixed a problem in the codedom provider that is used by the windows forms editor
-
-
-
- Changes in 1.2.0
- Compiler
-
-
You can now pass NULL for parameters declared by reference for compatibility with VO & Vulcan. We STRONGLY advise not to do this, unless you make sure that the function expects this and does not assign to the reference parameter without checking for a NULL reference first. This will only work when the /vo7 compiler option is enabled.
-
We have made some optimizations in the Lexer. The compiler should be a little faster because of that
-
We fixed a problem with the automatic constructor generation (/vo16) for classes that inherit from classes defined in an external DLL
-
When compiling with /vo2 any string fields assigned in a child class before the super constructor was called would be overwritten with an empty string. The generated code will now only assign an empty string when the string is NULL. Note: we do not recommend to assign parent fields in the child constructor before calling the super constructor. Manually coded default values for parent fields will still overwrite values assigned in the child constructor before the SUPER call
-
Fixed a problem with CHECKED() and UNCHECKED() syntax in the VO dialect
-
Fixed a problem with choosing overloads for methods where an overload exists with a single object parameter and also an overload with an object[] parameter.
-
Added support to the parser for LOCAL STATIC syntax
-
Fixed a problem with compiler option /vo9 (Allow missing return values) and procedures or methods that return VOID
-
Improved debugger sequence point generation. The compiler no longer generates 'hidden' breakpoint information for startup and closedown code in the VO/Vulcan dialects, and for expression statements no longer a double step is necessary.
-
ACCESS and ASSIGN for partial classes could generate error messages without source file name. This has been solved. The compiler now generates slightly different code for these "partial" properties. The Access and Assign are implemented as compiler generated methods and the property getter and property setter now call these methods.
-
The compiler was not recognizing the _WINCALL calling convention. This has been fixed.
-
The compiler now generates a warning when the #pragma command is used
-
- Visual Studio Integration
-
-
More performance improvements in the editor. Especially large source files with incorrect code could slow down the editor.
-
The editor parser no longer tries to parse include files repeatedly when these files contain #defines only (like the Vulcan header files)
-
The source code editor tried to show intellisense for words in a comment region. That has been fixed.
-
We have started work on Object Browser and Class Browser.
-
Opening and closing of projects should be slightly faster
-
The internal code model used by the editors now disposes its loaded information when projects are closed and no projects need this information anymore. This should reduce the memory usage of the X# project system
-
Matching keywords, such as IF .. ENDIF and FOR .. NEXT should now be highlighted in the editor
-
If you select an identifier in the editor then that identifier will be highlighted in the current method/function on all places where it is used
-
We have added several features that you need to enable/disable on the Tools/Options/Text Editor/XSharp/Intellisense dialog:
-
-
The code completion in the editor also supports instance member completion when a dot is pressed. Please note that the compiler ONLY accepts this in the Core language, not in the VO & Vulcan dialect. So the option has no effect inside projects with other dialects.
-
We have added some options to control the sorting of the DropDown comboboxes in the editor, as well as if fields/instance variables should be included in these comboboxes. When you do not sort, then the entries in the dropdown box will be shown in the order in which they are found in the source file.
-
We have added the option to autocomplete identifiers when typing. This includes locals, parameters, class fields, namespaces, types etc.
-
-
-
-
Overridden methods in subclasses with the same signature as the parent methods they override are no longer counted as overloads in completionlists
-
A missing reference DLL could "kill" the intellisense engine. This no longer happens. Of course the type info from a missing referenced DLL is not included.
-
Properties and methods in the generated source files for XAML code (the .g.prg files in the OBJ folder) are now also parsed and included in the completion lists in intellisense and in the Class Browser and Object Browser windows.
-
- VOXPorter
-
-
The installer now includes the correct version of VOXPorter <g>
-
VOXporter now supports the following commandline options: /s:<source folder or aef>
Some code corrections were added for issues found in the GUI classes
-
The template files can now also be found when VOXPorter is run from a different working directory
-
-
-
- Changes in 1.1.2
- Compiler
-
-
Added compiler warning for code that contains a #pragma
-
Fixed a problem with iif() functions and negative literal values
-
- Visual Studio Integration
-
-
Fixed a slowness in the editor after typing a send (: ) operator
-
Enum values are now properly decoded in the debugger
-
Fixed the CodeDom provider for handling literal FALSE values and negative numbers. As a result, more (Vulcan created) winforms should open without problems
-
Some positional keywords (such as ADD and REMOVE) are no longer colored as keyword in the editor for incomplete code when they appear after a colon ‘:’ or dot ‘.’;
-
- VOXPorter
-
-
Fixes for exporting the VO RDD Classes from the SDK
-
-
-
-
- Changes in 1.1.1
- Compiler
-
-
Fixed a problem with Debugger Breakpoints for DO CASE and OTHERWISE
-
Fixed a problem with Debugger Breakpoints for sourcecode that is defined in #included files
-
Added support for the Harbour Global Syntax where the GLOBAL keyword is optional
-
Fixed a problem with FOR.. NEXT loops with negative step values
-
In some situations the @@ prefix to avoid keyword conflicts was not removed from workarea names or field names. This has been fixed
-
In the VO/Vulcan dialect a warning (XS9015) was generated when a default parameterless SUPER constructor call was automatically generated. This error message is now suppressed. However a generated SUPER constructor call with parameters still generates a warning.
-
Prepared the compiler for Xbase type names and function names in the XSharp Runtime
-
- Preprocessor
-
-
Fixed a crash in the preprocessor
-
The preprocessor was generating an error "Optional block does not contain a match marker" for blocks without match marker. This is now allowed. (for example for the ALL clause in some of the Database UDCs )
-
When the same include files was used by multiple source files, and different sections of this file were included because of different #ifdef conditions, then the preprocessor would get "confused". This has been fixed.
-
Debugger file/line number information from source code imported from #include files is not processed correctly.
-
- Visual Studio Integration
-
-
Fixed several issues with the Windows Form Editor
-
The class declaration generated by the VO compatible editors now included the PARTIAL modifier.
-
-
-
- Changes in 1.1
- Compiler
-
-
Fixed a problem with Codeblocks used in late bound code after the release of X# 1.0.3
-
Fixed a problem with overriding properties in a subclass that inherit from a class where only the Assign (Set) or Access (Get) are defined.
-
The compiler option /vo16: automatically generate VO Clipper constructors has been implemented.
-
Fixed a crash in the compiler for compiler errors that occur on line 1, column 1 of the source file
-
Fixed a problem where overflow checking was not following the /ovf compiler option
-
Fixed problem with public modifier for interface methods
-
Added proper error message with unreachable fields in external DLLs
-
Fixed a problem with debugger sequence points (debugger stepping)
-
X# generated pdb files are now marked with the X# language GUID so they are recognized as X# in the VS debugger
-
DATETIME (26) and DECIMAL (27) are added as UsualType to the compiler in preparation of the X# runtime that allows usuals of these types
-
Compiler options /VO15 and /VO16 now produce an error message when used outside the VO/Vulcan dialect
-
Methods declared outside a class (VO style code) would declare a private class and not a public class
-
ASTYPE has been changed to a positional keyword
-
Fixed a problem with the Chr() and _Chr() functions for literal numbers > 127
-
Added support for the __CLR2__ and __CLR4__ compiler macros. The version is derived from the folder name of mscorlib.dll and/or system.dll
-
The Codeblock syntax was not working in the Core dialect.
-
Some new keywords, such as REPEAT, UNTIL, CATCH, FINALLY,VAR, IMPLIED, NAMESPACE, LOCK, SCOPE, YIELD, SWITCH etc are now also positional and will only be recognized as keyword when at the start of a line or after a matching other keyword. This should help prevent cryptic error messages when these keywords are used as function names.
-
- Visual Studio
- Source code editor
-
-
Added Goto Definition for Functions and Procedures
-
Improved Info tips for Functions and Procedures
-
Improved case synchronization
-
Added first version of smart indenting
-
Fixed lookup problems in the intellisense engine that could lock up VS
-
Compiler Generated types are now suppressed from the completion lists.
-
Added partial support for intellisense for LOCAL IMPLIED and VAR variables
-
Added support for Format Document. This also sets the case for identifiers according to the tools defined in the Tools/Options menu
-
Performance improvements for the background file scanner. This scanner is also paused during the build process to improve the compilation speed.
-
- Project System and MsBuild
-
-
Fixed a problem in the project files with conditioned property groups. Existing projects will be updated automatically
-
Added support for the /vo16 compiler option in MsBuild and the VS Project Property pages.
-
Fixed a problem with the /nostddef compiler option which was not working as expected.
-
Fixed a problem which would occur when entering resources or settings in the project property dialog
-
Fixed a problem with the /nostdlib compiler option
-
License.Licx files are now added as "Embedded Resource"
-
Fixed a problem with the automatic adding of License files
-
When a project has a "broken reference" and a new reference is added with the correct location, then the broken reference will be deleted and the new references will be added instead.
-
The MSBuild support DLL was unable to find the location of the compiler and native resource compiler when running inside a 64 bit process
-
- Form Editor
-
-
Improved Windows Form Editor support for types defined in project references. We will now detect the location of the output files for these projects, like the C# and VB project systems.
-
The Code parser for the Form Editor was having problems with untyped methods. This has been fixed.
-
- VO Window and Menu Editor
-
-
The code generator for the Window and Menu editor will delete old unused defines.
-
Changed the item template for VO windows to fix a problem when adding an event handler to a window that has not been saved yet
-
The code generator for the Window editor was not outputting a style for WS_VISIBLE. This has been fixed.
-
- Debugger
- This build introduces a first version of the XSharp debugger support
-
-
The Visual Studio debugger now shows the language X# in the callstack window and other places
-
Functions, Methods and procedures are now displayed in the X# language style in the callstack window
-
Compiler generated variables are no longer shown in the locals list
-
The locals list now shows SELF in stead of this
-
X# predefined types such as WORD, LOGIC etc are shown with their X# type names in the locals window
-
- Testing
-
-
Added support for the Test Explorer window
-
Added templates for unit testing with XUnit, NUnit and Microsoft Test
-
- Other
-
-
Added warning when Vulcan was (re)installed after XSharp, which could cause a problem in the Visual Studio integration
-
The VS Parser was marking Interfaces as structure in stead of interface. This has been fixed.
-
The tool XPorter tools have better names in the VS Tools Menu
-
The VS Background parser gets suspended while looking up type information to improve the intellisense speed
-
Several changes were made to the templates that come with X#
-
- XPorter
-
-
Fix problem in propertygroup conditions.
-
- VOXPorter
-
-
Generate clipper constructors is now disabled by default
-
Fixed a problem in the VS Template files.
-
-
-
- Changes in 1.0.3
- Compiler
-
-
Fixed a problem with the index calculation for Vulcan Arrays indexed with a usual argument
-
Fixed a problem with the generation of automatic return values for code that ends with a begin sequence statement or a try statement
-
Optimized the runtime performance for literal symbols. The compiler now generates a symbol table for the literal symbols and each literal symbol used in your app is only created once. You may experience a little delay at startup if your app uses a LOT (thousands) of literal symbols. But the runtime performance should be better.
-
Added a compiler error for code where numerics are casted to an OBJECT with the VO compatible _CAST operator. This is no longer allowed: LOCAL nValue as LONG LOCAL oObject as OBJECT nValue := 123 oObject := OBJECT(_CAST, nValue)
-
-
-
- Changes in 1.0.2
- Compiler
-
-
Added support for XML doc generation. We support the same tags that the C# compiler and other .Net compiler support.
-
Improved some parser errors.
-
Created separate projects for portable and non portable (.Net framework 4.6) for the compiler and scripting
-
Fixed the code generation for conversion from USUAL to a known type. Now the same error is generated that Vulcan produces when the object type in the usual does not match the type of the target variable
-
When declaring a type with the same name as the assembly now a compiler error is generated with a suggested work around.
-
Fixed a strange compiler message when using a PTR() operation on a method call
-
Indexed access to bytes in a PSZ is now 1 based like in VO when the VO dialect is used. The Vulcan dialect needs 0 based index access like Vulcan.
-
The error message for compound assignments of FLOAT and USUAL has been removed. The compiler now contains a workaround for the problem in the Vulcan Runtime
-
For ambiguous code where the compiler has to choose between a Function call and a static method call in any other class, the compiler now chooses the function call over the method call (Vo and Vulcan dialect). The warning will still be generated.
-
When passing a variable by reference with the @ sign the compiler will now check to see if the declared type of the function/method parameter matches the type of the local variable.
-
Some compiler warnings for unused variables were being suppressed in the VO/Vulcan dialect. They are activated again.
-
- Scripting
-
-
The scripting was not working in release 1.01
-
- Visual Studio Integration
-
-
QuickInfo could generate a 'hang' in the VS editor. This has been fixed
-
Added quickinfo for globals and defines
-
Added completionlists for globals and defines
-
Added VO Form editor to edit vnfrm/xsfrm files and generate the code and resources
-
Added VO Menu editor to edit vnmnu/xsmnu files and generate the code and resources
-
Added VO DbServer editor and VO Fieldspec editor to edit vndbs/xsdbs and vnfs/xsfs files and generate the code and resources
-
Added keyword and identifier case synchronization.
-
Fixed a problem where typing SUPER( in the editor could throw an exception
-
Prebuild and Postbuild entries in the project file are now configuration specific
-
Added support for XML Doc generation in the project system
-
Fixed a 'hang' that could occur with Visual Studio 2017 version 15.3 and later
-
- VO Xporter
-
-
Fixed a problem when importing certain VO 2.7 AEF files
-
Fixed a problem with acceptable characters in the solution folder name
-
VO Form and menu entities are also included in the xsproj file
-
Added an option to the INI files to specify the Vulcan Runtime files location ()
-
-
-
- Changes in General Release (1.0.1.1)
- Compiler
-
-
Fixed a problem with VERY old versions of the Vulcan Runtime
-
Variables declared as DIM Byte[] and similar are now Pinned by the compiler
-
[Return] attribute was not properly handled by the compiler. This has been fixed
-
Compound Assignment (u+= f or -=) from USUAL and FLOAT were causing a stackoverflow at runtime caused by a problem in the Vulcan Runtime. These expressions now generate a compiler error with the suggestion to change to a simple assignment ( u := u + f)
-
- Visual Studio Integration
-
-
Project References between XSharp Projects were also loaded as assemblyreference when resolving types. This could lead to speed problems and unnecessary memory usage
-
Improved the speed of the construction of Completion Lists (such as methods and fields for a type).
-
We have also added Completion List Tabs, where you can see fields, properties, methods etc. on separate tabs. You can enable/disable this in the Tools/Options/Text Editor/XSharp/Intellisense options page.
-
- VO XPorter
-
-
We have added a check to make sure that the default namespace for a X# project cannot contain a whitespace character
-
-
-
- Changes in General Release (1.0.1)
- New Features
-
-
We have added support for ENUM Basetypes (ENUM Foo AS WORD)
-
We have added a separate syntax for Lambda Expressions
-
We have added support for Anonymous Method Expressions
-
Typed local variables can now also be used for PCALL() calls
-
Methods with the ExtensionAttribute and Parameters with the ParamArrayAttribute attributes now compile correctly, but with a warning
-
- Compiler
-
-
Fixed a problem with a late bound assign of a literal codeblock
-
Resolved several name conflicts
-
Improved several of the error messages
-
Fixed compilation problem for Properties with only a SET accessor
-
Fixed a crash in a switch block with an if .. endif statement
-
Fix problem with virtual instance methods and structures
-
Fixed name conflict foreach variables used in Array Literals
-
Changed resolution for Functions and static methods with the same name. In the VO/Vulcan dialect functions take precedence over static methods. If you want to call the static method then then you need to prefix the method call with the classname.
-
There is a separate topic in this documentation now that describes the syntax differences and similarities between Codeblocks, Lambda Expressions and Anonymous Method Expressions.
-
Fixed incorrect error message for Start() function with wrong prototype.
-
When an ambiguity is detected between a function and a static method then a warning is displayed
-
- Visual Studio
-
-
Added parameter tips for Functions and methods from "Using Static" classes
-
Added parameter tips for Clipper Calling Convention functions and methods
-
Added support for generics in Intellisense
-
Intellisense will show keywords in stead of native type names (WORD in stead of System.UInt16 for example)
-
Parameter tips are now shown when a opening '(' or '{' is typed as well as when the user types a comma ','.
-
Parameter tips will show REF OUT and AS modifiers
-
Added intellisense for COM references, both for normal COM references as well as for Primary Interop Assemblies. Also members from implemented interfaces are now included in intellisense code completion (this is very common for COM).
-
Improved intellisense for Project References from other languages, such as C# and VB.
-
Added intellisense for Functions in referenced projects and referenced Vulcan and/or X# assemblies
-
Suppress "special type names" in intellisense lists
-
Added support for "VulcanClassLibrary" attribute to help find types and functions
-
Errors from the Native Resource compiler are now also included in the error list
-
Fixed problem with parameter tips for Constructors
-
Added memberlist support for X# type keywords such as STRING, REAL4 etc.
-
Fixed several issues with the Windows Form editor in relation to ActiveX controls
-
Added a menu option to start the VO Xporter tool
-
Added background scanning for dependent items, to make sure that newly generated code is scanned and available for intellisense.
-
Several changes to the Windows Forms editor and project system:
-
-
Added support for adding ActiveX controls
-
Added support for Form Inheritance. Our forms are also visible in the C# Inherited form wizard
-
Added support to add our Windows Forms Custom Controls to the ToolBox in Visual Studio
-
Some performance enhancements in the Codedom Parser that is used by the Windows Form Editor. You should notice this for larger forms.
-
-
-
-
Fixed several crashes reported by users
-
Native Resource files (.rc) now open in the Source code editor
-
Improved background parsing speed
-
Improved keyword colorization speed
-
Improved handling of Type and Member dropdowns in the editor
-
- Tools
-
-
Added a first version of the VO Xporter tool
-
The installer now registers .xsproj files, .prg, .ppo. .vh, .xh and .xs files so they will be opened with Visual Studio
-
- Documentation
-
-
We have added some chapters on how to convert your VO AEF and/or PRG files to a XIDE project and/or a Visual Studio solution.
-
-
-
- Changes in 0.2.12
- Scripting
-
-
We have added the ability to use X# scripts. Some documentation about how this works can be found here. You can also find scripting examples in the c:\Users\Public\Documents\XSharp\Scripting folder
-
- Compiler
- All dialects
-
-
The compiler is now based on the Roslyn source code for C# 7.
-
Accesses and Assigns with the same name for the same (partial) class in separate source files are now merged into one property. This will slow down the compiler somewhat. We recommend that you define the ACCESS and ASSIGN in the same source file.
-
Added support for repeated result markers in the preprocessor
-
We have added the compiler macro __DIALECT_HARBOUR__
-
Fixed the name resolution between types, namespaces, fields, properties, methods, globals etc. The core dialect is very close to the C# rules, the other dialect follows the VO rules.
-
Some warnings for ambiguous code have been added
-
_Chr() with untyped numeric values would crash. This has been fixed.
-
We made some changes to the character literal rules. For the VO and Harbour dialect there are now other rules then for Core and Vulcan. See the help topic for more information
-
- VO and Vulcan Dialect
-
-
Several VO compatibility issues have been fixed
-
The QUIT, ACCEPT, WAIT, DEFAULT TO and STORE command are now removed from the compiler and defined in our standard header file "XSharpDefs.xh" which is located in the \Program Files(x86)\XSharp\Include folder. These commands are not compiled in the core dialect
-
Added support for CONSTRUCTOR() CLASS MyClass and DESTRUCTOR CLASS MyClass (in other words, outside the CLASS .. ENDCLASS construct
-
-
-
The # (not equal) operator is now recognized when used without space before the keywords NIL, NULL_STRING, NULL_OBJECT etc. so #NIL is not seen as the symbol NIL but as Not Equal To NIL
-
SizeOf and _TypeOf were special tokens in VO and could not be abbreviated. We have changed the X# behavior to match this. This prevents name conflicts with variables such as _type.
-
We have added support for DLL entrypoints with embedded @ signs, such as "CAVOADAM.AdamCleanupProtoType@12"
-
(DWORD) (-1) would require the unchecked operator. This is now compatible with Vulcan and generates a DWORD with the value System.Uint32.MaxValue.
-
STATIC VOSTRUCT now gets compiled as INTERNAL VOSTRUCT. This means that you cannot have the same structure twice in your app. Why would you want to do that ?
-
Fixed several cases of "incorrect" code that would be compiled by VO, such as a codeblock that looks like: cb := { |x|, x[1] == 1 } Note the extra comma. This now compiled into the same codeblock as:
-
- cb := { |x| x[1] == 1 }
-
-
The /vo16 compiler option has been disabled for now (does not do anything) because it had too many side effects.
-
- Visual Studio Integration
-
-
Deleted files and folders are moved them to the Trash can.
-
Fixed an intellisense problem in the XAML editor
-
Added support for Code Completion between different X# projects
-
Added support for Code Completion and other intellisense features for source code in VB and C# projects
-
Added support for parameter info
-
- Documentation
-
-
We have added (generated) topics for all undocumented compiler errors. Some topics only contain the text that is shown by the compiler. More documentation will follow. Also some documentation for the X# Scripting has been added.
-
-
-
- Changes in 0.2.11
- Compiler
- All dialects
-
-
Improved some error messages, such as for unterminated strings
-
Added support for the /s (Syntax Check only) command line option
-
Added support for the /parseonly command line option which is used by the intellisense parser
-
-
-
Added some compiler errors and warnings for invalid code
-
The preprocessor did not properly handle 4 letter abbreviations for #command and #translate. This has been fixed
-
Fixed some problems found with the preprocessor
-
We switched to a new Antlr parser runtime. This should result in slightly better performance.
-
Changed the way literal characters and strings are defined:
-
-
In the Vulcan dialect a literal string that is enclosed with single quotes is a char literal. Double quotes are string literals
-
In the Core and VO dialect a literal string that is enclosed with single quotes is a string literal. Double quotes are also string literals. To specify a char literal in Core and VO you need to prefix the literal with a 'c':
-
-
-
- LOCAL cChar as CHAR cChar := c'A'
-
-
Changed the way literal characters and strings are defined:
-
sizeof() and _sizeof() no longer generate a warning that they require 'unsafe' code, when compiling for x86 or x64. When compiling for AnyCpu the warning is still produced.
-
When the includedir environment variable was not set then the XSharp\Include folder would also not be found automatically.
-
- VO/Vulcan Compatibility
-
-
Added /vo16 compiler option to automatically generate constructors with Clipper calling convention for classes without constructor
-
- Harbour Compatibilty
-
-
Started work on the Harbour dialect. This is identical with the VO/Vulcan dialect. The only difference so far is that the IIF() expressions are optional
-
- Visual Studio
- New features / changed behavior:
-
-
Added Brace Matching
-
Added Peek definition (Alt-F12)
-
All keywords are not automatically part of the Completionlist
-
Fixed a member lookup problem with Functions and Procedures inside a Namespace
-
Increased background parser speed for large projects
-
Fixed type lookup for fields and properties from parent classes
-
Fixed problem where CSharp projects could not find the output of a XSharp project reference
-
The Intellisense parser now properly used all current projects compiler options.
-
Prevent crashes when the X# language buffer is fed with "garbage" such as C# code
-
- Installer
-
-
The local template cache and components cache for VS2017 was not cleared properly this has been fixed.
-
Added code to properly unregister an existing CodeDomProvider when installing
-
- Documentation
-
-
Several empty chapters are now hidden.
-
Added description of the templates
-
-
-
- Changes in 0.2.10
- This build focuses on the last remaining issues in the VO and Vulcan compatibility and adds a lot of new features to the Visual Studio integration.
- Compiler
- VO/Vulcan Compatibility
-
-
We have completed support for the DEFINE keyword. The type clause is now optional. The compiler will figure out the type of the define when no type is specified. The DEFINEs will be compiled to a Constant field of the Functions class, or a Readonly Static field, when the expression cannot be determined at compile time (such as for Literal dates or symbols).
-
We have extended the preprocessor . It now has support for #command, #translate, #xcommand and #xtranslate. Also "Pseudo function" defines are supported, such as :
#define MAX(x,y) IIF((x) > (y), (x), (y))
This works just like a #xtranslate, with the exception that the define is case sensitive (unless you have enabled the "VO compatible preprocessor" option (/vo8). The only thing that is not working in the preprocessor is the repeated result marker.
-
In VO/Vulcan mode the compiler now accepts "garbage" between keywords such as ENDIF and NEXT and the end of the statement, just like the VO compiler. So you no longer have to remove "comment" tokens after a NEXT or ENDIF. This will compile without changes in the VO and Vulcan dialect:
IF X == Y DoSomething() ENDIF X == Y or FOR I := 1 to 10 DoSomething() NEXT I We do not recommend this coding style, but this kind of code is very common...
-
Fixed an issue with recognition of single quoted strings. These were always recognized as CHAR_CONST when the length of the string was 1. Now they are treated as STRING_CONST and the compiler backend has been adjusted to convert the STRING literals to CHAR literals when needed.
-
In VO and Vulcan dialect when the compiler option /vo1 is used then RETURN statements without value or with a return value of SELF are allowed for the Init() and Axit() methods. Other return values will trigger a compiler warning and will be ignored.
-
- New features / changed behavior:
-
-
The compiler now produces an error when a source file ends with an unterminated multi line comment
-
Added ASTYPE expression, similar to the AS construct in other languages. This will assign a value of the correct type or NULL when the expression is not of the correct type:
-
- VAR someVariable := <AnExpression> ASTYPE <SomeType>
-
-
The Chr() and _Chr() functions are now converted to a string or character literal when the parameter is a compile time constant
-
Compilation speed for assemblies with larger numbers of functions, procedures, defines, globals or _dll functions has been improved.
-
_DLL FUNCTIONS now automatically are marked with CharSet.Auto
-
Fixed some inconsistencies between Colon (:) and Point (.) interoperability and the super keyword
-
Fixed several compiler issues reported by FOX subscribers and other users.
-
- Visual Studio
- New features / changed behavior:
-
-
Tested and works with the release version of Visual Studio 2017
-
-
-
We have added support for regions inside the VS editor. At this moment most "entities" are collapsible as well as statement blocks, regions and lists of usings, #includes and comments.
-
We have added support for member and type drop downs in the VS Editor
-
We have added support for Code completion in the VS editor
-
We have added support for Goto definition in the VS Editor
-
Errors detected by the intellisense scanner are now also included in the VS error list.
-
We have added help links to the errors in the VS error list. The help links will bring you to the appropriate page on the X# website. Not all the help pages are complete yet, but at least the infrastructure is working.
-
We have added support for snippets and included several code snippets in the installer
-
We have made several changes to the project properties dialogs
-
-
The pre and post build events are now on a separate page for the Project Properties. These are now also not defined per configuration but are shared between the various configurations. If you want to copy output results to different folders for different configurations you should use the $(Configuration) and $(Platform) variables
-
We have moved the Platform and Prefer32Bits properties to the Build page to make them configuration dependent
-
Fixed a problem with casing of the AnyCPU platform which would result in duplicate items in the VS Platform combobox
-
Added support for ARM and Itanium platform types
-
Some properties were saved in project file groups without a platform identifier. This has been fixed
-
We have added a project property to control how Managed file resources are included: Use Vulcan Compatible Managed Resources When 'True' then resources files are included in the assembly without namespace prefix. When 'False' then the resource files are prefixed with the namespace of the app, just like in other .Net languages, such as C#
-
-
-
-
We have fixed some code generation problems
-
The parser that is used in the Windows Forms editor now also properly handles background images. Both images in the resx for the form and also background images in the shared project resources
-
We have added Nuget support for our project system.
-
We have made several changes to fix problems in project files
-
-
The project system now silently fixes problems with duplicate items
-
Fixed a problem with dependencies between xaml files and their dependent designer.prg files and other dependent files
-
Fixed a problem with dependent items in sub folders or in a folder tree that includes a dot in a folder name.
-
Fixed a problem in the WPF template
-
-
-
-
Fixed a refresh problem when deleting a references node
-
Added implementation of the OAProject.Imports property, which is used by JetBrains
-
- XPorter
-
-
Fixed a problem converting WPF style projects
-
-
-
- Changes in 0.2.9
- Compiler
- With this build you can compile the Vulcan SDK without changes, except for some obvious errors in the Vulcan SDK that Vulcan did not find! We consider the Vulcan Compatibility of the compiler finished with the current state of the compiler. All Vulcan code should compile without proble now.
- VO/Vulcan Compatibility
- New features / changed behavior:
-
-
All Init procedures are now properly called at startup. So not only the init procedures in the VOSDK libraries but also init procedures in other libraries and the main exe
-
Changed the method and type resolution code:
-
-
A method with a single object parameter is now preferred over a method with an Object[] parameter
-
When both a function (static method) exists and an instance method we will now call the static method in code inside methods that does not have a SELF: or SUPER: prefix.
-
In situations where the @ operator is used to pass variables by reference.
-
To make it more compatible with Vulcan for overloads with different numeric types.
-
To prefer a method with specific parameters over a method with usual parameters
-
To avoid problems with Types and Namespaces with the same name.
-
To prefer a method with an OBJECT parameter over the one with OBJECT[] parameters when only 1 argument is passed
-
When 2 identical functions or types are detected in referenced assemblies we now choose the one in the first referenced assembly like Vulcan does, and generate warning 9043
-
-
-
-
The sizeof operator now returns a DWORD to be compatible with VO and Vulcan.
-
Added support for EXIT PROCEDURES (PROCEDURE MyProcedure EXIT). These procedures will automatically be called during program shutdown, just before all the global variables are cleared. The compiler now generates an $Exit function for each assembly in which the exit procedures will be called and the reference globals in an assembly will be cleared. In the main app a $AppExit() function is created that will call the $Exit functions in all references X# assemblies. When a Vulcan compiled assembly is referenced, then all the public reference globals will be cleared from the $AppExit() function.
-
Added support for PCALL and PCALLNATIVE
-
Added support for several Vulcan compatible compiler options:
-
-
/vo1 Allow Init() and Axit() for constructor and destruction
-
/vo6 Allow (global) function pointers. DotNet does not "know" these. They are compiled to IntPtr. The function information is preserved so you can use these pointer in a PCALL()
-
/ppo. Save the preprocessed compiler output to a file
-
/Showdefs Show a list of the defines and their values on the console
-
/showincludes Show a list of the included header files on the console
-
/verbose Shows includes, source file names, defines and more. on the console
-
DEFAULT TO command
-
ACCEPT command
-
WAIT command
-
-
-
-
Several code generation changes:
-
-
Changed the code generation for DIM elements inside VOStruct arrays because the Vulcan compiler depends on a specific naming scheme and did not recognize our names.
-
Improved the code generation inside methods with CLIPPER calling convention.
-
-
- Bug fixes
-
-
Implicit namespaces are now only used when the /ins compiler option is enabled. In Vulcan dialect the namespace Vulcan is always included.
-
Fixed several problems with the @ operator and VOSTRUCT types
-
Fixed a problem with DIM arrays of VOSTRUCT types
-
Fixed a problem with LOGIC values inside VOSTRUCT and UNION types
-
Fixed several problems with the VOStyle _CAST and Conversion operators.
-
Fixed several numeric conversion problems
-
Fixed several problems when mixing NULL, NULL_PTR and NULL_PSZ
-
Fixed several problems with the _CAST operator
-
Fixed several problems with PSZ Comparisons. X# now works just like Vulcan and VO and produces the same (sometimes useless) results
-
Fixed a problem with USUAL array indexes for multi dimensional XBase Arrays
-
Fixed codeblock problems for codeblocks where the last expression was VOID
-
Changed code generation for NULL_SYMBOL
-
Preprocessor #defines were sometimes conflicting with class or namespace names. For example when /vo8 was selected the method System.Diagnostics.Debug.WriteLine() could not be called because the DEBUG define was removing the classname. We have changed the preprocessor so it will no longer replace words immediately before or after a DOT or COLON operator.
-
Fixed a compiler crash when calling static methods in the System.Object class when Late Binding was enabled
-
Fixed String2Psz() problem inside PROPERTY GET and PROPERTY SET
-
And many more changes.
-
- All dialects
- New features / changed behavior:
-
-
Several code generation changes:
-
-
The code generation for ACCESS and ASSIGN has changed. There are no longer separate methods in the class, but the content of these methods is now inlined in the generated Get and Set methods for the generated property.
-
Optimized the code generation for IIF statements.
-
The debugger/step information has been improved. The debugger should now also stop on IF statements, FOR statements, CASE statements etc.
-
-
-
-
Indexed access to properties defined with the SELF keyword can now also use the "Index" property name
-
Functions and Procedures inside classes are not allowed (for now)
-
RETURN <LiteralValue> inside an ASSIGN method will no longer allocate a variable and produce an warning
-
Several keywords are now also allowed as Identifier (and will no longer have to be prefixed with @@ ): Delegate, Enum, Event, Field, Func, Instance, Interface, Operator, Proc, Property, Structure, Union, VOStruct and many more As a result the following is now valid code (but not recommended):
FUNCTION Start ASVOID LOCALINTERFACEASSTRING LOCALOPERATORAS LONG ? INTERFACE, OPERATOR RETURN
-
- You can see that the Visual Studio language support also recognizes that INTERFACE and OPERATOR are not used as keywords in this context
- Bug fixes
-
-
Fixed a problem with the REPEAT UNTIL statement
-
Fixed a crash for code with a DO CASE without a matching END CASE
-
Fixed several issues for the code generation for _DLL FUNCTIONs and _DLL PROCEDUREs
-
Fixed a problem (in the Roslyn code) with embedding Native Resources in the Assembly.
-
Fixed a problem with the _OR() and _AND() operators with more than 2 arguments.
-
Added support for Pointer dereferencing using the VO/Vulcan Syntax : DWORD(p) => p[1]
-
Fixed several problems with the @ operator
-
When two partial classes had the same name and a different casing the compiler would not properly merge the class definitions.
-
Fixed a crash when a #define in code was the same as a define passed on the commandline
-
Indexed pointer access was not respecting the /AZ compiler option (and always assumed 0 based arrays). This has been fixed
-
Fixed a problem with the caching of preprocessed files, especially files that contain #ifdef constructs.
-
Fixed a problem which could occur when 2 partial classes had the same name but a different case
-
Fixed a compiler crash when a referenced assembly had duplicate namespaces that were only different in Case
-
Fixed problems with Functions that have a [DllImport] attribute.
-
Error messages for ACCESS/ASSIGN methods would sometimes point to a strange location in the source file. This has been fixed.
-
Fixed a problem with Init Procedures that had a STATIC modifier
Default Parameters are now handled like VO and Vulcan do. This means that you can also have date constants, symbolic constants etc as default parameter
-
String Single Equals rules are now 100% identical with Visual Objects. We found one case where Vulcan does not return the same result as Visual Objects. We have chosen to be compatible with VO.
-
When compiling in VO/Vulcan mode then the init procedures in the VO SDK libraries are automatically called. You do not have to call these in your code anymore Also Init procedures in the main assembly are called at startup.
-
The /vo7 compiler option (Implicit casts and conversions) has been implemented. This also includes support to use the @ sign for REF parameters
-
You can now use the DOT operator to access members in VOSTRUCT variables
-
We have fixed several USUAL - Other type conversion problems that required casts in previous builds
-
The compiler now correctly parses VO code that contains DECLARE METHOD, DECLARE ACCESS and DECLARE ASSIGN statements and ignores these
-
The compiler now parses "VO Style" compiler pragma's (~"keyword" as white-space and ignores these.
-
Fixed a problem where arrays declared with the "LOCAL aSomething[10] AS ARRAY" syntax would not be initialized with the proper number of elements
-
Fixed a problem when calling Clipper Calling Convention constructors with a single USUAL parameter
-
Attributes on _DLL entities would not be properly compiled. These are recognized for now but ignored.
-
Fixed several numeric conversion problems
-
- New features
-
-
We have added support for Collection Initializers and Object Initializers
-
Anonymous type members no longer have to be named. If you select a property as an anonymous type member then the same property name will be used for the anonymous type as well.
-
Missing closing keywords (such as NEXT, ENDIF, ENDCASE and ENDDO) now produce better error messages
-
IIF() Expressions are now also allowed as Expression statement. The generated code will be the same as if an IF statement was used
-
- FUNCTION IsEven(nValue as LONG) AS LOGIC LOCAL lEven as LOGIC IIF( nValue %2 == 0, lEven := TRUE, lEven := FALSE) RETURN lEven
- We really do not encourage to hide assignments like this, but in case you have used this coding style,it works now <g>.
-
-
AS VOID is now allowed as (the only) type specification for PROCEDUREs
-
We have added a .config file to the exe for the shared compiler that should make it faster
-
The XSharpStdDefs.xh file in the XSharp is now automatically included when compiling. This file declares the CRLF constant for now.
-
Include files are now cached by the compiler. This should increase the compilation speed for projects that depend on large included files, such as the Win32APILibrary header file from Vulcan
-
When a function is found in an external assembly and a function with the same name and arguments is found in the current assembly, then the function in the current assembly is used by the compiler
-
Compiler error messages for missing closing symbols should have been improved
-
Compiler error messages for unexpected tokens have been improved
-
- Bug fixes
-
-
Several command-line options with a minus sign were not properly handled by the compiler
-
Fixed several crashes related to assigning NULL_OBJECT or NULL to late bound properties have been fixed
-
Partial class no longer are required to specify the parent type on every source code location. When specified, the parent type must be the same of course. Parent interfaces implemented by a class can also be spread over multiple locations
-
We have fixed a crash that could happen with errors/warnings in large include files
-
Abstract methods no longer get a Virtual Modifier with /vo3
-
Fixed a problem with virtual methods in child classes that would hide parent class methods
-
Automatic return value generation was also generating return values for ASSIGN methods. This has been fixed.
-
We fixed a problem with the Join Clauses for LINQ Expressions that would cause a compiler exception
-
The /vo10 (compatible iif) compiler option no longer adds casts in the Core dialect. It only does that for the VO/Vulcan dialect
-
- Visual Studio Integration
- We have changed the way the error list and output window are updated. In previous version some lines could be missing on the output window, and the error code column was empty. This should work as expected now.
-
-
We have merged some code from some other MPF based project systems, such as WIX (called Votive), NodeJS and Python (PTVS) to help extend our project system. As a result:
-
-
Our project system now has support for Linked files
-
Our project system now has support for 'Show All Files' and you can now Include and Exclude files. This setting is persisted in a .user file, so you can exclude this from SCC if you want.
-
We have made some changes to support better 'Drag and Drop'
-
-
-
-
We have fixed several issues with regard to dependent items
-
When you include a file that contains a form or user control, this is now recognized and the appropriate subtype is set in the project file, so you can open the windows forms editor
-
We are now supporting source code generation for code behind files for .Settings and .Resx files
-
The combobox in the Managed Resource editor and Managed Settings tool to choose between internal code and public code is now enabled. Selecting a different value in the combobox will change the tool in the files properties.
-
The last response file for the compiler and native resource compiler are now saved in the users Temp folder to aid in debugging problems.
-
-
-
The response file now has each compiler option to a new line to make it easier to read and debug when this is necessary.
-
The code generation now preserves comments between entities (methods)
-
We fixed several minor issues in the templates
-
When the # of errors and warnings is larger than the built-in limit of 500, then a message will be shown that the error list was truncated
-
At the end of the build process a line will be written to the output window with the total # of warnings and errors found
-
The colors in the Source Code Editor are now shared with the source code editors for standard languages such as C# and VB
-
When you have an inactive code section in your source code, embedded in an #ifdef that evaluates to FALSE then that section will be visibly colored gray and there will be no keyword highlighting. The source code parser for the editor picks up the include files and respects the path settings. Defines in the application properties dialog and the active configuration are not respected yet. That will follow in the next build.
-
-
-
- Changes in 0.2.7.1
- Compiler
-
-
The compiler was not accepting wildcard strings for the AssemblyFileVersion Attribute and the AssemblyInformationVersion attribute. This has been fixed
-
The #Pragma commands #Pragma Warnings(Push) and #Pragma Warnings(Pop) were not recognized. This has been fixed.
-
The compiler was not recognizing expressions like global::System.String.Compare(..). This has been fixed
-
- Visual Studio Integration
-
-
Dependent items in subfolders of a project were not recognized properly and could produce an error when opening a project
-
Fixed a problem in the VulcanApp Template
-
The Windows Forms Editor would not open forms in a file without begin namespace .. end namespace. This has been fixed
-
Source code comments between 'entities' in a source file is now properly saved and restored when the source is regenerated by the form editor
-
Unnecessary blank lines in the generate source code are being suppressed
-
The XPorter tool is now part of the Installation
-
Comments after a line continuation character were not properly colored
-
Changed the XSharp VS Editor Color scheme to make certain items easier to read
-
New managed resource files would not be marked with the proper item type. As a result the resources would not be available at runtime. This has been fixed.
-
Added 'Copy to Output Directory' property to the properties window
-
- Setup
-
-
The installer, exe files and documentation are now signed with a certificate
-
-
-
- Changes in 0.2.7
- Compiler
- New features:
-
-
Added support for the VOSTRUCT and UNION types
-
Added support for Types as Numeric values, such as in the construct IF UsualType(uValue) == LONG
-
Added a FIXED statement and FIXED modifier for variables
-
Added support for Interpolated Strings
-
Empty switch labels inside SWITCH statements are now allowed. They can share the implementation with the next label. Error 9024 (EXIT inside SWITCH statement not allowed) has been added and will be thrown if you try to exit out of a loop around the switch statement. This is not allowed.
-
Added support for several /vo compiler options: - vo8 (Compatible preprocessor behavior). This makes the preprocessor defines case insensitive. Also a define with the value FALSE or 0 is seen as 'undefined' - vo9 (Allow missing return statements) compiler option. Missing return values are also allowed when /vo9 is used. Warnings 9025 (Missing RETURN statement) and 9026 (Missing RETURN value) have been added. - vo12 (Clipper Integer divisions)
-
The preprocessor now automatically defines the macros __VO1__ until __VO15__ with a value of TRUE or FALSE depending on the setting of the compiler option
-
The FOX version of the compiler is now distributed in Release mode and much faster. A debug version of the compiler is also installed in case it is needed to aid in finding compiler problems.
-
- Changed behavior
-
-
The compiler generated Globals class for the Core dialect is now called Functions and no longer Xs$Globals.
-
Overriding functions in VulcanRTFuncs can now be done without specifying the namespace: When the compiler finds two candidate functions and one of them is inside VulcanRTFuncs then the function that is not in VulcanRTFuncs is chosen.
-
Warning 9001 (unsafe modifier implied) is now suppressed for the VO/Vulcan dialect. You MUST pass the /unsafe compiler option if you are compiling unsafe code though!
-
Improved the error messages for the Release mode of the compiler
-
- Bug fixes
-
-
RETURN and THROW statements inside a Switch statement would generate an 'unreachable code' warning. This has been fixed
-
Fixed several problems with mixing signed and unsigned Array Indexes
-
Fixed several problems with the FOR .. NEXT statement. The "To" expression will now be evaluated for every iteration of the loop, just like in VO and Vulcan.
-
Fixed several compiler crashes
-
Fixed a problem with implicit code generation for constructors
-
Fixed a visibility problem with static variables inside static functions
-
- Visual Studio Integration
-
-
Fixed a problem that the wrong Language Service was selected when XSharp and Vulcan.NET were used in the same Visual Studio and when files were opened from the output window or the Find Results window
-
Fixed some problems with 'abnormal' line endings in generated code
-
Fixed a problem in the Class Library template
-
Fixed a problem with non standard command lines to Start the debugger
-
-
- Changes in 0.2.6
- Compiler
-
-
Added alternative syntax for event definition. See EVENT keyword in the documentation
Added support for /vo4 (VO compatible implicit numeric conversions)
-
Aliased expressions are now fully supported
-
Fixed a problem with the &= operator
-
Fixed several crashes for incorrect source code.
-
Fixed several problems related to implicit conversions from/to usual, float and date
-
Indexed properties (such as String:Chars) can now be used by name
-
Indexed properties can now have overloads with different parameter types
-
Added support for indexed ACCESS and ASSIGN
-
Fixed a problem when calling Clipper Calling Convention functions and/or methods with a single parameter
-
Fixed a crash with defines in the preprocessor
-
_CODEBLOCK is now an alias for the CODEBLOCK type
-
Fixed a crash for properties defined with parentheses or square brackets, but without actual parameters
-
- Visual Studio Integration
-
-
Completed support for .designer.prg for Windows.Forms
-
Fixed an issue in the CodeDom generator for generating wrappers for Services
-
The XSharp Language service will no longer be used for Vulcan PRG files in a Side by Side installation
-
Editor performance for large source files has been improved.
-
All generated files are now stored in UTF, to make sure that special characters are stored correctly. If you are seeing warnings about code page conversions when generating code, then save files as UTF by choosing "File - Advanced Save Options", and select a Unicode file format, from the Visual Studio Menu.
-
-
- Changes in 0.2.51
- Visual Studio Integration & Build System
-
-
The Native Resource compiler now "finds" header files, such as "VOWin32APILibrary.vh" in the Vulcan.NET include folder. Also the output of the resource compiler is now less verbose when running in "normal" message mode. When running in "detailed" or "diagnostics" mode the output now also includes the verbose output of the resource compiler.
-
- Compiler
-
-
Fixed a problem that would make PDB files unusable
-
The error "Duplicate define with different value" (9012) has been changed to warning, because our preprocessor does a textual comparison and does not "see" that "10" and "(10)" are equal as well as "0xA" and "0xa". It is your responsibility of course to make sure that the values are indeed the same.
-
Exponential REAL constants were only working with a lower case 'e'. This is now case insensitive
-
Made several changes to the _DLL FUNCTION and _DLL PROCEDURE rules for the parser. Now we correctly recognize the "DLL Hints " (#123) and also allow extensions in these definitions. Ordinals are parsed correctly as well, but produce an error (9018) because the .Net runtime does not support these anymore. Also the Calling convention is now mandatory and the generated IL code includes SetLastError = true and ExactSpelling = true.
-
Fixed a problem with the ~ operator. VO and Vulcan (and therefore X#) use this operator as unary operator and as binary operator. The unary operator does a bitwise negation (Ones complement), and the binary operator does an XOR. This is different than C# where the ~ operator is Bitwise Negation and the ^ operator is an XOR (and our Roslyn backend uses the C# syntax of course).
-
-
- Changes in 0.2.5
- Visual Studio Integration
-
-
Fixed a problem where the output file name would contain a pipe symbol when building for WPF
-
Fixed a problem with the Item type for WPF forms, pages and user controls
-
The installer now has an option to not take away the association for PRG, VH and PPO items from an installed Vulcan project system.
-
Added support for several new item types in the projects
-
Added support for nested items
-
Added several item templates for WPF, RC, ResX, Settings, Bitmap, Cursor etc.
-
- Build System
-
-
Added support for the new /vo15 command line switch.
-
Added support for compiling native resources.
-
- Compiler
-
-
A reference to VulcanRT and VulcanRTFuncs is now mandatory when compiling in VO/Vulcan dialect
-
Added support for indexed access for VO/Vulcan Arrays
-
Added support for VO/Vulcan style Constructor chaining (where SUPER() or SELF() call is not the first call inside the constructor body)
-
Added support for the &() macro operator in the VO/Vulcan dialect
-
Added support for the FIELD statement in the VO/Vulcan dialect
-
-
-
-
The statement is recognized by the compiler
-
Fields listed in the FIELD statement now take precedence over local variables or instance variables with the same name
-
-
-
-
Added support for the ALIAS operator (->) in the VO/Vulcan dialect, with the exception of the aliased expressions (AREA->(<Expression>))
-
Added support for Late bound code (in the VO/Vulcan dialect)
-
-
-
-
Late bound method calls
-
Late bound property get
-
Late bound property set
-
Late bound delegate invocation
-
-
-
-
Added a new /vo15 command line option (Allow untyped Locals and return types): By default in the VO/Vulcan dialect missing types are allowed and replaced with the USUAL type. When you specify /vo15- then untyped locals and return types are not allowed and you must specify them. Of course you can also specify them as USUAL
-
-
-
The ? and ?? statement are now directly mapped to the appropriate VO/Vulcan runtime function when compiling for the VO/Vulcan dialect
-
We now also support the VulcanClassLibrary attribute and VulcanCompilerVersion attribute for the VO & Vulcan dialect. With this support the Vulcan macro compiler and Vulcan Runtime should be able to find our functions and classes
-
The generated static class name is now more in par with the class name that Vulcan generates in the VO & Vulcan dialect.
-
Added several implicit conversion operations for the USUAL type.
-
When accessing certain features in the VO & Vulcan dialect (such as the USUAL type) the compiler now checks to see if VulcanRTFuncs.DLL and/or VulcanRT.DLL are included. When not then a meaningful error message is shown.
-
Added support for the intrinsic function _GetInst()
-
Fixed a problem with case sensitive namespace comparisons
-
Fixed a problem with operator methods
-
-
-
Added preprocessor macros __DIALECT__, __DIALECT_CORE__, __DIALECT_VO__ and __DIALECT_VULCAN__
-
The _Chr() pseudo function will now be mapped to the Chr() function
-
-
-
Added support for missing arguments in arguments lists (VO & Vulcan dialect only)
-
Fixed a crash when calculating the position of tokens in header files
-
The installer now offers to copy the Vulcan Header files to the XSharp Include folder
-
Added support for skipping arguments in (VO) literal array constructors
-
- Documentation
-
-
Added the XSharp documentation to the Visual Studio Help collection
-
Added reference documentation for the Vulcan Runtime
-
-
- Changes in 0.2.4
- Visual Studio Integration
-
-
Double clicking errors in the error browser now correctly opens the source file and positions the cursor
-
Fixed several problems in the project and item templates
-
The installer now also detects Visual Studio 15 Preview and installs our project system in this environment.
-
- Build System
-
-
Fixed a problem with the /unsafe compiler option
-
Fixed a problem with the /doc compiler option
-
Treat warnings as error was always enabled. This has been fixed.
-
- Compiler
-
-
Added support for Lambda expressions with an expression list
-
- LOCAL dfunc AS System.Func<Double,Double>
- dfunc := {|x| x := x +10, x^2}
- ? dfunc(2)
-
-
Added support for Lambda expressions with a statement list
-
- LOCAL dfunc AS System.Func<Double,Double>
- dfunc :={|x|
- ?'square of', x
- RETURN x^2
- }
-
-
Added support for the NAMEOF intrinsic function
-
- FUNCTION Test(cFirstName AS STRING) AS VOID
- FUNCTION Test(cFirstName ASSTRING) ASVOID
- IF String.IsNullOrEmpty(cFirstName)
- THROW ArgumentException{"Empty argument", nameof(cFirstName)}
- ENDIF
-
-
Added support for creating methods and functions with Clipper calling convention (VO and Vulcan dialect only)
-
Using Statement now can contain a Variable declaration:
-
- Instead of:
- VAR ms := System.IO.MemoryStream{}
- BEGINUSING ms
- // do the work
-
- ENDUSING
- You can now write
- BEGINUSINGVAR ms := System.IO.MemoryStream{}
- // do the work
- ENDUSING
-
-
Added support for /vo10 (Compatible IIF behavior). In the VO and Vulcan dialect the expressions are cast to USUAL. In the core dialect the expressions are cast to OBJECT.
-
- New language features for the VO and Vulcan dialect
-
-
Calling the SELF() or SUPER() constructor is now allowed anywhere inside a constructor (VO and Vulcan dialect only). The Core dialect still requires constructor chaining as the first expression inside the constructor body
-
Added support for the PCOUNT, _GETFPARAM and _GETMPARAM intrinsic functions
-
Added support for String2Psz() and Cast2Psz()
-
Added support for BEGIN SEQUENCE … END
-
Added support for BREAK
-
- Fixed several problems:
-
-
Nested array initializers
-
Crash for BREAK statements
-
Assertion error for generic arguments
-
Assertion on const implicit reference
-
Allow ClipperCallingConvention Attribute on Constructors, even when it is marked as ‘for methods only’
-
-
- Changes in 0.2.3
- Visual Studio Integration
-
-
We have changed to use the MPF style of Visual Studio Integration.
-
We have added support for the Windows Forms Editor
-
We have added support for the WPF Editor
-
We have added support for the Codedom Provider, which means a parser and code generator that are used by the two editors above
-
The project property pages have been elaborated. Many more features are available now.
-
We have added several templates
-
- Build System
-
-
Added support for several new commandline options, such as /dialect
-
The commandline options were not reset properly when running the shared compiler. This has been fixed.
-
-
-
The build system will limit the # of errors passed to Visual Studio to max. 500 per project. The commandline compiler will still show all errors.
-
- Compiler
-
-
We have started work on the Bring Your Own Runtime support for Vulcan. See separate heading below.
-
The __SIG__ and __ENTITY__ macros are now also supported, as well as the __WINDIR__, __SYSDIR__ and __WINDRIVE__ macros
-
The debugger instructions have been improved. You should have a much better debugging experience with this build
-
Several errors that indicated that there are visibility differences between types and method arguments, return types or property types have been changed into warnings. Of course you should consider to fix these problems in your code.
-
The #Error and #warning preprocessor command no longer require the argument to be a string
-
The SLen() function call is now inlined by the compiler (just like in Vulcan)
-
The AltD() function will insert a call to "System.Diagnostics.Debugger.Break" within a IF System.Diagnostics.Debugger.IsAttached check
-
Several compiler crashes have been fixed
-
Added support for the PARAMS keyword for method and function parameters.
-
Fixed a problem for the DYNAMIC type.
-
- BYOR
-
-
XBase type names are resolved properly (ARRAY, DATE, SYMBOL, USUAL etc)
-
Literal values are now resolved properly (ARRAY, DATE, SYMBOL)
-
NULL_ literals are resolved properly (NULL_STRING follows the /vo2 compiler option, NULL_DATE, NULL_SYMBOL)
-
The /vo14 compiler option (Float literals) has been implemented
-
The compiler automatically inserts a "Using Vulcan" and "using static VulcanRtFuncs.Functions" in each program
-
You MUST add a reference to the VulcanRTFuncs and VulcanRT assembly to your project. This may be a Vulcan 3 and also a Vulcan 4 version of the Runtime. Maybe Vulcan 2 works as well, we have not tested it.
-
Calling methods with Clipper calling convention works as expected.
-
Methods/Functions without return type are seen as methods that return a USUAL
-
If a method/function contains typed and typed parameters then the untyped parameters are seen as USUAL parameters
-
Methods with only untyped parameters (Clipper calling convention) are not supported yet
-
The ? command will call AsString() on the arguments
-
-
- Changes in 0.2.2
- Visual Studio Integration
-
-
Added more project properties. One new property is the "Use Shared Compiler" option. This will improve compilation speed, but may have a side effect that some compiler (parser) errors are not shown in details. If you experience this, then please disable this option.
-
Added more properties to the Build System. All C# properties should now also be supported for X#, even though some of them are not visible in the property dialogs inside VS.
-
Added a CreateManifest task to the Build System so you will not get an error anymore for projects that contain managed resources
-
The performance of the editor should be better with this release.
-
Marking and unmarking text blocks as comment would not always be reflected in the editor colors. This has been fixed.
-
- Compiler
-
-
We have added a first version of the preprocessor. This preprocessor supports the #define command, #ifdef, #ifndef, #else, #endif, #include, #error and #warning. #command and #translate (to add user defined commands) are not supported yet.
-
Missing types (in parameter lists, field definitions etc) were sometimes producing unclear error messages. We have changed the compiler to produce a "Missing Type" error message.
-
We rolled the underlying Roslyn code forward to VS 2015 Update 1. Not that you see much of this from the outside <g>, but several fixes and enhancements have made their way into the compiler.
-
Added a YIELD EXIT statement (You can also use YIELD BREAK).
-
Added an (optional) OVERRIDE keyword which can be used as modifier on virtual methods which are overridden in a subclass.
-
Added a NOP keywordwhich you can use in code which is intentionally empty (for example the otherwise branch of a case statement. The compiler will no longer warn about an empty block when you insert a NOP keyword there.
-
The On and Off keywords could cause problems, because they were not positional (these are part of the pragma statement). This has been fixed.
-
_AND() and _OR() expressions with one argument now throw a compiler error.
-
The compiler now recognizes the /VO14 (store literals as float) compiler switch (it has not been implemented yet).
-
Added a ** operator as alias for the ^ (Exponent) operator.
-
Added an "unsupported" error when using the Minus operator on strings.
-
Fixed a "Stack overflow" error in the compiler that could occur for very long expressions.
-
The right shift operator no longer conflicts with two Greater Than operators, which allows you to declare or create generics without having to put a space between them. (var x := List<Tuple<int,int>>{}
-
-
- Changes in 0.2.1
- Visual Studio Integration
-
-
Added and improved several project properties
-
Fix a problem with the "Additional Compiler Options"
-
Improved coloring in the editor for Keywords, Comments etc. You can set the colors from the Tools/Options dialog under General/Fonts & Colors. Look for the entries with the name "XSharp Keyword" etc.
-
Added Windows Forms Template
-
- Compiler
-
-
Several errors have been demoted to warnings to be more compatible with VO/Vulcan
-
Added support for Comment lines that start with an asterisk
-
Added support for the DEFINE statement. For now the DEFINE statement MUST have a type DEFINE WM_USER := 0x0400 AS DWORD
-
Fixed problem with Single Line Properties with GET and SET reversed
-
Several fixes for Virtual and Non virtual methods in combination with the /VO3 compatibility option
-
-
- Changes in 0.1.7
-
-
The "ns" (add default namespace to classes without namespace) has been implemented
-
The "vo3" compiler option (to make all methods virtual ) has been implemented
-
Fixed an issue where the send operator on an expression between parentheses was not compiling properly
-
Relational operators for strings (>, >=, <, <=) are now supported. They are implemented using the String.Compare() method.
-
Fixed a problem with local variables declared on the start line from FOR .. NEXT statements
-
Added first version of the documentation in CHM & PDF format
-
Added several properties to the Visual Studio Project properties dialog to allow setting the new compiler options
-
Fixed a problem in the Targets files used by MsBuild because some standard macros such as $(TargetPath) were not working properly
-
XIDE 0.1.7 is included. This version of XIDE is completely compiled with XSharp !
-
The name of some of the MsBuild support files have changed. This may lead to problems loading a VS project if you have used the VS support from the previous build. If that is the case then please edit the xsproj file inside Visual Studio and replace all references of "XSharpProject" with "XSharp" . Then safe the xsproj file and try to reload the project again
-
The WHILE.. ENDDO (a DO WHILE without the leading DO) is now recognized properly
-
-
- Changes in 0.1.6
-
-
This version now comes with an installer
-
This version includes a first version of the Visual Studio Integration. You can edit, build, run and debug inside Visual Studio. There is no "intellisense" available.
-
The compiler now uses 1-based arrays and the “az” compiler option has been implemented to switch the compiler to use 0-based arrays.
-
The "vo2" compiler option (to initialize string variables with String.Empty) has been implemented
-
Please note that there is no option in the VS project properties dialog yet for the az and vo2 compiler options. You can use the "additional compiler options" option to specify these compiler options.
-
The text "this" and "base" in error messages has been changed to "SELF" and "SUPER"
-
Error of type “visibility” (for example public properties that expose private or internal types) have been changed to warnings
-
Fixed a problem with TRY … ENDTRY statements without CATCH clause
-
The compiler now has a better resolution for functions that reside in other (X#) assemblies
-
Fixed a problem which could lead to an "ambiguous operator" message when mixing different numeric types.
-
-
- Changes in 0.1.5
-
-
When an error occurs in the parsing stage, X# no longer enters the following stages of the compiler to prevent crashes. In addition to the errors from the parser also an error 9002 is displayed.
-
Parser errors now also include the source file name in the error message and have the same format as other error messages. Please note that we are not finished yet with handling these error messages. There will be improvements in the format of these error messages in the upcoming builds.
-
The compiler will display a “feature not available” (8022) error when a program uses one of the Xbase types (ARRAY, DATE, FLOAT, PSZ, SYMBOL, USUAL).
-
Fixed an error with VOSTRUCT and UNION types
-
Fixed a problem with the exclamation mark (!) NOT operator
-
-
- Changes in 0.1.4
-
-
Several changes to allow calculations with integers and enums
-
Several changes to allow VO compatible _OR, _AND, _NOT an _XOR operations
-
Fix interface/abstract VO properties
-
Insert an implicit “USING System” only if not explicitly declared
-
Error 542 turned to warning (members cannot have the same name as their enclosing type)
-
Changes in the .XOR. expression definition
-
Fix double quote in CHAR_CONST lexer rule
-
Allow namespace declaration in class/struct/etc. name (CLASS Foo.Bar)
-
Fix access/assign crash where identifier name was a (positional) keword: ACCESS Value
-
Preprocessor keywords were not recognized after spaces, but only at the start of the line. This has been fixed.
-
Prevent property GET SET from being parsed as expression body
-
Fix default visibility for interface event
-
Unsafe errors become warnings with /unsafe option, PTR is void*
-
Fix dim array field declaration
-
Initial support of VO cast and VO Conversion rules (TYPE(_CAST, Expression) and TYPE(Expression)). _CAST is always unchecked (LONG(_CAST, dwValue)) and convert follows the checked/unchecked rules (LONG(dwValue))
-
Fixed problem with codeblock with empty parameter list
-
Fixed problems with GlobalAttributes.
-
An AUTO property without GET SET now automatically adds a GET and SET block
Change inconsistent field accessibility error to warning and other similar errors
-
Added commandline support for Vulcan arguments. These arguments no longer result in an error message, but are not really implemented, unless an equivalent argument exists for the Roslyn (C#) compiler. For example: /ovf and /fovf are both mapped to /checked, /wx is mapped to /warnaserror. /w should not be used because that has a different meaning /warning level). /nowarn:nnnn should be used in stead
-
Fixed problem where the PUBLIC modifier was assigned to Interface Members or Destructors
-
Prevent expression statements from starting with CONSTRUCTOR() or DESTRUCTOR()
-
Added support for ? statement without parameters
-
The default return type for assigns is now VOID when not specified
-
Added support for “old Style” delegate instantiation
-
Added support for Enum addition
-
Added an implicit empty catch block for TRY .. END TRY without catch and finally
-
Added support for the DESCENDING keyword in LINQ statements
-
Added support for VIRTUAL and OVERRIDE for Properties and Events
-
Prevent implied override insertion for abstract interface members
-
Fixed a problem where System.Void could not be resolved
-
Fixed problem with Property Generation for ACCESS/ASSIGN
-
Fixed problem with Abstract method handling
-
-
- Changes in 0.1.2.1
-
-
Added default expression
-
Fixed problem with events
-
Fixed some small lexer problems
-
Fixed problem with _DLL FUNCTION and _DLL PROCEDURE
-
-
- Changes in 0.1.2
-
-
Fixed problem with handling escape sequences in extended strings
-
Fixed issue in FOR.. NEXT statements
-
Fixed a problem with SWITCH statements
-
Fixed a problem with the sizeof() operator
-
Fixed a problem in the REPEAT .. UNTIL statement
-
Fixed a problem in TRY .. CATCH .. FINALLY .. END TRY statements.
-
Fixed issue in Conditional Access Expression ( Expr ? Expr)
-
Allow bound member access of name with type args
-
Fixed problem in LOCAL statement with multiple locals
-
Fixed a problem when compiling with debug info for methods without a body
-
Optimized the Lexer. This should increase the compile speed a lot
-
Fixed a problem in the code that reports that a feature is not supported yet
-
Fixed a problem when defining Generic types with a STRUCTURE constraint
-
Compiler macros (__ENTITY__, __LINE__ etc) were causing a crash. For now the compiler inserts a literal string with the name of the macro.
-
Build 0.1.1 did not contain XSC.RSP
-
Fixed a problem where identifiers were not recognized when they were matching a (new) keyword
Documentation generation for VFP classes for members without visibility modifier was not working (#1664)
-
Fixed an issue with default parameter values, where the type of the default did not match the type of the parameter. For example using a LONG default value for a Decimal parameter (#1733)
-
- Build System Bug fixes
-
-
The WriteCodeFragment task now properly supports the _Parameter1, _Parameter2 etc parameters, just like the C# build system does.
-
- Runtime Bug fixes
-
-
Fixed an issue with late bound calls to overloaded methods (#1696)
-
Fixed problem with ambiguous call error on the GoMonth() function (VFP dialect) (#1724)
-
Fixed problem with the COPY TO command when using the VIA clause (#1726)
-
- Visual Studio integration Bug fixes
-
-
When a file was deleted from a project, then the file would not be deleted from the intellisense database. This has been fixed.
-
Goto definition no longer includes source from prg files with buildaction None (#1630)
-
Intellisense was not showing field in VFP classes for fields without visibility modifier (#1725)
-
The ToggleLineComment and ToggleBlockComment functions were not properly maintaining leading whitespace (#1728)
-
Fixed an issue with Code Generation for AssemblyCustomAttributes
-
Fixed a problem with the Debugger Expression Evaluator in VS 2017 and VS 2019
-
- New Features
-
-
Added context menu option to generate Windows Forms Form from an existing VO Form (#1366)
-
The code generator now automatically generates END CONSTRUCTOR, END METHOD etc.
-
- VOXporter
- New features
-
-
Add special tags "VXP-NOCHANGE", "{VOXP:NOCHANGE}" that instruct VOXporter to not modify at all the code from a module/prg file (#1723)
-
- XIDE
- General
-
-
Added View->Hide Side Panes (SHIFT+F4) option to quickly show/hide the left/right panes in the IDE
-
Enabled the Debug->View DB Workareas debug window
-
Fixed problem with new applications defaulting to CLR2 when no gallery template is used
-
Added folder button for "App to run" option in th application properties window
-
Added several "Tip of the day" items
-
Added Preferences/Highlight active file caption option
-
Added Preferences/Paint file captions per application option
-
Added keyboard shortcut information to the File->Navigate menu items
-
Added "Dock To Pane" options to tab page context menu of toolwindows
-
Added Detach/Attach to main IDE window context menu options for editor files
-
Added regular context menu options also for files in floating windows
-
Toolwindows can now be closed also with middle mouse button click
-
- Changes in 2.23.0.2
- Compiler
- New features
-
-
Added a compiler warning when assigning a constant "NIL" to a non-usual var (#1688)
-
- Bug fixes
-
-
Fixed a problem with XML documentation generation for class properties in the VFP dialect (#1664)
-
Fixed compiler crash with syntax errors in interpolated strings (#1672)
-
Fixed problems with static entities when an app has prg files with similar names (#1677)
-
Fixed conflict between same named access and field in a parent class (#1679)
-
Fixed problem with the star (*) comment line marker when used with a semi-colon (;) in the VFP dialect (#1685)
-
- Build System
-
-
Moved suppressed warnings from the DisabledWarnings property to NoWarn (#1697)
-
- Runtime
- New features
-
-
Added additional sort functions ASortFunc() and ASortEx() for arrays allowing .Net style sorting (#1683)
-
Added untyped overloads for VFP functions GoMonth(), Quarter(), Week(), DMY() and MDY() (#1724)
-
Implemented the Seek() function in the VFP runtime library (#1718)
-
Allow to register special error handler that is called for errors during macro compilation (#1686) To use this, declare a function or method with the following prototype:
DELEGATE CodeblockErrorHandler(cMacro asSTRING, oException as Exception) AS ICodeBlock
-
- And register it as the codeblock error handler like this: RuntimeState.CodeBlockErrorHandler := CodeBlockErrorHandler When the function / method returns NULL then an exception is thrown. When the function/ error handler returns a Codeblock then this codeblock is used to evaluate the macro. For example:
FUNCTION CodeBlockErrorHandler(cMacro ASSTRING, oEx AS Exception) AS ICodeblock ? Mmacro ? oEx:Message // Visual Objects returns NIL when an error like this happens RETURN {|| NIL }
FUNCTION Start() ASVOIDSTRICT RuntimeState.MacroCompilerErrorHandler := CodeBlockErrorHandler ? &("'aaa'bbb'") // uneven # of single quotes, an error. // Returns NIL because the ErrorHandler returns a codeblock with NIL
- Bug fixes
-
-
Fixed problem with COPY TO ARRAY / DbCopyToArray() with fields of type "G" (#1530)
-
Fixed problem with ASort() returning inconsistent results when using the .Net Framework 4.5 sorting routines (#1653)
-
Fixed problem with Integer() function depending on the SetFloatDelta() setting (#1676)
-
Fixed several problems with default method parameters in late bound calls (#1684)
-
Fixed problem with IVarGetInfo() with overrided ASSIGN methods with different casing (#1692)
-
Fixed problem with ENUM parameters in alte bound calls (#1696)
-
Fixed (handled) exception inside FindMethod() in late bound code with similar named method and assign (#1702)
-
Fixed problem with ProcName(x) returning incorrect results (#1704)
-
Fixed problem with calling class access method through object instance in the XBase++ dialect (#1705)
-
Fixed problem with File() function not finding files after changing the current directory with DirChange() (#1706)
-
Fixed several compatibility issues with the Directory() function (#1707 and #1708)
-
- Macro compiler
-
-
Integer divisions in macros now return a float result instead of INT (#1641)
-
Allowed the macro compiler to access protected and private members in the FoxPro dialect (#1662)
-
Fixed macro compiler problem with IN parameters (#1675)
-
Fixed various problems with scripting and ExecScript() (#1646, #1682)
-
Fixed problem with failing to find overload with explicit cast to interface (#1720)
-
- RDD System
-
-
Fixed problem with opening dbf files with no extension (#1671)
-
Fixed problem with DbServer:OrderScope() always returning NIL without a new value and setting the scope to NIL (#1694)
-
- Typed VO SDK
-
-
Fixed problem with MouseMove( oMev) not being called for a FixedText (#1680)
-
Added a property EnableDispatch to the Window class. When set to TRUE then the Dispatch() method is called. (#1721)
-
- Visual Studio integration
- Bug fixes
-
-
Fixed editor problem with incorrectly displaying region markers for multiline statements with comments (#1667)
-
Fixed incorrect code highlight of the "is not null" code pattern (#1699)
-
- New Features
-
-
Added support for the editor commands Edit.ToggleLineComment and Edit.ToggleBlockComment
-
- XIDE
- General
-
-
Added toolbar button to collapse all nodes in the Project window
-
Added support for selecting the editor color for escaped literals in the Preferences window and through the plugin system
-
Added context menu option to copy all contents/only code in the Find results window
-
The control order window now support moving items (tab order) with the keyboard, by using CTRL or SHIFT + Up/Down
-
Fixed a problem with incorrectly highlighting Func<T> as a keyword
-
Project/application export now includes also native resource files (.rc)
-
Some improvements to the TipOfTheDay window
-
Messages in the Errors tool window can now be sorted by file, application etc., by clicking on their respective column header
-
Improved functionality of the Remove/Remove All toolbar button in the Breakpoints, Bookmarks and Watch tool windows
-
Fixed modifying values of local variables in the debugger (still can't modify object members though)
-
A lot of improvements to the Edit->Sort Entities command
-
- Plugin System
-
-
Added callback method Plugin:OnProjectItemSelected() that gets called when any item is selected in the Project tool window
-
Added method PluginService:GetPropertiesPad() AS PropertiesPad for retrieving the Properties tool window
-
Added support for handling (through PluginService:GetSelectedProjectItem()) many more item types in the Project tool window: ReferenceGroup, Reference, Resource files etc
-
Fixed a problem (crash) with manipulating hidden editor files
-
- Documentation
- Bug fixes
-
-
Fixed documentation problems for the topics CONSTRUCTOR, DESTRUCTOR, ENUM, EVENT, FUNCTION, METHOD OPERATOR, PROPERTY, STRUCTURE (#1655)
Fixed problem with incorrect error line for unknown var in RECOVER USING statement (#1567)
-
Fixed a compiler crash with default values in parameters (#1647)
-
Fixed problem with text in the VOWED ToolBox window appearing mangled when font scaling is used in the OS (#1650)
-
Fixed error when adding COM references to a project (#1654)
-
- Build System
-
-
Some project files that were converted from Vulcan could cause problems locating errors from the error list. This has been fixed: the property GenerateFullPaths is now always set to TRUE when building inside Visual Studio.
-
The files LastXSharpResponseFile.Rsp and LastXSharpNativeResourceResponseFile are now always created in the temp folder, and not in the MSBuildTemp subfolder in the temp folder.
-
- Runtime
- Bug fixes
-
-
ExecScript() now calls the scripting code in the new macro compiler (#1646)
-
- New features
-
-
Marked SetCPU() and SetMath() as obsolete
-
Bin2Ptr() and Ptr2Bin() now also work in X64 mode. The strings returned or expected are 8 characters long.
-
- RDD System
-
-
Fixed problem with DbOrderInfo() returning wrong key count when using a bottom scope higher that the highest index value (#1652)
-
- VOSDK
-
-
Fixed problem with DataDialog:ToolBar returning always NULL, even if a toolbar object is assigned (#1660)
-
- VOXporter
- New features
-
-
Now binaries and support files for visual editors are being generated also when importing from .mef (#1661)
-
- Visual Studio integration
- Bug fixes
-
-
Fixed IntelliSense problem with user extensions methods (#1421)
-
Fixed problem in Format Document with DEFINEs (#1642)
-
Fixed problem with reading Assembly info when assembly does not exist (#1645)
-
Fixed problem in the VFP Class project template with the DEFINE CLASS syntax (#1648)
-
Fix for issue with the font size on the toolbox for the Window Editor (#1650)
-
Fix for issue adding a COM reference to a project (#1654)
-
- XIDE
- General
-
-
Implemented "Tip of the Day" feature
-
Increased the time Project window searcher tip appears visible from 2 to 5 seconds
-
Added functionality in the Project window to repeat last search with F3
-
Added vertical scrollbar to the Locals details edit box
-
- Editor
-
-
Fixed problem with recognizing some positional keywords like CONSTRUCTOR
-
Fixed intellisense problems with X# specific data types (USUAL, FLOAT, DATE etc)
-
Fixed intellisense problem reading functions from X# assemblies with special characters in their names
-
- Designers
-
-
Fixed a problem with unlocking controls in the Forms designer
-
- Plugin System
-
-
Added method ProjectItemBase:SelectNodeInProjectPad() (applies to all project item types)
-
Added properties Editor:LineHeight, Editor:LineCount and Editor:FirstVisibleLine
-
Added methods PluginService:GetEditorColor(eColor AS EditorColor) and PluginService:SetEditorColor(eColor AS EditorColor, oColor AS Color)
-
- Documentation
- Bug fixes
-
-
The [View Source] link was pointing to a feature branch on Github. It now points to the main branch.
-
Updated the help topic about Interpolated strings.
-
- Changes in 2.21.0.5
- Possibly breaking changes in 2.21.0.5
- All dialects
- Until now, the compiler had several built-in defaults for command line options based on the dialect.
- That meant that when a command line option was NOT present and a certain dialect was chosen, then that option would be automatically enabled. We are talking about the following options:
-
-
-
-
- Dialect
-
-
- Option
-
-
-
-
- Core
-
-
- AllowNamedArgs
-
-
-
-
- Core
-
-
- AllowDot
-
-
-
-
- FoxPro
-
-
- AllowDot
-
-
-
-
- FoxPro
-
-
- AllowOldStyleAssignments
-
-
-
-
- FoxPro
-
-
- Vo9
-
-
-
-
- FoxPro
-
-
- Vo15
-
-
-
-
- FoxPro
-
-
- InitLocals
-
-
-
-
- Other
-
-
- Vo15
-
-
-
-
- This was confusing for some of you (and also for us). For example, you would have to explicitly add the command line option /initlocals- when compiling in the FoxPro dialect if you wanted to disable the option.
-
- On top of that, the MsBuild system also did not pass command line arguments to the compiler, if a certain property that matched that compiler option was not present in the project file. So, if the project file did not contain the <AllowDot> node, then the command line option /allowdot would be enabled if the project was compiled in the Core dialect, but disabled when the project was compiled in the VO or Xbase++ dialect. Very confusing!
-
- To fix this, we have done the following
-
-
The defaults are removed from the compiler.
-
The Build system will generate command line options with a '-' flag for options that are not defined in the project file. This will happen for X# specific commandline options only. Compiler options that we have "inherited" from Roslyn, such as /debug, /optimize etc. will remain working like before.
-
When opening a project file inside Visual Studio, we will check for the dialect and the options that are listed above. If an option is missing from the projectfile then we will add that option with the value "true". We will also remove options that are not relevant to the dialect. For example: for the core dialect, the foxpro and xpp specific settings will be removed.
-
-
- This should normally result in the same compilation as before. The only difference that you may see is that project files are automatically updated when you open them with this build.
- FoxPro dialect
- Until now the DEFINE CLASS syntax could be used to create classes that inherit from the FoxPro Compatible Custom class, but also from other .Net classes. That has proven to be a bit complicated.
- There also was a /fox1 compiler option that makes the AS ParentClass clause from the DEFINE CLASS command optional. Classes without AS ParentClass will then automatically inherit from Custom.
-
- We have made the following changes:
-
-
The AS BaseType clause will be mandatory like in Visual FoxPro
-
The ParentType must be Custom, or a class derived from Custom.
-
The /fox1 compiler is now obsolete
-
-
- If you want to inherit from a class outside the VFP class hierarchy (a standard .Net class) then you will have to use the CLASS ... END CLASS syntax.
- Compiler
- Bug fixes
-
-
Fixed Internal Compiler Error with duplicate declaration of fields/memvars (#1475)
-
Fixed a bogus warning when calling a function with in VFP dialect with /fox2 enabled (#1476)
-
Fixed problem with Min/Max IEnumerable extension methods of FLOAT type (#1482)
-
Fixed a StackOverflowException on access/assign method in the XBase++ dialect (#1483)
-
Fixed problem reading clipper/harbour .prg files with end of file marker (#1485)
-
Fixed problem with the extended expression match marker in the preprocessor (#1487)
-
Fixed problem passing array reference or ivar by reference in the XBase++ dialect (#1492)
-
Fixed AmbiguousMatchException in Evaluate() function for methods included in an interface (#1494)
-
Fixed problem with /fox1 switch being ignored in some cases (#1496)
-
The Build System now automatically adds a TargetFramework Attribute to assemblies compiled with X# (#1507)
-
Fixed an ambiguity problem with identical names in namespace and property, and several issues encountered when the /allowdot option is disabled (#1515)
-
Fixed problem in TEXT TO/ENDTEXT with TEXTMERGE clause (#1517)
-
Fixed misleading line number reported in the compiler error about requiring the /memvar option (#1531)
-
Fixed some issues with defining indexed properties (#1543)
-
Fixed several issues with the /vo9 (handle missing RETURN statements and return values) compiler option (#1544)
-
Fixed parser problem with END DEFINE, END PROCEDURE and END FUNCTION in the VFP dialect (#1564)
-
Fixed problem with using attributes in CLASS Statement in the FoxPro dialect (#1566)
-
Fixed macro compiler problem with compiling strongly typed codeblocks (#1591)
-
Fixed problem with Attributes being ignored for properties defined with the DEFINE CLASS syntax in the VFP dialect (#1612)
-
The compiler could crash when building a solution that has a .editorconfig file
-
Fixed an issue with generating the property output for attributes on Members inside a FoxPro style class definition
-
Fixed typo in error message about defining a class without an AS clause in the VFP dialect (#1611)
-
Added support for generic types without type parameters, like in typeof(List< >) and typeof(Dictionary<,>) (#1623)
-
Changes to the FoxPro compatible DEFINE CLASS (see above)
-
Changes to the way how missing commandline arguments are handled (see above)
-
We have added the double colon (::) separator for interpolated strings to separate the expression from the format specifier. C# uses the single colon (:) but that character is also used as member access operator in X#.See the String Literals topic for more information.
-
- Build System
-
-
We have fixed an issue in the build system that would sometimes lead to a recompilation, even when nothing was changed.
-
-
-
Fixed an issue where the language in the machine.config did not match the language defines in the built system
-
Fixed a problem that caused the .xml doc files to be written to the wrong folder
-
Changes on how missing project file properties are translated to command line arguments (see above)
-
- Runtime
- Bug fixes
-
-
Fixed some DBSetFilter() incompatibilities with VO (#1489)
-
Fixed problem with DBSetFilter() with no matching records causing subsequent calls to DBSetFilter() or DBClearFilter() to fail (#1493)
-
Fixed problem (missing implementation) with the WITH CDX clause in the FoxPro COPY command (#1497)
-
Fixed problem with SCATTER/GATHER MEMO MEMVAR (#1510, #1534)
-
Fixed a problem with the Collection class not increasing the Count property when adding an item (FoxPro dialect) (#1528)
-
Fixed problem with the APPEND FROM command with a FOR clause (#1529)
-
Fixed macro compiler problem with using Str() in the FoxPro dialect (which was causing problems in the INDEX ON command) (#1535)
-
Fixed a macro compiler problem with some language keywords (like REF, FIELD, DEFAULT) used as identifiers (#1557)
-
Fixed problems with the REPLACE, DELETE and UPDATE commands in the VFP dialect (#1574, #1575, #1576, #1577)
-
Fixed an issue in the USUAL type where CompareTo for Float values was not correctly implemented (#1616)
-
Fixed an issue in the USUAL type where the ! operator was not producing the correct results compared with the (LOGIC) cast.
-
We have fixed several issues in the XSharp.VFP.UI library
-
- RDD System
-
-
Fixed a problem in DbZap() with DBFNTX (#1509)
-
Fixed problem with DBSetOrder(0) always returning FALSE in DBFNTX (#1520)
-
Suppressed runtime error when using FieldPut() when workarea is at EOF, for compatibility with VO (#1542)
-
Fixed problem in OrderDescend() with the AXDBFCDX driver (#1608)
-
Fixed problems with reading variable-length fields in DBF files stored using MultiByte encoding.
-
Fixed a problem where DBFs encoded with Simplified Chinese were interpreted as Cantonese.
-
Fixed an issue in the DBF RDD where the currentbuffer was not reloaded after a record or file lock was acquired.
-
We have fixed an issue with DBF files larger than 2 Gb (0x7FFFFFFF bytes)
-
Creating UNIQUE indexes in the DBFCDX driver would exclude the first record from the DBF file
-
- VOSDK
-
-
Fixed typo in Window:__CommandFromEvent that was causing commands from SEUIXP to throw a runtime error.
-
- Visual Studio integration
- Bug fixes
-
-
Fixed problem with saving/reading the OldStyleAssignment compiler option project setting (#1495, #1582)
-
Fixed an issue in VS2022 where several features in the editor were no longer working due to a change in VS (#1545)
-
Fixed editor indentation problem with SCAN...END SCAN (#1549)
-
Fixed a problem with putting the .resx file for windows forms user controls in an incorrect location in the Solution Explorer (#1560)
-
Fixed problem with editor snippets no longer working in VS 2022 version 17.11 (#1564)
-
Fixed problem with the parameter list auto-showing tooltip when using <Enter> to accept a method from the member completion list (#1570)
-
Fixed a problem with indenting lines with end keywords, such as NEXT and ENDDO, when these keywords were following by 'garbage'.
-
Opening a form in the VS Form designer could fail when one of the include files declared entities, such as USING SomeNameSpace (#1595, #1596)
-
Fixed an issue in the debugger where identifiers that start with a '$' character, such as "$exception" in the exception dialog were not properly evaluated (#1602)
-
Fixed a problem with the indentation of VFP Style classes declared with DEFINE CLASS ... ENDDEFINE (#1609)
-
- New features
-
-
The TargetFramework attribute is now automatically added to the assembly when building any project type in VS. (#1507)
-
Added support for the GotoBrace command.This works for normal braces, but also for keyword pairs such as IF .. ENDIF. (#1522)
-
The editor now has a combobox on the top left that shows the project in which the file is defined.
-
When a file is present in multiple projects (as Linked file), the project's combobox will show the names of all projects that use the file.
-
When selecting a different project from this combobox, the buffer will be repainted, because conditional compilation symbols may differ for each of the projects.
-
When you use intellisense in the editor, the lookup engine will use the project selected. So, if a file is used in 2 projects, the references and source files of the selected project will be used to find reference data.
-
Added support for correct indentation with FoxPro variations of closing keywords, such as ENDFOR and ENDWITH.
-
We have moved several X# language related features from the Project System to the Language Service to prepare for the new Project System for SDK projects.
-
We have added support for Snippets in the CompletionLists at "file" level.
-
We no longer create an X# intellisense database for solutions that do not have any X# projects.
-
We have made several changes to the X# intellisense database structure. When you open a solution with an existing database, the database will be deleted and all source files will be rescanned (only once).
-
The X# source code editor now has an extra combobox on the top, listing the projects where a file is included. When a file is included in more than one project, all these projects can be seen. Switching to a new project will change the 'evaluation context'. Conditional compiles (#ifdef) will reflect the change in the editor.
-
We have added support for the commands Edit.NextMethod and Edit.PreviousMethod in the editor. There usually is no shortcut for these commands, but you can assign them with the "Customize" option on the Toolbar in Visual Studio. You could assign Ctrl-DownArrow and Ctl-UpArrow for example.
-
Improved the Clone Window selection dialog in the VOWED (#1508)
-
When selecting multiple controls in the VOWED, now that lastly selected control becomes the "active" one for the Properties window
-
When pasting a control in the VOWED, it now goes to the bottom of the control order list
-
-
-
Added option in the VOWED Control Order dialog to start adjusting the control order of controls after the currently selected one when using "Use Mouse"
-
The VO binary editors now preserve the SEALED modifier when generating code. Also PROTECT fields of sealed classes become PRIVATE (#1628)
-
-
-
Updated the Mono.Cecil library to 0.11.6
-
Project files are adjusted when properties that were "implicit" before are missing (see above)
-
- XIDE
- General
-
-
Replaced System.Reflection with Mono.Cecil in intellisense for improved performance and stability.
-
The Toolbox Editor also now uses Mono.Cecil for reading controls from dlls.
-
When closing a file directly after opening it (without first activating another file), focus now goes back to the previously active file just before opening the new one.
-
Improved support for standalone files, added options in their properties window for dialect, references etc.
-
Changed default names of various XIDE support files to "xi" instead of "vi" (.xiaef, xiapp etc).
-
Fixed problem with accidentally calling older versions of the XIDE resource compiler and toolbox editor.
-
Added "%OUTPUTEXT% (extension of output assembly) macro in build events.
-
Added support for the /allowdot compiler option in the application properties, enabled by default in all applications.
-
Fixed problem with not properly saving the compiler options /initlocals, /modernsyntax, /allowoldstyleassignments and /namedargs.
-
The Clipboard item in the main XIDE window statusbar now shows the current clipboard contents in a tooltip.
-
The Clipboard selection context menu now also displays the contents of every virtual clipboard.
-
Added Open Bin Folder context menu option for the project node in the Project tool window.
-
Added option to the windows resource editor to include strings and text files.
-
Added application templates for FoxPro, XBase++, and Harbour dialects.
-
Application templates shown in the New Application dialog are now sorted by the GalleryIndex setting of each gallery file template.
-
Implemented new menu options View|Load/Save/Reset Layout, for switching between different layouts for the IDE window and tool windows
-
Added some new templates (code snippets) in template.cfg
-
Added project support for the /vo15 compiler option
-
Added standalone files default setting for the allowdot compiler option (Preferences/Compiler)
-
Added option to set the console location when running console apps (Preferences/Advanced)
-
Included several "hidden" commands in the main menu (File/Navigate and Edit/Advanced)
-
Improved deletion of items in the Watch tool window
-
Improved the About XIDE dialog.
-
- Editor
-
-
Improved Recognition of positional keywords in the code.
-
Fixed recognition of two-letter long functions in code.
-
Fixed problem with intellisense on functions defined in core dialect apps.
-
Added intellisense support for FOREACH VAR.
-
Fixed crash with VAR locals in the editor.
-
Fixed several issues with LOCAL IMPLIED.
-
Fixed problem with parsing modified classes in namespaces.
-
Improved editor support for the FoxPro, Harbour, and XBase++ dialects.
-
Added editor support for a lot of FoxPro keywords.
-
Added editor support for FoxPro functions.
-
The editor now recognizes && for line comments marker in FoxPro dialect.
-
Added intellisense support for Nullable types specified with the ? postfix (for example, INT?).
-
Added intellisense support for the ?: operator.
-
Added intellisense support for IF <identifier> IS <type> VAR <local>
-
Added option (Preferences/Editor/Edit) to automatically adjust numeric literals containing underscores
-
Added context menu Surround with options for REPEAT..UNTIL and BEGIN SCOPE...END
-
Added (experimental) option to sort entities in the editor (Edit->Sort Entities)
-
-
- Designers
-
-
Items in the properties window of the VOWED are now sorted by name.
-
Controls in the WED can now be resized through the keyboard, using SHIFT+ Arrow keys.
-
When loading a WindowsForms form in the designer, all TabControls now have their first TabPage selected initially.
-
Auto-generated eventhandler method names now include an underscore between the control- and event-part of the name
-
Added option (Preferences/Designers) to add an END (METHOD, CONSTRUCTOR, etc.) statement in generated code.
-
Added option (Preferences/Designers) to enter current OS scaling setting (fixes problem with showing lasso lines at the wrong place when creating/moving controls in non-default settings).
-
Added toolbar button to Lock/Unlock controls in the Windows.Forms and VO Window editors.
-
Locked state of controls is now preserved in the Windows.Forms designer (needs a Save Form to apply).
-
Fixed problem with setting the Text property of strip items to empty.
-
Added option in the VOWED Control Order dialog to start adjusting the control order of controls after the currently selected one when using "Use Mouse".
-
Added components SaveFileDialog, OpenFileDialog and FolderBrowserDialog in the Windows.Forms toolbox
-
-
- Debugger
-
-
Exception dialog while debugging now properly shows the exception message.
-
Fixed a problem with incorrectly breaking on excluded handled exceptions.
-
Fixed a common crash that could happen in the debugger.
-
-
- Plugin System
-
-
Some small corrections to the Plugin System (you may need to recompile your plugins)
-
Added Plugin:OnAfterCompileApplication(oApp AS Application, eResult AS CompileResult) callback method
-
Added Editor:SetSelection() method to select text in the editor
-
Entity objects returned from the plugin system no longer include END CLASS and END NAMESPACE statements
-
- Documentation
- Bug fixes
-
-
Made many corrections to the documentation (#1504, #1506, #1514).
Fixed problem with the USE command with an AGAIN clause in the FoxPro dialect (#235).
-
Fixed problem with calling typed array constructors with named parameters when compiling with the /namedargs compiler option enabled (#1430).
-
Fixed inconsistency with the INSTANCE keyword and the use inside the class (#1432).
-
Fixed problem with the REPLACE UDC that could prevent the use of a variable named "replace" (#1443).
-
Fixed problem with the /vo9 (handle missing RETURN statements) compiler option with ACCESSes in PARTIAL classes (#1450).
-
Fixed problem with the Lexer recognizing line continuation characters inside a string in the FoxPro dialect (#1453).
-
Fixed problem with the memvar pragma option (#1454).
-
Fixed a problem with the /xpp compiler option. (#1243, #1458).
-
Fixed a problem with accessing Hidden class members in a method from the class where the member was defined, when the object involved was untyped (#1335, #1457).
-
Fixed an internal compiler error with a line of code containing a single comma (#1462).
-
Fixed a problem with the USE command when the filename was specified as a bracketed string (#1468).
-
- New Features
-
-
You can now use the NULL() and DEFAULT() expression to initialize any variable with a default value. This is the equivalent of the default keyword in C#.
-
We have added a new compiler option /modernsyntax (#1394). This disables certain legacy features:
-
-
&& for line comments;
-
* at the start of a line for a comment line;
-
Bracketed strings;
-
Parenthesized expression lists (making it easier to recognize tuples).
-
-
-
-
Added support for IS NULL and IS NOT NULL pattern (#1422).
-
Added support for file wide FIELD statements in the Harbour dialect (#1436).
-
- Runtime
- Bug fixes
-
-
Fixed runtime error in Transform() with PTR argument (#1428).
-
Fixed problem with several String runtime functions throwing a runtime error when passed a PSZ argument (#1429).
-
Fixed problem with OrdKeyVal() and ADS/ADT files in the ADS RDD (#1434).
-
Fixed incompatibilities with various xBase dialects with creating and using orders with long names (#1438).
-
Fixed VO incompatibility in OrderKeyNo() with the ADS RDD when the setting Ax_SetExactKeyPos() is TRUE (#1444).
-
Fixed a problem in the macro compiler with passing more than two arguments by reference (#1445).
-
Fixed problem with DBSetIndex() seting the record pointer at eof (#1448).
-
Fixed problem reading fields from OEM dbfs (#1449).
-
- New Features
-
-
Implemented the DBFMEMO driver (#604).
-
Implemented the DBFBLOB driver (#605).
-
Added missing SetColor() function overload with no parameters (#1440).
-
-
-
This version includes the new XSharp.VFP.UI.DLL that is used by forms exported from Visual FoxPro with the VFP Exporter.
-
- Visual Studio integration
- Bug fixes
-
-
Fixed a problem with "Jump to File" command in VS 2019 (#1146).
-
Fixed problem with "Go to definition" not working for local function (#1415).
-
Fixed problem with the Class navigation box showing the wrong current entry in some cases (#1426).
-
Fixed problem with setting the "enable named arguments" project option (#1431).
-
Fixed problem with the code generator for types in external assemblies not generating parameters for Indexed properties (#1442).
-
Fixed problem with the VODBServer editor not saving access/assigns and other entities of the [DBSERVER] section in CAVOFED.TPL (#1452).
-
Fixed problem with loading supplemental files provided in the cavowed.inf file for the VO Window Editor with absolute or relative paths (#1470).
-
Fixed some indentation issues in the editor (#1541).
-
Fixed a problem in the VS2022 Debugger when different DLLs contained the same namespace but different casing.
-
Fixed an issue where the entity parser inside the editor did not correctly determine the end of an entity containing a local function or procedure.
-
Fixed a problem where the entity parser inside the editor failed to handle a param token at the start of a line when the /memvars compiler option was NOT enabled.
-
- New features
-
-
We have added a menu entry to the Help menu for the Chinese version of the documentation.
-
- VOXporter
- Bug fixes
-
-
Fixed problem with incorrectly converting attributes to string literals (#1404).
-
- New Features
-
-
It is now possible to define special TEXTBLOCK entities in the VO code in any module with name "VXP-TOP" or "{VOXP:TOP}", and VOXporter will automatically insert the contents of the text block in the beginning of the exported X# .prg file for the module. This is particularly helpful for specifying top level commands like #using statements (#1425).
-
- VFPXporter
-
-
This version of X# includes the VFP Exporter. This tool takes a Visual FoxPro project file and converts that into a Visual Studio solution
-
- XIDE
-
-
Added option when trying to debug a 32/64bit app in the wrong XIDE version, to automatically open the alternative version.
-
Fixed coloring of several positional keywords in the editor.
-
Improved editor support for TEXT...END TEXT.
-
Added editor support for the NOT NULL code pattern.
-
Added project support for the compiler options /namedargs, /initlocals, /modernsyntax and /allowoldstyleassignments.
-
When pressing the SHIFT key on startup, the layout of the IDE is now reset to default positions (rather than saved on exit).
-
Added menu command View->Save Current Layout.
-
Fixed a problem with toggling case (CTR+U) of text selected in a column selection.
-
Fixed several issues with incorrectly identifying a line with identifiers like PROC or FUNC as entity definitions.
-
- Documentation
- Bug fixes
-
-
Fixed typo in the /namedargs compiler option topic.
-
- New Features
-
-
We have added several chapters about modifiers.
-
We have added a (partially) translated help file in (Simplified) Chinese.
Now the compiler properly reports an error when duplicate field names are defined in a type (#1385)
-
Fixed problem with defining multiple type constraints in a generic type (#1389)
-
Fixed problem with global MEMVARs hiding local variables or parameters with the same name (#1294)
-
Bogus compiler error messages with not found type (#1396)
-
Fixed compiler crash with missing reference to XSharp.VFP in the FoxPro dialect (#1405)
-
Fixed problem with /initlocals compiler option incorrectly also initializing class fields (#1408)
-
Fixed a problem in the preprocessor where an extended match symbol would not properly match an expression that started with a string literal
-
- New features
-
-
We added support for dimensioning (FoxPro) class properties, such as in DIMENSION this.Field(10)
-
We have added support for FOREACH AWAIT, like in the following example. (Works in .Net Core, .Net 5 and later)
-
- FOREACHAWAITVAR data IN GenerateNumbersAsync(number) SELF:oListView1:Items:Add(data) NEXT
-
-
We have added support for "Coalescing Member Access, such as in the following example where FirstName and LastName are both properties of the oPerson object:
-
-
- ? oPerson:(FirstName+" "+LastName)
-
-
-
The WITH command now also recognizes the AS DataType clause
-
-
-
XBase++ Class declarations now also allow “END CLASS” as closing token.
-
-
-
Now the compiler reports an error when attempting to convert from Lambda Expression to usual (#1343)
-
-
-
We have added support for TUPLE datatypes. This includes declaring local variables, parameters, return value etc. We also support decomposition of a tuple return value into multiple locals. See the TUPLE help topic for more information.
-
- Runtime
- Bug fixes
-
-
Fixed problem calling DoEvents() from the macro compiler (#872 )
-
Fixed problem with __Mem2StringRaw() (undocumented) function (#1302)
-
Fixed problem opening DBFCDX index file with incorrect collation information in the header #1360
-
Fixed problem with OrdSetFocus() resetting the current order when called without arguments (#1362)
-
Fixed problems with some index files after a DBPack() (#1367)
-
Fixed problem with Deleted() returning TRUE on a table with all records deleted (#1370)
-
Fixed problem with opening and writing to a file with FWrite() etc functions when opened in exclusive and write only mode (#1382)
-
Fixed several problems (VO incompatibilities) with the SplitPath() function (#1384)
-
Now when there is no codepage found in a dbf header, then the DOS codepage from the RuntimeState is used and no longer the hardcoded codepage 437 (#1386)
-
Replaced the Dictionary<,> class used in some areas of the runtime with ConcurrentDictionary<,> to avoid issues in multi threaded apps (#1391)
-
Fixed problem with NoIVarget when using IDynamicProperties (FoxPro dialect) (#1401)
-
Fixed problem with Hex2C() giving different results with lower case letters than with upper case. Note that this bug existed also in VO, so now the behavior of Hex2C() with lower case hex letters in X# with is different to VO (#1402)
-
-
-
Accessing properties on a closed DbServer object that was opened with the Advantage RDD could cause problems in the debugger. The DbServer class now returns empty values when the server is closed.
-
- New features
-
-
Implemented CREATE CURSOR command [FoxPro] (#247). Also implemented CREATE TABLE and ALTER TABLE (FoxPro dialect)
-
Implemented INSERT INTO commands (FoxPro dialect for inserting variables from values, arrays, objects and memory variables. INSERT INTO from a SQL query does not work yet. (FoxPro dialect)
-
-
-
Implemented new FoxPro-compatible version of Str() function in XSharp.VFP (#386)
-
Now an error is thrown when opening an index file fails (#1358)
-
Added AscA() function and made Asc() dependent on the SetAnsi() setting in the runtime (#1376)
-
- Header files
- Bug fixes
-
-
Implemented several missing commands (#1407)
-
Fixed typo in the SET DECIMALS TO command (#1406)
-
Added missing clauses NAME and MEMVAR for the GATHER command (FoxPro) (#1409)
-
Updated several commands to make some tokens optional and more compatible to various dialects (#1410, #1412)
-
Fixed various incompatibilities with COMMIT command in various dialects (#1411)
-
- Visual Studio Integration
- Bug fixes
-
-
Fixed problem with looking up public static field in type referenced by static using (#1307)
-
Fixed intellisense problem with locals defined inside block statements (#1345)
-
Fixed problem with intellisense incorrectly resolving type specified in code with full name to another from the usings list (#1363)
-
Fixed problem with member completion incorrectly showing static methods after typing a colon (#1379)
-
Fixed editor freezing with specific code (#1380)
-
Fixed problem with Class Navigation bar not showing the method name in certain cases (#1381)
-
- New features
-
-
Added support for IEnumerable and DataTable Debugger visualizers (#1373). Please note that when browsing X# arrays the results in the visualizer are really ugly because the visualizer ignores attributes to hide properties and fields for our USUAL class.
-
Adjusted the Globals, Workareas etc debugger windows to respect the global theme selected in VS (#1375). Also added status panel to the Workarea window, so you can see the workarea status or field names/values
-
Added intellisense support for locals declared with USING VAR or USING (LOCAL) IMPLIED (#1390)
-
Now the intellisense database uses an SQLite package that has ARM support, so the it will work also on a Mac and other platforms (#1397)
-
- VOXporter
- Fixes
-
-
Fixed problem with VOXporter incorrectly modifying previously commented code with {VOXP:UNC} tags (#1404)
-
- Documentation
- Bug Fixes
-
-
The documentation of functions in the runtime help was describing functions incorrectly. For example the topic title for the "Left" function was "Functions.Left Method" This has been changed to "Left Function"
-
The "SingleLineEdit" class in the documentation was called "Real4LineEdit". This has been fixed.
-
- New Features
-
-
We have added additional documentation to the X# Programming guide about several subjects.
Fixed some preprocessor issues with XBase++ related commands (#1213, #1288, #1337)
-
Fixed problem with implicit access to static class members (XBase++ dialect) (#1215)
-
Fixed a parser error with the DIMENSION command (VFP dialect) (#1267)
-
Fixed preprocessor problem with UDCs in code spanning in multiple lines (#1298)
-
Now each "unused variable" warning is reported at the exact location of a variable definition, instread of always at the first one (#1310)
-
Fixed bogus "unreachable code" warning in the SET RELATION command (#1312)
-
Fixed a problem in generating XML documentation for the compiler generated <Module>.$AppInit and <Module>.$AppExit methods (#1316)
-
Fixed problem with accessing hidden fields of another object (XBase++ dialect) (#1335)
-
Fixed problem with calling parent methods with an explicit class indication (Xbase++ dialect) (#1338)
-
Fixed problem with incorrectly calling function twice, in code like "SLen(c := SomeFunction())" (#1339)
-
Fixed problem with parent Сlass methods not being visible in derived classes (Xbase++ dialect) (#1349)
-
Fixed problem with ::new() not working properly in class methods (Xbase++ dialect) (#1350)
-
Fixed an exception when an error occurred for a token that was defined in a header file
-
Fixed a compiler error when returning super:Init() from a XBase++ method (#1357)
-
Fixed a problem with STATIC DEFINEs in same named .prg files (#1361)
-
- New features
-
-
Introduced warning for not specifying the OUT keyword for OUT parameters (#1295)
-
The parser rules for method and constructor calls without parameters have been updated. This may result in a bit faster compilation.
-
SLen() is no longer "inlined" by the compiler. If you reference XSharp.Core in your app, SLen() now gets resolved to the SLen() function inside X# Core. If you compile without X# runtime, or compile against the Vulcan Runtime you now need to add a SLen() function to your code. This is the code inside X# Core that you can use as a template FUNCTION SLen(cString ASSTRING) ASDWORD LOCAL len := 0 ASDWORD IF cString != NULL len := (DWORD) cString:Length ENDIF RETURN len
-
Added support for preprocessor commands #ycommand and #ytranslate that are also supported by Harbour. They work the same as #xcommand and #xtranslate, but the tokens are compared in case sensitive mode (#1314)
-
Code generation for some of the Xbase++ specific features has changed.
-
We have added several more UDCs with the IN <cursor> clause
-
-
-
We have added UDC support for the FoxPro CAST expression
-
Several more SET commands now also support the & operator
-
The compiler now supports "Late bound names" in more locations, such as in the REPLACE command, With command etc. This now compiles without problems:
-
- cVar := "FirstName" WITH oCustomer .&cVar := "John" ENDWITH and this too
Fixed problem with incorrectly closing dbf file before relations are cleared (#1237)
-
Fixed incorrect index scope visibility immediately after file creation (#1238)
-
Fixed problem in FFirst()/FNext() not finding all files specified by filter (#1315)
-
Fixed problem with DBSetIndex()/VoDbOrdListAdd() always reseting the controlling order to 1 (#1341)
-
Fixed problem with updating index keys in the DBFCDX driver when the key expression was of type DATE.
-
Fixed a problem when Str() and StrZero() had a built-in maximum string length of 30.(#1352)
-
The RegisteredRDD Class now uses a ConcurrentDictionary.
-
Fixed a bug in the RDD TransRec() method when a field is missing in the target table (#1372)
-
Fixed a problem in the Advantage RDD to prevent ADS functions from being called when the table is closed
-
Fixed a problem in the Advantage RDD that could occur when an field with an incorrect name was read
-
Fixed a problem in the CurDir() function when the current directory is a UNCPath (\\Server\Share\SomeDir) (#1378)
-
- New features
-
-
Added support for accessing indexers in the USUAL type (#1296 )
-
We have added a DbCurrency type that is returned from the RDD when a currency field is read.
-
Implemented the TEXT TO FILE command (#1304)
-
Now the RDD reports an error (dialog) when tagname > maximum length when creating an index order (#1305)
-
Added a function _CreateInstance() that accepts a System.Type parameter
-
The late binding code now detects from where Send(), IVarGet() and IVarPut() are called and allow access to private/hidden fields when the calling code is of the same type as the type where the class members were declared. This is used in some of the XBase++ related changes.
-
The classes in the XBase++ have been restructured a bit.
-
The mapping of several DBF / Workarea / Cursor related UDCs has been changed to be more FoxPro compatible.
-
We have added runtime support for the FoxPro CAST expression
-
We have done some small code optimizations w.r.t. dictionaries(#1371)
-
Several DbServer properties no longer call into the RDD when the server is closed, but return blank values instead.
-
- Typed SDK classes
-
-
Added a DbServer:Append() overload without parametrs (#1320)
Fixed runtime error when creating a DataWindow with a ShellWindow as owner (#1324)
-
Changed DataWindow:Show() method to CLIPPER for compatibility with existing code (#1325)
-
Fixed exception when using a ComboBox on a VO Window (#1328)
-
Fixed error when opening a datawindow with an assigned server (#1332)
-
Fixed runtime error when instantiating a DBServer object with an untyped FileSpec object as first argument (#1348)
-
Fixed problem with displaying items in Comboboxes and Listboxes (#1347)
-
Several DbServer properties no longer call into the RDD when the server is closed, but return blank values instead.
-
- Visual Studio Integration
- Bug fixes
-
-
Fixed problem with the "allow dot" setting in the project file (#1192)
-
Several macros such as $CALLSTACK were not returning values in expected format. This has been fixed (#1236)
-
Fixed build problem when there is a block comment in the first line of form.prg (#1334)
-
Fixed probelm with block commenting a code snippet in a single line (#1336)
-
Fixed failing project build when the project file contains a property <GenerateAssemblyInfo>True</GenerateAssemblyInfo> (#1344)
-
Fixed a problem in the Parser that was causing errors parsing DebuggerDisplay attributes in the expression evaluator.
-
The new debugger windows were not following the current windows theme. This is now partially fixed. (#1375)
-
- VO Compatible Editors
-
-
Fixed design time display issue with CheckBox and RadioButton captions with specific fonts in the VOWED (#796)
-
Fixed problem with the VOWED editor changing all existing classes in the prg to PARTIAL (#814)
-
Fixed problem with incorrectly adding constructor code to instantiate the DataBrowser in the VOWED, even when there are no (non-deleted) data columns (#1365)
-
Fixed several problems in the VOMED with menu item define names in source code and resource files (#1374)
-
- VOXporter
- New features
-
-
Introduced options (inline in existing code) to comment, uncomment and delete lines from the original VO code (#1303)
-
- - {VOXP:COM} // comment out line
- - {VOXP:UNC} // uncomment line
- - {VOXP:DEL} and // {VOXP:REM} // remove line
- Installer
- New features
-
-
The installer now detects if the required Visual Studio components "Core Editor" and ".Net Desktop Development" are installed. When it finds one or more VS installations but none of these installations has both the required components then a warning is shown.
Fixed several incompatibilities with XBase++ regarding using class members (#1215) UNCONFIRMED
-
Fixed /vo3 option not working correctly in XBase++ dialect. Also added support for modifiers final, introduce and override (#1244)
-
Fixed problem with using the NEW modifier on class fields (#1246)
-
Fixed several preprocessor issues with XPP dialect UDCs (#1247, #1250)
-
Fixed VO incompatibility with special handling of INSTANCE fields in methods and properties (#1253)
-
Fixed problem with the debugger erratically stepping to incorrect lines (#1254, #1264)
-
Fixed problem with showing the wrong error line number in some cases with nested statements (#1268)
-
Fixed problem where a DO CASE statement without CASE lines was producing an internal error in the compiler (#1281)
-
Fixed a couple preprocessor issues (#1284, #1289)
-
Fixed missing compiler error on calling with SUPER a method that does not exist, when late binding is enabled (#1285)
-
Fixed a Failed to emit Module error with CONST class field missing value assignment (#1293)
-
Fixed a problem with repeated match markers (such as in the SET INDEX TO command) in the preprocessor.
-
Fixed a problem that an property definition with an explicit interface prefix could lead to a compiler crash when the interface was "unknown" at compile time and/or the property name was not "Item" (#1306)
-
- New features
-
-
Added support for "classic" INIT PROCEDURE and EXIT PROCEDURE (#1290)
-
Added warnings when statement list inside case blocks, if blocks and other blocks are empty. To suppress the warning you can add a NOP statement in your code.
-
We have made some changes to the lexer and parser in the compiler. This may result in a bit smaller memory footprint and faster compilation speed for code with many nested blocks.
-
- Runtime
- Bug fixes
-
-
Fixed several problems (incompatibilities with VO) in CToD() (#1275)
-
Added support for 3rd parameter in AAdd() for specifying where to insert the new element (#1287)
-
The Default() function now no longer updates usuals that have a value of NULL_OBJECT to be compatible with Visual Objects.(#1119)
-
We have added support for parameters for the AdsSQLServer class (#1282)
-
- Visual Studio integration
- New Features
-
-
We have added debugger pane windows for the following items:
-
-
Global variables
-
Dynamic memory variables (Privates and Publics)
-
Workareas
-
Settings
-
-
-
-
You can open these windows from the Debug/XSharp menu during debugging. There is also a special "X# Debugger Toolbar" which is also only shown during debugging.
-
These windows will only show information when the app being debugged uses the X# runtime (so they will not work in combination with the Vulcan Runtime). If you are debugging an application written in another language that uses the X# runtime then these windows will also show information. We have planned to add more features to these windows in future builds, like the properties of the current selected area and the field/values in the current selected workarea
-
We have added support for "FileCodeModel" for X# files. This is used by the WPF designer and XAML editor. This now also fixes the Goto definition in the XAML editor (#1026)
-
Several properties of X# projects are now cached. This should result in slightly faster performance.
-
We have added support for "Goto Definition" for User Defined commands. For example choosing "Goto definition" on the USE keyword from the USE command will bring you to its definition in our standard header file.
-
- Bug fixes
-
-
Fixed member completion issue with Type[,] arrays (#980)
-
Fixed missing member completion in class inside namespace when same named class exists without namespace (#1204)
-
Fixed an auto indent problem when an entity has an attribute in the precessing line (#1210)
-
Fixed intellisense problems with static members in some cases (#1212)
-
Fixed some intellisense issues with code or declarations spanning in multiple lines (#1221, #1260)
-
Fixed intellisense problem with nested classes inside a namespace (#1222)
-
Fixed incorrect resolving of VAR local type, when using a type cast (#1224)
-
Fixed several problems with collapsing/expanding code in the editor (#1233)
-
Fixed showing of bogus member completion list with unknown types (#1255)
-
Fixed some problems with auto typing text with Ctrl + Space (complete Word) (#1256)
-
Fixed coloring of Text .. EndText statements (#1257)
-
Fixed several issues with tooltip hints with generic types (#1258, #1259, #1273)
-
Fixed problem with delegate signature not showing in intellisense tooltips (#1265)
-
Fixed invalid coloring of code with multiline comments (#1269)
-
Fixed invalid entries in member completion after typing "self." (#1270)
-
Fixed problem with calling the disassembler when path specified (in option X# Custom Editors\Other Editors\Disassembler) with spaces (#1271)
-
Fixed editor coloring completely stopping when using some UDC calls (#1272)
-
Fixed problem with hint not showing on CONSTANT locals in FOR statements (#1274)
-
Fixed auto indent problem when code contains a LOOP or EXIT keyword (#1278)
-
Fixed an exception in the editor when typing a parenthesis under specific circumstances (#1279)
-
Fixed problem with incorrectly trying to open in design mode files with filenames starting with an opening bracket (#1292 )
-
The "XSharp Website" menu option inside VS was broken (#1297)
-
Fixed problem with the Match Identical Identifiers functionality that could slow down Visual Studio
-
Fixed a VS lock up that could happen when a file was opened during debugging.
-
Parameter tips for classes with a static constructor and a normal constructor were not processed correctly. This has been fixed.
-
-
-
When a project was opened where the dependency between a dependent item (like a .resx file or a .designer.prg file) and its parent was missing, then an exception could occur, which prevented the project from opening. This has been fixed.
-
When 2 compiler errors occurred on the same line with the same error code they were sometimes shown in the VS output window but not in the Error List. This has been fixed (#1308)
-
- VOXporter
- New Features
-
-
Added support for special tags {VOXP:COM}, {VOXP:UNC} and {VOXP:DEL} / {VOXP:REM} to comment out, uncomment and remove lines from the original VO code (#1303)
-
- Changes in 2.16.0.5
- Compiler
- New Features Xbase++ dialect
- We have made several changes in the way how Xbase++ class definitions are generated. Please check your code extensively with this new build !
-
-
We now generate a class function for all classes. This returns the same object as the ClassObject() method for Xbase++ classes. This class function is generated, regardless of the /xpp1 compiler option. The Class function depends on the function __GetXppClassObject and the XSharp.XPP.StaticClassObject class that both can be found in the XSharp.XPP assembly(#1235). From the Class function you can access class variables and class methods.
-
In Xbase++ you can have fields (VAR) and properties (ACCESS / ASSIGN METHOD) with the same name, even with same visibility. Previously this was not supported. The compiler now automatically makes the field protected (or private for FINAL classes) and marks it with the [IsInstance] attribute. Inside the code of the class the compiler will now resolve the name to the field. In code outside of the class the compiler will resolve the name to the property.
-
For derived classes the compiler now automatically generates a property with the name of the parentclass, that is declared as the parent class and returns the equivalent to SUPER.
-
We have fixed an issue with the FINAL, INTRODUCE and OVERRIDE keywords for Xbase++ methods (#1244)
-
We have fixed some issues with accessing static class members in the XBase++ dialect (#1215)
-
You can now use the "::" prefix to access class variables and class methods inside class methods.
-
When a class is declared as subclass from another class then the compiler generates a (typed) property in the subclass to access the parent class, like Xbase++ does. This property returns the value "super".
-
We are now supporting the READONLY clause for Vars and Class Vars. This means that the variable must be assigned in the Init() method (instance variables) or InitClass() method (Class vars)
-
-
- New Features other dialects
-
-
Inside Visual Objects you could declare fields with the INSTANCE keyword and add ACCESS/ASSIGN methods with the same name as the INSTANCE field. In previous builds of X# this was not supported. The compiler now handles this correctly and resolves the name to the field in code inside methods/properties of the class and resolves the name to the property in code outside of the class.
-
The PPO file now contains the original white space from user defined commands and translates.
-
- Bug fixes
-
-
Fixed some method overload resolution issues in the VO dialect (#1211).
-
Fixed internal compiler error (insufficient stack) with huge DO CASE statements and huge IF ELSEIF statements (#1214).
-
Fixed a problem with the Interpolated/Extended string syntax (#1218).
-
Fixed some issues with incorrectly allowing accessing static class members with the colon operator or instance members with the dot operator (#1219,#1220).
-
Fixed Incorrect visibility of MEMVARs created with MemVarPut() (#1223).
-
Fixed problem with _DLL FUNCTION with name in Quotes not working correctly (#1225).
-
If the preprocessor generated date and/or datetime literals, then these were not recognized. This has been fixed (#1232).
-
Fixed a problem with the preprocessor matching of the last optional token (#1241)
-
Fixed a problem with recognizing the ENDSEQUENCE keyword in the Xbase++ dialect (#1242).
-
Using a default parameter value of NIL is now only supported for parameters of type USUAL. Using NIL for other parameter types will generate a (new) warning XS9117 . Also assigning NIL to a Symbol or using NIL as parameter to a function/method call that expects a SYMBOL will now also generate that warning (#1231).
-
Fixed a problem in the preprocessor where two adjacent tokens were not merged into one token in the result stream. (#1247).
-
Fixed a problem in the preprocessor where the preprocessor was not detecting an optional element when the element started with a Left parenthesis (#1250)
-
Fixed a problem with interpolated strings that contained literal double quotes like in i"SomeText""{iNum}"" "
-
Fixed a problem that was introduced in an earlier build of 2.16 with local functions / procedures.
-
A warning generated at parse time could lead to another warning about a preprocessor define even when that is not needed. This has been fixed.
-
Fixed issue with default parameter values for parameters declared as "a := NIL,b := NIL as USUAL" introduced in an earlier build of 2.16
-
Fixed issue with erratic debugger behavior introduced in an earlier build of 2.16.
-
When you are referring to a type in an external assembly that depends on another external assembly, but you did not have a reference to that other external assembly, then compilation could fail without proper explanation. Now we are producing the normal error that you need to add a reference to that other assembly.
-
Omitting the type for a parameter for a function or method that does not have the CLIPPER calling convention is allowed. These parameters are assumed to be of type USUAL. This now produces a new warning XS9118.
-
- Breaking changes
- If you are using our parser to parse source code, please check your code. We have made some changes to the language definition for the handling of if ... else statements as well as for the case statements (a new condBlock rule that is shared by both rules). This removes some recursion in the language. Also some of the Xbase++ specific rules have been changed. Please check the language definition online
- Runtime
- New Features
-
-
Added the DOY() function.
-
Addeding missing ADS_LONG and ADS_LONGLONG defines.
-
-
-
Improved the speed of CDX skip operations on network drives (#1165).
-
- Bug fixes
-
-
Fixed a problem with DbSetRelation() and RLock() (#1226).
-
Adjusted implicit conversion from NULL_PSZ to string to now return NULL instead of an empty string.
-
Some initialization code is now moved from _INIT procedures to the static constructor of the SQLConnection Class, in order to make it easier to use this class from non-X# apps.
-
Fixed an issue with the visibility of dynamic memory variables that were created with the MemVarPut function (#1223).
-
Fixed a problem with the DbServer class in exclusive mode (#1230).
-
Implicit conversions from NULL_PSZ to string were returning an empty string and not NULL (#1234).
-
Fixed a problem in the CTOD() function when the day, month or year were prefixed with spaces.
-
Fixed an issue with OrderListAdd() in the ADS RDD. When the index is already open, then the RDD no longer returns an error.
-
Fixed an issue with MemRealloc where the second call on the same pointer would return NULL_PTR (#1248).
-
- VOSDK
-
-
Global arrays in the SDK classes are now initialized from the class constructor of the SQLConnection class to fix problems when the main app does not include a link to the SQL Classes assembly.
-
- Visual Studio integration
- Debugger
-
-
The debugger expression evaluator now also evaluates late bound properties and fields (if that compiler option is enabled inside your project). If this causes negative side effects then you can disable that in the "Tools/Options Debugging/X# Debugger options screen".
-
The debugger expression evaluator now is initialized with the compiler options from your main application (if that application is an X# project). The settings on the Debugger Options dialog are now only used when debugging DLLs that are loaded by a non X# startup project.
-
The debugger expression evaluator now always accepts a '.' character for instance fields, properties and methods, regardless of the setting in the project options. This is needed because several windows in the VS debugger automatically insert '.' characters when adding expressions to the watch window or when changing values for properties or fields.
-
- New Features
-
-
Added support for importing Indexes in the DbServer editor.
-
The X# project system now remembers which Windows were opened in the Windows editor in design mode and reopens them correctly when a solution is reopened.
-
We have added templates for a Harbour console application and Harbour class library.
-
We have added item templates for FoxPro syntax classes and Xbase++ syntax classes.
-
The Class templates for the FoxPro and XBase++ dialect now include a class definition in that dialect.
-
We have improved the support for PPO files in the VS Editor.
-
We have updated some of the project templates.
-
- Bug fixes
-
-
Fixed a problem with incorrectly showing member list in the editor for the ":=" operator (#1061).
-
Fixed VOMED generation of menu item DEFINE names that were different to the ones generated by VO (#1208).
-
Fixed VOWED incorrect order of generated lines of code in some cases (#1217).
-
Switched back to our own version of Mono.Cecil to avoid issues on computers that have the Xamarin (MAUI) workload in Visual Studio.
-
Fixed a problem opening a form in the Form Designer that contains fields that are initialized with a function call (#1251).
-
Windows that were in [Design] mode when a solution is closed, are now properly opened in [Design] mode when the solution is reopened.
-
- Changes in 2.15.0.3
- Compiler
- New Features
-
-
Implemented the STACKALLOC syntax for allocating a block of memory on the stack (instead of the heap) (#1084)
-
Added ASYNC support to XBase++ methods (#1183)
-
- Bug fixes
-
-
Fixed missing compiler error in a few specific cases when using the dot for accessing instance members, when /allowdot is disabled (#1109)
-
Fixed some issues with passing parameters by reference (#1166)
-
Fixed some issues with interpolated strings (#1184)
-
Fixed a problem with the macro compiler not detecting an error with incorrectly accessing static/instance members (#1186)
-
Fixed incorrect line number reported for error messages on ELSEIF and UNTIL statements (#1187)
-
Fixed problem with using an iVar named "Value" inside a property setter, when option /cs is enabled (#1189)
-
Fixed incorrect file/line info reported in error message when the Start() function is missing (#1190)
-
Fixed bogus warning about ambiguous methods in some cases (#1191)
-
Fixed a preprocessor problem with nested square brackets (in SUM and REPLACE commands) (#1194)
-
Fixed incorrect method overload resolution in some cases in the VO dialect (#1195)
-
Fixed incorrect ambiguous call error with OBJECT/IntPtr parameters (#1197)
-
Fixed erratic debugging while stepping over code in some cases (#1200, #1202)
-
Fixed a problem where a missing "end keyword", such as ENDIF, NEXT, ENDDO was not reported when the code between the start and end contained a compiler warning (#1203)
-
Fixed a problem in the build system where sometimes an error message about an incorrect "RuntimeIdentifier" was shown
-
- Runtime
- Bug fixes
-
-
Fixed runtime error in DBSort() (#1196)
-
Fixed error in the ConvertFromCodePageToCodePage function
-
A change in the startup code for the XSharp.RuntimeState could lead to incorrect codepages
-
- Visual Studio integration
- New Features
-
-
Added VS option for the WED to manually adjust the x/y positions/sizes in the generated resource with multipliers (#1199)
-
Added new options page to control where the editor looks for identifiers on the Complete Word (Ctrl+Space) command.
-
A lot of improvements to the debugger expression evaluator (#1050). Please note that this debugger expression evaluator is only available in Visual Studio 2019 and later
-
Added a debugger options page that controls how expression are parsed by the new debugger expression evaluator. You can also change the setting here that disallows editing while debugging.
-
We have added context help to the Visual Studio source code editor. When you press F1 on a symbol then we inspect the symbol. If it comes from X# then the relevant page in the help file is opened. When it comes from Microsoft then we open the relevant page from the Microsoft Documentation online. In a next build we will probably add an option for 3rd parties to register their help collections too.
-
When a keyword is selected in the editor that is part of a block, such as CASE, OTHERWISE, ELSE, ELSEIF then the editor will now highlight all keywords from that block.
-
The Jump Keywords EXIT and LOOP are now also highlighted as part of the repeat block that they belong to.
-
When a RETURN keyword is selected in the editor, then the matching "Entity" keyword, such as FUNCTION, METHOD will be highlighted too.
-
Added a warning to the Application project options page, when switching the target framework.
-
- Bug fixes
-
-
Fixed previously broken automatic case synchronization, when using the cursor keys to move to a different line in the editor (#722)
-
Fixed some issues with using Control+Space for code completion (#1044, #1140)
-
Fixed an intellisense problem with typing ":" in some cases (#1061)
-
Fixed parameter tooltips in a multiline expressions (method/function calls) (#1135)
-
Fixed problem with Format Document and the PUBLIC modifier (#1137)
-
Fixed a problem with Go to definition not working correctly with multiple partial classes defined in the same file (#1141)
-
Fixed some issues with auto-indenting (#1142, #1143)
-
Fixed a problem with not showing values for identifiers in the beginning of a new line when debugging (#1157)
-
Fixed Intellisense problem with LOGICs in some cases (#1185)
-
Fixed an issue where the completionlist could contain methods that were not visible from the spot where the completionlist was shown (#1188)
-
Fixed an issue with the display of nested types in the editor (#1198)
-
Cleaned up several X# project templates, fixing problems with incorrect placement of Debug/Output folders (#1201)
-
Undoing a case synchronization in the VS editor was not working, because the editor would immediately synchronize the case again (#1205)
-
Rebuilding the intellisense database no longer restarts Visual Studio (#1206)
-
Now the VO Menu Editor uses the same menu item DEFINE values, as those used in the original VO app (re-porting of the app is necessary for this to work) (#1207)
-
A Change to our project system and language service could lead to broken "Find in Files" functionality in some versions of Visual Studio. This has been fixed.
-
Fixed an issue where goto definition was not working for protected or private members
-
Fixed an issue where for certain files the Dropdown combo boxes on top of the editor were not correctly synchronized.
-
- Documentation
- Changes
-
-
Some methods in the typed SDK were documented as Function. They are now properly documented as Method
-
Property Lists and Method lists for classes now include references to methods that are inherited from parent classes. Methods that are inherited from .Net classes, such as ToString() from System.Object are NOT included.
-
- Changes in 2.14.0.2, 3 & 4
- Visual Studio Integration
- Bug fixes
-
-
Fixed an exception in the X# Editor when opening a PRG file in VS 2017
-
Selecting a member from a completion list with the Enter key on a line immediately after an entry that has an XML comment could lead to extra triple slash (///) characters to be inserted in the editor
-
The triple slash command to insert XML comments was not working. This has been fixed.
-
Fixed a problem with entity separators not shown on the right line for entities with leading XML comments
-
Fixed a peek definition problem with types in source code that do not have a constructor
-
Fixed a problem with the Implement Interface action when the keyword case was not upper case
-
Fixed a problem that the keyword case was prematurely synchronized in the current line.
-
Fixed a problem with indenting after keywords such as IF, DO WHILE etc
-
Fixed a problem with selecting words at the end of a line when debugging
-
Fixed a problem where Format Document could lock up VS
-
Fixed a problem that accessors such as GET and SET were not indented inside the property block
-
Fixed a problem that Format Document was not working for some documents
-
Changed the priority of the background scanner that is responsible for keyword colorization and derived tasks inside VS.
Fixed a problem with date literals resulting in a message about an unknown alias "gloal" (#1178)
-
Fixed a problem that leading 0 characters in AssemblyFileVersion and AssemblyInformationalVersion were lost. If the attribute does not have the wildcard '*' then these leading zeros are preserved (#1179)
-
- Runtime
- Bug fixes
-
-
The runtime DLLs for 2.14.0.0 were marked with the TargetFramework Attribute. This caused problems. The attribute is no longer set on the runtime DLLs (#1177)
Fixed a problem resolving methods when a type and a local have the same name (#922)
-
Improved XML doc messages for methods implicitly generated by the compiler (INITs, implicit constructors) (#1128)
-
Fixed an internal compiler error with DELEGATEs with default parameter values (#1129)
-
Fixed a problem with incorrect calculation of the memory address offset when obtaining a pointer to a structure element (#1132)
-
Fixed problematic behavior of #pragma warning directive unintentionally enabling/.disabling other warnings (#1133)
-
Fixed a problem with marking the complete current executing line of code while debugging (#1136)
-
Fixed incompatible to VO behavior with value initialization when declaring global MEMVAR (#1144)
-
Fixed problem with compiler rule for DO not recognizing the "&" operator (#1147 )
-
Fixed inconsistent behavior of the ^ operator regarding narrowing conversion warnings (#1160)
-
Fixed several issues with CLOSE and INDEX UDC commands (#1162, #1163)
-
Fixed incorrect error line reported for error XS0161: not all code paths return a value (#1164)
-
Fixed bogus filename reported in error message when the Start() function is missing (#1167)
-
The PDB information for a command defined in a UDC now highlights the entire row and not just the first keyword
-
Fixed a problem in the CLOSE ALL and CLOSE DATABASES UDC.
-
- Runtime
- New Features
-
-
Added 2 new values to the DbNotificationType enum: BeforeRecordDeleted and BeforeRecordRecalled. Also added AfterRecordDeleted and AfterRecordRecalled which are aliases for the already existent RecordDeleted and RecordRecalled (#1174)
-
- Bug fixes
-
-
Added/updated several defines in the Win32API SDK library (#696)
-
Fixed a problem with "SkipUnique" not working correctly (#1117)
-
Fixed an RDD scope problem when the bottom scope is larger than the highest available key value (#1121)
-
Fixed signature of LookupAccountSid() function in the Win32API SDK library (#1125)
-
Improved exception error message when attempting to use functions like Trim() (which alter the key string length) in index expressions (#1148)
-
Fixed a Macro Compiler runtime exception when there is an assignment in an IIF statement (#1149)
-
Fixed a problem with resolving the correct overloaded method in late bound calls (#1158)
-
Fixed a problem with parametrized SQLExec() statements in the FoxPro Dialect
-
Fixed a problem in the Days() function where the incorrect number of seconds in a day was used.
-
Fixed a problem in the Advantage RDD when a FieldGet returned fields with trailing 0 characters. These are now replaced with a space.
-
Fixed a problem with DBI_LUPDATE in the ADS RDDs
-
Fixed the Debugger display of the USUAL type.
-
- Visual Studio integration
- New Features
-
-
Now using the "Reference Manager" instead of the "Add Reference Dialog Box" for adding References (#21, #1005)
-
Added an option to the Solution Explorer context menu to split a Windows Form in a form.prg and form.designer.prg (#33)
-
We have added an options page to the Tools / Options TextEditor/X# settings that allows you to enable/disable certain features in the X# source code editor, such as "Highlight Word", "Brace Matching" etc. The option to backup the source code for the Windows Forms Editor has been moved from the Texteditor options page to the Custom Editor options page. Search for 'Backup" in the Tools/Options dialog to find the setting.
-
Tooltips for all source code items now contain the Location (file name and the line/column).
-
We have added "search keywords" to all of our option page. you may be able to find a page by typing the keyword that you are looking for in the search control.
-
- Bug fixes
-
-
Fixed a problem renaming files when a solution is under SCC with Team Foundation Server (#49)
-
The WinForms designer now ignores differences in the namespaces specified in the form.prg and designer.prg files (the one from form.prg is used) (#464)
-
Fixed incorrect mouse tooltip for a class in some cases (#871)
-
Fixed a code completion issue on enum types with extension methods (#1027)
-
Fixed some intellisense problems with enums (#1064)
-
Fixed a problem with Nuget packages in VS 2022 causing first attempts to build projects to fail (#1114)
-
Fixed a formatting problem in XML documentation tooltips (#1127)
-
Fixed a problem with including bogus extra static members in the code completion list in the editor (#1130)
-
Fixed problem with Extension methods not included in Goto Definition, Peek definition, QuickInfo tips and Parameter Tips (#1131)
-
Fixed a problem in determining the correct parameter number for parameter tips when a compiler pseudo function such as IIF() was used inside the parameter list (#1134)
-
Fixed a problem with selecting words with mouse double-click in the editor with underscores while debugging (#1138)
-
Fixed a problem with evaluating values of identifiers with underscores in their names while debugging (#1139)
-
Fixed identifier highlighting causing the VS Editor to hang in certain situations (#1145)
-
Fixed indenting of generated event handler methods in the WinForms designer (#1152)
-
Fixed a problem with the WinForms designer duplicating fields when adding new controls (#1154)
-
Fixed a problem with the WinForms designer removing #region directives (#1155)
-
Fixed a problem with the WinForms designer removing PROPERTY declarations (#1156)
-
Fixed a problem that the type lookup for locals was failing in some cases (#1168)
-
Fixed a problem where the existence of extension methods in code was causing a problem filling the member list (#1170)
-
Fixed a problem when completing the member completion list without selecting an item (#1171)
-
Fixed a problem with showing member completion on types of static members of a class (#1172)
-
Fixed a problem with the indentation after single line entities, such as GLOBAL, DEFINE, EXPORT etc. (#1173)
-
Fixed a problem with parameter tips for extension methods (#1175)
-
Fixed a problem with tooltips for namespaces and nested classes (#1176)
-
Optional tokens in UDCs were not colored as Keyword in the source code editor
-
Fixed a problem in the CodeDom provider that failed to load on a Build Server because of a dependency to Microsoft.VisualStudio.Shell.Design version 15.0 when generating code for WPF projects.
Class members declared with only the INSTANCE modifier were generated as public. This has been changed to protected, just like in Visual Objects (#1115)
-
- Runtime
- Bug fixes
-
-
IVarGetInfo() returned incorrect values for PROTECTED and INSTANCE members. This has been fixed.(#1116)
-
The Default() function was changing usual variables initialized with NULL_OBJECT to the new value. This was not compatible with Visual Objects (#1119)
-
- Visual Studio integration
- New Features
-
-
The Rebuild Intellisense Database menu option now asks for confirmation before restarting Visual Studio (#1120)
-
The "Include Files" node in the solution explorer can now be hidden (Tools/ Options X# Custom Editors/Other Editors)
-
- Bug fixes
-
-
The type information for variables declared in a CATCH clause was not available. This has been fixed (#1118)
-
Fixed several issues with parameter tips (#1098, #1065)
-
Fixed a performance issue when the cursor was on a undeclared identifier in a "global" entity such as a function or procedure in VERY large projects
-
The "Include Files" node could contain duplicate references when the source code for an #include statement contained relative paths, such as #include "..\GlobalDefines.vh"
-
-
-
Suppressed the expansion of the "Include Files" node in the Solution Explorer when a solution is opened.
-
Single character words (like i, j, k) were not highlighted with the 'highlight word' feature
-
The type 'ptr' was not marked in the keyword color in quickinfo tooltips
-
The nameof, typeof and sizeof keywords were not synchronized in the keyword case
-
- Changes in 2.13.2.1
- Compiler
- New Features
-
-
The parser now recognizes AS <type> clause for PUBLIC and PRIVATE memory variable declarations but ignores these with a warning
-
We have added support for AS <type> for locals declared with LPARAMETERS. The function/procedure is still clipper calling convention, but the local variable is of the declared type.
-
- Bug fixes
-
-
The PUBLIC and PRIVATE keywords are sometimes misinterpreted as memvar declarations when the /memvar compiler option is not even selected. We have added parser rules to prevent this from happening: when /memvar is not selected then PUBLIC and PRIVATE are only used as visibility modifiers
-
Fix to an issue with selecting function and method overloads (#1096, #1101)
-
Build 2.13.2.0 introduced a problem that could cause a big performance problem for VERY large source files. This has been fixed in 2.13.2.1.
-
-
- Runtime
- Bug fixes
-
-
When the runtime cannot resolve a late bound call to an overloaded method it produces an error message that includes a list of all relevant overloads (#875, #1096).
-
The .NULL. related behavior that was added for the FoxPro dialect was breaking existing code that involves usuals. In the FoxPro dialect DBNull.Value is now seen as .NULL. but in the other dialects as a NULL_OBJECT / NIL
-
Several internal members of the PropertyContainer class in the VFP library are now public
-
- Visual Studio integration
- Bug fixes
-
-
The lookup code for Peek definition, Goto definition etc. was filtering out instance methods and only returning static methods. This has been fixed (#1111, #1100)
-
Several changes to fix issues with indentation while typing (#1094)
-
Fixed several problems with parameter tips (#1098, #1066, #1110)
-
A recent change to support the wizard that converts packages.config to package references has had a negative impact on nuget restore operations during builds inside Visual Studio. This was fixed. (#1113 and #1114)
-
Fixed recognition of variables in lines such as CATCH, ELSEIF, FOR, FOREACH etc (#1118)
-
Fixed recognition of types in the default namespace (#1122)
-
- Changes in 2.13.1
- Compiler
- New Features
-
-
The PUBLIC and PRIVATE statements in the FoxPro dialect now support inline assignments, such as in PUBLIC MyVar := 42 Without initialization the value of the PUBLIC will be FALSE, with the exception of the variable with the name "FOXPRO" and "FOX". These will be initialized with TRUE in the FoxPro dialect
-
- Bug fixes
-
-
Fixed a problem with initialization of File Wide publics in the foxpro dialect
-
Column numbers for error messages were not always correct for complex expressions. This has been fixed (#1088)
-
Corrected an issue in the lexer where line numbers were incorrect when the source contains statements that span multiple lines (by using a semicolon as line continuation character) (#1105)
-
Fixed a problem in the overload resolution when one or more overloads have a Nullable parameter(#1106), such as in class Dummy method Test (param asusual) asint . method Test(param asInt? asint . endclass
-
Fixed a problem with the code generation for late bound method calls and/or array access in the FoxPro dialect with the /fox2 compiler compiler option ("compatible array handling") for variables of unknown type (#1108). An expression such as
undefinedVariable.MemberName(1)
was interpreted as an array access but it could also be a method call. The compiler now generates code that calls a runtime function that checks at runtime if "MemberName" is either a method or a property. If it is a property then the runtime will assume that it is an array and access the first element. Code with more than 2 parameters or with non-numeric parameters, such as
undefinedVariable.DoSomething("somestring")
was not affected, since "somestring" cannot be an array index. TIP: We recommend however, to always declare variables and specify their type. This helps to find problems at compile time and will generate MUCH faster code.
-
-
- Runtime
- New Features
-
-
Added functions to resolve method calls or array access at runtime (#1108)
-
Added GoTo record number functionality to the WorkareasWindow in the XSharp.RT.Debugger library
-
- Visual Studio Integration
- New Features
-
-
Now the VS Project tree shows (in a special node) include files that are used by a project (#906). This includes include files inside the project itself but also include files in the XSharp folder or Vulcan folder (when applicable).
-
We are using the built-in images of Visual Studio in the project tree and on several other locations when possible.
-
Our background parser inside VS is now paused during the built process to interfere less with the build.
-
We have added a setting to the indentation options so you can control the indentation for class fields and properties separately from methods. So you can choose to indent the fields and properties and to not indent the methods. This has also been added to the .editorconfig file
-
- Bug Fixes
-
-
Fixed problems with Peek Definition and Goto Definition
-
When looking up Functions we were (accidentally) sometimes also including static methods in other classes.
-
When parsing tokens for QuickInfo and Peek Definition then a method name would not be found if there was a space following the name and before the open parenthesis.
-
Fixed a problem where project wide resources and settings (added from the project properties page) did not get the code behind file when saving
-
Quick Info and Goto definition on a line that calls a constructor will now show / goto the first constructor of the type and no longer to the type declaration
-
When the build process of a project was failing due to missing resources or other resource related problems, then the error list was not properly updated. This has been fixed (#1102)
-
The XSharpDebugger.DLL was not installed properly into VS2017 and VS2019.
-
- Changes in 2.13
- Compiler
- New Features
-
-
We have implemented a new compiler option /allowoldstyleassignments, which allows using the "=" operator instead of ":=" for assignments. This option is enabled by default in the VFP dialect and disabled by default in all other dialects.
-
-
-
We have revised the behavior of the /vo4 and /vo11 command line options that are related to numeric conversions. Before /vo4 only was related to conversions between integral numbers. It has now been extended to also include conversions between fractional numbers (such as float, real8, decimal and currency) and integral numbers. In the original languages (VO, FoxPro) you can assign a fractional number to a variable with integral value without problems. In .Net you can't do that but you will have to add a cast to the assignment:
-
- LOCAL integerValue asINT LOCAL floatValue := 1.5 asFLOAT integerValue := floatValue // no conversion: this will not compile in .Net without conversion integerValue := (INT) floatValue // explicit conversion: this does compile in .Net ? integerValue
If you enable the compiler option /vo4 then the assignment without the cast will also work. The /vo4 compiler option adds an implicit conversion In both cases the compiler will produce a warning: warning XS9020: Narrowing conversion from 'float' to 'int' may lead to loss of data or overflow errors The value of the integer integerValue above is controlled by the /vo11 compiler option: By default in .Net conversions from a fractional value to an integer value will round towards zero, so the value will then be 1. If you enable the compiler option /vo11 then the fractional number will be rounded to the nearest even integral value, so the value of integerValue in the example will be 2. This is not new. We have made a change in build 2.13, to make sure that this difference is no longer determined at runtime for the X# numeric types but at compile time. In earlier builds this was handled inside conversion operators from the FLOAT and CURRENCY types in the runtime. These classes choose the rounding method based on the /vo11 setting from the main program which is stored in the RuntimeState object. However that could lead to unwanted side effects when an assembly was compiled with /vo11 but the main program was not. This could happen for example with ReportPro or bBrowser. If the author of such a library now chooses to compile with /vo11 then he can be certain that all these conversions in his code will follow rounding to zero or rounding to the nearest even integer, depending on his choice.
-
-
The DebuggerDisplay attribute for Compile Time Codeblocks has changed. You now see the source code for compile time codeblocks in the debugger.
-
- Bug fixes
-
-
Fixed a code generation issue with ASYNC/AWAIT (#1049)
-
Fixed an Internal compiler error with Evaluate() in CODEBLOCK in VFP dialect (#1043)
-
Fixed an Internal compiler error with UDCs incorrectly inserted after an END FUNCTION statement
-
Fixed a problem in the preprocessor with #region and #endregion in nested include files (#1046)
-
Fixed some problems with evaluating DEFINEs based on the order they appear (#866, #1057)
-
Fixed a compiler error with nested BEGIN SEQUENCE .. END SEQUENCE statements (#1055)
-
Fixed some problems with codeblocks containing complex expressions (#1056)
-
Fixed problem assigning function to delegate, when /undeclared+ is enabled (#1051)
-
Fixed a bogus warning when defining a LOCAL FUNCTION in the Fox dialect (#1017)
-
Fixed a problem with the Linq Operation Sum on FLOAT values (#965)
-
Fixed a problem with using SELF in an anonymous method/lamda expression (#1058)
-
Fixed an InvalidCastException when casting a Usual to a Enum defined as DWord (#1069)
-
Fixed incorrect emitted code when calling AScan() with param nStart supplied and similar functions (#1062, #1063)
-
Fixed a problem with resolving the correct one form overloads of the same function that span across different assemblies (#1079)
-
Fixed unexpected behavior of the preprocessor with #translate for specific XBase++ code (#1073)
-
Fixed a problem with unexpected behavior of "ARRAY OF" (#885)
-
Fixed some issues with calling specific overloads of functions accepting an ARRAY as a first argument (#1074)
-
Fixed a bogus XS0460 error when using the PUBLIC keyword on a method (#1072)
-
Fixed incorrect behavior when enabling Named Arguments option (#1071)
-
Fixed Access violation when calling a function/method with DECIMAL argument with default value (#1075)
-
Fixed some issues with #xtranslate not recognizing the Regular match marker in the preprocessor. Also fixed an issue with recognizing the double colon (::) inside expression tokens in the preprocessor. (#1077)
-
Fixed some issues with declaring arrays in the VFP dialect (#848)
-
-
- Runtime
- Bug fixes
-
-
Fixed some incompatibilities with VO in the Mod() function
-
Fixed an exception with Copy to array in the VFP dialect when dimensions do not match (#993)
-
Fixed a seeking problem with SetDeleted(TRUE) and DESCEND order (#986)
-
Fixed a problem with DataListView incorrectly showing (empty) deleted records with SetDeleted(TRUE) (#1009)
-
Fixed problem with SetOrder() failing with SYMBOL argument (#1070)
-
Reverted a previous incorrect change in the SDK in DBServer:FieldGetFormatted() (#1076)
-
Fixed several issues with StrEvaluate(), including not recognizing MEMVARs with underscores in their names (#1078)
-
Fix for a problem with InList() and string values (#1095)
-
The Empty() function now returns false for the values .NULL. and DBNull.Value to be compatible with FoxPro
-
Fixed a problem with GetDefault()/ SetDefault() to make them compatible with Visual Objects (#1099)
-
-
- New Features
-
-
Enhancements for Unicode AnyCpu SQL classes (#1006):
-
Added a property to open a Sqlselect in readonly mode. This should prevent Append(), Delete() and FieldPut()
-
Implemented delay creating InsertCmd, DeleteCmd, UpdateCmd until really needed
-
Added callback mechanism so customers can override the commandtext for these command (and for example route them to stored Procedures)
-
When a late bound method call cannot be resolved because the method is overloaded then a better error message is now generated that also includes the prototypes of the methods found (#1096)
-
-
-
- FoxPro dialect
-
-
Added ADatabases() function
-
- Visual Studio Integration
- New features
-
-
You can now control how indenting is done through the Tools/Options Text Editor/X# option pages. We have added several options that control indenting of your source code. You can also set these from an .editorconfig file if you want to enforce indenting rules inside your company.
-
We have now added extensive code formatting options to the source code editor. See Tools/Options/Text Editor/X#/Indentation for available options (#430)
-
We have implemented the option "Identifier Case Synchronization". This works as follows: The editor picks up the first occurrence of an Identifier (class name, variable name etc) in a source file and make sure that all other occurrences of that identifier in the same source file use the same case. This does NOT enforce casing across source files (that would be way too slow)
-
We have added color settings to the VS Color dialog for Matched braces, Matched keyword and Matched identifiers. Open the Tools/Options dialog, Choose Environment/Fonts and Colors and look for the colors in the listbox that start with the word "X#". You can customize these to your liking.
-
X# projects that use the Vulcan Runtime now have a context menu item that allows you to convert them to the X# runtime. Standard Vulcan assemblies will be replaced with the equivalent X# runtime assemblies. If you are using 3rd party components such as bBrowser or ReportPro then you need to replace the references to these components yourself.(#32)
-
We have added an option to the language page of the project properties to set the new /allowoldstyleassignments commandline option for the compiler
-
-
- Bug fixes
-
-
Fixed a problem with Get Latest Version for solution that is under TFS (#1045)
-
Fixed WinForm designer changing formatting in main-prg file (#806)
-
Fixed some problems with code generation in the WinForms designer (#1042, #1052)
-
Fixed a problem with formatting of DO WHILE (#923)
-
Fixed problem with Light Bulb "Generate default constructor" feature (#1034)
-
Fixed problem with ToolTips in the Debugger. We now parse the complete expression from the first token until the cursor location. (#1015)
-
Fixed some remaining intellisense issues with .Net array locals defined with VAR (#569)
-
Fixed a problem with indenting not working correctly in some cases (#421)
-
Fixed a problem with auto outdenting (#919)
-
Several improvements to keyword pair matching (#904)
-
Fixed a problem with Code Completion showing also static members after typing a dot in "ClassName{}." #1081
-
Fixed a performance Issue when typing . for .and. (#1080)
-
Fixed a problem with the navigation bar while typing new classes/methods (#1041)
-
Fixed incorrect info tooltips on keywords (#979)
-
Fixed a possible VS freeze when using "Clean Solution" (#1053)
-
Fixed incorrect positioning of caret in eventhandlers in the form designer (#1092)
-
Fixed a problem with the form designer failing to open forms after creating a new one (#1093)
-
Right Click on a packages.config file and choosing the option "Migrate to packagereferences" did not work because inside Visual Studio there is a hardcoded list of supported project types. We are now "faking" the projecttype to make VS happy and enable the wizard.
-
- Build System
-
-
The XSharp.Build.Dll, which is responsible for creating the command line when compiling X# projects in VS, was not properly passing the /noconfig and /shared compiler options to the compiler. As a result the shared compiler was not used, even when the project property to use the Shared Compiler was enabled. Also the compiler was automatically including references to all the assemblies that are listed inside the file xsc.rsp, which is located inside the XSharp\bin folder. You may experience now that assemblies will not compile because of missing types. This will happen if you are using a type that is inside an assembly that is listed inside xsc.rsp. You should add explicit references to these assemblies in your X# project now.
Fixed a bug in the code generation for handling FoxPro array access with parenthesized indices (#988, #991)
-
The compiler was generating incorrect warnings for locals declared with IS. This has been fixed.
-
The compiler was not reporting an error on invalid usage of the OVERRIDE modifier on ACCESS/ASSIGNs, this has been fixed (#981)
-
Fixed inconsistent behavior in reporting warnings and errors in several cases when converting from various numeric data types to another (#951, #987)
-
Fixed some "failed to emit module" issues with iif() statements in some cases (#989)
-
Fixed a problem with compiling X# code scripts (#1002)
-
Fixed a problem with using classes for some specific assemblies in the macro compiler (#1003)
-
Fix an incorrect error message when adding an INT to a pointer in AnyCPU mode (#1007)
-
Fixed a problem with casting STRING to PTR syntax (#1013)
-
Fixed a problem with PCount() when passing a single NULL argument to a CLIPPER function/method (#1016)
-
- New Features
-
-
We have added support for the TEXT .. ENDTEXT command in all dialects. Please note that there are several variations of this command. One variation work in ALL dialects (TEXT TO varName). Other variations depend on the dialect chosen. We have moved the support for TEXT .. ENDTEXT now also from the compiler to the preprocessor. This means that there are also 2 new preprocessor directives, #text and #endtext (#977, #1029)
-
Implemented new compiler option /vo17, which implements a more compatible to VO behavior for the BEGIN SEQUENCE..RECOVER command (#111, #881, #916):
-
-
For code that contains a RECOVER USING, a check is made for wrapped exceptions. When the exception is not a wrapped exception then a function in the runtime is called (FUNCTION _SequenceError(e AS Exception) ASUSUAL) that can process the error. It can for example call the error handler, or throw the error
-
When there is no RECOVER USING clause , then the compiler generates one and from within this generated clause detects if the RECOVER was reached with a wrapped exception or a normal exception. For wrapped exceptions it gets the value and calls a special function in the runtime (FUNCTION _SequenceRecover(uBreakValue ASUSUAL) ASVOID). When the generated recover is called with a 'normal' exception then _SequenceError function from the previous bullet is called.
-
-
-
-
We have added support for CCALL() and CCALLNATIVE()
-
The #pragma directives are now handled by the preprocessor. As a result you can add #pragma lines anywhere in your code: between entities, inside the body of an entity etc.
-
- Runtime
- Bug fixes
-
-
Changed the prototype for AdsGetFTSIndexInfo (#966)
-
Fixed a problem with TransForm and decimal types (#1001)
-
Added several missing return types in the VFP assembly
-
Fixed a problem with browsing a DBFVFP table in the FoxPro dialect
-
Fixed an inconsistency with handling values provided by BREAK commands inside surrounding BEGIN...RECOVER statements, depending on if early or late bound call is used (#883)
-
Fixed a problem with floating point format when assigning a System.Decimal value to a USUAL var (#1001)
-
Fixed a runtime error with DbCopyToArray() when copying to an array that has more columns than the table, in the FoxPro dialect (#993)
-
Fixed a problem with the typecast expression and numeric literals with the +/- sign in the macro compiler (#1025)
-
Fixed problem in the Late binding code where a string was sometimes passed in and not properly converted to symbol
-
IVarPut()/IVarGet() now throw an appropriate exception when trying to use an inaccessible (due to limiting visibility modifiers) property getter/setter (ACCESS/ASSIGN) (#1023)
-
Fixed an issue with IVarGet() and IVarPut() for properties that are redefined in a subclass with the NEW modifier (#1030)
-
DbDataSource now tries to lock a record when deleting or recalling the record
-
Foreach was not working correctly on properties containing collections that were returned from a late bound property access such as IVarGet()(#1033)
-
- New Features
-
-
Youcan now register a delegate in the runtime state that allows you to control how the macro compiler caches types from loaded assemblies(#998). This delegate has to have the format:
XSharp.RuntimeState.MacroCompilerIncludeAssemblyInCache := { a => DoNotCacheDevExpress(a)} FUNCTION DoNotCacheDevExpress(ass asAssembly) ASLOGIC) // do not cache DevExpress assemblies RETURN ass:Location:IndexOf("devexpress", StringComparison.OrdinalIgnoreCase) == -1
-
- Compatible VO SDK
-
-
Fixed an issue where SetAnsi(FALSE) causes SingleLineEdit controls with pictures to show random characters when entering umlauts (#1038)
-
- Typed VO SDK
- There are 2 new properties for the SQLSelect class.
-
-
ReadOnly - which makes the SQLSelect Readonly
-
BatchUpdates - which controls how updates are handled
-
- ReadOnly cursors and delayed creation of command objects
- Previously the SQLSelect class created DbCommand objects to update, insert and delete changes made to a cursor immediately when the result set was opened. That could cause problems when a complex query was used to select data, because the DbCommandBuilder object could not figure out how to create these statements.
- We are now delaying the creation of these commands until the first time they are needed. At the same time we have now added a ReadOnly property with a default value of FALSE.
- If you set ReadOnly to true then:
-
-
Calling FieldPut(), Delete() and Append() will generate an error with Gencode EG_READONLY.
-
No Command objects will be created for the SQLSelect, because the cursor cannot be updated.
-
- If ReadOnly remains FALSE then the command objects to update, insert and delete will be created the first time they are needed. These commands are created in the __CreateDataAdapter() method. You can override this method and create the commands in your own subclass when you want. The command creation and the updates work as follows:
-
-
First a DataAdapter (of type DbDataAdapter) is created using the CreateDataAdapter method from the SQLFactory class
-
Then a CommandBuilder object (of type DbCommandBuilder) is created from the CreateCommandBuilder method of the SQLFactory class
-
Then the Insert, Delete and Update Command objects (all of type DbCommand) are created from the GetInsertCommand() etc methods from the DbCommandBuilder object. The DBCommandBuilder object takes the Select statement and creates commands with parameters based on the SQLSelect command
-
These command objects are assigned to the DataAdapter and then the DataAdapter:Update() method is called with the DataTable that is behind the SQLSelect as argument.
-
- Batch Updates
- Normally updates in a SQLSelect will be sent to the server when you move the record pointer to a new row, or when you call Update()
- If you set the BatchUpdates property to TRUE then the SQLSelect will delay sending updates to the server and will not do that for each record movement, but will wait until you call the Update() method with an argument TRUE. This will then write all the buffered changes to the server. This may then also trigger the creation of the DBCommand objects (see before). If your table has autoincrement fields then you may want to call Requery() afterwards to see the newly assigned key values.
- Visual Studio Integration
- Bug fixes
-
-
Fixed the handling for project property pages for flavored projects (#992)
-
When trying to start the debugger with a non existing working directory or program file name, now an appropriate error is displayed (#996)
-
Fixed a problem with the form designer generating sometimes invalid code with #regions (#1020, #935)
-
The WinForms designer now by default adds the OVERRIDE keyword modifier to the generated Dispose() method (was added in the template) (#1004)
-
Due to a changed threading model inside the latest VS2022 releases, error messages were sometimes not shown in the output window and the error list. This has been fixed
-
Fixed a problem in the windows forms designer code generation with nested classes inside the main form class (#1031).
-
Fixed problem with windows forms editor failing to open form with command based on UDC (#1037).
-
- Sourcecode Editor
-
-
Type lookups on full names were sometimes failing because the fullname was defined as case sensitive (#978)
-
Nested type lookup was sometimes failing. This has been fixed.
-
The indenting options can now also be overridden in the .editorconfig file (#999)
-
When a source file was loaded in the editor then the combo boxes with types and members were not activated until the caret was moved in the buffer (#995)
-
The member combobox in the editor was getting confused for code that contains local functions or local procedures.
-
Fixed a lookup problem for expressions inside a conversion or cast with a keyword, such as DWORD( SomeExpression). There were no quick info tips for the expression inside the parentheses for the conversion (#997)
-
Fixed an intellisense problem with DATATYPE(<expression>) conversion expressions (#997)
-
Fixed a problem with properties declared with the => symbol in their implementation causing Navigation Bar contents to be incomplete (#1008)
-
Fixed several issues with code folding and formatting (#975)
-
Fixed problem with typing a comma inside an argument list did not invoke the Parameters Tooltip (#1019)
-
Fixed some issues with the detection of variable types for the VAR keyword (#903)
-
Fixed an Intellisense problem with typing ":" or "." inside a string literal (#1021)
-
Fixed a problem with unknown identifiers sometimes causing bogus member completion list to show (#1022)
-
Pressing CTRL+SPACE in the editor now always invokes a code completion list (#957)
-
- New Features
-
-
Added options to insert page and reorder pages in a tabcontrol, in the VOWED (#1024)
-
We have updated the WPF Application template. The Main window is now called "MainWindow".
-
Added the following new settings to the .editorconfig file to set indentation options (#999).
-
-
-
indent_entity_content (true or false)
-
indent_block_content (true or false)
-
indent_case_content (true or false)
-
indent_case_label (true or false)
-
indent_continued_lines (true or false)
-
-
- VOXporter
-
-
The VOXporter now correctly enabled or disables the Allow MEMVAR/Undeclared vars compiler options, if they were enabled in the VO app (#1000)
Fixed an internal compiler error with CLIPPER calling convention delegates (#932)
-
Fixed an AccessViolationException at runtime with the Null-conditional operator ?. on a usual property (#770)
-
[XBase++ dialect] Fixed a problem with parsing method declarations with parentheses (#927)
-
[XBase++ dialect] Fixed a problem with parsing the (obsolete in X#) ANNOUNCE and REQUEST statements (#929)
-
[XBase++ dialect] Fixed a problem with parsing INLINE ACCESS and ACCESS ASSIGN statements (#926)
-
[VFP dialect] Fixed a problem with parsing FOR EACH statements containing "M." variables usage where the variable was not typed in the FOR EACH line (#911) .
-
Fixed a problem where the PPO files contains some output twice, when a single UDC was producing several statements (#933)
-
Fixed some issues with the "FIELDS" clause in several UDCs (#931, #795)
-
Fixed a problem in the preprocessor with parentheses in #xtranslate directives (#963)
-
Fixed several more issues with #command and #translate directives (#915)
-
In some cases, the compiler would emit code that does not throw a runtime exception, when casting/converting from one type to an incompatible one. This has been fixed (#961, #984)
-
The compiler was not reporting narrowing conversion warnings in several cases, this has been fixed (#951)
-
The compiler was not reporting signed/unsigned conversion warnings. This has been fixed (#971)
-
Fixed a problem that could lead to the "Could not emit module" error message, caused by NULL values inside IIF() expressions(#989)
-
- New features
-
-
Added compiler option /noinit to not generate $Init calls for libraries without INIT procedures for the sake of postponed loading (#854)
-
Added preprocessor support for #stdout and #if. (#912)
-
The full contents of #include files is now written to the ppo file (#920)
-
When a parser error occurs because an identifier was replaced by a define with the same name, then the compiler will now generate a second warning.
-
If a header file contains actual code and this code is called during debugging then the debugger will now step into the header file when debugging this code. Previously all statements were linked to the #include line from the place where the header was included. (#967)
-
When you are suppressing compiler errors with the /vo11 (Compatible numeric conversion) compiler option you will now see a XS9020 "narrowing" warning indicating that a runtime error may happen or that data may be lost.
-
When you are suppressing conversion errors between signed and unsigned integers with /vo4 then you will now see as XS9021 warning indicating that data may be lost or an overflow error may occur.
-
- Visual Studio Integration
- New features
-
-
The source code editor now also supports the new #if and #stdout preprocessor commands (#912)
-
There is new "Lightbulb" option to generate constructors for classes.
-
- Bug Fixes
-
-
Fixed a problem with specifying custom preprocessor defines in the project properties (#909)
-
The VO-style editors now retain existing "CLIPPER" clause to methods/constructors when generating code (#913)
-
Fixed incorrect parsing of classes as nested to each other (#939)
-
Fixed a problem with using embedded variables in the form of $(SomeName) in the project settings (#928)
-
Fixed a problem where deleting items from a project would fail.
-
Fixed a problem resolving the DLL produced by project files from other development languages, in particular SDK style C# projects (#950)
-
Fixed a problem with quick info tooltip after an unrecognized identifier (#894)
-
Fixed a problem with the editor incorrectly adding parentheses after auto typing a property (#974)
-
Fixed extremely slow editor response when creating a new line after an #endif directive (#970)
-
Fixed some intellisense issues with .Net array types (#569)
-
Fixed a problem with the DevExpress DocumentManager control at design time (#976)
-
Fixed an ArgumentNullException in the Output window when "Show output from" is set to "Extension" (#940)
-
- Runtime
- New features
-
-
Added a constructor with IEnumerable to the array class (#943)
-
Implemented missing functions AdsSetTableTransactionFree() and AdsGetFTSIndexInfo() (#966)
-
Moved functions GetRValue(), GetGValue() and GetBValue() from the Win32API library to XSharp.RT, so they can be used by AnyCPU code (#972)
-
[VFP dialect] Implemented function APrinters() (#952)
-
[VFP dialect] Implemented function GetColor() (#973)
-
[VFP dialect] Implemented functions Payment(), FV() and PV() (#964)
-
[VFP dialect] Implemented commands MKDIR, RMDIR and CHDIR (#614)
-
- Bug fixes
-
-
Fixed a problem with the ListView TextColor and TextBackgroundColor ACCESSes in the SDK (#896)
-
Fixed a problem with soft Seek not respecting order scope when to strict key is found (#905)
-
Fixed DBUseArea() search logic for files in various folders. Also SetDefault() is no longer initialized with the current directory (for VO compatibility) (#908)
-
Fixed problem with creating dbfs with character fields with length > 255 (#917)
-
Fixed a problem with the buffered read system in some cases when a dbf was being read, closed, overwritten and then reopened (#968)
-
Fixed a VO compatibility problem with how DBSetIndex() changes the active order when opening index files (#958)
-
Fixed a problem with db append, copy etc, when both source and destination files have the same structure and include a memo file (#945)
-
Fixed an incorrect result of DBOrderInfo(DBOI_ORDERCOUNT) with a non existing or not open index file (#954)
Fixed some problems with COPY TO ARRAY command in the FoxPro dialect (#673)
-
Fixed a problem with using a System.Decimal type on a SWITCH statement (#725)
-
Fixed an internal compiler error with Type() in the FoxPro dialect (#840)
-
Fixed a problem with generating XML documentation (#783, #855)
-
Prevented a warning from appearing for members of SEALED classes when /vo3 (all members VIRTUAL) is enabled (#785)
-
Fixed problems with assigning and comparing "ARRAY OF <type>" vars to NULL_ARRAY (#833)
-
Fixed some issues with passing arguments by reference with the @ operator and/or using it as the AddressOf operator (#810, #899, #902)
-
Fixed a problem resolving parameters passed by reference with the @ operator when the function/ method had a parameter of the pointer type (#899, #902)
-
- New features
-
-
Added compiler option (-enforceoverride) to make the OVERRIDE modified mandatory when overriding a parent member (#786, #846)
-
The compiler now reports an error when using String2Psz() and Cast2Psz() in a non local context (since such PSZs are being released on exiting the current entity) (#775)
-
FUNCTIONs and PROCEDUREs now support the ASYNC modifier (#853)
-
You can now suppress the automatic generation of the $Init1() and $Exit() functions by passing the compiler commandline option -noinit (#854). This is NOT yet supported in the VS Properties dialog
-
Added support for the ASTYPE operator also for USUAL vars (#857)
-
Allowed specifying AS <type> clause in PUBLIC var declarations (ignored by the compiler, but used by the editor in the future for intellisense) (#853)
-
The AS <datatype> OF <classlib> clause is now also supported for several other FoxPro compatible commands, such as PARAMETERS and PUBLIC. Since these variables are untyped at runtime by nature, the clause is ignored by the compiler and a warning is shown.
-
- Build System
- Bug Fixes
-
-
Running MsBuild on a X# WPF project could fail (#879)
-
- Visual Studio Integration
- New features
-
-
We have added Visual Studio integration for VS 2022
-
We have added support for Package References
-
Now XML comments are automatically inserted in the editor when the user types "///". (#867, #887) Conditions:
-
-
Cursor must be on a line before the start of an entity
-
Cursor must NOT be before a comment line
-
-
-
-
Now the tooltip on a class includes also information about the parent class and implemented interfaces (if any) (#860)
-
We have added tooltips, parameter completion etc for the pseudo functions that are built into the compiler, such as PCount() and String2Psz().
-
We have added a first version of Lightbulb tips. For now to implement missing interface members and to convert a field to a Property. More implementations and configuration options will follow
-
We have added a new dialog to configure source code formatting with visual examples of the effects of the options.
-
We have added the ability to log operations of the X# VS integration to the Windows debug window and/or a logfile. If you are experiencing unexplainable problems we will contact you and tell you how to enable these options, so you can send us a log file that shows what happened before a problem occurred inside Visual Studio. We have used Serilog for this.
-
The Highlight Word feature now is case insensitive and no longer hightlights words that are part of a comment, string or inactive editor region
-
We have added 'Brace Completion' to the editor
-
- Bug Fixes
-
-
Fixed some problems with the Format Document command (#552)
-
Fixed several issues with Parameter Tooltips (#728, #843)
-
Fixed problem with code completion list showing even for not defined vars/identifiers (#793)
-
Fixed member completion and parameter tooltips with chained expressions (#838)
-
Fixed recognition of type for VAR locals in some cases (#844)
-
Fixed member completion and tooltip info problems with VOSTRUCT vars (#851)
-
Fixed a problem with ignoring Line Breaks in XML Comments (#858)
-
Fixed some WinForms designer problems with CHAR properties (#859)
-
Fixed a problem with Goto Definition not working correctly with SUPER() constructor calls (#862)
-
Fixed an error with the Rebuild Intellisense Database command, when the solution contains a space in the path (#865)
-
Goto Definition for types from external assemblies was failing when there was more than one copy of VS running at the same time.
-
Fixed a problem with a VOSTRUCT some times confusing the parser (#868)
-
Fixed some more problems with quickinfo and member completion (#870)
-
Fixed a problem in the Windows Forms designer (#873)
-
Fixed an intellisense problem with ENUMs using no MEMBER keywords (#877)
-
Fixed a member completion problem with inherited exception types (#884)
-
If an XML topic had sub elements of type <see> or other these were not shown in the editor. This has been fixed (#900)
-
Unbalanced braces were sometimes matched in the editor with keywords. This has been fixed (#892)
-
Line separators were sometimes flickering. This has been fixed (#792)
-
When parsing for local variables we were not processing the include files. This could lead to a situation where a local that was declared in a conditional block (#ifdef SOMEVAR) was not found. This has been fixed. The editor parser now includes the header files and #defines and #undefines found in the code even when parsing a part of the source file (#893)
-
#include lines are now included in the fields/members combobox in the editor (when fields are shown). They are also saved to the intellisense database.
-
The editor was trying to show QuickInfo tooltips when the cursor was over an inactive preprocessor region (#ifdef). This no longer happens.
-
- Runtime
- Bug fixes
-
-
Fixed DBFCDX corruption that could happen with simultaneous updates (#585)
-
Fixed a problem opening FoxPro tables with indexes on nullable fields (#631)
-
The BlobGet() function was returning a LOGIC instead of the actual field value (#681)
-
Greatly improved speed of index creation with large number of fields in the index expression (#711)
-
Fixed some problems with FieldPutBytes() and FieldGetBytes() (#797)
-
DBSeek() with 3rd param (lLast) TRUE had incorrect behavior in some cases (#807)
-
Fixed a potential NullreferenceException that could happen when creating indexes (#849)
-
Improved indentation in the text produced by the method Error.WrapRawException() (#856)
-
Fixed a runtime problem when converting .Net Array <-> USUAL (#876)
-
DbInfo() was returning TRUE even when an info enum was not supported.(#886)
-
Fixed also a possible DBFNTX corruption problem (#889)
-
DbEval() could fail in FoxPro when the codeblock was returning NIL or was VOID (#890)
-
Fixed a problem with Softseek and descending indexes.
-
Fixed a problem where incorrect scope expressions could lead to unexpected results. Now the server goes to (and stays at) EOF with an incorrect scope.
-
Fixed a problem with accessing FoxPro arrays with the parenthesis operators in a macro expression (#805). Please note that for this to work you have to compile the main program with /fox2
Fixed a problem introduced in 2.9.0.2 with define symbols not respecting the /cs compiler option in combination with the /vo8 compiler option (#816)
-
Fixed an internal compiler error with assignment expressions inside object initializers when the /fox2 compiler option is enabled (#817)
-
Fixed some problems with DATEs in VOSTRUCTs (#773)
-
Fixed a problem in the preprocessor that would occur when using a list rule like FIELDS <f1> [,<fn> ] in the middle of a UDC.
-
Fixed a problem compiling UDCs such as SETCENTURY &cOn because cOn was not parsed as an identifier but as a keyword.
-
- New features
-
-
There is a new result marker (the NotEmpty result marker) in the preprocessor that does the same as the regular result marker, but writes a NIL value to the output when the (optional) match marker is not found in the input. This can be used when you want to make the result a part of an IIF() expression in the output, since the sections inside an IIF expression may not be empty. The result marker looks like this: <!marker!>
-
Using a Restricted match marker as the first token in an UDC was not allowed before. This has been fixed. You can now write a rule like this, which will output the keyword (SCATTER, GATHER or COPY) followed by the stringified list of options.
-
- #command <cmd:SCATTER,GATHER,COPY> <*clauses*> => ? <"cmd">, <"clauses"> FUNCTION Start ASVOID SCATTER TO TEST // is preprocessed into ? "SCATTER" , "TO TEST" RETURN
- Visual Studio Integration
- Bug Fixes
-
-
Fixed a problem introduced in 2.9.0.2 with code generation for WPF projects (#820)
-
Fixed a VS freezing problem after building (#819)
-
Fixed some problems with code collapsing and the navigation bar for source files that contains a SELF property (#825)
-
Fixed a problem with the form designer emitting invalid code when the form prg contains nested classes (#828)
-
Fixed a problem with code completion showing the wrong members when opened just left to a closing paren (#826)
-
Fixed a VS crash when clicking on a generic class (#827)
-
Fixed a problem with the keyword colorization for expressions such as SETCENTURY &cOn, where &cOn was colored in the keyword color.
-
Parameter tips for nested function calls required an extra space before the name of the nested function (#728)
-
Fixed a problem with the form designer deleting delegates and other nested types in the form.prg (#828)
-
The background process to load the types in the ClassView / ObjectView windows was slowing down the VS performance. This has been disabled for now.
-
Fixed type lookup for Generic types.
-
Hovering the mouse over a constructor keyword was showing a tooltip for the class and not for the constructor. This has been fixed.
-
Fixed an issue in the code generator for Windows Forms for literal characters with special values (such as '\0') (#859)
-
Fixed an exception in the project system when the project system was initialized in the background (for example when no X# projects were opened) (#852)
-
Fixed missing code completion for the LONGINT and SHORTINT keywords (#850)
-
The context menu option "View in Disassembler" is now only shown for X# projects
-
Fixed code generator problem with ARRAY OF <type> (#842)
-
Fixed a performance problem when clicking on code in the editor (#829)
-
Fixed a problem with loading Windows Forms when the lookup of a nested type failed.
-
-
- New features
-
-
We have added a context item to the project context menu in the solution explorer to edit the project file. This will unload the project when needed and then open the file for editing.
-
The Rebuild Intellisense Database menu option in the Tools/XSharp menu now unloads the current solution, deletes the intellisense database and reopens the solution to make sure that the database is recreated correctly.
-
We have made some changes to the process that parses the source code for a solution in the background.
-
Generic Typenames are now stored in the Name`n format in the Intellisense database, for example IList`1 for IList<T>
-
- Runtime
- New features
-
-
Added missing ErrorExec() function (#830)
-
Added support for BlobDirectExport, BlobDirectImport, BlobDirectPut and BlobDirectGet (#832)
-
Fixed a problem with creating DBF files with custom file extension. Also added support for _SET_MEMOEXT (#834)
-
When you do a numeric operation on two USUALs of different types we now make sure that decimal values are no longer lost (#808). For example a LONG + DECIMAL will result in a DECIMAL. See the table in the USUAL type page in this help file for the possible return values when mixed types are used.
-
-
-
- Bug Fixes
-
-
Fixed a problem with _PrivateCount() throwing an InvalidateOperationException (#801)
-
Fixed a problem with member completion in the editor sometimes showing methods of the wrong type (#740)
-
Fixed some problems with the ACopy() function (#815)
-
Fixed a few issues that were remaining related to DATEs in VOSTRUCTs (#773)
-
- Macro compiler
- New features
-
-
Added support for the & operator (#835)
-
Added support for parameters by reference (both @ and REF are supported) for late bound method calls (#818)
-
- VOXporter
- Bug Fixes
-
-
Fixed problem with incorrectly prefixing PUBLIC declarations with "@@"
-
-
- Changes in 2.9.0.2 (Cahors)
- Compiler
- New features
-
-
The parser now supports class variable declarations and global declarations with multiple types(#709)
If you are using our parser you should be aware that the ClassVarList rule has disappeared and that the ClassVars, VoGlobal and ClassVar rules have changed.
-
-
-
We have added a command to fill a foxpro array with a single value
-
- STORE <value> TOARRAY <arrayName>
-
-
-
When you create a VOSTRUCT or UNION that contains a DATE field, then the compiler will now use the new __WinDate structure that is binary compatible with how DATE values are stored inside a VOSTRUCT or UNION in Visual Objects (#773)
-
It is now possible to use parentheses for (instead of brackets) accessing ARRAY elements in the FoxPro dialect. The compiler option /fox2 must be enabled for that to work (#746)
-
We have added support (for the FoxPro dialect only) for accessing WITH block expressions inside code of a calling function / method. So you can type .SomeProperty and access the property that belongs to a WITH BLOCK expression inside the calling code. To use this Late Binding must be enabled, since the compiler does not know the type of the expression from the calling code (#811).
-
-
- Bug fixes
-
-
When you use the NEW or OVERRIDE modifier for a method where no (virtual) method in a parent class exists an error will now be generated (#586, #777)
-
Fixed a problem with LOGICAL AND and OR for USUAL variables in an array (#597)
-
Error messages and Warnings for some compiler generated code (such as Late bound code) were not always pointing to the right line number, but to the first line in the body of the method or function. This has been fixed. (#603)
-
Fixed a problem incorrect return values for IIF expressions (#606)
-
Fixed a problem in the compiler when parsing multiple method names on a DECLARE METHOD line (#708)
-
Fixed a problem in the FoxPro dialect with assigning a single value to an array to fill the array (#720)
-
Fixed a problem with the calculation of VOSTRUCT sizes when the structure contained a member of type DATE (734)
-
The previous problem caused runtime errors (#735)
-
Fixed a problem in code like this (#736) var aLen := ALen(Aarray)
-
Fixed a compiler crash when overriding CLIPPER method with STRICT for methods with typed return value (#761)
-
When the interface implementation had different casing then the definition then an incorrect error message was shown (#765)
-
Fixed a compiler crash with incorrect function parameters inside a codeblock (#759)
-
Recursive definitions of DEFINEs could result in an infinate loop inside the compiler causing a StackOverflowException(#755)
-
Fixed a problem with late bound calls and OUT parameters (#771)
-
If you compile with warning level 4 or lower then certain warnings for comparing value types to null are not shown. We have changed the default warning level to 5 now. (#772)
-
Fixed a compiler crash with multiple PRIVATE &cVarName statements in the same entity (#780)
-
Fixed a problem with possibly corrupting the USUAL NIL value when passing USUAL params by reference (#784)
-
Fixed a problem with declared PUBLIC variables getting created as PRIVATE in the FoxPro dialect (#753)
-
Fixed a problem with using typed defines as default arguments (#718)
-
Fixed a problem with typed DEFINEs that could produce constants of the wrong type (#705)
-
Fixed a problem with removing whitespace from #warning and #error directive texts (#798)
-
- Runtime
- New Features
-
-
We have added several strongly typed overloads for the Empty() function that should result in a bit better performance (#669)
-
We have added an event handler to the RuntimeState class. This event handler is called "StateChanged" and expected a method with the following signature: Method MyStateChangedEventHandler(e AS StateChangedEventArgs) ASVOID The StateChangeEventArgs type has properties for the Setting Enum, the OldValue and the NewValue. You can use this if you have to synchronize the state between the X# runtime and an external app, for example a Vulcan App, VO App or for example (this is where we are using it) with an external database server, such as Advantage.
-
We have added a new (internal) type __WinDate that is used when you store a DATE value into a VoStruct or Union. This field is binary compatible with the Julian date that VO stores inside structures and unions.
-
We have added an entry to the RuntimeState in which the compiler stores the current /fox2 compiler setting for the main app.
-
Added runtime support to support filling FoxPro arrays by assigning a single value.
-
-
- Bug Fixes
-
-
Fixed a problem (incompatibility with VO) in the Descend() function (#779) - IMPORTANT NOTE: If you are using Descend() in dbf index expressions, then those indexes need to be reindexed!
-
Late bound code that was returning a PSZ value was not correctly storing that inside a USUAL (#603)
-
Fixed a problem in the Cached IO that could cause problems with low level file IO (#724)
-
The VODbAlias() function now returns String.Empty and not NULL when called on an area where no table is open. (#733)
-
Fixed a compatibility problem with the MExec() function (#737)
-
The M-> prefix was not recognized correctly inside codeblocks (#738)
-
The Explicit DATE -> DWORD cast was returning an incorrect value for NULL_DATE.
-
Fixed a problem with late bound calls and OUT parameters (#771)
-
Added a new __WinDate type that is used to store DATE values inside a VOSTRUCT or UNION. (#773)
-
Fixed several problems with FoxPro arrays
-
Removed TypeConstraints on T for functions that manipulate __ArrayBase<T>
-
Fixed a problem with Directory() including files that match by shortname but not by longname (#800)
-
- RDDs
-
-
When creating a new DBF with the DBFCDX driver an existing CDX file is not automatically deleted anymore (#603)
-
Fixed a problem with updating memo contents in DBFCDX (#782)
-
Fixed a runtime exception when creating DBFCDX index files with long filenames (#774)
-
Fixed a problem with with DBSeek() with active OrderDescend() finding even deleted records
-
Fixed a problem with a missing call to AdsClearCallbackFunction() in the ADS RDD in OrderCreate() (#794)
-
Fixed a problem with VODBOrdCreate function failing it the cOrder parameter contains an empty string (#809)
-
- Macro compiler
-
-
Fixed a problem in the Preprocessor
-
Added support for parameters passed by reference with the @ operator
-
Added support for M->, _MEMVAR-> and MEMVAR-> prefixes in the macro compiler
-
When the Macro compiler finds 2 or more functions with the same name it now uses the same precedence rules that the compiler uses:
-
-
Functions in User Code are used first
-
Functions in the "Specific" runtimes (XSharp.VO, XSharp.XPP, XSharp.VFP, XSharp.Data) take precedence over the ones inside XSharp.RT and XSharp.Core
-
Functions in XSharp.RT take precedence over functions inside XSharp.Core
-
-
- Visual Studio Integration
- In this build we have started to use the "Community toolkit for Visual Studio extensions" that you can find on GitHub. This toolkit contains "best practices" for code for VS Extension writers, like we are. As a result more code is now running asynchronously which should result in better performance.
- We have also started to remove 32 bit specific code that would become a problem when migrating to VS 2022 which is a 64 bits version if Visual Studio that is expected to ship in November 2021.
- New features
-
-
Added several new features to the editor
-
-
The editor can now show divider lines between entities. You can enable/disable this in the options dialog (#280)
-
Keyword inside QuickInfo tooltips are now colored (#748)
-
Goto definition now also works on "external" types. The editor generates a temporary file that contains the type information for the external type. In the options dialog you can also control if the generated code should contains comments (as read from the XML file that comes with an external DLL). (#763)
-
You can control which keyword is used for PUBLIC visibility from the Tools/Optons menu entry (PUBLIC, EXPORT or No modifier at all)
-
You can control which keyword is used for PRIVATE visibility from the Tools/Optons menu entry (PRIVATE or HIDDEN).
-
-
-
-
The various code generators inside VS now follow the capitalization rules from the source code editor.
-
The intellisense database now has views that return the unique namespaces in the source code and in the external assemblies
-
The X# specific menu points in the Tools menu have been moved to a separate submenut
-
Added option for the WinForms designer to generate backup (.bak) files of form.prg and form.designer.prg files when saving (#799)
-
- Bug Fixes
-
-
Fixed several problems in the editor:
-
-
We have made several improvements to increase the speed inside the editor (#689, #701)
-
Fixed a problem in the type lookup of variables for FOREACH loops (#697)
-
Parameter tips were not shown for methods selected from a completion list (#706)
-
Keyword case synchronization did not work when the keyword was not followed by a space (#722)
-
Goto definition always went to line 1 / column 1 in the file where a function was defined (#726)
-
Code completion for Constant members of classes (#727)
-
QuickInfo for DEFINES (#730, #739)
-
VOSTRUCT Member completion with the '.' operator (#731)
-
The ENUM and FUNC keywords are now recognized as identifier and not case synchronized in these cases.(#732)
-
Fixed a problem when opening files (#742)
-
Fixed parameter tip display for default values NULL, NULL_DATE and NULL_OBJECT (#743)
-
Fixes broken parameter tips for constructors (#744)
-
Nested classes were not always handled correctly by the intellisense (#745)
-
Fixed a problem in the type lookup of variables declared with ARRAY OF <something> (#749)
-
The Editor could sometimes "freeze" when the buffer contained invalid code (#751)
-
Non-existing namespaces would produce a bogus completion list (#760)
-
Fixed an editor exception in some cases when typing invalid code (#791)
-
-
-
-
The code generator for Windows Forms was replacing tab characters with spaces. This has been fixed.(#438)
-
Fixed a problem with the Form Designer corrupting code that contains EXPORT ARRAY OF <type>
-
Fixed a problem with the Form Designer that when removing an event handler in the editor, some code was deleted (#812)
-
Fixed a problem with the Form Designer converting EXPORT, INSTANCE and HIDDEN keywords to PUBLIC and PRIVATE (#802)
-
- VO-Compatible Editors
-
-
Now all VO-compatible editors support full Undo/Redo functionality. Also added cut/copy/paste functionality to the Menu editor
-
Fixed several visual problems with VOWED controls in Design and Test mode (#741)
-
Fixed a VS crash when Alt-Tabbing out of the editors, with the Properties window having focus (#764)
-
Adjusted ComboBoxEx controls to have the same fixed height, as in VO. Also allowed the previous behavior, when the user has manually increased the height by more than 50 pixels, then this height is being used instead (#750)
-
Added a bitmap thumbnail for the "Button Bmp" property of the Menu Editor in the Properties Window
-
Added support for specifying a Ribbon in the Menu Editor. The ribbon (bitmap) to be used needs to be specified as a filename in the properties of the Menu's main item (#714)
-
Fixed some issues with event code generation in the Window Editor (#441, #46)
-
-
- Changes in 2.8.3.15 (Cahors)
- Compiler
- New features
-
-
You can now use the .AND. logical operator and .OR. logical operator between variable names or numbers without leading or trailing whitespace (a.AND.b)
-
The PRIVATE declaration in the FoxPro dialect no longer allows an initializer.
-
Added support for the FoxPro NULL date ( { / / }, { - - } and { . . }) in the FoxPro dialect
-
- Bug fixes
-
-
Fixed a problem with a DIM array that uses a DEFINE for its dimension (#638)
-
Fixed a problem with the FoxPro PUBLIC ARRAY command (The ARRAY keyword is no longer mandatory) (#662).
-
Fixed a problem with DEFAULT(Usual) expressions as parameters for function / method calls (#664)
-
Fixed a problem with variables declared with the LOCAL declaration and dimensioned with the DIMENSION command (#683)
-
Fixed issue with overloads with the same name in different X# runtime assemblies that manifested itself with problems with FRead()(#686)
-
Fixed a problem with passing PRIVATE and PUBLIC memory variables by reference (#691)
-
Fixed a problem with PARAMETERS statement (#691)
-
Fixed a problem with real numbers (#704) that was caused by the change in handling of .AND. and .OR.
-
Fixed a problem parsing the DECLARE METHOD / ACCESS / ASSIGN lines inside class declarations.
-
Fixed a problem with truncating results for binary operators (+, -, *, /) for mixed integral types (e.g. int and word)
-
- Runtime
- Bug Fixes
-
-
The _shutdown flag in the Runtime State is now set when the system shuts down.
-
Fixed a problem with the FoxPro ALen() function (#650)
-
Added default values on several locations (#678)
-
Fixed a problem where FRead() on a file opened by an RDD would go into an endless loop (#688)
-
Fixed a problem with FieldGet() when the file is at EOF (#698)
-
Fixed a scope problem when the scope was empty and a record matching the scope was added in another workarea or by another workstation (#699)
-
Fixed a problem with the BOF setting after a Skip(0) (#700)
-
- MacroCompiler
- New features
-
-
You can now use the .AND. operator between variable names or numbers without leading or trailing whitespace
-
Added support for the FoxPro NULL date ( { / / }, { - - } and { . . }) in the FoxPro dialect
-
Strings containing .AND. and .OR. are no longer reformatted by the macro compiler (#694)
-
We have added an experimental new faster script compiler. This script compiler allows to compile statements, so no functions, classes etc. This new script compiler is much faster than the existing script compiler and uses a lot less memory. To call this script compiler use the new function ExecScriptFast() which has the same parameters as ExecScript(). You can compile multiline scripts. The compiler should recognize all statements including PARAMETERS and LPARAMETERS to receive parameters. If you are using scripts in your code we would love to hear feedback. An example of code that should work:
FUNCTION CallMe(a,b,c) ASUSUAL ? "Inside function, parameters received",a,b,c RETURN a+b+c
- Please test this new functionality and let us know what you think of it.
- Visual Studio Integration
- New Features
-
-
"Highlight word" now highlights words in the whole file when the cursor is outside of an entity (for example on the USING statements in the start of the file).
-
- Bug Fixes
-
-
Fixed a problem with displaying names of custom controls in the toolbox of the VO compatible Windows Editor
-
Fixed a problem with extra spaces when loading settings from cavowed.inf for the VO compatible Windows Editor
-
Fixed a problem with an incorrect completion list after an assignment statement (#658)
-
Fixed an exception in the editor after deleting code (#674)
-
Fixed a "freeze" problem in the VS IDE when attaching a file to the shell window (#676)
-
Fixed a problem when using dot instead of colon in VO Dialect with AllowDot (#679)
-
Fixed a problem with showing a completion list inside class (#685)
-
Fixed a performance problem in the editor (#689)
-
Fixed a problem with showing function overloads in the editor (#692)
-
Fixed a problem with intellisense after a !, .NOT. or other operator (#693)
-
Fixed a problem where the incorrect methods were shown in the completion list (#695)
-
- Tools
-
-
Fixed an issue in VOXPorter with resources and the copying to the Resources subfolder
-
-
- Changes in 2.8.2.13 (Cahors)
- Compiler
-
-
Fixed issues with extension methods that were not marked as STATIC (#660)
-
Fixed problem with IIF() expressions that returned an OBJECT and were assigned to a Decimal
-
The pragma commands were not checking for the current dialect
-
Fixed an exception in the preprocessor
-
The FoxPro LOCAL ARRAY was not generating a LOCAL variable but a PRIVATE variable.
-
Functions in XSharp.RT that are overridden in XSharp.VO, XSharp.VFP or XSharp.RT will no longer generate a warning. The version that is not in XSharp.RT will have preference
-
Enumerating a USUAL variable in a FOREACH loop will now call a runtime function that returns the ARRAY inside the USUAL or throws an error otherwise
-
Implicit conversions from OBJECT -> NUMERIC are now supported when /vo7 is enabled.
-
- Runtime
-
-
Enumerating a USUAL variable in a FOREACH loop will now call a runtime function that returns the ARRAY inside the USUAL or throws an error otherwise (#246)
-
Fixed a problem creating index with an Eval block and 0 records (#619)
-
Fixed an incompatibility with the ALen() function and array handling compared to FoxPro (#642)
-
We have fixed some issues in FoxPro AIns() function (#650)
-
We have added a ShowFoxArray() function that will be automatically called when you call ShowArray() on a FoxPro array (650)
-
Added support for OClone()
-
The _Quit() function now closes all databases and then kills the current running process (#665)
-
Fixed a problem with DbOrderInfo (#666)
-
Fixed a problem with the unary minus operator for currency values (#670)
-
Fixed a problem in the Integer function when a Currency value was sent in (#671)
-
We have added an implementation of MemCheckPtr() (#677)
-
-
- Macro compiler
-
-
Fixed a problem calling functions after a new assembly was loaded with Assembly.Load()
-
Added support for passing variables by references (not yet for functions with Clipper calling convention) (#653)
-
- VO SDK
-
-
Fixed a problem in GetObjectByHandle() in the GUI Classes(#677)
-
- Visual Studio Integration
-
-
Fixed an exception on the Build Options page inside VS (#654)
-
The project system did not write back the right property for the XML documentation generation (#654)
-
Intellisense could crash in header files (#657)
-
We have added #defines and user defined commands (#command, #translate) to the members combobox in the editor as members of the global type. You can now also do a Goto definition on a value defined with #define.
-
We have fixed a problem with member completion for enums (656)
-
We have fixed a problem with the Windows Forms Editor that could happen if another VS extension had loaded an older version of Mono.Cecil (#661)
-
Code completion was not showing instance members when the project option "Allow dot" was enables (#679)
-
The "header" new item template had a .VH extension. This has been changed to .XH
-
Fix a crash in the VO Compatible windows editor that happened with an incorrect CAVOWED.INF
-
Code completion inside parentheses for a method or function call was not working correctly
-
Improved Build Speed in Visual Studio when no files are changed (#675)
-
- Tools
-
-
VO Xporter was generating 2 lines in the .xsproj file for the output folder (#672)
Fixed issues with interpolated strings (#598, #622):
-
-
The script compiler now correctly sets the AllowDot compiler option from the current active dialect in the runtime (Core & FoxPro: AllowDot = true)
-
When compiling with DOT(.) as instance method separator then the ":" character is used inside interpolated strings to prefix the format string.
-
When compiling with COLON (:) as instance method separator then the colon can not be used to separate expressions from the format string inside interpolated strings. In that case we now support a double colon (::) between the expression and the format string. For example
-
-
- LOCAL num asLONG num := 42 ? i"num = {num::F2}" // this diplays num with 2 decimals WAIT
-
-
You can now use DATE fields inside VOSTRUCT and UNION (#595)
-
Fixed an assertion error 'UnconvertedConditionalOperator' (#616)
-
Fixed an assertion error in the compiler when the namespace "xsharp" is used (#618)
-
Fixed an "failed to emit" problem for methods defined in COM assemblies with default arguments and arguments passed by reference (#626)
-
Fixed a problem with the handling of default parameters and method calls (#629)
-
Fixed a problem where the _SizeOf() operator was not calculating the right size for a VOSTRUCT (#635). Please note that _SizeOf() can only be calculated at compile time when your application is compiled for x86 or x64 mode. When compiling for AnyCpu we will be calculating _SizeOf() at runtime.
-
Fixed a problem where the "IS Pattern" was not always working correctly for variables of type USUAL (#636)
-
- Runtime
-
-
Implemented the FoxPro Evl() function (#389)
-
DbCloseArea() was returning TRUE even when no area was open. This was incompatible with VO. We are returning FALSE now.(#611)
-
Macro compiler was not able to find functions in assemblies that were loaded dynamically (#607)
-
When a DBF file was opened "readonly" and then an index was created, then a runtime error would happen when the file was closed, because the RDD was trying to set the "production index" flag in the DBF header. This flag is no longer set for files that are opened "readonly" (#610)
-
Fixed an exception (that was caught) inside DbOrderInfo(DBOI_KEYCOUND) (#613)
-
Fixed a problem with the Workareas debug window (#625)
-
DbOrderInfo() was returning incorrect values when an index was not abailable (#627)
-
Fixed a problem with TransForm() and symbol arguments (#628)
-
Fixed a problem with the StrZero function (#637)
-
Fixed a problem with the AELement() function (#639)
-
- RDD System
-
-
Fixed a problem with indexes on workareas/cursors created with the SqlExec() function when the index expression contained "nullable" fields (#630)
-
- Macrocompiler
-
-
The macro compiler had problems finding functions that were inside an assembly that was loaded later (#607)
-
- Visual Studio Integration
-
-
Fix problem with saving dialect from General Page
-
Quick info and Goto definition were not working for members inside the same class when they were not prefixed with SELF:
-
Fix code completion for nullable types with the '?' syntax (#567)
-
Methods combobox was not correctly synchronized (#602)
-
Todo comments were not always parsed correctly, They were also included when they were part of another word or when they were not the first word on the line. This has been fixed.(#617)
-
Fix problem that "warnings as errors" was not saved from the Build properties page (#621)
-
Fix problems that would start occurring after editor window was split (#641)
-
After selecting a member of type "Assign" from the completion list the editor was incorrectly inserting a '(' character (#643)
-
Typing '(' on the declaration line of an entity (function, method) would trigger parameter completion. This has been fixed.(#643)
-
Parameter tips were not shown for Constructor calls (#645)
-
Completion list was incorrectly including static members (#646)
-
QuickInfo for external types was not including "AS Type" for the parameters (#647)
-
Fixed a problem when resolving parser options for a project that was not yet completely loaded (#649)
-
Local variables were not always recognized with their correct type in the editor (#651)
-
- Installer
-
-
The installer was adding an incorrect version of XSharp.CodeAnalysis.dll to the Global Assembly Cache. This has been fixed.
-
-
- Changes in 2.8.0.0 (Cahors)
- Compiler
- General
-
-
We have migrated to the latest version of the Roslyn source code.
-
Passing a typed variable by reference to a function/method with clipper calling convention (untyped parameters) was not updating the local variable. This has been fixed.
-
Using the @ operator in a program in the VO Dialect when the /vo7 compiler option is NOT enabled could generate code that produces an error "Cannot be boxed". (#551)
-
The generated code for NULL_PSZ and NULL_SYMBOL has been optimized (#398)
-
The generated VoStructAttribute on structures and unions had the wrong size when an element with the PSZ type was used. This has been fixed.
-
Fixed an internal compiler error when converting NULL to LOGIC
-
The _SIZEOF() operator will generate a constant now for VOSTRUCTS and UNIONS. (#545)
-
Using a keyword as field name could cause problems. For example FIELD->NEXT was not handled properly. The compiler now allows that. Of course you can also use the @@ prefix to tell the compiler that in a particular case you do not mean the keyword but an identifier.
-
-
-
Parenthesized expression that contained an expression list were not compiled correctly. This has been fixed. This could happen when you wanted to have more than one expression as part of an IIF() expression. LOCAL l ASLOGIC LOCAL v ASSTRING l := TRUE v := "abcd" ? iif (l, (v := Upper(v), Left(v,3)), (v := Lower(v), Left(v,4))) Since Roslyn (the C# compiler) does not allow an expression list inside a conditional expression, we are converting the parenthesized expression now to a function call to a local function. The expressions inside the Parenthesized expression become the body of the new local function and the compiler calls the generated local function.
-
The compiler now warns if you call a Function in a class that has a member with the same name. For example
-
-
- CLASS Test METHOD Left(sValue asSTRING, nLen asDWORD) ASSTRING RETURN "Test" METHOD ToString() ASSTRING RETURN Left("abc",2) // This will generate a warning that the function Left() is called and not the method Left(). // if you want to call the method you will have to prefix the call with SELF: ENDCLASS
- New language features
-
-
We have added support for LOCAL FUNCTION and LOCAL PROCEDURE statements. These functions and procedures become part of the statement list of another function, procedure, method etc. They have the following restrictions:
-
-
A LOCAL FUNCTION must be terminated with END FUNCTION, a LOCAL PROCEDURE must be terminated with END PROCEDURE
-
The full "signature" of normal functions is supported, so Parameters, Return type, Type Parameters and Type Parameter constraints.
-
They cannot have Attributes (they are not compiler into methods but in a special kind of Lambda expression)
-
The only valid Modifiers for a local function are UNSAFE and ASYNC
-
Because they cannot have Attributes, we also do not support untyped parameters, so all parameters must be typed
-
If you need a local function with a variable number of parameters then you can define default parameter values or use a PARAMS array
-
Local functions can access local variables from its surrounding code. Roslyn creates a special structure where it stores the variables that are shared between the local function and its surrounding code.
-
-
-
-
-
Added support for Expression bodied members. Expression body definitions let you provide a member's implementation in a very concise, readable form. You can use an expression body definition whenever the logic for any supported member, such as a method or property, consists of a single expression. An expression body definition has the following general syntax: MEMBER => expression An expression-bodied method consists of a single expression that returns a value whose type matches the method's return type, or, for methods that return void, that performs some operation. For example, types that override the ToString method typically include a single expression that returns the string representation of the current object. An example of this could be
-
- CLASS MyClass METHOD ToString() ASSTRING => "My Class" ENDCLASS
The result of this code is exactly the same as
CLASS MyClass METHOD ToString() ASSTRING RETURN "My Class" ENDCLASS
- So you could say that the => operator replaces the RETURN keyword.
-
-
-
We have added support for the Null Coalescing Operator (??) like C# has as well as the Null Coalescing assignment operator (??=). This operator does a check for != null. The operator will only work on Reference types so not on value types like USUAL, DATE and the built-in types like INT.
-
- FUNCTION Start() ASVOID LOCAL s := NULLASSTRING s := s ?? "abc" // The ?? is the Null Coalescing Operator s ??= "abc" // This is the same as the line before but compacter ? s RETURN // So this will not compile LOCAL i := 0 ASLONG i := i ?? 42 // Operator '??' cannot be applied to operands of type 'int' and 'int' // But this will compile LOCAL i := NULLASLONG? // Nullable LONG i := i ?? 42
-
-
We have added support for the Properties with INIT accessors. These accessors allow you to assign a value to a property but only in the constructor. The property will be read only outside of he constructor of the class / structure.
-
We have added a new compiler option /enforceself. When this option is used then all calls to instance methods inside a class must be prefixed with SELF (or SUPER). In the FoxPro dialect THIS is supported too. Please note that some generated code, such as inside the Windows Forms editor does not use SELF: and applying this compiler option may force you to change the generated code, or may force you to add an #pragma options("enforceself", disable) to the code to disable the option for that file.
-
We have added a new compiler option /allowdot. With this option you can control if the DOT (".") operator is allowed to be used to access instance members. The default for the Core and FoxPro dialect is /allowdot+. The default for the other dialects is /allowdot-. You can also use this with a #pragma: #pragma options("allowdot", enable)
-
XML comments in the source code no longer require fully qualified cref names (#467)
-
- Preprocessor
-
-
The preprocessor now automatically declares a match marker with the name <udc>. This match marker will contain all the tokens that were matched with the UDC by the preprocessor. This can be used for example to add the original source as string to the result: #command INSERTINTO <*dbfAndFields*> FROMMEMVAR => __FoxSqlInsertMemVar(<"udc">)
-
Wildcard markers (such as the dbfAndFields marker in the previous bullet) now can also appear in the middle of a UDC. They will continue to match until the first token after the Wildcard marker (in the above example the FROM keyword) is found.
-
The standard header files (from the XSharp\Include folder) are now also included in the compiler as resource. When the file is missing then these files will be loaded from the resource.
-
The preprocessor was not generating macros for __FOX2__ . This has been fixed (but it is now obsolete, see the FoxPro dialect)
-
When wildcard tokens are included with a stringify result marker then the white space between these tokens is correctly included in the output of the UDC.
-
- FoxPro dialect
-
-
The feature to allow parentheses as array delimiters for the FoxPro dialect that was added in the previous build had too many side effects. We have removed this feature for now. You have to use bracketed array arguments again.
-
-
-
The /fox2 compiler option is no longer needed (and ignored by the compiler). The compiler now checks to see if a runtime function is marked NeedsAccessToLocalsAttribute, which is defined in the XSharp.Internal namespace. If the compiler finds a function that is marked with this attribute, such as the Type() function or the SQLExec() function then it will add some code before and after the function call to allow these functions to access the locals on the stack. This will only happen if the /memvar compiler option is enabled and only in the FoxPro dialect. The NeedsAccessToLocalsAttribute has a mandatory parameter which indicates if a function is expected to write to the locals or only read the locals. When the function is expected to write to locals then the compiler will generate extra code after the call to make sure that the locals are updated when needed.
-
-
-
We have added a standard header file for the FoxPro embedded SQL statements. This header file should parse embedded SQL but will output warnings that the embedded SQL is not yet supported.
-
We have added the FoxPro array support, with a special subtype of the Array type in the runtime and support for DIMENSION and (Re)DIMENSION and filling arrays by assigning a single value. (#523)
-
- Runtime
- General
-
-
Fixed a problem with the return value of FSeek() and FSeek3()
-
AsHexString() and AsString() were not displaying the same result for PTR values as Visual Objects.
-
Fixed a problem with SetScope() for the DBFCDX RDD when the previous scope was empty. (#578)
-
Adjusted the Secs() function to make it more Visual Objects compatible.
-
The enumerator for Array and Array Of now returns an enumerator for a clone of the internal data, to prevent runtime errors when you are modifying the array from within your code.
-
The various Xbase types (DATE, FLOAT, CURRENCY, BINARY, ARRAY, USUAL etc.) are now marked with a [Serializable] attribute and implement ISerializable. They all work fine with the BinaryFormatter() classes, since that class not only stores the values but also the values in the stream. Most of the types also work with the JsonSerializer, however not all of values can be correctly deserialized with the Json serializers. (#529)
-
The CompareTo() operator on the Date type was not sorting the values correctly because it was making an incorrect assumption about the memory layout of the elements in the structure. This has been fixed.
-
We have made some changes in the error handling for functions such as DbUseArea() and DbSkip(). They were not always behaving the same as Visual Objects when an error occurs (for example when a file could not be opened). We have now also added an error handler similar to the default error handler in Visual Objects with a dialog that has the Abort, Retry and Ignore buttons. The Retry button is only enabled when the error object has the property "CanRetry" set to TRUE. (#587, #594)
-
Fixed Val() incompatibility with string that has more than one decimal place (#572)
-
Fixed a problem with comparing dates "in reverse" (#543)
-
We have added a couple of functions that bring up dialogs to display the current open workareas, settings, globals and private and public memory variables. See DbgShowGlobals(), DbgShowWorkareas(), DbgShowMemvars() and DbgShowSettings()
-
- RDD system
-
-
DbCommit and DbCommitAll were failing when a workarea is opened Read only. This has been fixed. (#554)
-
When FoxPro CDX file has more than one tag and one of the tags has an invalid index expression (for example a missing closing parenthesis, which was accepted by Visual Objects) then the RDD system did not open the CDX at all. We now open the CDX with the exception of the tag with the corrupted index expression. (#542)
-
Added support for Advantage GUID and Int64 columns. GUIDs are returned as string and INT64 as INT64. We have also added some missing DEFINE values from the ACE header file.
-
Fixed a problem with incorrect negative Lock Offsets in the DBFNTX driver.
-
We have fixed several "exotic" problems with index "information" (KeyCount, KeyNo) etc. with indexes with Scopes, Descending indices etc. (#423, #578, #579, #580, #582, #583, #593, #599)
-
Fixed problems when opening MEMO files (Fpt and DBT) from different threads and different workstations (#577)
-
We have fixed a locking and corruption problem that could occur when 2 stations were frequently writing to the same CDX file. (#575, #592)
-
Improved Locking Speed when a lock fails. (#576)
-
SetOrder(0) was not working for ADS tables (#570)
-
Changed several method prototypes for ADS to have the correct IN / OUT modifiers (#568)
-
- Macro Compiler
-
-
Fixed a problem in the FoxPro dialect assigning a value to an expression in the form of VariableName.PropertyName
-
The X# macro compiler was allowing to reference GLOBAL and DEFINE values in macros. This made the compiler incompatible with VO and this would cause problems when indexing on a field with the same name as a GLOBAL or DEFINE. The support to reference GLOBALs or DEFINEs has been removed from the macro compiler. (#554)
-
The Macro compiler had a problem with a variable name was surrounded with parentheses. It was seeing that as a typecast. This has been fixed. (#584)
-
- Visual Objects SDK
-
-
Added some missing defines to the Win32APILibrary assembly, such as DUPLICATE_SAME_ACCESS.
-
DbServer:Filter was sometimes returning NIL instead of an empty string (#558)
-
-
- VO Dialect
-
-
We have added support for SysObject (#596)
-
- Xbase++ dialect
-
-
Fixed a problem with XPP Collation tables that was introduced in 2.7
-
- FoxPro dialect
-
-
Added the NeedsAccessToLocalsAttribute for the /fox2 compiler option
-
Adjusted the code that exposes the values of LOCAL variables to functions such as Type() and SqlExec().
-
Several functions have been marked with the new attributes so they will be able to "see" local variables.
-
Added an overload of TransForm() with a single argument.
-
Fixed a problem with the SQLExec() function and sql statements that contain a ":" (colon) character.
-
We have added the Bit..() functions (thanks Antonio)
-
We have added CapsLock(), NumLock() and InsMde (hanks Karl-Heinz)
-
We have improved the FoxPro array code (#523)
-
-
- Runtime Scripting
- This build introduces Runtime Scripting through the ExecScript() function. At this moment you will have to include the Full macro compiler (XSharp.MacroCompiler.Full.dll) and its support DLLs (XSharp.Scripting.dll , XSharp.CodeAnalysis.dll ) if you use Runtime scripting,
- We are working on a light weight version of the Runtime Scripting which will be included in one of the next builds.
- See the topic Runtime Scripting for more information.
- Visual Studio Integration
- The Visual Studio integration in this build no longer supports Visual Studio 2015. Only Visual Studio 2017 and 2019 are supported.
- General
-
-
New code templates in a subfolder were generated with a namespace name that starts with "global::". This has been fixed.
-
Added support for LOCAL FUNCTION and LOCAL PROCEDURE.
-
Adding an item from the Class template in a folder prefixed the namespace with "global::". This has been fixed.
-
When the intellisense database file on disk was corrupted then an error occurred. Now the file is deleted and all code information is collected again.
-
The Editor options in the Tools/Options dialog are now marked with "X#" and no longer with "XSharp".
-
We have added a window under Tools/Options where you can set several values for our VO compatible editors, such as the grid size, paste offset etc. Look for X# in the tools options dialog.(#279, #440)
-
We have added 2 new options to the formatting options for the editor: "Trim Trailing Whitespace" and "Insert Final Newline"
-
Loading a MsTest project did not always work. The project file for MsTest projects will be adjusted when opening the project. (#563)
-
We have added support for t4 templates (text files with a .tt extension containing scripts to generate code)
-
Adding an existing .resx file did not make it a child of a parent form.prg (#197)
-
The project property dialogs have been completely redesigned.
-
-
- Source code editor
-
-
Longer QuickInfo tooltips are now shown over multiple lines to make them easier to read.
-
Refactored the "type lookup" code to improve the speed of the source code editor
-
Member completion in the source code editor was not always working for variables declared with the VAR keyword where there were nested curly braces and/or parentheses. (#541, #560)
-
Fixed a problem with member completion for project references (#540)
-
Fixed an exception when uncommenting a block of lines when one of the lines in the block was an empty line.
-
We have added support for .editorconfig files. See the chapter about .editorconfig files in the documentation file.
-
Collapsing the last entity om the editor did not work correctly (#564)
-
Fixed a problem with syntax highlighting after line continuation comments(#556)
-
Added parameter completion for delegates (#581)
-
Fixed a problem with certain cyrillic characters in QuickInfo tooltips (#504)
-
-
- Code generator
-
-
Character literals are now always prefixed with the 'c' prefix and values > 127 are written in Hex notation to make sure they work in all codepages.
-
- Windows Forms Editor
-
-
We have fixed several issues with DevExpress controls.
-
Fixed a problem with a control that has the same name as a X# keyword (#566)
-
Fixed a problem with a control that has a property of type DWORD (#588)
-
Fixed a problem with the code generation for character literals (#550)
-
The .designer.prg no longer has to have the "INHERIT FROM " clause. (#533)
-
- Object Browser
-
-
Goto definition was not working when you had performed a search first (#565)
-
- VO Compatible Forms editor
-
-
Added support in the WED for correctly visually displaying custom controls that do not have the expected control class inheritance defined
-
Fixed a problem with custom controls in cavowed.inf not recognized that are not data aware
-
Added support for Cloning Windows (#508)
-
Fixed a problem with the display of Checkboxes (#573)
-
Fixed a problem with the code generation (#553)
-
There is a menu option in Tools/Options to set several settings (#279, #440)
-
- Debugger
-
-
The debugger now fully supports 64 bits debugging
-
Added support for the new type names for CURRENCY and BINARY
-
- Templates
-
-
We have made adjustments to several VS item templates and project templates (#589)
-
We have added a new X# t4 template (.tt file)
-
-
- Changes in 2.7.0.0 (Cahors)
- Compiler
- General
-
-
Fixed a problem with Nullable types that were missing an explicit cast for an assignment
-
-
-
Fixed a problem with calling a parent constructor in a class hierarchy where a parent level was being skipped and the constructor for the grandparent was called instead.
-
-
-
The /usenativeversion commandline option was not checking +/- switches. This has been fixed.
-
Fixed a problem with PCall() and PCallNative() in source files with an embedded DOT in the filename (my.file.prg)
-
We have added a new header files to the files in the XSharp\Include files that helps to add custom User Defined Commands or defines that you want to include in every project. This file (CustomDefs.xh) will be automatically include by our XSharpDefs.xh. The default contents of this file is just some comments. The installer will NOT overwrite the file in this folder and will not delete it when the product is uninstalled. You can choose to customize this file in the Include folder under Project Files. However you can also add a file with the same name to your project folder or to a common include folder for your project/solution. That last location allows you to keep the header file under source code control with the rest of your source code.
-
- FoxPro dialect
-
-
The compiler now allows a M Dot (M.) prefix in LOCAL, PRIVATE and PUBLIC declarations. (LOCAL m.Name)
-
The compiler now also accepts parentheses as array delimiters in the Foxpro Dialect (aMyArray(1,2))
-
The compiler now allows (and ignores) AS Type OF Classlib clauses for PRIVATE, PUBLIC, PARAMETERS and LPARAMETERS declarations.
-
-
-
Support for TO keyword in CATCH clause of TRY CATCH
-
Added support for the ASSERT command and SET ASSERT
-
-
-
Added support for SET CONSOLE and SET ALTERNATE
-
Assignments to macros with a single equals operator were not working ( &myVar = 42). This has been fixed.
-
Added support for zero length binary literals (0h)
-
- Build System
-
-
Added a project property to control if RC4005 errors (duplicate defines) should be suppressed for the Native Resource compiler
-
- Runtime
- General
-
-
IsMethod() now returns TRUE for overloaded methods.
-
AbsFloat() was "losing" the settings for # of decimal places. This has been fixed.
-
Binary:ToString() was using single digit numbers for binary values < 15. This has been fixed.
-
Added an implicit operator to assign a usual to a binary.
-
Added an implicit conversion for USUAL values that contain an integer to an Intptr.
-
Some low level functions now set the OS error number FERROR_EOF when operations fail, just like in VO.
-
Exceptions in late bound code were not always showing the correct location where the error occurred. This has been fixed.
-
We have added support for DataSessions. The list of open workareas/cursors in the runtime is now called "DataSession" (the old name Workareas is still available). You can have multiple datasessions. You can also swap the "active" DataSession in the RuntimeState with a new method SetDataSession on the RuntimeState class. FoxPro databases are opened in their own datasession. You can inspect the open DataSessions in the debugger by adding the watch expression: XSharp.RDD.DataSession.Sessions Each DataSession is associated with a Thread. When the Thread is stopped or aborted then the DataSession will be closed, which also closes all of its tables. At program shutdown all DataSessions are closed including their tables. This is done through an AppDomain:ProcessExit event handler.
-
Low level File IO functions (including the RDD system) that open a file in Exclusive mode now use "buffered IO". This should result in faster performance.
-
The (undocumented) functions to convert a Stream from/to a MemoryStream have been removed. This is replaced with the buffer I/O from the previous bullet.
-
We have added System.Enum types for the FoxPro CursorProperties, DatabaseProperties and SQLProperties.
-
We have added a DatabasePropertyCollection type. This type is used to add "additional" properties to Fields, such as the DBF fields for FoxPro tables.
-
- Terminal API
-
-
We have added support for Alternate files. SETALTERNATETO SomeFile.txt. AlsoSET ALTERNATE ONandSET ALTERNATE OFF
-
The ? statement now respects the sessions for Set Console and Set Alternate .
-
We have added support for the SETCOLOR command. Only the fist color in the settings is used and the blink attribute is ignored and interpreted as "highlight". For example SETCOLORTO w+/b
-
We have added a CLEAR SCREEN command
-
- FoxPro dialect
-
-
Added an Assert dialog
-
Added support for DBC files. This includes the SET DATABASE to commands, DbGetProp() and reading properties for files that are part of a database without explicitly opening the database first. DbSetProp() does not do anything yet. Also functions like DbAlias() and similar have been implemented.
-
The Runtime now works with DataSession object. The DBC files are opened in their own datasession as well of the files per thread. Each datasession has a list of open tables and a unique list of aliases and cursor/workarea numbers.
-
AutoIncrement columns in cursors returned by SqlExec() now have a numbering scheme that starts with -1 and subtracts 1 for every new row added.
-
-
-
Several settings needed for the FoxPro dialect have been added to the Set Enum.
-
- Macro Compiler
-
-
Until now the macro compiler was producing runtime codeblocks that take an array of objects and return an object return value. There was a class in the runtime that wrapped this and took care of usual -> object conversion for the parameters and for object-> usual conversion of the return value. This caused a problem when macros were returning a NIL value because that was converted to NULL_OBJECT. The reason for the OBJECT API is that the macro compiler needs to be used in the Core dialect (in the RDD system) and this dialect does not support the USUAL type. We have now added a new IMacroCompilerUsual interface in the XSharp.RT assembly that allows you to compile a string into a codeblock that supports USUAL arguments and a USUAL return value. The macro compiler now supports both this interface as well as the 'old' interface. As a result you may see a (very small) performance improvement when compiling macros.
-
Calling Altd() and _GetInst() inside a macro was not supported. This has been fixed.
-
The macro compiler was reporting an error when you had overridden a built-in function in your own code. We have now implemented a default MacroCompilerResolveAmbiguousMatch delegate in the runtime that now gives preference to functions that are defined in your code over functions in our code.
-
When choosing between 2 overloads of a method or function the Macro compiler now chooses the method with a USUAL parameter over a method without a USUAL parameter
-
Fixed a problem with calling functions/methods with a parameter by reference or an out parameter
-
Added support for the CURRENCY and BINARY types to the macro compiler.
-
- RDD System
-
-
Exclusive DBF access now works in "buffered" mode which should make it a lot faster
-
Internally the RDDs now work with the Stream objects, which makes it a bit faster.
-
Fixed a problem when updating a key in an index where many duplicate key values existed.
-
Removed duplicate Foxpro "machine" collations for several codepages, since they were all the same.
-
For VFP compatible DBF files with field names > 10 characters you can now use the short (10 char) or the full fieldname to retrieve the values.
-
The DBFVFP driver now uses the built in DBC support in the runtime to read "extended" properties for DBF files. These properties are the longer fieldname, but also the Caption etc. When a DBFVFP table is used as datasource for a DbDataSource or DbDataTable and when this data source is assigned to a Grid then the columns headers in the Grid should show the Captions from the DBC.
-
DBF files with an empty codepage byte are now opened as DOS - US just like in VO and Vulcan.
-
GoTop(), GoBottom() and other operations were failing for when a DBFCDX/DBFVFP area was a child in a SetRelation and when the previous parent value was resulting in an "empty" resultset.
-
We have added structures and functions for the ADS Management API to the RDD assembly.
-
- Visual Studio integration
-
-
When creating a new VO compatible UI form in the VS IDE you can now clone an existing form.
-
Fixed some problems with custom controls in the VO compatible form editor.
-
Fixed several problems in the Windows Forms editor for the code parsing and code generation for DevExpress controls
-
Solutions with "flavored" projects (such as MsTest projects) were not always opened correctly. An exception could occur.
-
We have added an (internal) property FieldValues() to the workarea class that allows you to inspect the fieldnames and their values for the current record in the debugger. To see the current workarea in the debugger you have to add a watch expression: XSharp.RuntimeState.DataSession.CurrentWorkarea
-
Added Project property to set the new flag to suppress RC4005 (duplicate defines) errors for the resource compiler.
-
-
- Changes in 2.6.1.0 (Cahors)
- This is a bug fix release with fixes for some issues found in 2.6.0.0
- Compiler
-
-
Fixed problems with passing typed variables by reference to late bound code and to untyped constructors
-
Fixed an internal compiler error in code where a define containing a logic was cast to a byte BYTE(_CAST, LOGICDEFINE). Of course this is code that should be avoided at all times, but unfortunately even the VO SDK is full of code like this.. The example above should be written as IIF(LOGICDEFINE, 1,0) for example. The compiler will see that the define is constant and will replace that code with either 1 or 0.
-
The compiler was not recognizing $.50 as a valid Currency literal (because the 0 is missing). This is now accepted.
-
- Runtime
-
-
Updated the code in the runtime that handles late bound calls to improve the handling of parameters by reference
-
Fixed a problem in late bound code when accessing properties such as fInit, dwFuncs and dwVars in the OleAutoObject class
-
Added operator TRUE and operator FALSE to the Usual type
-
Calling Val() with a NULL_STRING could cause an exception. This has been fixed.
-
String properties returned by DbDataTable() and DbDataSource() are now trimmed with the TrimEnd() method of the string class.
-
Added a DbTableSave() function to save changes in a DbDataTable to the current workarea.
-
- Visual Studio integration
-
-
Opening and upgrading project files that are under Scc could sometimes cause problems. This has been fixed
-
Fixed a regression introduced in 2.6.0.0. causing the task list to no longer be updated.
-
Opening a solution that referenced X# projects that do not exist on disk could cause an exception. This has been fixed.
-
Opening a X# Project file that is not part of a solution could also cause an exception. This has been fixed. We'll assume the project is part of a solution file in the same folder as the project and with the same name (but different extension) as the project.
-
The project system no longer makes backup files of projects that are updated. We assume you're all making backups yourself or using some kind of SCC system.
-
Fixed a regression that caused the VS Tasklist not to work for X# projects.
-
-
- Changes in 2.6.0.0 (Cahors)
- Please note that there are some breaking changes in this build. Therefore the Assembly version number of the Runtime Components has been changed and you will need to recompile all your code and you need new versions of 3rd party components!
- Compiler
-
-
The compiler was ignoring a (USUAL) cast. This has been fixed.
-
When the compiler detects a TRY .. ENDTRY without CATCH and FINALLY then it automatically adds a CATCH class that catches all exceptions silently. This was already the case, but we now generate a warning XS9101 when this happens.
-
Passing parameters by reference with an @ sign was not working correctly for late bound method calls. This has been fixed.
-
Compiler option vo15 and compiler option vo16 can now also be set with a #pragma
-
When /vo16 (Automatically generate Clipper calling convention constructors) was enabled then the compiler was also adding constructors to classes that are marked with the [COMImport] attribute. This has been fixed.
-
Currency literals ($12.34) were not compiled into the Currency type but were stored as System.Double. This has been fixed.
-
Fixed a problem with automatic version number generation for version numbers that are specified as [assembly: AssemblyVersion ("1.0.*")] or [assembly: AssemblyVersion ("1.0.0.*")]. If you are building with the /deterministic compiler option then an error message XS8357 is shown.
-
Fixed a problem when passing a single USUAL argument to a constructor with a parameter array.
-
Fixed a problem when calling an overloaded method in a class tree where one level has a parameter of one type and another level the same method name but a parameter of another type and when there is an implicit typecast from the one type to the other (like between Date and Datetime, or between String and Symbol). The compiler now first looks to see if there is an overload with exactly the same type and where there is not then it looks for overloads for which the argument can be passed with an implicit conversion.
-
The __CastClass() pseudo function can now be used to box a usual into an object or to unbox a usual from an object. __CastClass(USUAL, <objectValue>) unboxes the usual that is inside the object. __CastClass(OBJECT, <usualValue>) boxes the usual into an object.
-
The <usualValue> IS SomeType VAR <newVariableOfTypeSomeType> clause was boxing the Usual into the Object before assigning it to the new variable instead of extracting the object from the usual. This has been fixed.
-
Late bound assignments (such as obj.&prop = "Jack") were failing when the assignment operator was a single equals character. This has been fixed.
-
Aliased Expressions such as SomeArea->(SomeExpression()) were returning an error on the incorrect source code line when SomeArea was not open. This has been fixed.
-
We have added support for the BINARY type and BINARY Literals. See the topics about binaries and binary literals in the documentation.
-
Expressions such as LOCAL dwDim := 512 IS DWORD were parsed as and compiled into LOCAL dwDim := (512 IS DWORD) AS USUAL As a result dwDim contained a USUAL with a LOGICAL value. This has been fixed and this code will now throw an error that DWORD variables cannot be declared with the IS keyword. This also happens for GLOBAL variables and Class Variables.
-
We have added a MatchLike preprocessor token to match expressions that contain wildcard characters, such as in the UDC SAVE ALL LIKE a*,*name TO SomeFileName. The token to use for MatchLike is <%name%>
-
Added support for pattern matching (WHEN clauses) in TRY .. CATCH statements, such as in the example below. The WHEN keyword is positional, so it can also be used as a variable name like in the example.
-
- FUNCTION Test ASVOID local when := 42 aslong TRY THROW Exception{"FooBar"} CATCH e as Exception WHEN e:Message == "Foo" ? "Foo", when, e:Message CATCH e as Exception WHEN e:Message == "Bar" ? "Bar", when, e:Message CATCHWHEN when == 42 ? "No Foo and No Bar", when ENDTRY RETURN
-
-
Added support for pattern matching and filters for SWITCH statements. We support both the "Identifier AS Type" clause as well as the "WHEN expression" filter clause, like in the examples below
-
- VAR foo := 42 VAR iValues := <LONG>{1,2,3,4,5} FOREACHVAR i IN iValues SWITCH i CASE 1 // This is now called the 'constant pattern' ? "One" CASE 2 WHEN foo == 42 // Filter with a constant pattern ? "Two and Foo == 42" CASE 2 ? "Two" CASE 3 ? "Three" CASE 4 ? "Four" OTHERWISE ? "Other", i ENDSWITCH
- VAR oValues := <OBJECT>{1,2.1,"abc", "def", TRUE, FALSE, 1.1m} FOREACHVAR o in oValues SWITCH o CASE i ASLONG// Pattern matching ? "Long", i CASE r8 ASREAL8// Pattern matching ? "Real8", r8 CASE s ASSTRINGWHEN s == "abc" // Pattern matching with filter ? "String abc", s CASE s ASSTRING// Pattern matching ? "String other", s CASE l ASLOGICWHEN l == TRUE // Pattern matching with filter ? "Logic", l OTHERWISE ? o:GetType():FullName, o ENDSWITCH NEXT
-
-
Please note that the performance of these patterns and filters is just like normal IF statements or DO CASE statements. The difference is that the compiler checks for duplicate CASE expressions so you are less likely to make mistakes.
-
We have added support for the IN parameter modifier. This declares a parameter that is a REF READONLY parameter. You could consider to use this when passing large structures to methods or functions. Instead of passing the whole structure then the compiler will only pass the address of the structure which is 4 bytes or 8 bytes depending on if you are running in 32 bits or 64 bits. We are planning to use this in the X# runtime for functions that accept USUAL parameters which should give you a small performance benefit (Usual variables are 16 bytes in 32 bits mode and 20 bytes when running in 64 bit mode).
-
- Runtime
-
-
Error messages in Late Bound code were not always showing the error causing the exception. We now retrieve the "inner most" exception so the message shows the first exception that was thrown.
-
We have added runtime state settings for Set.Safety and Set.Compatible and the functions for SetCompatible and SetSafety
-
-
-
A UDC used to save and restore workareas for various Db..() functions was incorrect, causing the wrong area to be selected after the function call. This has been fixed.
-
-
-
The VFP MkDir() function has been added.
-
Fixed a problem in late bound IVarGet() / IVarPut() when a subclass of a type implements only the Getter or the Setter and the parent class implements both.
-
-
-
We have added a IDynamicProperties interface and added an implementation of this on the XPP DataObject, VFP Empty and VO OleAutoObject classes. This interface is used to optimize late bound access to properties in these classes.
-
An Exception in OleAutoObject.NoMethod was not forwarded "as is" but as an argument exception.
-
-
-
The Select() function now behaves differently in the FoxPro dialect to be compatible with FoxPro (no exception is thrown when the alias that is passed does not exist)
-
When an Error object is created from an exception then the innermost exception is used for the error information.
-
The casing of the Default() function has changed.
-
We have added a new XSharp.__Binary type. See the compiler topic above for more information.
-
We have added the CLOSE ALL UDC to dbcmd.xh as synonym for CLOSE DATABASES.
-
- RDD System
-
-
Fixed a problem in the Advantage RDD for the ADSADT driver when field names were > 10 characters.
-
In the Advantage RDD the EOF, BOF and FOUND flags for tables that are a child in a relation were not properly set. This has been fixed.
-
In the FoxPro dialect the 'AutoOrder' behavior has changed. In this dialect no longer the first order in the first index is selected. The index file is opened but the file stays in natural order and when opening the file the cursor is positioned on the record number 1.
-
When exporting to CSV and SDF there was an exception for empty dates. This has been fixed.
-
When an CDX is opened for which one of the order expressions could not be compiled (because a function is missing) then previously the complete CDX was ignored. Now the other tags are opened succesfully. The RuntimeState.LastRddError property will contain an Exception object that contains the error message for the tag that failed to open.
-
The calculation of Index keys for fields of type "I" (in the DBFVFP driver) was incorrect. This has been fixed.
-
Fixed a problem with the OrdDescend() function/
-
- Visual Studio integration
-
-
Fixed a problem in the VS parser for default expressions in parameter lists
-
Parameters for external methods/functions were not always showing the right "As"/"Is" modifiers
-
The location on the QuickInfo tooltip is now shown on its own line inside the tooltip.
-
Fixed a problem where the XML tooltips or parameter tips for the first member in a XML file were not shown.
-
We have made a change to the project file format (see comment below). All project files will be updated when opened with this build of X#.
-
Improved the speed of closing a solution inside Visual Studio.
-
The project system will no longer try to update SDK style project files.
-
When looking for a method such as Foo.SomeMethod() the codemodel sometimes returned a method Bar.SomeMethod(). This was leading to problems when opening forms in the Windows Forms editor. This has been fixed.
-
- VO Compatible editors
-
-
Code generated from the VO Compatible editors now preserves the INTERNAL or other modifiers as well as IMPLEMENTS clauses for classes.
-
We have fixed the display of "LoadResString" captions in PushButton controls
-
- Foxpro commands
-
-
We have added support for several new Foxpro compatible commands:
-
CLOSE ALL
-
SCATTER
-
GATHER
-
COPY TO ARRAY
-
APPEND FROM ARRAY
-
COPY TO SDF|CSV|DELIMITED|FOXPLUS|FOX2X
-
APPEND FROM SDF|CSV|DELIMITED|FOXPLUS|FOX2X
-
All variations support a fields list, FIELDS LIKE or FIELDS EXCEPT clause and the relevant commands also support the MEMO and BLANK clauses.
-
-
-
Not all variations from COPY TO and APPEND FROM are supports, such as copying to excel and sylk
-
The Database and name clause in the COPY TO command are ignored for now as well as the CodePage clause
-
- Build System
-
-
We have prepared the X# Build System to work with SDK type projects that are used by .Net 5 and .Net Core. See the topic below for what this means for the project files.
-
Please note that the source code for the Build System has been moved to the Compiler repository on GitHub, since the build system is also needed for automated builds that run outside of Visual Studio.
-
- Changes to project files
-
-
We are now no longer deploying our MSBuild support to a folder inside each VS version separately but we are only deploying it once in a folder inside the XSharp installation folder. The installer sets an environment variable XSharpMsBuildDir which points to that folder. As a result all project files will be updated when opened with this version of X#.
-
-
-
The change that we make is that the macro "$(MSBuildExtensionsPath)\XSharp" is replaced with "$(XSharpMsBuildDir)" which is an environment variable that points to the location of the X# MsBuild support files on your machine. If you are running X# on a build server you can set this environment variable in your build scripts when needed.
-
The installer automatically adds this environment variable and points it to the <XSharpDir>\MsBuild folder.
-
-
- Changes in 2.5.2.0 (Cahors)
- Compiler
-
-
When a define contains an expression that contains the _Chr() function with a value > 127 then a warning is generated about possible code page differences between the development machine and the end users machine
-
Fixed an issue where a define was defined as PTR(_CAST,0) and this define was also used as a default value for a function/method.
-
- Runtime
-
-
Calling IsAccess, IsAssign and similar methods on a NULL_OBJECT was causing an exception. This has been fixed.
-
EmptyUsual now also works for the type OBJECT
-
When a float division was returning an Infinite value then no divide by zero exception was generated. This has been fixed.
-
When a parameter is skipped in a late bound call, and when that parameter has a default value, then we will now use the default value instead of NIL
-
The default value of the 5th parameter (uCount) of StrTran() was "only" 65000 replacements. The default value now takes care of replacing all occurences.
-
The variable name passed to NoIVarGet() and NoVarPut() is now converted to Uppercase.
-
- RDD System
-
-
Fixed a problem with skipping forward when a Scoped Descending Cdx was at Eof()
-
- VOSDK
-
-
Several DbServer methods were calling a method to write changes before the correct workarea was selected. This was an old bug originating in VO and has been fixed.
-
- Visual Studio integration
-
-
Looking up XML documentation was sometimes not working in VS 2019. This has been fixed.
-
ClassView and Objectview are working "somewhat" now. This needs to be improved.
-
Improved the loading of so called "Primary Interop Assemblies"
-
Fixed a problem in the Type and Member dropdown bars in the editor window
-
Improved the renaming of controls when applying copy/paste in the VO Compatible window editor.
-
The X# toolbar for the VO Window editor is now automatically visible when the VO Window editor is opened
-
The position and size of the property window and toolbox of the VO Window editor (and the other VO Editors) is now saved between sessions of Visual Studio.
-
- Build System
-
-
The generated XML files were generated in the project folder and not in the intermediate folder. This has been fixed.
-
- Documentation
-
-
The [Source] links were missing for most topics. This has been fixed.
-
Corrected some docs
-
-
- Changes in 2.5.1.0 (Cahors)
- Compiler
-
-
no changes to the compiler in this build (it is still called 2.5.0.0)
-
- Runtime
-
-
(VO Compatibility) Fixed a VO compatibility issue for arrays . Accessing an single dimensional array with an index with 2 dimensions now returns NIL and does not generate an exception. This is stupid but compatible.
-
(VO Compatibility) Comparing a usual with a numeric value with a symbol no longer generates an exception. The numeric value is now casted to a symbol and that symbol is used for the comparison.
-
(XPP compatibility) Accessing a USUAL variable with the index operator (u[1]) is not allowed for usuals containing a LONG. This will return TRUE or FALSE and is a simple way to check if a bit is set.
-
The Literals for "DB" and "CR" are now stored in the resources and may be changed for other languages.
-
Added some optimizations to the support code for late binding
-
- Visual Studio integration
-
-
Reading type information for external assemblies would fail when the external assembly contained 2 types for which the names were only different in case.
-
The entity parser did not recognize GET and SET accessors that were prefixed with a visibility modifier (PROTECTED SET)
-
The entity parser did not recognize ENUM members that did not start with the MEMBER keyword
-
Added support for the Visual Studio Task Window. Source code comments containing the words TODO or HACK (this is configurable in the Tools/Options window) are now added to the Task List. These tasls are persisted in the intellisense database, so all tasks are immediately visible after opening a solution without (re)scanning the source files.
-
Fixed a problem in the Type and Member lookup for the WIndows Forms editor
-
Fixed a problem in the VS debugger where we were subtracting one from index operators for arrays and collections. This was not correct (obviously).
-
- Build System
-
-
The file name of the generated XML file was derived from the project file name instead of the output assembly name. This has been fixed.
#pragma lines that were followed by incorrect syntax would "eat" the incorrect syntax causing entire methods to be excluded from compilation. This has been fixed.
-
Multiline compile time codeblocks in a method /function with a VOID return type were not being compiled correctly. This has been fixed.
-
The compiler now allows to type the parameters in a codeblock. Since the codeblock definition requires parameters of type USUAL this gets transformed by the compiler. The parameters will still be of type USUAL, but inside the codeblock a local variable of the proper type will be allocated. So this compiles now
-
- { | s asstring, i asint| s:SubString(i,1) }
-
-
The code to fill in missing parameters was causing problems when passing parameters to COM calls (Word Example from Peter Monadjemi)
-
Fixed a problem passing an IntPtr, Typed pointer of the address of a VOSTRUCT to a function that accepts an object.
-
We have added code to add an integer value to a PSZ, which results in a new PSZ that starts at a relative location in the original PSZ. No new buffer is allocated.
-
We have fixed a problem with complex collection initializers.
-
Chr() and _Chr() with an DEFINE as argument, such as _Chr(ASC_TAB) were not properly resolved by the compiler.
-
The compiler was not properly parsing the syntax PUBLIC MyVar[123]. This has been fixed.
-
Some special characters (such as the Micro Character, U+00B5) were not recognized by the compiler as valid identifiers. We have now adopted the same identifier rules that C# uses.
-
Passing a pointer or PSZ in a value of type OBJECT is now handled by "boxing" the variable. So a NULL_PTR is no longer passed as NULL_OBJECT but as an object containing an IntPtr.Zero value.
-
The compiler now allows to store IntPtr.Zero to a constant variable
-
The compiler now allows to embed quotes inside a string by writing double quotes. So this works:
-
- ? "Some String that has an embedded "" character"
-
-
When you declare a MEMVAR with the same name as a function, the compiler will now have no problem anymore resolving the function call. Please note that you HAVE to declare the memvar for this resolution to work. For example
-
- FUNCTION Start() ASVOID MEMVAR Test Test := 123 // assign to the memory variable Test(Test) // call the function 'Test' with the value of 'Test' RETURN FUNCTION Test(a) ? a RETURN a
-
-
- Common Runtime
-
-
The Workareas class no longer has an array of 4096 elements, but uses a dictionary to hold the open RDDs. This reduces the memory used by the runtime state.
-
Fixed a problem in the WrapperRDD class
-
OrdSetFocus() now returns the previous active tag as STRING
-
Fixed a problem in FRead() , it was not ignoring the SetAnsi() setting as it should
-
Added operators on the PSZ type for PSZ + LONG and PSZ + DWORD.
-
The Usual class now implements the IDisposable() interface. When it contains an object that implements IDisposable then it will call the Dispose method on that object.
-
We have added Array index properties with one and two numeric indices to make code that accesses array elements a bit faster
-
The code SELECT 10, was not working properly. This has been fixed. Thanks Karl Heinz.
-
The return value of VoDbOrdSetFocus() was TRUE even when trying to set the order to a non existing index. This has been fixed.
-
We fixed a problem with Set(_SET_CENTURY) when the parameter passed was a string in the "ON" or "OFF" format
-
VODbOrdSetFocus() was returning TRUE even when the selected order could not be selected.
-
ArrayCreate<T> was not filling the array. This has been fixed.
-
Trailing or Leading spaces are now ignored by the CToD() function.
-
Calling VoDbSeek() with 2 parameters now does not set lLast to FALSE but to the LAST value from the Current Scope.
-
In the previous build the format for the stack trace for errors was changed (the names are all uppercase like in VO). You can now choose to enable or disable this. We have added a function SetErrorStackVOFormat() that takes and returns a logical value. The default format for the error stack is the VO format for the VO and Vulcan dialects and the normal .Net format for the other dialects.
-
We have implemented the StrEvaluate() function.
-
We have implemented the PtrLen() and PtrLenWrite() functions. These only work on the Windows OS() when running in x86 mode. For other OSes or for apps running in 64 bits these functions returns the same value as MemLen().
-
When dividing 2 float numbers results in a NaN (Not a Number) value because the divisor is zero, then a DivideByZero exception will now be generated.
-
When dividing 2 usual numbers results in a NaN (Not a Number) value because the divisor is zero, then a DivideByZero exception will now be generated.
-
Please note that dividing 2 REAL8 (System.Double) values can still result in a NaN, because we are not "intervening" with this division.
-
The OS() function now returns a more appropriate version description when running on Windows. It reads the version name from the registry and also includes a x86 and x64 flag in the version.
-
- RDD System
-
-
The DBF RDD Now forces a disk flush when writing a record in shared mode.
-
Fixed a problem in the DBFCDX rdd that could corrupt indexes.
-
We have built in a validation routine inside the DBFCDX RDD that validates the integrity of the current tag. To call this routine call DbOrderInfo with the DBOI_VALIDATE constant. This will validate:
-
-
If all records are included exactly once in the index
-
If the values for each record in the index are correct
-
If the order of the index keys in a page is correct
-
If the list of index pages in the index is correct
-
-
- When a problem is found then this call returns FALSE and a file will be written with the name <BagName>_<TagName>.ERR containing a description of the errors found.
-
-
Most exported variables inside the Workarea class (inside XSharp.Core) and other RDD classes have been changed to PROTECTED. We have also added some properties for variables that need to be accessed from outside of the RDD
-
Fixed a problem that occurred when skipping back repeatedly from the BOF position in a scoped CDX index.
-
The Zap() operation for DBFCDX was not clearing one of the internal caches. This has been fixed.
-
The DBFCDX driver now closes and deletes a CDX file when the last tag in that CDX has been deleted.
-
- Macro compiler
-
-
The macro compiler was not recognizing 0000.00.00 as an empty date. This has been fixed.
-
The macro compiler now also exotic characters in identifiers like the normal compiler. We have added the same identifier name rules that the C# compiler uses.
-
-
- XBase++ Functions
-
-
Fixed a problem in the XPP function SetCollationTable()
-
DbCargo() can now also set the cargo value for a workarea to NULL or NIL
-
We have added several functions, such as PosUpper(), PosLower(), PosIns() and PosDel().
-
-
- VFP Functions
-
-
Added AllTrim() , RTrim(), LTrim() and Trim() variations for FoxPro (thanks Antonio)
-
Added StrToFile() and FileToStr() (thanks Antonio and Karl Heinz)
-
-
- VOSDK
-
-
We have created a Destroy() method on the CSession and CSocket class, so you can 'clean up' objects (in VO you could call Axit(), but that is no longer allowed). The derstructor on these classes will also call Destroy().
-
Fixed a problem in TreeView:GetItemAttributes. It can now also be called with a hItem (which happens inside TreeViewSelectionEvent:NewTreeViewItem)
-
The OpenDialog class is now resizable.
-
Fixed a problem in FormattedString:MatchesTemplChar(), that was causing problems with edit controls with a picture
-
Calling DataWindow:__DoValidate() late bound was not working because there are 2 overloads. This has been fixed. Please note that in the VO SDK DataWindow:__DoValidate() expects a parameter of type Control, but inside the DataBrowser code it is called with a parameter of type DataColumn. VO does not complain but in .Net that does not work !
-
Fixed a problem in GetMailTimeStamp() in the Internet classes.
-
We have included "typed" versions of Consoleclasses, SystemClasses and RDD classes. These are mostly strongly typed and can run in AnyCPU mode. The SQL classes and GUI classes will follow.
-
- Visual Studio Integration
- Code Model
-
-
We have totally rewritten the background parser and code model that is used to parse "entities" in the VS editor and that is used to build a memory model of the types, methods, functions etc in your VS solution. This parser now uses the same lexer that the compiler uses, but the entities are collected with a hand written parser (since the code in the editor buffer may contains incomplete code we can't reliably use the normal parser).
-
We are now using a SQLite database to persist the code model between sessions. This reduces the memory needed by the X# project system. We are no longer keeping the entire code model in memory.
-
This also means that when you reopen an existing solution we will only have to parse files that have changed since the last time they were processed. That should speed up loading of large VS solutions.
-
We are now also reading type information from external code (assembly references and project references to non X# projects) using the Mono.Cecil library instead of the classes in the System.Reflection namespace. This is faster, uses less memory and, most important, we can easily unload and reload assemblies when they were changed.
-
As a result of all of this, opening VS solutions should be faster and "lock up" VS less often (hopefully not at all). Also code completion and other intellisense features should be improved.
-
-
- Source code editor
-
-
Fixed a problem with the dropdown comboboxes above the editor when the cursor is in a line of code before the first entity.
-
Fixed a problem that functions in the editor after a class declaration had no collapsible regions
-
The code completion inside the editor now also picks up extension methods for the types themselves, but also extension methods for interfaces implemented by these types.
-
The editor code now properly recognizes variables declared with the VAR keyword when they are followed by a constructor call
-
If you have XML comments in your source code for entities in your solution, then these comments should be picked up by the tooltips inside Visual Studio and by the parameter completion.
-
Fixed several problems in the "reformatting" code
-
- Windows Forms editor
-
-
Some inline assignments to fields inside classes that are used by the Windows Forms could make the form unusable by the form editor. This has been fixed.
-
The Windows Forms editor was sometimes removing blank lines between entities. This has been fixed.
-
User Defined Commands in code parsed by the Windows Forms Editor were not recognized and disappeared when the form was changed and saved. This has been fixed.
-
Fixed a problem with setting images and similar properties with resources stored in the project resources file (which are prefixed with "global::" in the source code)
-
- VOXporter
-
-
We have added support to export VO Forms from the AEFs to XML format
-
We have added support to export VO Menus from the AEFs to XML format
-
-
- Changes in 2.4.1.0 (Bandol GA 2.4a)
- Compiler
-
-
Bracketed strings are now no longer supported in the Core dialect to avoid problems with single line external property declarations that contain attributes between the GET and SET keywords
-
The PROPERTY keyword was not properly recognized after an EXTERN modifier.
-
Fixed a XS9021 warning for a IIF expressions with 2 numeric constants
-
In the FoxPro dialect late bound calls are now always allowed on certain types (even when the /lb compiler option is not enabled), such as USUAL and the Empty class. These types are marked with the AllowLateBound attributes in the runtime. They WILL generate a new compiler warning (XS9098).
-
We have added a new compiler option -fox2. This option makes local variables visible to the macro compiler and should also be used when you use SQL statements with embedded parameters. This compiler option must be used in combination with -memvar and the FoxPro dialect
-
- Runtime
-
-
Fixed a problem in the DELIM Rdd that would occur when using DbServer:AppendDelimited() and DbServer:CopyDelimited().
-
Fixed a problem with DbSetOrder() returning TRUE even when the order was not found.
-
Fixed a problem where the File() function would return FALSE when using wildcard characters
-
SqlExec() now returns columns of type Date for SQL providers that have a separate Date type
-
Workareas/Cursors created with SqlExec() now have the NULL flags, Binary flags etc. set properly according to the settings read from the backend.
-
Fixed and added implementation of VFP functions (Gomonth, Quarter, ChrTran, At in various variations, RAt in various variations, DMY, MDY). Thanks Karl Heinz.
-
First work on parameterized SQL functions. Not finished yet.
-
Some types in the runtime are now marked with a special "AllowLateBound" attribute. These types will be accepted in the FoxPro dialect as candidates for compiling latebound even when the /lb compiler option is not enabled.
-
We have added support for the macro compiler to access local variables by name. This is built into the VarGet() and VarPut() functions and also the MemVarGet() and MemVarPut() functions. Local variables will have preference over same named private or public variables. You have to enable the -fox2 compiler option for this.
-
ValType() now returns "Y" for currency values and "T" for DateTime values
-
No copy of the runtime state is created when that state is accessed in the Garbage collector thread.
-
SQLExecute() now returns -1 when an invalid SQL statement is executed.
-
Added the VarType() function
-
IVarGet() and Send() now return Empty strings when a method returns a NULL_STRING and the return type is STRING
-
- RDD
-
-
Getting the OrdKeyNo for a scoped index was resetting the index position to the top of the index. This would affect scrollbars in browsers for scoped indexes
-
- VOSDK
-
-
The Console classes assembly is now marked as AnyCpu.
-
Fixed a problem introduced in the previous build with the calling convention for certain functions imported from Shell32.DLL such as the Drag and Drop support.
-
Fixed a problem in the PrintingDevice constructor for reading of printers when running on a Remote Desktop
-
We have changed several calls to IsInstanceOf with <var> IS <Type> constructs
-
Fixed typo in several IsInstanceOf() calls
-
Improved "column scatter" code for the DataBrowser class
-
- Visual Studio Integration
-
-
If you removed all the characters from the "Commit Completion List" control in the XSharp editor options, then after restarting VS all default characters would appear. We now remember that you have cleared the list and will not refill the list again.
-
Fixed a problem that caused the editor not to rescan the current buffer for changed entities
-
Added project property for the new -fox2 compiler option
-
The VO MDI template now has Drag and Drop enabled
-
Fixed a problem in the Debugger with some of the runtime types, such as DATE that could cause an exception while debugging in VS 2019
-
Fixed a problem in the part of the editor code that is responsible for showing collapsible regions and updating the comboboxes with type names and member names.
-
Fixed the code generation for Tab pages in the VO compatible forms editor
-
-
- Changes in 2.4.0.0 (Bandol GA 2.4)
- Compiler
-
-
Fixed problems where certain operations on integers would still return the wrong variable type
-
The Unary Minus operator on unsigned integral types (BYTE, WORD, DWORD, UINT64) was returning the same type as the original, so it was not returning a negative value. This has been changed. The return value of this operator is now the next larger signed integral type.
-
Using a compiler macro, such as __VERSION__ in an interpolated string was causing an internal error in the compiler. This has been fixed.
-
The vo11 compiler option now only works for operations between integral and non integral types. Other behavior has been removed because the VO behavior for mixing integral types was confusing and impossible to emulate.
-
Bracketed strings are now also recognized after a RETURN and GET keyword.
-
- Runtime
-
-
Fixed problems when subtracting a dword from a date (related to the signed/unsigned problems in the compiler)
-
LUpdate() now returns a NULL_DATE for workareas have no open table.
-
Added the missing ErrorStack() function (thanks Leonid)
-
Added the Stack property to the Error class
-
Added the SQL..() functions from Visual FoxPro. Please note that SQLExec() and SQLPrepare() with embedded parameters in the SQL statements are not supported yet. This requires a change in the compiler that is planned for the next build.
-
Added a DbDataTable() function that returns a (detached) DataTable with the data from the current workarea
-
Added a DbDataSource() function that returns a BindingList attached to the current workarea. Updates to properties in the bindinglist will be directly written to the attached workarea.
-
Added 2 classes DbDataTable and DbDataSource that are returned by the functions with the same name.
-
Fixed a problem with incorrectly formatted USUALs with numeric values
-
We have added the defines from FoxPro.h to the VFP assembly
-
We have added the VFP MessageBox functions, including a message box that automatically closes when a timeout has reached.
-
Fixed AsHexString() to display large DWORD values that are stored inside USUALs
-
Fixed several incompatibilities with VO for FLOAT->STRING conversions
-
- RDD System
-
-
Fixed a problem with skipping backward in a DBFCDX table with a scope
-
Fixed a problem with creating unique indexes with the DBFCDX and DBFNTX drivers
-
Writing NULL values to DBF columns is now always supported. When the column is a Nullable column in a DBFVFP table then the null flags are set. For other RDDs a NULL value will be written as a blank value.
-
Fixed a performance issue in Append operations for all DBF based RDDs
-
Fixed a problem with the DBFCDX driver that could happen when index pages were nearly full with key-value pairs with all blanks
-
Fixed a problem in WrapperRDD:Open()
-
Added the SDF RDD
-
Added a special DbfVFPSQL RDD that is used by the SQL..() functions in the VFP support to store the results from SQL queries. The column information describing the original column from the Sql Resultset can be retrieved with the DbFieldInfo() and the DBS_COLUMINFO define. The return value for this call is an object of the type XSharp.RDD.DbColumnInfo.
-
Added the DELIM RDD and 2 subclasses (CSV and TSV). These RDDs all return separated values. The default format for the DELIM RDD is to use the comma as separator. CSV uses semi colons and TSV uses Tabs to delimit the fields. On top of that CSV and TSV write a header row with field names. The "normal" Delimited operations still use DELIM. If you want to use the CSV or TSV RDDs you need to set a global setting:
-
- RddSetDefault("DBFNTX") DbUseArea(TRUE,"DBFNTX", "c:\Test\TEST.DBF") DbCopyDelim("C:\test\test.txt") // this uses the DELIM RDD
RuntimeState.DelimRDD := "CSV" // Tell the runtime to use the CSV RDD for delimited writes DbCopyDelim("C:\test\test.csv") // this uses the CSV RDD
RuntimeState.DelimRDD := "TSV" // Tell the runtime to use the TSV RDD for delimited writes DbCopyDelim("C:\test\test.tsv") // this uses the TSV RDD DbZap()
RuntimeState.DelimRDD := "CSV" // Tell the runtime to use the CSV RDD for delimited reads DbAppDelim("C:\test\test.csv") // this uses the CSV RDD
- VO SDK
-
-
PrintingDevice:Init() no longer tries to read the default printer from win.ini but from the registry
-
Several other locations where the code was still accessing win.ini (with the GetProfile..() funcitons) have been updated.
-
The GUI Classes were delay loading several calls to common dialog DLL and winspool.drv. This has changed because that is no longer needed in .Net.
-
Cleaned up all PSZ(_CAST operations in GUI Classes.
-
- Visual Studio integration
-
-
Parameter tips for OUT variables were shown as REF
-
XML descriptions for member with REF or OUT parameters were not found
-
Fixed an exception in the VS Editor
-
- VOXporter
-
-
No changes in this build
-
-
- Changes in 2.3.2 (Bandol GA 2.3b)
- Compiler
-
-
Added support for Bracketed Strings ([Some String containing quotes: '' and ' ] )
-
Added support for Support for PRIVATE/PUBLIC syntax with &Id and &Id.Suffix notation
-
EXE files were created without manifest before, unless you were using a WIN32 resource with a manifest. This manifest is now correctly added to exe files when no manifest is supplied.
-
The handling of unmanaged resources in relation to version resources and manifests has changed:
-
-
When the compiler detects native resources it will now check to see if there is a version and/or manifest resource included.
-
When there is no manifest resource, then the default manifest resource will be added to the resources from the Win32 resource file.
-
When there is a version resource then this version resource will be replaced by the version resource that the compiler generates from the Assembly attributes.
-
This should help people coming from VO, so they can use AssemblyVersion etc for all their assemblies, also the ones that have menu and window resources. If there happens to be a versioninfo resource in the source then this is ignored.
-
Of course we have added a command line option to suppress this: if you use the commandline option "-usenativeversion" then the native version that is included in the Win32 resource will be used. If there is no version resource included in the Win32 resource file, then this commandline option is ignored.
-
-
-
-
PCOUNT() and ARGCOUNT() are now supported inside ACCESS/ASSIGN methods. The number of parameters that you can pass is still fixed, but both functions will now return the # of parameters defined in ACCESS and/or ASSIGN methods.
-
We fixed a problem that a compiler error "Failed to emit module" was produced instead of showing the real problem in the code (a missing type) .
-
Extended match markers in the preprocessor, such as <(file)> in the USE udc, now also properly match file names.
-
Improved the detection algorithm that distinguishes parenthesized expressions and typecasts. This algorithm is now:
-
-
Built in type names between parentheses are always seen as a typecast. For example (DWORD), (SHORT) etc.
-
Other type names between parentheses may be treated as typecast but also as parenthesized expression. This depends on the token following the closing parenthesis. When this token is an operator such as +, -, / or * then this is seen as parenthesized expression. When the token following the closing parenthesis is an opening parenthesis then the expression is seen as a typecast. Some examples:
-
-
- ? (DWORD) +42 // this is a typecast ? (System.UInt32) +42 // this is a parenthesized expression and will NOT compile ? (System.UInt32) 42 // this is a typecast because there is no operator before 42 ? (System.UInt32) (+42) // this is a typecast because +42 is between parentheses
-
-
Code that calls the Axit() method now generates a compiler error.
-
We have implemented the /vo11 compiler option
-
We have fixed several signed/unsigned warnings
-
You can now use PCall() on typed function pointers stored inside structures (this is used in the VO Internet Server SDK)
-
The lexer now recognizes (in the FoxPro dialect) the For() and Field() functions and you do not need to prefix these with @@ anymore.
-
- Runtime
-
-
Fix for StrZero() with negative values
-
Fix for IsSpace() crashing with empty or null string
-
AFill() in the VFP dialect now fills also elements in subarrays (for multi dimensional arrays)
-
NoIVarGet() and NoIvarPut() no longer convert the IVar names to Symbol. That way the original casing is kept when calling the NoIVarGet() and NoIVarPut() methods in a class
-
The VFP and XPP Abstract classes are now really abstract.
-
Implemented VFP Empty class.
-
Implemented VFP AddProperty and VFP RemoveProperty functions.
-
Fixed a typo in PropertyVisibility enum name
-
Fixed several errors when calling DBF related functions for a workarea that did not contain an open table.
-
The Seconds() function now returns 3 decimals when running in the FoxPro dialect. Please note that you have to add SetDecimal(3) to actually see the 3rd decimal
-
The Like() function is now case sensitive in the FoxPro dialect and case insensitive in all other dialects. The _Like() function is case sensitive in all dialects.
-
ASort() was not accepting a 4th argument of type Object(). This has been correct: when you pass an object that has an Eval() method then this method will be called to determine the right sort order.
-
When setting/restoring global State with the Set() function, some values that are synchronized by the runtime could get out of sync. This could result in incorrect date formats or similar errors. This has been fixed.
-
Several VFP compatibility functions have been added (some contributed by Thomas Ganss).
-
We have added several VFP functions such as
-
When you set a "global setting" using the Set() function the runtime now makes sure that related settings are set accordingly. For example Setting Set.DateFormat now also updates the DateFormatNet and DateFormatEmpty.
-
Fix for PadC() function with non standard filler
-
We have added DBOI_COLLATION and DBS_CAPTION for FoxPro specific properties
-
- VO SDK
-
-
We have removed the versioninfo resource from the GUI classes sourcecode. The version info is now generated from the Assembly attributes
-
We have cleaned up the code and removed the warnings 9020 and 9021 from the suppressed warnings, since the compiler now handles this correctly.
-
- RDD system
-
-
The DBFVP driver no longer fails to open a DBF when the DBC file is used exclusively by someone else
-
Added support for reading captions with DBS_CAPTION and collations with DBOI_COLLATION
-
The DBFNTX driver was not setting the HPLocking flag properly when creating new indexes
-
- Visual Studio integration
-
-
The type lookup for variables declared with a VAR keyword could sometimes go into an infinite loop. This has been fixed.
-
Members starting with '__' are now only hidden from completion lists when the 'Hide Advanced members' checkbox in the general editor options is checked
-
Added support for colorizing BRACKETED_STRING constants
-
Fixed a bug in the keyword case synchronization code.
-
The code behind the VS Form editor had problems with methods declared without return type. As a result forms could not be opened. This has been fixed.
-
Improved intellisense info for Defines and Enum members
-
You can now enable/disable /vo11 in the project properties dialog
-
- VOXporter
-
-
When porting from Clipboard contents, now VOXporter puts back the modified code to the clipboard
-
Added option to remove ~ONLYEARLY pragmas
-
- Installer
-
-
The installer now has a new command line parameter "-nouninstall" that prevents the automatic installation of a previous version. This allows you to install multiple versions of X# side by side. Please note that the installer sets a registry key to the location where X# is last installed. This location will be used by the Visual Studio integration to locate the compiler. If you don't change this then all VS installations will always use the version of X# that is last installed. See the topic about the build process in VS and with MsBuild for information about how this mechanism works. Also if you choose to install the X# runtime assemblies in the GAC then newer versions of these runtime DLLs will/may overwrite older versions. This depends on the fact if the newer DLLs have a new Assembly version. At this moment all X# runtime DLLs (still) have version 2.1.0.0 even when X# itself is now on version 2.3.2.
-
The installer now lists all found instances of VS 2017 and VS 2019, including the Visual Studio Buildtools, so you can choose to install in a particular instance of these versions of Visual Studio or simply in all instances. Please note that when you run X# with the -nouninstall command line option, this will prevent the installer from removing X# from VS installations where it was previously installed.
-
We have added some documentation about all the installer command line options to the help file.
-
- Documentation
-
-
Fixed errors in the documentation of escape codes
-
We have added a chapter with tips and tricks that contains the following topics at this moment.
-
Added description of the installer command line arguments
-
Added description of the Build process in VS and with MsBuild
-
Added topics describing the dialect "incompatibilities" in the X# runtime. Please note that this topic is not complete yet.
-
How to catch errors at startup
-
Compiler magic in the startup code
-
Special classes generated by the compiler.
-
-
- Changes in 2.3.1.0 (Bandol GA 2.3a)
- Compiler
-
-
When compiling in case sensitive mode, the compiler now checks to see if a child class declares a method that only differs from a method in its parent class by case
-
-
-
The warning message about assigning to a foreach iterator variable has been changed from "Cannot assign" to "Should not assign"
-
#pragma warnings was not working with the xs1234 syntax but only with numbers. This has been corrected
-
-
- Runtime
-
-
Added the SetFieldExtent method to the IRdd interface
-
The USUAL type no longer "caches" the dialect setting
-
Fixed some problems with ACopy() with skipped or negative arguments.
-
The return value for Alias() is now in upper case.
-
- VO SDK
-
-
The VO SDK Console class now uses the System.Console class internally. The only functionality that is no longer available is:
-
-
It does not respond to the mouse anymore
-
Creating a "new" console window is not supported.
-
-
- RDD system
-
-
Fixed a problem in the Advantage RDDs that was caused by a casing problem (a method in a child class had a different case than the method in the parent class that it tried to override). This is why we also added a check to the compiler.
-
Creating an NTX with the DBFNTX driver could fail in some situations due to timing issues. This has been fixed.
-
- Visual Studio integration
-
-
Fixed a problem in keyword case synchronization that could corrupt the editor contents.
-
-
- Changes in 2.3.0.0 (Bandol GA 2.3)
- Compiler
-
-
Syntax errors (1003) or Parser errors (9002) in a source file could lead to multiple errors in the error list. We are now only reporting the first of these error types in a source file.
-
Implemented the -cs (Case Sensitive identifiers) compiler option
-
The compiler now includes the source for a compiletime codeblock as string in that codeblock. Calling ToString() on a compile time codeblock will retrieve this string.
-
Fixed a problem that memory variables were not updated when passed to a DO <proc> WITH statement
-
Accessing or assigning undefined properties or calling undefined methods in typed code was generating a compiler error. The compiler now detects if the type has a NoIVarGet(), NoIVarPut() or NoMethod() method, and when it finds the appropriate methods then a compiler warning (XS9094) is generated instead of a compiler error.
-
Casting a numeric to a LOGIC with the LOGIC(_CAST, numValue) construct was only looking at the lowest byte of numValue. If the lowest byte was zero and a higher byte was non zero the result would be FALSE. The compiler now compiles this into (numValue <> 0).
-
The compiler now supports an (optional) THEN keyword for the IF statement
-
Added support for the FoxPro CURRENCY type.
-
The Value keyword is always compiled in lower case in PROPERTY SET methods
-
Unterminated strings are now detected at the end of the line.
-
Added ENDTRY UDC for FoxPro
-
Added support for #pragma warning(s). See the #pragma warnings topic in the help file for more info.
-
Added support for #pragma options. See the #pragma options topic in the help file for more info.
-
- Runtime
-
-
Added XSharp.Data.DLL which contains support code for .Net SQL based data access used by the RDD system and the new Unicode SQL classes.
-
DbEval() was throwing an exception when no FOR block or no WHILE block was passed
-
DbEval() was throwing an exception when the block that is evaluated was not returning a logical expression
-
The workarea event for OrdSetFocus() had an error which would result in an "Operation Failed" error for this event, even when the event succeeded.
-
The index operator on USUALs containing STRINGS (which is only supported in the Xbase++ dialect) was not taking into account that the indices were already ZERO based,
-
Calling DbCreate() with incorrect lengths for Date or Logic fields was throwing an exception, these are now automatically corrected
-
Added a fix for converting USUAL values of type STRING with NULL to STRING
-
Fixed a problem in __FIeldSetWa() when the area was NIL or "M".
-
-
-
Added the FoxPro CURRENCY type. These are also supported in USUAL variables. Internally the values of a CURRENCY variable are stored as Decimal but rounded to 4 decimal places.
-
Most runtime DLLs are now compiled in Case Sensitive mode.
-
Fixed a problem in the STOD() function, so it allows strings that are longer than 8 characters.
-
We have added some VFP functions to the runtime, such as the Just..() functions and AddBs(). Several other functions are there but not implemented. They are marked with an [Obsolete] attribute and will throw a NotImplementedException when called.
-
When running on windows the low level File IO system now uses native windows File access in stead of the managed access. This also affects the RDD system.
-
Fixed problems in ACopy(), Transform(), Str()
-
- VOSDK Classes
-
-
Added DbServer:FieldGetBytes() and DbServer:FieldPutBytes() to read the 'raw' bytes of a string field. Please note that (in ccOptimistic mode) the bytes value is NOT cached and that you have to manually lock and unlock the server when calling FieldPutBytes().
-
Added several missing defines
-
Synchronized the VO SDK to the VO 2.8 SP4 SDK. The only changes that are not included are the ones from the DateTimePicker class. These changes were causing conflicts with the existing code in the X# VOSDK.
-
- RDD System
-
-
Querying the header size for the Advantage RDD would cause an exception. This has been fixed
-
Fixed a problem with DbRlockList() and the advantage RDD
-
Skipping in a cursor for the Advantage RDDs was not refreshing the EOF and BOF flags for related tables
-
Fixed a problem writing strings in FPT files
-
The AX_Get.. Handle() functions were not properly returning the handles
-
We have added several missing Advantage related functions.
-
The DBFVFP driver was not writing the block for DBC backlinks to the file header when creating a new file, which resulted in negative record numbers.
-
We have added (temporary) support for reading field names from DBC files for the DBFVFP driver. As a result CDX files which use the long field names in index expressions are now also opened correctly
-
Fixed a problem in the CopyDb() code for the DBF RDD
-
The DBFCDX RDD now implements the BLOB_GET and also BlobExport() and BlobImport()
-
Packing, Zapping or Rebuilding a CDX index with a Custom or Unique flag would not keep these flags. This has been fixed.
-
When you create a file with the DBFVFP driver you can now include Field Flags in the field type of the DbCreate() array by following the type with a colon and one or more flags, where flags is one of: N or 0:Nullable BBinary +AutoIncrement UUnicode. (not supported by FoxPro) Other flags may follow ( for example Harbour also has E = Encrypted and C = Compressed) Note:
-
-
Please note that the size of the field is the # of bytes, so {"NAME","C:U",20,0} declares a Unicode character field of 10 Unicode characters and 20 bytes.
-
We do not validate combinations of flags. For example AutoIncrement is only working for fields of type Integer.
-
-
-
-
DbFieldInfo(DBS_PROPERTIES) returns 5 for all RDDs with the exception of the DBFVFP driver. That driver returns 6. The 6th property is the FLAGS field. This field is a combination of the DBFFieldFlags enum values.
-
Fixed a problem with AppendDb() and CopyDb() for the Advantage RDD
-
Fixed a problem in the Append() code of the DBF RDD. When Append() was called and no data was written then the record that was written to disk could be corrupted. The Append() method now directly writes the new record with blanks..
-
The Fully qualified names of the Advantage RDDs inside XSharp.RDD.DLL are now the same as in the AdvantageRDD.DLL for Vulcan.
-
-
-
We have added a FileCommit event to the notifications. This sent when a workarea is committed.
-
- Macro compiler
-
-
The macro compiler now also recognizes the Array(), Date() and DateTime() functions.
-
Fixed problems with Aliased expressions
-
On the place where the macro compiler expects a single expression you can now also have an expression list between parentheses. The last expression in the list is seen as the return value of the expression list
-
- Visual Studio integration
-
-
The option to compile case sensitive has been enabled in the VS project system
-
-
-
The speed of 'Format Document' has improved a lot.
-
The XSharp Intellisense Optionspage in Tools/Options now has a scroll bar when needed
-
The ToolPalette in the VO Window editor now has icons
-
-
-
We have added templates for VO MDI windows and VO SDI windows.
-
- Build System
-
-
When compiling native resources the resource compiler now automatically includes a file with some defines such as VS_VERSION_INFO
-
- Debugger
-
-
When you enter a watch expression in the debugger or a breakpoint condition, you can now use 1 based array indices. Our debugger will now automatically subtract 1 when evaluating the expression.
-
- VOXporter
-
-
Fixed a problem in the Windows Forms code generation
-
-
-
You can now also export single MEF files, single PRG files and data from the Clipboard.
-
Code between #ifdef .. #endif is not touched by VOXPorter
-
-
- Changes in 2.2.1.0 (Bandol GA 2.2a)
- Compiler
-
-
When compiling code that contained an assign and not an access then trying to read the access could lead to a compiler exception. This has been fixed.
-
- Runtime
-
-
Added a missing _Run() function
-
- Visual Studio integration / Build system
-
-
Fixed a problem that caused a dialog to be shown with the message "The 'XSharp Project System' package did not load correctly."
-
Fixed a problem with writing response files for the resource compiler when the source file names contained ASCII characters with accents or other characters > 128. Even though this is now fixed we still recommend not go to crazy with file names, because these names have to be converted from Unicode to Ansi, since the resource compiler can only read response files in Ansi format.
-
Fixed a problem for certain QuickInfo / Tooltip windows
-
The VO item templates now have a condition around the #include statements for the Vulcan include files, since these are no longer needed when compiling for the X# runtime.
-
Added Support for the "Auto" window in the debugger
-
Expressions in the Watch window, Breakpoint conditions etc may now contain SELF, SUPER and a colon separator. Unfortunately they are still case sensitive.
-
- VOXPorter
-
-
we now detect that a class has fieldnames and accesses/assigns with the same name. This was allowed in VO but no longer in .Net. The field names will be prefixed with an underscore inside the class.
-
We now prefix the name "Trace" with @@ because this is quite often used to conditional compile tracing code in VS.
-
-
- Changes in 2.2.0.0 (Bandol GA 2.2)
- Compiler
-
-
The compiler now recognizes the functions Date(), DateTime() and Array(), even though their names are the same as type names. Date() with 1 parameter will still be seen as a cast from that parameter to a Date(), like in the following example LOCAL dwJulianDate ASDWORD LOCAL dJulianDate ASDATE dwJulianDate := DWORD( 1901.01.01) dJulianDate := DATE(dwJulianDate) // This is still a cast from Date to DWORD However when Date is called with 0 or 3 parameters then either the current date is returned (like with Today()) or a date is constructed from the 3 parameters (like in ConDate()) The DateTime() function takes 3 or more parameters and constructs a DateTime() value. The Array() function takes the same parameters as the ArrayNew() function.
-
When choosing overloads for String.Format() and a usual expression is passed as first reference we no longer allow the compiler to choose one of the overloads that expects an IFormatProvider interface.
-
Parameters passed by reference to untyped methods/functions now have the IsByRef flag set. You can query for "By Reference" parameters by checking the parameter with IsByRef(uParameter). Please note that after assigning a new value to a parameter, this flag will be cleared.
-
The compiler now also allows to pass aliased fields and memvars by reference to untyped functions. Even undeclared memvars are allowed. Please note that the assignment back to the field and memvar will happen after the call to the function returns. So inside the function the field or memvar will still have its original value.
-
Using ':' as send operator in Interpolated strings is ambiguous because ':' is also used add format specifiers to interpolated strings. The compiler now detects and allows "SELF:", "SUPER:" and "THIS:". If you want to be safe use the '.' as send operator inside interpolated strings for other variables, or simply don't use interpolated strings, but use String.Format like in: ? String.Format("{0} {1}", oObject:Property1, oObject:Property2) in stead of ? i"{oObject:Property1} {oObject:Property2}" This is the code that the compiler will produce anyway
-
-
- Macrocompiler
-
-
The macro compiler now recognizes and compiles nested codeblocks, such as LOCAL cb := {|e| IIF(e, {||SomeFunc()}, {||SomeOtherFunc}) } ASCODEBLOCK cb := Eval(cb, TRUE) // cb will now contain {||SomeFunc()} ? Eval(cb)
-
In the FoxPro dialect the macro compiler now recognizes AND, OR, NOT and XOR as logical operators
-
- Runtime
-
-
Added some Xbase++ compatible functions, such as DbCargo(), DbDescend() and DbSetDescend().
-
The DateCountry Enum now also the values System and Windows, which both read the date format from the Regional settings in the System.
-
We have added a WrapperRDD class that you can inherit from. This allows you to wrap an existing RDD and subclass methods of your choice. See the documentation of WrapperRDD for an example.
-
We had added a XPP member to the CollationMode enum with the same number as Clipper. This was confusing to some users. We have now give the XPP member a new number.
-
OleAutoObject:NoMethod() now behaves different in the Vulcan dialect (to be compatible with Vulcan). In the Vulcan dialect the method name is inserted at the beginning of the list of arguments. In the other dialects the arguments are unchanged, and you need to call the NoMethod() function to retrieve the name of the method that was originally called.
-
All settings in the runtime state are now initialized with a default value, so the Settings() dictionary in the runtimestate will have values for all Set enum values.
-
The previous change has fixed a problem with the Set() function when setting values for logical settings with a string "On" or "Off". Because some settings were not initialized with a logic this was not working.
-
When creating indexes with SetCollation(#Ordinal) the speed is a bit better now.
-
The runtimestate now has a setting EOF. When this is TRUE (which is done automatically for the FoxPro dialect) then MemoWrit() will write a ^Z (chr(26)) after a text file, and MemoRead() will remove that character when it finds it.
-
The runtimestate now has a setting EOL. This defaults to CR - LF (chr(13+chr(10)). This setting is used for line delimiters when writing files with FWriteLine().
-
- RDD system
-
-
-
Fixed locking problems in the DBFCDX RDD that were causing problems when opening files shared between multiple apps but also between multiple threads. The RDD now should properly detect that the CDX was updated by another process or thread.
-
Fixed a problem with the File IO system when running multiple threads
-
Fixed a problem with the File() and FPathName() functions when running multiple threads
-
Added support for Workarea Cargo (See DbCargo())
-
Numeric columns with trailing spaces were returned as 0. This has been fixed.
-
Fixed a problem in the DBFCDX driver that was happening when many keys were deleted / updated and index pages were deleted.
-
Fix a read error at EOF for the DBF RDD.
-
- VOSDK
-
-
Fixed a problem in the DbServer destructor when called at application shutdown for a server that was already closed.
-
- Visual Studio integration
-
-
Fixed speed problem in the "Brace Matching" code with the help of a user (thanks Fergus!)
-
You should no longer be able to edit source code when the debugger is running.
-
We have added a property "Register for COM Interop" to the build options of the Project Properties.
-
We have updated the assembly info templates . They now have a GUID and Comvisible attribute.
-
Empty lines in the editor buffer could sometimes trigger an exception. This has been fixed
-
Text between TEXT .. ENDTEXT is no longer changed by formatting options in the editor, such as indenting or case synchronization.
-
Incomplete strings will have the color of normal strings in the editor.
-
QuickInfo and Completion lists will follow the "format case" setting of the editor for keywords.
-
If a certain option from the Tools/Options was not set then loading a project that was saved with files open in the editor could result in an exception, causing the project to be loaded with no visible items. Unload and Reload would fix that. This will no longer happen.
-
We have made some changes to make solutions open and close faster.
-
Some colors were difficult to read when the Visual Studio Dark theme was selected. This has been fixed.
-
Brace matching was sometimes incorrectly matching an END CLASS with the BEGIN NAMESPACE. This should no longer happen.
-
Fixed an exception when opening a solution under certain circumstances which would display an error inside VS that the XSharp Project System was not loaded correctly.
-
The Code Generator for Windows Forms, Settings and Resources now respect the keyword case setting from the Tools - Options TextEditor/XSharp page.
-
- VOXPorter
-
-
Folder names ending with a backslash could confuse VOXPorter
-
-
- Changes in 2.1.1.0 (Bandol GA 2.11)
- Compiler
-
-
We have added new syntaxes for OUT parameters. You can now use one of the following syntaxes
-
- LOCAL cString asSTRING cString := "12345" IF Int32.TryParse(cString, OUTVAR result) // this declares the out variable inline, the type is derived from the method call ? "Parsing succeeded, result is ", result ENDIF IF Int32.TryParse(cString, OUT result2 AS Int32) // this declares the out variable inline, the type is specified by us ? "Parsing succeeded, result is ", result2 ENDIF IF Int32.TryParse(cString, OUTNULL) // this tells the compiler to generate an out variable, we are not interested in the result ? "Parsing succeeded" ENDIF IF Int32.TryParse(cString, OUTVAR _) // this tells the compiler to generate an out variable, we are not interested in the result.
- // The name "_" has a special meaning "ignore this" ? "Parsing succeeded" ENDIF
-
-
The compiler now allows the function names Date(), DateTime() and Array(). The runtime has these functions (see below)
-
Fixed a preprocessor problem where the <token> match marker inside UDCs was stopping matching tokens when the .not. or ! operator was found after another logical operator such as .AND. or .OR..
-
Added support for <usualValue> IS <SomeType>. The compiler will automatically extract the contents of the USUAL and wrap it in an object and then apply the normal IS <SomeType> operation.
-
Fixed a problem with Interpolated strings where the '/' character was not properly recognized.
-
The compiler now supports the FoxPro syntax for cursor access. When dynamic memory variables are disabled this always gets translated to reading a field from the current cursor/workarea.
USE Customer SCAN ? Customer.LastName ENDSCAN USE
-
- When memory variables are enabled then this code could also mean that you are trying to read the Lastname property of a variable with the name "Customer" like in the example below:
- USE Invoices Customer = MyCustomerObject{} SCAN ? Customer.LastName, Invoice.Total ENDSCAN USE
- You can also use the M prefix to indicate a local variable or memory variable. The compiler will try to resolve the variable to the local first and when that fails it will try to resolve the variable to a memory variable (when dynamic memory variables are enabled).
- Runtime
-
-
We have added support functions for the FoxPro cursor access syntax.
-
In the Vulcan dialect the NoMethod() method now receives the methodname as first parameter (this is NOT compatible with VO)
-
Added functions Date() (can have 0 or 3 parameters, equivalent to Today() and ConDate()), DateTime() and Array().
-
Added fixes and optimizations for functions such that take an area parameter such as Used(uArea) and Eof(uArea).
-
AScan() and AScanExact() now return 0 when a NULL_ARRAY is passed.
-
-
- RDD
-
-
There was a problem reading negative numbers from DBFs. This has been fixed
-
Fixed an exception when FPT drivers were writing data blocks in the FPT file with a 0 byte length.
-
The DBF() function returns the Full filename in the FoxPro dialect and the alias in the other dialects.
-
When creating an CDX index for a completely empy DBF file then an index key would be inserted for the phantom record. This has been fixed.
-
-
- Changes in 2.1.0.0 (Bandol GA 2.1)
- Compiler
-
-
We have added support for parameters by reference to function and method calls for untyped parameters
-
In the Xbase++ and FoxPro dialect arguments passed with '@' are always treated as BY REF arguments because these dialects do not support the 'AddressOf' functionality
-
When /undeclared was used and an entity added a new private then this private was not cleared when the entity went out of scope. This has been fixed.
-
Compiling oObject?:Variable was not handled correctly by the compiler
-
Fixed an internal compiler error when calling SELF:Axit()
-
Parameters for the DO statement are now passed by reference
-
Changed the order of 'necessary' assembly names when compiling for not core dialect.
-
We have added support for several SET commands, such as SET DEFAULT, SET PATH, SET DATE, SET EXACT etc.
-
- Runtime
-
-
We have made some changes to get XSharp.Core to run on Linux
-
We have fixed a problem in the Subtract operator for the Date type. This changes the signature of the Subtract operator which has forced us to increase the Assemblyversion of the runtime.
-
The Xbase++ dialect now allows the [] operator on a string inside a usual. This returns a substring of 1 character for the given position.
-
We have fixed an incorrect event for the OrderChanged event
-
CoreDb.BuffRefresh was sending an incorrect enumerator value to the IRDD.RecInfo() method.
-
The IVarList() function was including protected Fields and Properties. This has been fixed.
-
IsInstanceOfUsual() could not be used if an objects was of a subclass of CodeBlock. This has now been fixed.
-
We have added many overloads of workarea related functions with an extra parameter to indicate a workarea number or workarea name. For example for the EoF(), Recno(), Found() and Deleted() functions
-
We have added Xbase++ collation tables. The SetCollationTable() function now selects the right collation.
-
Several Array related functions now have better checks for NULL arrays
-
The SubcodeText property in the error class is now Read/Write. When the value has not been written then the subcode number is used to lookup the value of the property.
-
MExec() was not always evaluating the compiled codeblock. This has been fixed.
-
We have added some missing Goniometric functions, such as ACos(), ASin() and more.
-
In the Xbase++ dialect the FieldGet() and FieldPut() functions no longer throw an error for incorrect field numbers
-
We have added a missing MakeShort() function and SEvalA() function.
-
The DateCountry settings now include a System setting which will read the date format from the settings for the current culture.
-
- Macrocompiler
-
-
When the macro compiler detects an ambiguous method or constructor it now includes the signatures of these in the error message
-
We have added a new IMacroCompiler2 interface that adds an extra property "Resolver". This property will may receive a Delegate of type "MacroCompilerResolveAmbiguousMatch". This delegate has the following prototype: DELEGATE MacroCompilerResolveAmbiguousMatch(m1 as MemberInfo, m2 as MemberInfo, args as System.Type[]) ASLONG
-
The delegate will be called when the macro compiler detects an ambiguous match and receives the System.Reflection.MemberInfo for possible candidates and an array of the detected types of the arguments (detected at compile time). The delegate can return 1 or 2 to choose between either candidate. Any other value means that the delegate does not know which of the ambiguous members to choose. If the macro compiler finds more than 2 alternatives, it first calls the delegate with alternatives 1 & 2, and then the selected delegate from these 2 and alternative 3 etc.
-
You can register a function or method as delegate with the new function SetMacroDuplicatesResolver()
-
We are now handling (one level of) nested Macros. So the macro compiler correctly compiles a codeblock like {|e| iif(e, {||TRUE}, {||FALSE})}
-
The macrocompiler now allows comparisons between Integers and Logics (just like the Usual type in the runtime). This is still not recommended !
-
The macrocompiler now allows the use of '[' and ']' as string delimiters. This is NOT allowed in the normal compiler because these delimiters will be impossible to differentiate from attributes.
-
We have fixed a problem when a late bound call was needed for method names that were matching method names or property names in the Usual type (such as a method with the name Item()).
-
PCount() for macro compiled codeblocks was always returning 1. This has been fixed.
-
- VOSDK
-
-
Fixes a problem with DbServer objects that were not closed in code. The existing code was trying to close the workarea from the destructor. But in .Net the destructor runs in a separate thread and in that GC Thread there where no files open...
-
Removed unneeded calls to DbfDebug()
-
The AdsSqlServer class is now added to the VORDDClasses assembly
-
- RDD
-
-
We have fixed a problem with parsing incorrect or empty dates
-
We have fixed a problem with reading Dates in the Advantage RDD that could cause a Heap error when reading dates.
-
We have added several 'missing' functions for Advantage support that were in the 'Ace.Aef' for VO
-
We have added support for Character fields > 255 characters
-
DbSetScope() now moves the record pointer to the first record that matches the new scope.
-
DbCreate() for the DBFNTX driver with SetAnsi(TRUE) was creating a file with a first byte of 0x07 (or 0x87) . This no longer happens in the Xbase++, FoxPro and Harbour dialects because this first byte is VO specific only
-
Some FoxPro memo values are written with an extra 0 byte at the end. This extra byte is now suppressed when reading these values.
-
We have fixed a problem with the version numbers in CDX files not being updated and also improved CDX locking.
-
Xbase++ was not recognizing NTX indices when the tag name in the index header was not in uppercase. This has been fixed.
-
We have fixed a (performance and size) problem when creating CDX indexes.
-
When opening a DBF file that does not have a codepage byte, we default to the current Windows or DOS codepage, depending on the current SetAnsi() setting.
-
Optimized reading numeric, date and logical columns
-
-
- Visual Studio integration
-
-
The WCF Service template has been fixed
-
We have migrated the project system to the Asynchronous API. This should make loading of solutions with a large number of X# projects a bit faster.
-
Fixed a problem in the Keyword Case synchronization that could lock up the UI for several seconds
-
Fixed an exception in the BraceMatching code.
-
Uncommenting a block of lines was sometimes leaving the comments in front of empty lines. This has been fixed.
-
We have improved the (XML) documentation lookup for types, methods, fields, properties and parameters.
-
We have improved the type lookup between X# projects.
-
- VOXPorter
-
-
DbServer and FieldSpec entities are now also exported
-
VOXPorter now also can genarate a separate project/application that contains Windows Forms versions of the VO GUI windows found in the VO Applications.
-
When running VOXPorter you now can choose to export to XIDE, Visual Studio or Both.
-
-
- Changes in 2.0.8.1 (Bandol GA 2.08a)
- Compiler
-
-
Fixed a recursion problem in the preprocessor
-
MEMVAR-> and FIELD-> were no longer correcty detected This has been fixed.
-
We have fixed several issues in dbcmd.xh
-
Fixed a problem with return statements inside Lambda expressions.
-
The = Expression() statements (FoxPro dialect) was not generating any code. This has been fixed.
-
- Runtime
-
-
XPP.Abstract.NoMethod() and XPP.DataObject.NoMethod() were still expecting the method name as 1st parameter.This has been fixed.
-
StretchBitmap() was doing the same as ShowBitmap() because of an incorrect parameter. This has been fixed.
-
- Visual Studio integration
-
-
Improved the Format-Document code
-
Fixed a problem in the VS Parser when looking up the type for variables defined with the VAR keyword which could send VS in an endless loop.
-
The contents of the TEXT .. ENDTEXT block and the line after the \ and \\ tokens now has its own color
-
-
- Changes in 2.0.8 (Bandol GA 2.08)
- Compiler
-
-
The compiler had a problem with the "return" attribute target
-
Errors inside the "statementblock" rule are now better detected and the compiler will no longer report many errors after these for correct lines of code.
-
Fixed a problem with Casts to logic
-
Fixed a problem with undeclared variables used as counter for For Loops
-
Improved the code generation for FIELDs, MEMVARs and undeclared variables for prefix operation, postfix operations and assignments.
-
Improved the code generation for method calls where the parameter is a ref or out variable when default parameters are involved. The compiler now generates extra temporary variables for these calls.
-
-
-
In the dialects where this relevant the compiler now also supports ENDFOR as alias for NEXT and FOR EACH as alias for FOREACH.
-
Added support for the DO <proc> [WITH arguments] syntax
-
- Runtime
-
-
The DbCreate() function now creates a unique alias when the base filename of the file to create is already opened as an alias
-
The Numeric overflow checking for USUAL values now follows the overflow checks of the main app
-
DbUnLock() now accepts an (optional) record number as parameter
-
XMLGetChild() was throwing an exception when no elements were found
-
XMLGetChildren() was throwing an exception
-
Fixed a problem in 2 rules inside "dbcmds.xh"
-
The XSharpDefs.xh file now automatically includes "dbcmd.xh"
-
Some datatype errors were reported incorrectly.
-
The "NoMethod" method for late bound code was called with incorrect parameters. This has been fixed.
-
Fixed some problems with translating usuals with a NIL value to string or object.
-
In Xbase++ the Set() function also accepts strings with the value "ON" or "OFF" for logical settings. We are now allowing this too.
-
Set(_SET_AUTOORDER) now accepts a numeric second parameter just like in VO (Vulcan was using a Logic parameter)
-
We have added some support classes to the FoxPro class hierarchy for the FoxPro class support (Abstract, Custom and Collection). More classes will follow later.
-
Fixed a problem with transform and "@ez" picture.
-
- VOSDK
-
-
Fixed a problem in the SQLSelect class when re-opening a cursor.
-
- RDD System
-
-
Fixed a problem reading Advantage MEMO fields
-
Improved the error messages when an index cannot be opened due to an index expression with an error (for example a missing function)
-
We have added the option to install an event handler in the RDD system. See the topic Workarea Events for more information.
-
Skip, Gobottom and other workarea operations that change the current record will no longer set EOF to FALSE for workareas with 0 records.
-
Clearing the scope in an Advantage workarea would throw an exception when there was no scope set. This has been fixed.
-
Unlocking a record in an Advantage workarea would throw an exception when there was no record locked. This has been fixed.
-
DbSetRelation() was not working correctly. This has been fixed.
-
- VS Integration
-
-
Fixed a problem with the code generation for DbServer and FieldSpec entities
-
Added support for the Import and Export buttons in the DbServer Editor
-
Improved entity parsing inside the editor in the Xbase++ dialect.
-
The VS Parser was not colorizing the UDC tokens (including ENDFOR) unless the source file had preprocessor tokens itself. This has been fixed.
-
Improved block detection for new END keywords.
-
The VS Integration now recognized the class syntax for VFP type classes.
-
Fixed a problem in the code that was checking to see which project system "owns" the PRG extension.
-
Added compiler option to the Project Property pages to suppress generating a default Win32 manifest.
-
- VOXporter
-
-
VOXPorter was ignoring entities that were not properly prototyped in VO. This has been fixed
-
- FoxPro dialect
-
-
We have added a compiler option /fox1 that controls the class hierarchy for objects. With /fox1 enabled (the default in the FoxPro dialect) all classes must inherit from the Custom class. The code generation for properties stores the values for properties in a collection inside the Custom class. With /fox1- properties will be generated as "auto" properties with a backing field.
-
We have added support for FoxPro classes. See the topic FoxPro class syntax for more information about what works and what doesn't work.
-
We have added support for DIMENSION and DECLARE statements (which create a MEMVAR initialized with an array)
-
-
- Changes in 2.0.7 (Bandol GA 2.07)
- Possible breaking change
-
-
We have removed the #define CRLF from the standard header file. There is a DEFINE CRLF in XSharp.Core now. If you are compiling against Vulcan and you are seeing an error about a missing CRLF then you may want to add the following to your code: DEFINE CRLF := e”\r\n”
-
- Compiler
-
-
UDCs that were resulting in an empty list of tokens were triggering a compiler error in the preprocessor. This has been fixed.
-
-
-
Calling a method on an array would be translated to a ASend() with the method name as parameter when the method does not exist in the underlying array class. The compiler will generate a warning now when this happens,.
-
The compiler was producing incorrect code for (USUAL) casts. This has been fixed. In rare cases this may produce a compilation error. If that happens to you then simply create a usual by calling the USUAL constructor: USUAL{somevalue}
-
Fixed several problems with methods declared outside of a CLASS .. END CLASS
-
In the FoxPro dialect NOT, AND, OR and XOR are now allowed as alternate syntax for .NOT.,.AND., .OR. and .XOR.
-
In the FoxPro dialect you can now include statements before the first entity in the file. The compiler will recognize these and will automatically create a function with the name of the source file and will add the code in these statements a body of this function.
-
The compiler now allows to cast an integer expression to logic when /vo7 is enabled. The LOGIC(_CAST is always supported for expressions of type integer
-
Incorrect use of language features (such as using a VOSTRUCT in the Core or FoxPro dialect) is now detected earlier by the compiler leading to somewhat faster compile times for incorrect code.
-
The compiler now also initialized multi dimensional string arrays with an empty string when /vo2 is enabled, like in the code below: CLASS TestClass EXPORTDIM aDim[3,3] ASSTRING ENDCLASS
-
-
-
In previous builds you could not set breakpoints on the source code line with a SELF() or SUPER() call if this line was immediately after the CONSTRUCTOR(). This has been fixed.
-
When a project contains "_DLL METHOD", "_DLL ASSIGN" or "_DLL ACCESS" (after exporting from VO) then the compiler will now generate a more meaningful errormessage.
-
The compiler will no longer produce hundreds of the same error messages when a source file contains many of the same error. After 10 errors per source file the compiler will only report unique error numbers. So if your source code has 20 different error messages then you will still see 20 errors reported, but if your source contains the same error type 100 times then the list will be truncated after 10 errors.
-
The compiler no longer allows code behind end tokens such as ENDIF or NEXT. The standard header file 'XSharpDefs.xh' now includes rules that will eliminate these tokens.
-
- Runtime
-
-
The ++ and -- operators for the usualtype were not working for Date and Datetime values
-
FErase() and FRename() now set FError() to 2 when the source file does not exist
-
The File() function was throwing an exception for paths with invalid characters. It now returns FALSE and sets the Ferror()
-
Several specific numbers were producing incorrect Str() results. This has been fixed.
-
The case of the name of the Value property for several types was changed from Value to VALUE. This caused problems for people that were interfacing with X# code from C# code. The original case has been restored. This change has been reversed.
-
Under certain situations the error stack would not contain the complete list of frames. This has been fixed.
-
The size of the Close and Copy buttons of the Error Dialog has been enlarged so there is more space for translated strings
-
The Pad..() functions were returning a padded version of "NIL" for NIL values. This was not compatible with Xbase++. They now return a string with all spaces. Btw: VO throw an exception when you call Pad..() with a NIL value.
-
Fixed a problem with the PadC() function for values > 1 character.
-
We have changed the Val() function to be more compatible with Visual Objects
-
The runtime contained a second overload for the Space() function that accepted an Int parameter. This was causing problems in the macro compiler. This overload has been removed. You may have to change your code because of that.
-
Fixed a problem in EnforceType() and EmptyUsual() with the STRING type
-
AEval and AEvalOld() now both pass the array index as second parameter to the codeblock that is evaluated
-
- RDD System
-
-
Fixed a problem that EOF and BOF were not both set to true when opening an empty DBF with an index
-
Fixed a problem with DbSeek() and Found() for DBFNTX and DBFCDX
-
The DBF class was not properly decoding field names and/or index expressions that contain Ascii characters > 127 (field names like STRAßE)
-
File dates were updated when a dbf was closed even when nothing was changed. This has been fixed.
-
The runtime now contains code that closes all open workareas at shutdown. This should help to prevent DBF or index corruption.
-
The Advantage RDD was automatically doing a GoTop after the index order was changed. This no longer happens.
-
The Advantage RDD now retries opening DBF and Index files a couple of times before failing.
-
Fixed a small incompatibility between DBFCDX and AXDBFCDX
-
- VS Integration
-
-
The Core Classlibrary template had a typo in a file name which caused it not to be loaded correctly
-
The code generator for the Windows Forms editor was duplicating USING statements. This has been fixed. Duplicate using statements will be deleted when a form is opened and saved in the designer.
-
The compilation messages on the output window for the compile time and the number of warnings and errors is now only shown for the build verbosity normal and higher. The warnings and errors message is also shown for lower build verbosity if there are compiler errors.
-
The project system will no longer update the version number in the project file if the project file was created with build 2.0.1 or later.
-
Fixed a problem with setting and clearing the "Specific version" property for Assembly References.
-
The default templates for the VO compatible editors are now installed in the XSharp\Templates folder and the editor uses this location as 'fallback' when you don't have templates in your project
-
The Properties folder is now placed as first child in the tree of a Project, and the VO Binaries items are placed before resource items in the list of children of a source item in the tree.
-
- VOXporter
-
-
VOXPorter now prefixes Debug tokens with @@
-
VOXPorter now removes INSTANCE declaration for properties that are also declared as ACCESS/ASSIGN
-
VOXPorter now adds spaces between variable names that are delimited with .AND. or .OR.. So "a.and.b" becomes "a .and. b"
-
- Documentation
-
-
We have "lifted" some of the documentation of the Visual Objects runtime functions and added these to our runtime documentation. This is 'work in progress', some topics will need some extra work.
-
-
- Changes in 2.0.6.0 (Bandol GA 2.06)
- General
-
-
We received a request to keep the version numbering simpler. For that reason this new build is called Bandol 2.06 and the file versions for this build are also 2.06. The assembly versions for the runtime assemblies are all 2.0, and we intend to keep those stable as long as possible, so you will not be forced to recompile code that depends on the runtime assemblies.
-
Several fixes that were meant to be included in 2.0.5.0 were not included in that build. This has been corrected in 2.0 6.0
-
- Compiler
-
-
A missing ENDTEXT keyword now produces an error XS9086
-
Unbalanced textmerge delimiters produce a warning XS9085
-
The TEXT keyword in the FoxPro dialect is now only recognized when it is the first non whitespace token on a line. As a result of this you can use tokens like <text> in Preprocessor commands again.
-
The VO cast operations on literal strings no longer produce a compiler warning about possible memory leaks.
-
-
- Runtime
-
-
Runtime errors in late bound code were always shown as TargetInvocationException. The true cause of the error was hidden that way. We are now unpacking the error and rethrowing the original error, including the callstack that was leading to that error
-
Some texts in the string resources were updated
-
Calling the Str() function with a -1 value for length and/or decimals produced results that were not compatible with VO. This was fixed.
-
Fixed a problem with DBZap() and files with a DBT memo.
-
In some situations EOF and BOF were not set to TRUE when opening an empty DBF file. This has been fixed.
-
PSZ values with an incorrect internal pointer are now displayed as "<Invalid PSZ>(..)"
-
-
- RDD System
-
-
The code to read and write to columns in an Advantage workarea now uses separate column objects, just like the code for the DBF RDD. This makes the code a bit easier to understand and should make the code a bit faster.
-
-
- VS Integration
-
-
The text block between TEXT and ENDTEXT is now displayed in the same color as literal strings
-
The VO compatible Project Item templates no longer automatically add references to your project
-
Project files from version 2.01.0 and later will no longer be "touched" when opening with this version of the X# project system, since there have been no changes to the project file format since that build.
-
-
- VOXporter
-
-
The CATCH block in the generated Start function now calls ErrorDialog() to show the errors. This uses the new language resources to display the full error with VO compatible error information (Gencode, Subcode etc)
-
-
- Changes in 2.0.5.0 (Bandol GA 2.01)
- Compiler
-
-
Blank lines after an END PROPERTY could confuse the compiler. This has been fixed
-
The TEXT .. ENDTEXT command has been implemented in the compiler (FoxPro dialect only)
-
The \ and \\ commands have been implemented (FoxPro dialect only)
-
Procedures in the FoxPro dialect may now return values. Also the /vo9 options is now enabled by default in the FoxPro dialect. The default return value for a FUNCTION and PROCEDURE is now TRUE in the foxpro dialect and NIL in the other dialects.
-
Error messages no longer refer to Xbase types by their internal names (XSharp.__Usual) but by their normal name (USUAL).
-
- MacroCompiler
-
-
Creating classes with a namespace prefix was not working. This has been fixed.
-
- Runtime
-
-
Fixed a problem with ArrayNew() and multiple dimensions
-
When calling constructor of the Array class with a number the elements were already initialized. This was not compatible with Vulcan.NET. There is now an extra constructor whtich takes a logical parameter lFill which can be used to automatically fill the array
-
The text for the ERROR_STACK language resource has been updated
-
Calling Str() with integer numbers was returning a slightly different result from VO. This has been fixed.
-
Added support functions for TEXT .. ENDTEXT and TextMerge and an output text file.
-
Fixed a problem in the DTOC() function
-
You can now add multiple ImplicitNamespace attributes to an assembly
-
We have added several FoxPro system variables (only _TEXT does something at this moment)
-
- RDDs
-
-
Zap and Pack operations were not properly setting the DBF file size
-
An Append() in shared mode was not properly setting the RecCount
-
Opening a file with one of the Advantage SQL RDDs was not working. This has been fixed.
-
Writing DateTime.Minvalue to a DBF would not write an empty date but the date 1.1.1 This has been fixed.
-
- VO SDK
-
-
Fixed a problem in ListView:EnsureVisible().
-
Some questionable casts (such as the one that cause the previous problem) have been cleaned up
-
- Visual Studio Integration
-
-
Parameter tips for constructor calls were off by one parameter. This has been fixed.
-
When looking for types, the XSharp namespace is now the first namespace that is searched.
Fix a problem in assignment expressions where the Left side is an aliased expression with a workarea in parentheses: (nArea)->LastName := AnotherArea->LastName
-
Multiline statements, such as FOR blocks, no longer generate Multiline breakpoints in the debugger.
-
Fixed a problem where blank lines or lines with 'inactive' preprocessor comments after a class definition would generate a compiler error.
-
Errors for implicit conversions between INT/DWORD and PTR now produce a better error message when they are not supported.
-
USUAL.ToObject() could not be called with the latebinding compiler option was enabled. This has been fixed.
-
Fixed an internal compiler error with untyped STATIC LOCALs.
-
Fixed a problem with aliased expressions.
-
Indexing PSZ values is no longer affected by the /az compiler option
-
- MacroCompiler
-
-
Fixed a problem with some aliased expressions
-
The macro compiler now detects that you are overriding a built-in function in your own code and will no longer throw an "ambigous method" exception but will choose function from your code over functions defined in the X# runtime
-
- Runtime
-
-
FIxed several problems in the Directory() function
-
Fixed problem with indexing PSZ values
-
Added StackTrace property on the Error object so also errors caught in a BEGIN SEQUENCE will have stack information.
-
Fixed problems with "special" float values and ToString(), such as NaN, PositiveInfinity
-
Fixed a problem with RddSetDefault() with a null parameter
-
DbInfo(DBI_RDD_LIST) was not returning a value. This has been fixed.
-
We have updated many of the language resources, Also the Error:ToString() now uses the language resources for captions like 'Arguments' and 'Description'.
-
Low level file errors now include the callstack
-
Fixed some problems in AsHexString()
-
The DosErrString() no longer gets its messages from the language string tables. The messages have been removed and also the related members in the XSharp.VOErrors enum.
-
Added a Turkish language resource.
-
- RDD System
-
-
Fix locking problem in FPT files
-
Fixed several problems with OrdKeyCount() and filters, scopes and SetDeleted() setting
-
Some DBF files have a value in the Decimals byte for field definitions for field types that do not support decimals. This was causing problems. These decimals are now ignored.
-
Opening and closing a DBF without making changes was updating the time stamp. This has been fixed.
-
Fixed problems in Pack() and Zap()
-
Fixed a problem where custom indexes were accidentally updated.
-
Fixed several problems with OrdKeyCount() in combination with Filters, SetDeleted() and scopes.
-
- VO SDK Classes
-
-
Most of the libraries now compile with "Late Binding" disabled for better performance. To help in doing this some typed properties have been added such as SqlStatement:__Connection which is typed as SQLConnection.
-
- Visual Studio integration
-
-
Fixed a problem in the Brace matching code
-
Improved Brace matching for keywords. Several BEGIN .. END constructs have now been included as well as CASE statements inside DO CASE and SWITCH, RECOVER, FINALLY, ELSE, ELSEIF and OTHERWISE
-
Fix a problem with adding and deleting references when unloaded or unavailable references existed.
-
- VOXPorter
-
-
The program is now able to comment, uncomment and delete source code lines from the VO code when exporting to XSharp. You have to add comments at the end of the line. The following comments are supported:
-
- // VXP-COM : comments the line when exporting it // VXP-UNC : uncomments the line // VXP-DEL : deletes the line contents
Code generation for STATIC LOCALs of type STRING was not initializing the variables to an empty string when /vo2 was selected. We have also improved code generation for STATIC LOCALs when they are initialized with a compile time constant
-
In preparation for the support for variables passed by reference to functions/methods with clipper calling convention we are now assigning back the locals variables to the parameter array at the end of a function/method with clipper calling convention.
-
The compiler would not complain if you were assigning a value of one enum to a variable of another enum. This has been fixed.
-
Added support for the FoxPro '=' assignment operators. Other dialects also allow the assignment operator but a warning is generated in the other dialects.
-
Xbase++ classes inside BEGIN NAMESPACE .. END NAMESPACE were not recognized. This has been fixed.
-
Statements inside WITH blocks are no longer constrained to assignment expressions and method calls. You can now use the WITH syntax for expressions anywhere inside a WITH block. If the compiler can't find the WITH variable then it will output a new error message (XS9082)
-
Updated the Aliased Expression rules to make sure that compound expressions properly respect the parentheses.
-
The __DEBUG__ macro was not always set correctly. We have changed the algorithm that sets this macro. When the DEBUG define is set then this macro gets defined. When the NDEBUG define is set then this macro is not defined. When both defines are absent then __DEBUG__ is NOT set.
-
The compiler was allowing you to use the '+' operator between variables/ expressions of type string and logic. This is now flagged as an error.
-
- MacroCompiler
-
-
Fixed a problem with resolving Field names that were identical to keywords or keyword abbreviations (for example DATE and CODE) and for Field names that are equal to built-in function names (such as SET)
-
Fixed a problem where a complicated expression evaluated with an alias prefix was not evaluated correctly.
-
The macro compiler initializes itself from the Dialect option in the runtime to enable/disable certain behavior.
-
The macro compiler now recognizes the "." operator for workarea access and memvar access when running in the FoxPro dialect.
-
- Runtime
-
-
Added functions FieldPutBytes() and FieldGetBytes()
-
Added function ShowArray()
-
Added several defines that were missing, such as MAX_ALLOC and ASC_A.
-
Added Crypt() overloads that accept BYTE[] arguments
-
The ClassDescribe() method for DataObject classes (XPP dialect) now includes properties and methods that were dynamically added.
-
Fixed a problem with the RELEASE command for MemVars. This was also releasing variables defined outside the current function / method.
-
There is now also a difference between the FoxPro dialect and other dialects in the behavior of the RELEASE command. FoxPro completely deletes the variables, the other dialect set the value of the variables to NIL.
-
New PRIVATE memvars are initialized to FALSE in the FoxPro dialect. In the other dialects they are initialized to NIL.
-
Some numeric properties in the RuntimeState were giving a problem when a numeric of one type was written and another numeric type was expected when reading. This has been fixed.
-
Fixed a problem with return NIL values from Macro compiled codeblocks.
-
The parameter to DbClearScope() is now optional
-
The USUAL type now allows to compare between values of type PTR and LONG/INT64 The PTR value is converted to the appropriate Integral type and then an Integral comparison is done.
-
The USUAL type now also allows comparisons between any type and NIL.
-
Casts from USUAL values to SHORT, WORD, BYTE and SBYTE are no longer checked to be compatible with VO.
-
- RDD System
-
-
Added support for different block sizes in DBFFPT.
-
DBFFPT now allows to override the block size (when creating) from the users code. Please note that block sizes < 32 bytes prevent the FPT from opening in Visual FoxPro.
-
Added support for reading various Flexfile memo field types, including arrays.
-
Added support for writing to FPT files
-
When creating FPT files we now also write the FlexFile header. Please note that our FPT driver does not support "record recycling" for deleted blocks like FlexFile does. We also only support writing STRING values to FPT files and Byte[] values.
-
Added support for Visual FoxPro created CDX files that were created with the COLLATE option. The RDD dll now contains collation tables for all possible combinations of collation and CodePage.
-
Added support for USUALs with a NIL value and the comparison operators (>, >=, <, <=). These operators return FALSE, except the >= and <= operators which return TRUE when both sides of the comparison are NIL.
-
We exposed several Advantage related function and types. Also the function AdsConnect60() was defined. We have not created functions for all available functions in Ace32 and Ace64, but only the ones needed in the RDD.
-
If you are missing a function in the ACE class, please let us know. All functions should be available and accessible now in the Ace32 and Ace64 classes or in the ACEUNPUB32 or ACEUNPUB64 classes.
-
The ADS RDD was returning incorrect values for LOGIC fields.
-
Fixed some problems with skipping in CDX indexes and scopes and filters.
-
Executing DbGoTop() twice or DbGoBottom() twice for DBFCDX would confuse the RDD. This has been fixed.
-
Fixed a problem with Seeking() in an empty DBF file
-
FieldPut for STRING fields in the Advantage RDD now truncates the fields to the maximum length of the field before assigning the value
-
Fixed a problem with UNIQUE CDX Indexes.
-
You can now create VFP compatible DBF files with DBCreate(). To do so use the following field types (apart from the normal CDLMN):
-
- WBlob YCurrency BDouble TDateTime FFloat GGeneral IInteger PPicture QVarbinary VVarchar
- Special field flags can be indicated by adding a suffix to the type:
- "0" = Nullable "B" = Binary "+" = AutoIncrement
- So this creates a nullable date: "D0" and this creates an autoincremental integer "I+".
- Auto increment columns are initialized with a counter that starts with 1 and a step size of 1. You can change that by calling DbFieldInfo:
- DbFieldInfo(DBS_COUNTER, 1, 100) // sets the counter for field 1 to 100 DbFieldInfo(DBS_STEP, 1, 2) // sets the step size for field 1 to 2
-
-
Fixed a locking problem with FPT files opened in shared mode
-
Fixed several problems related to OrderKeyCount() and various settings of Scopes and SetDeleted() in the DBFCDX RDD.
-
- VO SDK Classes
-
-
Fixed a problem in the DateTimePicker class when assigning only a time value.
-
System classes and RDD classes have been cleaned up somewhat and now compile in AnyCPU mode. So this means that you can use the DbServer class in a 64 bit program ! The projects for these two libraries also no longer have the "Late Binding" compiler option enabled. There is still some late bound code in these libraries but this code now uses explicit late bound calls such as Send(), IVarGet() and IVarPut().
-
Because of the change in the handling of __DEBUG__ some SDK assemblies are not better optimized.
-
- Visual Studio integration
-
-
Added support for WITH .. END WITH blocks in the editor
-
When generating Native Resources (RC files) the BuildSystem now sets a #define __VERSION__. This will have the fileversion number of the XSharp.Build.DLL without the dots. (2.1.0.0 will be written as "2100")
-
The XSharp help item in the VS Help menu now opens the local Help (CHM) file
-
Fixed a problem in the WCF service template
-
Correction to the multi line indenting for code that uses attributes
-
Code generation for new Event handlers now includes a RETURN statement, even when VS does not add one to the statement list
-
The intellisense option "Show completionlist after every character" has been disabled since it was having a negative impact on performance and would also insert keywords with @@ characters in front of them.
-
Several changes to the code parsing for the Windows Forms editor. Comments and Regions should now be saved and regenerated as well as attributes on classes. Also code generation for images from project resources has been fixed as well as parsing of static fields and enumerators declared in the same assembly. Please note. If you are using values from types defined in the same assembly as the form then the assembly needs to be (re)compiled first before the form can be successfully opened in the Windows Forms Editor.
-
New methods generated from the Windows forms editors will now be generated with a closing RETURN statement.
-
We have made some improvements to the presentation of QuickInfo in the source code editor.
File wide PUBLIC declarations (for MEMVARs) were incorrectly parsed as GLOBALs. Therefore they were initialized with NIL and not with FALSE. They are now generated correctly as public Memvars. The creation of the memvars and the initialization is done in after the Init3 procedures in the assembly have run.
-
Instance variable initializers now can refer other fields and are allowed to use the SELF keyword. This is still not recommended. The order in which fields are initialized is the order in which they are found in the source code. So make sure the field initializers are defined in the right order in your code.
-
AUTO properties are now also initialized with an empty string when /vo2 is enabled.
-
The compiler was allowing you to define instance variables for Interfaces. They were ignored during code generation. Now an error message is produced when the compiler detects fields on interfaces.
-
When the compiler detects 2 ambiguous symbols with different types (for example a LOCAL and a CLASS with the same name) then the error message now clearly indicates the type for each of these symbols.
-
Fixed an exception in the Preprocessor
-
-
-
Added support for the FoxPro runtime DLL.
-
-
-
The ANY keyword (an alias for USUAL) is no longer supported.
-
Keywords that appear after a COLON (":") DOT (".") or ALIAS (->) operator are no longer parsed as keyword but as identifier. This should solve issues with parsing code that for example accesses the Date property of a DateTime class.
-
We have added support for the WITH .. ENDWITH statement block:
LOCAL oPerson as Person oPerson := Person{} WITH oPerson :FirstName := "John" :LastName := "Doe" :Speak() ENDWITH You can also use the DOT (.) as prefix for the names. The only expressions allowed inside WITH .. ENDWITH are assignments and method calls (like you can see above)
-
Added support for the FoxPro LPARAMETERS statement. Please not that a function or procedure can only have a PARAMETERS keyword OR a LPARAMETERS keyword OR declared parameters (names between parentheses on the FUNCTION/PROCEDURE line)
-
Added support for the FoxPro THIS keyword and .NULL. keyword
-
We have added support for the FoxPro Date Literal format {^2019-06-21} and FoxPro DateTime Literals {^2019-06-21 23:59:59}.
-
Date literals and DateTime literals are now also supported in the Core dialect. Date Literals will be represented as DateTime values in the Core dialect.
-
The standard header file xsharpdefs.xh now conditionally includes header files for the Xbase++ dialect and FoxPro dialect. These header files do not have much content at this moment, but that will change in the coming months.
-
When the compiler detects that some header files are included but that the defines in these header files are also available as constants in references assemblies then a warning will be generated and the include file will be skipped (XS9081)
-
The compiler now supports an implicit function _ARGS(). This will be resolved to the arguments array that is passed to functions/methods with clipper calling convention. This can be used to pass all the arguments of a function/method to another function/method.
-
We have added the TEXT ... ENDTEXT command for the FoxPro dialect. The string inbetween the TEXT and ENDTEXT lines is passed to a special runtime function __TextSupport that will receive 5 parameters: the string, the merge, NoShow, Flags and Pretext arguments. You will have to define this function yourself for now. it will be included in the XSharp Foxpro runtime in a future version.
-
We have added support for END keywords for all entity types that did not have one yet. The new end keywords are optional. They are listed in the table below. The FoxPro ENDPROC and ENDFUNC keywords will be mapped to END PROCEDURE and END FUNCTION with a UDC.
-
-
-
-
- Start
-
-
- End
-
-
-
-
- PROCEDURE
-
-
- END PROCEDURE
-
-
-
-
- PROC
-
-
- END PROC
-
-
-
-
- FUNCTION
-
-
- END FUNCTION
-
-
-
-
- FUNC
-
-
- END FUNC
-
-
-
-
- METHOD
-
-
- END METHOD
-
-
-
-
- ASSIGN
-
-
- END ASSIGN
-
-
-
-
- ACCESS
-
-
- END ACCESS
-
-
-
-
- VOSTRUCT
-
-
- END VOSTRUCT
-
-
-
-
- UNION
-
-
- END UNION
-
-
-
-
-
The compiler now registers the Dialect of the main in the Dialect property of the RuntimeState (Non Core dialects only)
-
- MacroCompiler
-
-
Fixed a problem with escaped literal strings
-
-
-
Fixed a problem with implicit narrowing conversions
-
Fixed a problem with macro compiled alias operations (Customer)->&fieldName
-
- Runtime
-
-
Fixed a problem in the Round() function.
-
Fixed a problem in the ExecName() function.
-
Added FoxPro runtime DLL.
-
Added XML support functions in the Xbase++ dialect runtime
-
Added support for dynamic class creation in the Xbase++ dialect runtime.
-
Fixed a problem in the Push-Pop workarea code for aliased expressions.
-
converting a NULL to a symbol would cause an exception. This has been fixed.
-
- RDD system
-
-
Fixed several problems in the ADS RDD
-
The DBFCDX RDD is now included
-
The DBFVFP RDD is now included. This RDD can be used to access files with DBF/FPT/CDX extension and support the Visual Foxpro field types, such as Integer, Double, DateTime and VarChar. Reading files should be fully supported. Writing should also work with the exception of the Picture and General formats and with the exception of the AutoIncremental Integer fields. You can also use the RDD to open the various "definition" files from VFP such as projects, forms and reports. The RDD 'knows' about the different extensions for indexes and memos. You can also open DBC files as normal tables. In a future version we will support the VFP database functionality.
-
- Visual Studio Integration
-
-
You can now specify that multi line statements should indent on the 2nd and subsequent lines.
-
Type lookup for functions inside a BEGIN NAMESPACE .. END NAMESPACE did not include the types in this namespace.
-
Started intellisense for INLINE methods in the Xbase++ dialect
-
Fixed several problems in intellisense
-
Improved intellisense for VAR keywords declared in a FOREACH loop
-
Several other (smaller) improvements.
-
- Tools
-
-
VOXporter now writes DEFINES in the RC files and no longer literal values.
-
VOXporter: fix for module names with invalid chars for filenames
Added support for the so called IF Pattern Expression syntax, which consists of an IS test and an assignment to a variable, prefixed with the VAR keyword: IF x is Foo VAR oFoo ? oFoo:DoSomething() ENDIF
The variable oFoo introduced in the expression will only be visible inside the IF statement. Of course you can also use the pattern on other places, such as ELSEIF blocks, CASE statements, WHILE expressions etc:
IF x is Foo VAR oFoo ? oFoo:DoSomething() ELSEIF x is Bar VAR oBar ? oBar:DoSomethingElse() ENDIF
-
Fixed a problem with method modifiers and generic methods
-
Fixed a problem with partial classes with different casing and destructors
-
Fixed a problem with Interfaces and methods with CLIPPER calling convention
-
The compiler now generates an error (9077) when an ACCESS or ASSIGN method has Type Parameters and/or Constraint clauses
-
Fixed a problem with DEFINEs with specific binary numeric values. Also overflow checking is now always of when calculating the result of numeric operations for the values of a DEFINE.
-
When a constant value was added or subtracted to a numeric value < 32 bits then the result was seen as 32 bits by the compiler. This sometimes forced you to use casts in your code. With this change that cast is no longer necessary.
-
The compiler allowed you to concatenate non string values and strings and was automatically calling ToString() on the non strings. This is no longer possible. The compiler now generates an error (9078)when it detects this.
-
We have added error trapping code to the compiler that should route internal errors to compiler error XS9999. If you see such an error, please let us know.
-
DIM arrays of literal strings are now initialized properly.
-
There was a problem when switching between dialects when using the shared compiler. It would sometimes no longer detect dialect specific keywords. This has been fixed.
-
Fixed a problem where incorrect code was producing an error "Failure to emit assembly"
-
Fixed a problem in code that uses _CAST to cast a 32 bits value to 16 bits
-
Fixed a problem with overloaded indexed properties where the index parameter in a subclass has a different type than the index parameter in the super class.
-
Changed implementation of several aliased operations (ALIAS->FIELD and (ALIAS)->(Expression))
-
Changed preprocessor handling of extended strings ( (<token>) )
-
The Roslyn code was not marking some variables as 'assigned but not read' to be compatible with the old C# compiler. We are now flagging these assignments with a warning. This may produce a lot of warnings in your code that were not detected before. To support this we have received some requests to "open up" the support for 1 based indexes in the compiler. In the past the compiler would only allow 1 based indexing for variables of type System.Array or of the XBase ARRAY Type. We have now added a couple of interfaces to the runtime. If your type implements one of these interfaces then the compiler will recognize this and allow you to use 1 based indexes in your code and then the compiler will automatically subtract 1 from the numeric index parameter. The XSharp ARRAY type and ARRAY OF type now also implement (one of) these interfaces/ The interfaces are: INTERFACE IIndexer PUBLICPROPERTYSELF[index PARAMSINT[]] ASUSUALGETSET ENDINTERFACE
Fixed several problems with DB..() functions in the runtime
-
Fixed several problems with the macro compiler
-
Fixed a problem with the handling of default parameters in late bound calls to methods
-
Improved error messages for missing methods and/or properties in late bound code.
-
The Select() function was changing the current workarea. This has been fixed.
-
Converting a USUAL to a STRING was not throwing the same exceptions as VO. It was always calling ToString() on the USUAL. Now the behavior is the same as in VO.
-
F_ERROR has been defined as a PTR now and no longer as numeric
-
CreateInstance can now also find classes defined in namespaces
-
Fix problems with missing parameters in late bound code. Also added (limited) support for calling overloaded methods and constructors in late bound code.
-
Fixed problems with TransForm(), and several of the Str() functions.
-
XSharp.Core is now fully compiled as Safe code.
-
Fixed a problem with late bound assigns and access
-
NIL<-> STRING comparisons are now compatible with Visual Objects
-
Fixed problem with AEval() and missing parameters
-
Added Set() function. Please be careful when using header files for _SET defines. There are subtle differences between the definitions in Harbour, Xbase++ and VO/Vulcan. We recommend NOT to use the defines from the header file but to use the defines that are defined inside the X# runtime DLLs
-
Changed implementation of the functions used by the compiler for Aliased operations
-
- RDD system
-
-
Added support for DBF character fields up to 64K.
-
Implemented the DBFCDX RDD
-
Fixed several problems related to the DBFNTX RDD
-
The DBF RDD was using the incorrect locking scheme for Ansi DBF files. It now uses the same scheme as VO and Vulcan.
-
Macro compiled index expressions are not of the type _CodeBlock and not of the type RuntimeCodeBlock (the RuntimeCodeblock is encapsulated inside the _CodeBlock object). That prevents problems when storing these expressions inside a USUAL
-
- Visual Studio integration
-
-
Fixed an exception that could occur when typing a VAR expression
-
When the project system makes a backup of a project file, we are now making sure that Readonly flags are cleared before writing to or deleting existing files.
-
Reading intellisense data from C++ projects could send the intellisense engine into an infinite loop. This has been fixed.
-
The changes to the Form.Designer.prg are now written to disk immediately, to make sure that changes to the form are recompiled if you press 'Run' or 'Debug' from the window of the form editor
-
Improved support for intellisense for the VAR keyword.
-
Added support for FoxPro on the Project Properties page to prepare for the Compiler and Runtime changes for FoxPro.
-
.CH files are now also recognized as "X#" files in Visual Studio.
-
You can now control the characters that select an entry from a Completion List. For example the DOT and COLON now also select the current selected element. The complete list can be found on the Tools-Options-TextEditor-XSharp-Intellisense page.
-
Assemblies added to a project would not be properly resolved until the next time the project was loaded. This has been fixed.
-
Fixed a problem in the codedom parser which feeds the windows form editor. You can now inherit a form from another form in the same assembly. You will have to compile the project first (of course).
-
The .CH extension is now also registered as relevant for the X# project system.
-
Changed auto indentation for #ifdef commands
-
Fixed an exception that could occur during loading of project files with COM references.
-
Added templates for class libraries in XPP and VO Dialect
-
Sometimes a type lookup for intellisense was triggered inside a comments region. This has been fixed.
-
- Tools
-
-
VOXPorter was not removing calling conventions when creating delegates. This has been fixed
-
VOXporter was sometimes generating project files with many duplicates of resource items. This has been fixed.
-
VOXporter now marks prefix identifiers that conflict with one of the new keywords with "@@"
-
The delay for the VOXporter welcome screen has been shortened.
The Lexer (the part of the compiler that recognizes keywords, literals etc) has been rewritten and is slightly faster.
-
The compiler now supports digit separators for numeric literals. So you can now write 1 million as: 1_000_000
-
-
-
Fixed problem where static local variables were not initialized with "" even when compiler option -vo2 was selected
-
#ifdef commands using preprocessor macros such as __XSHARP_RT__ were not working correctly.
-
The Xbase++ dialect now also supports the 'normal' class syntax.
-
We had changed the 'Entrypoint' algorithm in Beta 8. This has been restored now and the -main command line option now works again as well. In stead the "body" of the Start method is now encapsulated in an anonymous function.
-
-
-
Duplicate include files no longer produce an error but a warning
-
Fix for problem with default parameter values with 'L' or 'U' suffix
-
Added compiler error when specifying default parameter values for methods/functions with clipper calling convention
-
DIM arrays of STRING were not initialized with "" when /vo2 was specified. This has been fixed.
-
Added support for Dbase style memory variables (MEMVAR, PUBLIC, PRIVATE, PARAMETERS). See the MEMVAR topic in the help file for more information. This is only available for certain dialects and also requires the /memvar commandline option
-
Added support for undeclared variables (this is NOT recommended!). This is only available for certain dialects and requires the /memvar AND the /undeclared commandline options
-
Fixed a problem for comparisons between USUAL variables and STRING variables
-
Fixed a problem with partial classes where the classname had different casing in the various declarations
-
Fixed a problem with numeric default parameters with L or U suffixes
-
Fixed a problem with line continuation semi colons followed by a single line comment with the multiline comments style.
-
Fixed a problem with methods containing YIELD statements in combination with compiler option /vo9
-
When a visibility modifier was missing on a generic method then this method was created as a private method. This has been fixed.
-
When choosing between overloaded functions in XSharp.RT and XSharp.Core the function in the XSharp.RT assembly would sometimes be chosen although the overload in XSharp.Core was better
-
CASE statements without CASE block but only a OTHERWISE block would crash the compiler. This has been fixed and an warning about an empty CASE statement has been added.
-
- Runtime
-
-
Several changes to the Macro compiler, such as the parsing of Hex literals, case sensitivity of parameters (they are no longer case sensitive) and limited support for function overloading.
-
Several missing functions have been added, such as _Quit(),
-
The return value of several Ord..() functions was incorrect. This has been fixed.
-
Fixed a problem with CurDir() for the root directory of a drive
-
Fixed a problem with calling Send() with a single parameter with the value NULL_OBJECT.
-
Solved problem with incorrect parameters for DiskFree() and DiskSpace()
-
MemoRead() and MemoWrit() and FRead..() and FWrite..() now respect the SetAnsi() setting like the functions in the VO Runtime.
-
We have added 2 new functions to read/write binary files: MemoReadBinary() and MemoWritBinary()
-
Not all DBOI_ enum values had the same value as in Vulcan. This has been solved.
-
SetDecimalSep() and SetThousandSep() now also set the numeric separators in the current culture.
-
The USUAL -> STRING conversion now calls AsString()
-
-
-
Added support for Dbase style dynamic memory variables (MEMVAR, PUBLIC, PRIVATE, PARAMETERS). See the Memory Variables topic in the help file for more information.
-
The IsDate() function now also returns TRUE for USUALs of type DateTIme. There is also a separate IsDateTime() function. We have also added IsFractional() (FLOAT or DECIMAL) and IsInteger (LONG or INT64) and IsInt64()
-
Added missing Cargo slot to the Error class. Also improved Error:ToString()
-
Fix for problem in W2String()
-
And many more small changes.
-
- Visual Studio Integration
-
-
We have added a new tab page in the Project Properties dialog: Dialect. This contains dialect specific language options.
-
2 options from the Build options page (which is configuration dependent) have been moved to the Language page (which is build INdepedent), because that makes more sense:
-
-
Include Path
-
NoStdDef
-
-
-
-
We have also added a project property on the Language page to specify an alternative standard header file (in stead of XSharpDefs.xh)
-
The XSharp.__Array type was shown in the intellisense with the wrong name
-
We have added entries on the Project Properties dialog pages to enable MEMVAR support and to enable Undeclared variables
-
Fixed a problem in the CodeDom provider (used by the Windows Form editor) where fields with array types were losing their array brackets when writing back to the source.
-
When writing changes from the windows form editor we are no longer writing to disk but to the opened (sometimes invisible) windows of the .designer.prg. This should prevent warning messages about the .designer.prg file that was changed outside Visual Studio
-
Fixed a problem parsing source code where identifier names were starting with '@@'
-
The Debugger was showing UINT64 as typename for ARRAYs. This has been fixed.
-
Renaming forms in the Windows Forms editor was not working for forms with a separate .designer.prg. This has been fixed.
-
Fixed a (very old) problem where the OutPutPath property in the xsproj file was sometimes set to $(OutputPath).
-
Fixed an exception in the editor for empty source files or header files.
-
Fixed an exception when the error list was created for errors without errorcode
-
Commenting a single line in the editor will now always use the // comment format
The compiler source code has been upgraded to Roslyn 2.10 (C# 7.3). As a result of that there are some new compiler options, such as /refout and we also support the combination of the "PRIVATE PROTECTED" modifier that defines a type member as accessible for subclasses in the same assembly but not for subclasses in other assemblies
-
We have added support for Xbase++ class declarations. See the Xbase++ class declaration topic for more information about the syntax and what is supported and what not.
-
We have added support for simple macros with the &Identifier syntax
-
We have added support for late bound property access:
-
-
The <Expression>:&<Identifier> syntax. This translates to IVarGet(<Expression>, <Identifier>).
-
The <Expression>:&(<Expression2>) syntax. This translates to IVarGet(<Expression>, <Expression2>).
-
Both of these can also be used for assignments and will be translated to IVarPut: <Expression>:&<Identifier> := <Value> This becomes IVarPut(<Expression>, <Identifier>, <Value>)
-
All of these will work even when Late Binding is not enabled.
-
-
-
-
We have added a new compiler options /stddefs that allows you to change the standard header file (which defaults to XSharpDefs.xh)
-
We have added a new preprocessor Match marker <#idMarker> which matches a single token (all characters until the first whitespace character)
-
When you select a dialect now, then the compiler will automatically add some compiler macros. The VO dialect declares the macro __VO__, the Vulcan dialect declares the macro __VULCAN__ the harbour dialect declares the macro __HARBOUR__ and the Xbase++ dialect declares the macro __XPP__.
-
When compiling against the X# runtime then also the macro __XSHARP_RT__ will be defined.
-
We have added a new warning when you pass a parameter without 'ref' modifier (or @ prefix) to a method or function that expects a parameter by reference or an out parameter.
-
We have also added a warning that will be shown when you assign a value from a larger integral type into a smaller integral type to warn you about possible overflow problems.
-
- Runtime
-
-
This build includes a new faster macro compiler. It should be fully compatible with the VO macro compiler. Some of the .Net features are not available yet in the macro compiler.
-
We moved most of the generic XBase code to XSharp.RT.DLL. XSharp.VO.DLL now only has VO specific code. We have also added XSharp.XPP.DLL for XPP
-
Fix Ansi2OEM problem with FRead3(), FWrite3() and FReadStr
-
Added missing functions EnableLBOptimizations() and property Array:Count
-
Fixed problem with latebound assign with CodeBlock values
-
Fixed problem with AScan() and AEval() with missing parameters
-
Changed error return codes for DirChange(), DirMake() and DirRemove()
-
Send() was "swallowing" errors. This has been fixed
-
Fixed a problem with assigning to multi dimensional arrays
-
Fixed a problem with creating objects with CreateInstance() where objects are not in the "global" namespace
-
Fixed several problems in the RDD system and support functions.
-
Fixed several problems in the late binding support, such as IsMethod, IsAccess, IVarPut, IVarPutSelf etc.
-
Fixed several problems with TransForm()
-
Integer divisions for usuals containing integers now return either integers or else fractional numbers depending on the compiler setting of the main app.
-
We fixed several conversions problems during late bound calls
-
We have fixed several problems with the Val() and Str() functions.
-
The internal type names for DATE and FLOAT have been changed to __Date and __Float. If you rely on these type names please check your code !
-
DebOut32 was not outputting data to the debug terminal if the runtime was compiled in release mode. This has been fixed.
-
- Visual Studio Integration
-
-
Fixed filtering on 'current project' in the error list
-
Type lookup for local variables was sometimes failing. This has been fixed
-
Fixed a problem with Brace Matching that could cause an exception in VS
-
Fixed a problem with Tooltips that could cause an exception in VS
-
Fixed a problem with uncommenting that could cause an exception in VS
-
New references added in VS would not always be included in the type search in the editor. This has been fixed.
-
Member prototypes for constructors now include the type name and curly braces
-
We have started work on improved code completion for variables declared with VAR
-
We have started with support for code completion for members of Generic types. This is not finished yet.
-
PRG files that are not part of a X# project and not part of a Vulcan project are now also colorized in the editor.
-
- Tools
-
-
VulcanXPorter was always adjusting the referenced VO libraries and was ignoring the "Use X# Runtime" checkbox
-
VOXPorter now has an option to copy the resources referenced in the AEF files to the Resources subfolder in the project
-
VOXPorter now also copies the cavowed, cavofed and cavoded template files to the properties folders in your project.
When calling a runtime function with a USUAL parameter the compiler now automatically prefers methods or functions with "traditional' VO types over the ones with enhanced .Net types. For example when there are 2 overloads, one that takes a byte[] and another that takes a string, then the overload that takes a string will get preference over the overload that takes a byte[].
-
Resolved a problem with .NOT. expressions inside IIF() expressions
-
Improved debugger break point generation for Invoke expressions ( like String.Compare())
-
Fixed a pre-processor error for parameters for macros defined in a #define. These parameters must have the right case now. Parameters with a different case will not be resolved any longer.
-
Fixed a pre-processor error where optional match patterns in pre-processor rules were repeated. This is too complicated to explain here in detail <g>.
-
The code generated by the compiler for Array operations now uses the new interfaces declared in the X# runtime (see below).
-
- Runtime
-
-
We have added several missing functions, such as _GetCmdLine, Oem2AnsiA() and XSharpLoadLibrary
-
Fixed problems in CreateInstance, IVarGet, IVarPut(), CtoDAnsi() and more.
-
Added VO Compatible overload for FRead4()
-
No longer (cathed) exceptions are produced for empty dates
-
Ferror() was not always return the error of a file operation. This has been fixed
-
We have added a new FException() function that returns the last exception that occurred for a low level file operation
-
Casting a usual containing a PTR to a LONG or DWORD is now supported
-
Some new interfaces have been added related to array handling. The compiler no longer inserts a cast to Array inside the code, but inserts a cast to one of these interfaces depending on the type of the index parameter. The USUAL type implements IIndexer and IIndexProperties and dispatches the call to the objects inside the usual when this objects exposes the interface. This is used for indexed access of properties when using AEval or AScan on an ARRAY OF <type>
-
-
XSharp.IIndexer
-
XSharp.INamedIndexer
-
XSharp.IIndexedProperties
-
-
- SDK Classes
-
-
We have added the Hybrid UI classes from Paul Piko (with permission from Paul)
-
- Tools
-
-
The Vulcan XPorter now also has an option to replace the runtime and SDK references with references to the X# runtime
The compiler was sometimes still generating warnings for unused variables generated by the compiler. This has been fixed.
-
The compiler will now produce a warning that #pragmas are not supported yet (9006)
-
Added compiler macro __FUNCTION__ that returns the current function/method name in original casing.
-
Literal sub arrays for multidimensional arrays no longer need a type prefix when compiling in the Core dialect
-
Fixed problem with the Global class name that would happen when building the runtime assemblies (these have a special convention for the global class names)
-
When the calling convention of a method in an interface is different from the calling convention of the implementation (CLIPPER vs Not CLIPPER) then a new error (9067) will be generated by the compiler.
-
The calling convention for _DLL functions and procedures is now optional and defaults to PASCAL (stdcall)
-
The namespace alias for using statements was not working in all cases.
-
The compiler will now generate an error for code that incorrectly uses the VIRTUAL and OVERRIDE modifiers.
-
The compiler was throwing an exception for a specific kind of incorrect local variable initializer with generic arguments. This has been fixed.
-
Visibility modifiers on GET or SET accessors for properties were not working correctly (INTERNAL, PRIVATE etc). This has been fixed.
-
The compiler now handles PSZ(_CAST,...) and PSZ(..) differently. When the argument is a literal string, then the PSZ will only be allocated once and stored in a "PSZ Table" in your assembly. The lifetime of this PSZ is then the lifetime of your app. When this happens then the new compiler warning XS9068 will be shown. When the argument is a string stored in a local or global (or define) then the compiler can't know the lifetime of the PSZ. It will therefore allocate the memory for the PSZ with the StringAlloc() function. This ensures that the PSZ will not go out of scope and be freed. If you use this a lot in your application then you may be repeatedly allocating memory. We recommend that you avoid the use of the cast and conversion operators for PSZs and take control of the lifetime of the PSZ variables by allocating and freeing the PSZ manually. PSZ casts on non strings (numerics or pointers) simply call the PSZ constructor that takes an intptr (this is used on several spots in the Win32API library for 'special' PSZ values).
-
Named arguments are now also supported in the Vulcan dialect. This may lead to compiler errors if your code looks like the code below, because the compiler will think that aValue is a named argument of the Empty() function.
IF Empty(aValue := SomeExpression())
-
If you were inheriting a static class from another class then you would get a compiler warning before. This is now a compiler error, because this had a side effect where the resulting assembly contained a corrupted reference.
-
The overload resolution code now chooses a type method/function over a method/function with clipper calling convention.
-
The Xbase++ dialect is now recognized by the compiler. For the time being it behaves the same as Harbour. We have also added the compiler macro __DIALECT_XBASEPP__ that will be automatically define to TRUE when compiling in Xbase++ mode.
-
Fixed a problem in the PDB line number generation that would cause incorrect line numbers in the debugger
-
- Visual Studio integration
-
-
The source code editor was not always showing the correct 'active' region for #defines defined in #include files.
-
Opening a source file without entities (e.g. a header file) could result in an error message inside VS.
-
Fixed a null reference exception in the editor
-
Fixed a problem when un-commenting code in the editor
-
Improved load time performance for large solutions with many dependencies.
-
Fixed a problem where the intellisense engine could lock a DLL that was used by a project reference or assembly reference.
-
Fixed a problem where missing references (for example COM references that were not installed on the developers machine) could cause problems with the type lookup when opening forms in the windows forms editor.
-
Added an option to select the Harbour dialect on the project properties page.
-
- The Build System
-
-
The Build system did not recognize that begin NAMESPACE lines in source code were commented out. This has been fixed.
-
- VOXporter
-
-
We have added an option to sort the entities in alphabetical order in the output file.
-
We have added an option so you can choose to add the X# Runtime as reference to your application (otherwise the Vulcan runtime is used)
-
- Runtime
-
-
The SetCentury setting was incorrect after calling SetInternational(#Windows). This has been fixed.
-
The Descend function for dates now returns a number just like in VO
-
The functions ChrA and AscA have been renamed to Chr() and Asc() and the original functions Chr() and Asc() have been removed. The original functions were using the DOS (Oem) codepage and this is not compatible with Visual Objects.
-
On several places in the runtime characters were converted from 8 bit to 16 bit using the System.Encoding.Default codepage. This has been changed. We use the codepage that matches the WinCodePage in the Runtimestate now. So by setting the Windows codepage in the runtime state you now also control the conversions from Unicode to Ansi and back
-
The Oem2Ansi conversion was incorrect for some low level file functions.
-
We have changed several things in the Late Binding support
-
All String - PSZ routines (String2PSz(), StringAlloc() etc) now use the Windows Codepage to convert the unicode strings to ansi.
-
If you library is compiled with 'Compatible String comparisons' but the main app isn't, then the string comparisons in the library will follow the same rules as the main app because the main app registers the /vo13 setting with the runtime. The "compatible" stringcomparison routines in the runtime now detect that the main app does not want to do VO compatible string comparisons and will simply call the normal .Net comparison routines. We therefore recommend that 3rd party products always use the Compatible String comparisons in their code.
-
-
-
Preliminary documentation for the runtime was generated from source code comments and has been included as chapter in this documentation.
-
- The VO SDK
-
-
This build includes the first version of the VO SDK compiled against the X# runtime. We have included the following class libraries
-
-
Win32API
-
System Classes
-
RDD Classes
-
SQL Classes
-
GUI Classes
-
Internet Classes
-
Console Classes
-
Report Classes
-
-
-
-
All assemblies are named VO<Name>.DLL and the classes in these assemblies are in the VO namespace.
-
This SDK is based on the VO 2.8 SP3 source code. The differences between VO 2.8 SP3 and VO 2.8 SP4 will be merged in the source later,
-
The Libraries for OLE, OleServer and Internet Server are not included. The OleAutoObject class and its support classes is included in the XSharp.VO library. OleControl and OleObject are not included.
-
Preliminary documentation for these classes was generated from source code comments and has been included as chapter in this documentation.
-
- The RDD system
-
-
This build includes the first version of the RDD system. DBF-DBT is ready now. Other RDDs will follow in the next builds. Also most of the RDD related functions are working in this build.
-
This build also includes the first version of the Advantage RDD. With this RDD you can access DBF/DBT/NTX files , DBF/FPT/CDX files and ADT/ADM/ADI files. The RDD names are the same as the RDD names for Vulcan. (AXDBFCDX, AXDBFNTX, ADSADT). We also support the AXDBFVFP format and the AXSQLCDX, AXSQLNTX, AXSQLVFP. For more information about the differences and possibilities of these RDD look in the Advantage documentation. We have coded the Advantage RDD on top of the Advantage Client Engine. Our RDD system detects if you are running in x86 or x64 mode and calls functions in Ace32 or Ace64 accordingly. To use Advantage you copy the support DLLs from an Advantage Vulcan RDD to the folder of your application. Look at the Advantage docs for Vulcan to see the list of the DLLs. The Advantage RDD is part of the standard XSharp.RDD.DLL which therefore replaces the AdvantageRDD.Dll for Vulcan.
-
The XSharp.Core DLL now also has RDD support. We have chosen NOT to implement this in functions, but as static methods inside the CoreDb class. Old code that uses the VoDb..() functions can be simply ported by changing "VoDb" to "CoreDb." The parameters and return values that are USUAL in VO and Vulcan are implemented as OBJECT in the CoreDb class. The ..Info() methods have 2 overloads. One that takes an Object and one that takes a reference to an object. The methods inside CoreDb return success or failure with a logical value like the VODB..() functions in VO. If you want to know what the error was during the last operation then you can access that with the method CoreDb._ErrInfoPtr() . This returns the last exception that occurred in a RDD operation.
-
At this moment the CoreDb class only has a FieldGet() that returns an object. We will add some extra methods that return values in a specified type in the next build (such as FieldGetString(), FieldGetBytes() etc). We will also add overloads for FieldPut() that take different parameter types.
-
The XSharp.VO DLL has the VoDb..() functions and the higher level functions such as DbAppend(), EOF(), DbSkip() etc. The VoDb..() functions return success or failure with a logical value. If you want to know what the error was during the last operation then you can access that with the method _VoDbErrInfoPtr() . This returns the last exception that occurred in a RDD operation.
-
You can mix calls to the VoDb..() functions and CoreDb...() methods. Under the hood the VoDb..() functions also call the CoreDb methods.
-
The higher level functions may throw an exception just like in VO. For example when you call them on a workarea where no table is opened. Some functions simply return an empty value (like Dbf(), Recno()). Others will throw an exception. When you have registered an error handler with ErrorBlock() then this error handler will be called with the error object. Otherwise the system will throw an exception.
-
Date values are returned by the RDD system in a DbDate structure, Float values are returned in a DbFloat structure. These structures have no implicit conversion methods. They do however implement IDate and IFloat and they can and will be converted to the Date and Float types when they are stored in a USUAL inside the XSharp.VO DLL. The DbDate structure is simply a combination of a year, month and date. The DbFloat structure holds the value of fields in a Real8, combined with length and the number of decimals.
-
More documentation about the RDD system will follow later. Of course you can also look at the help file and source code on GitHub.
The strong named key for assemblies with native resources was invalid. This has been fixed
-
When an include file was included twice for the same source (PRG) file then a large number of compiler warnings for duplicate #defines would be generated. Especially when the Vulcan VOWin32APILibrary.vh was included twice then over 15000 compiler warnings would be generated per source file where this happened. This large number of warnings could lead to excessive memory usage by the compiler. We are now outputting a compilation error when we detect that the same file was included twice. We have also added a limit of 500 preprocessor errors per source (PRG) file.
-
A change in Beta 4 could result in compiler warnings about unused variables that were introduced automatically by the X# compiler. This warning will no longer be generated.
-
The compiler now correctly stores some compiler options in the runtime state of XSharp.
-
- Runtime
-
-
Fixed a problem in the Ansi2OEM and OEM2Ansi functions.
-
Fixed a problem in the sorting for SetCollation(#Windows)
-
Fixed a problem with string comparisons in runtime functions like ASort(). This now also respects the new runtime property CompilerOptionVO13 to control the sorting
-
- Visual Studio integration
-
-
The sorting of the members in the editor dropdown for members was on methodname and propertyname and did not include the typename. When a source file contained more than one type then the members would be mixed in the members dropdown
-
- Build System
-
-
The default value for VO15 has been changed back from false to undefined.
POSSIBLY BREAKING CHANGE: Functions now always take precedence over same named methods. If you want to call a method inside the same class you need to either prefix it with the typename (for static methods) or with the SELF: prefix. If there is no conflicting function name then you can still call the method with just its name. We recommend to prefix the method calls to make your code easier to read.
-
The compiler was accepting just an identifier without a INSTANCE, EXPORT or other prefix and without a type inside a class declaration. It would create a public field of type USUAL. That is no longer possible.
-
Improved the positional keyword detection algorithm (this also affects the source code editor)
-
The || operator now maps to the logical or (a .OR. b) and not to the binary or (_OR(a,b))
-
The VAR statement now also correctly parses
VAR x = SomeFunction()
-
- And will compile this with a warning that you should use the assignment operator (:=).
- We have added this because many people (including we) copy examples from VB and C# where the operator is a single equals token.
-
-
Error messages about conflicting types now include the fully qualified type name.
-
The compiler no longer includes the width for literal Floats. This is compatible with VO.
-
A Default parameter of type Enum is now allowed.
-
- Runtime
-
-
Added several functions that were missing, such as __Str() and DoEvents()
-
Fixed a problem in the macro compiler with non-english culctures.
-
Added several overloads for Is..() functions that take a PSZ instead of a string, such as IsAlpha() and IsUpper().
-
Added some missing error defines, such as E_DEFAULT and E_RETRY.
-
Fix for a problem with SubStr() and a negative argument
-
Fix for a problem with IsInstanceOf()
-
Fix for a problem with Val() and a hex value with an embedded 'E' character
-
Added implicit conversions from ARRAY to OBJECT[] and back.
-
Several changes to the code for Transform() and Unformat() to cover several exotic picture formats
-
Changes to the code for SetCentury() to automatically also adjust the date format (SetDateFormat())
-
Fixes for the Str() family of functions in combination with SetFixed() and SetDigitFixed().
-
- Visual Studio integration
-
-
Fixed a problem when building projects in the latest build of Visual Studio
-
Several 'keywords' were not case synchronized before, such as TRUE, FALSE, NULL_STRING etc,
-
Keywords are not case synchronized on the current line as long as the user has the cursor on them or immediately after them. That means that when you type String and want to continue to change it to StringComparer then the formatter will no longer kick in and change "String" to the keyword case before you have the chance to complete the word.
-
The Control Order dialog inside the form editor was not saving its changes.
-
Added an option to include all entities from the editor, or just the members from the current selected type in the right dropdown of the editor
-
The editor was also matching braces inside literal strings and comments. This has been fixed.
-
Fixed a problem with the CodeDom parser where extended strings (strings containing CRLF tokens or other special tokens) were parsed incorrectly. This resulted in problems in the windows forms editor.
-
The member resolution code in the editor was not following the same logic as the compiler: When a function and a method with the same name exist it was resolving to the method in stead of the function. This has been fixed.
-
Fixed a problem when debugging in X64 mode.
-
Fixed an exception when comparing source code files with SCC integration.
-
Fixed several problems w.r.t. the XAML editor:
-
-
Code is now generated with STRICT calling convention to avoid problems when compiler option "Impliciting CLIPPER calling convention" is enabled
-
WPF and other templates now include STRICT calling convention for the same reason
-
The XAML editor could not properly load the current DLL or EXE and had therefore problems resolving namespaces and adding user controls to the tool palette. This has been fixed.
-
-
-
-
We have added an option to the Tools/Editor/XSharp/Intellisense options that allow you to control how the member combobox in the editor works. You can choose to only show methods & properties of the current type or all entities in the right combobox. The left combobox always shows all types in the file.
-
Some of the project and item templates have been updated. Methods and constructors without parameters now have a STRICT calling convention. Also the compiler option /vo15 has been explicitly disabled in templates for the Core dialect.
When 2 method overloads have matching prototypes the compiler now prefers the non generic one over the generic one
-
Fixed an exception that could occur when compiling a single line of source code with a preprocessor command in it.
-
- Runtime
-
-
Added Mod() function
-
Added ArrayNew() overload with no parameters
-
-
-
Fixed problem in __StringNotEquals() when length(RHS) > length(LHS) and SetExact() == FALSE
-
Added missing string resource for USUAL overflow errors
-
- Visual Studio integration
-
-
Improved keyword case synchronization and indenting. Also a source file is 'Keyword Case' synchronized when opened.
-
Opening a source file by double clicking the find results window no longer opens a new window for the same source file
-
Improved type lookup speed for intellisense
-
Fixed a problem that would prevent type lookup for types in the same namespace
-
Fix for QuickInfo problem introduced in the latest Visual Studio 2017 builds
-
QuickInfo tips are no longer shown in the debugger where they were overlapping with debugger tooltips
-
The comboboxes with methods and functions in the editor window no longer shows parameter names and full type names. Now it shows the shortened type names for the parameters
-
These same comboboxes now show the file name for methods and properties defined in another source file
-
Fixed problem in the window editor with generating code for tab pages
-
- Vulcan XPorter
-
-
Project dependencies defined in the solution file were not properly converted
-
- VO XPorter
-
-
Fixed a problem where resource names were replaced with the value of a define
The compiler now transparently accepts both Int and Dword parameters for XBase Array indices
-
When the compiler finds a weakly typed function in XSharp.VO and a strongly typed version in XSharp.Core then it will choose the strongly typed version in XSharp.Core now.
-
In the VO and Vulcan dialect sometimes an (incorrect) warning 'duplicate usings' was displayed. This is now suppressed.
-
The debugger information for the Start function has been improved to avoid unnecessary step back to line 1 at the end of the code
-
The debugger break point information for BEGIN LOCK and BEGIN SCOPE has been improved
-
The debugger break point information for multi line properties has been improved
-
/vo6, /vo7 and /vo11 are now only supported in the VO/Vulcan dialect
-
- Runtime
-
-
Removed DWORD overloads for Array indexers
-
Fixed overload problem for ErrString()
-
Fixed overload problem for _DebOut()
-
Fixed problems in DTOC() and Date:ToString()
-
Fixed ASort() incompatibilities with VO
-
Fixed memory blocks now get filled with 0xFF when they are released to help detect problems
-
- Visual Studio
-
-
Fix 'Hang' in VS2017 when building
-
Fix 'Hang' in VS2017 when a tooltip (QuickInfo) was displayed
-
Fixed problem with debugging x64 apps
-
You can no longer rename or delete the Properties folder
-
Selecting 'Open' from the context menu on the the Properties folder now opens the project properties screen
-
Updated several icons in the Project Tree
-
Enhancements in the Goto Definition
-
- Build System
-
-
Fix problem with CRLF in embedded resource commandline option
-
-
-
- Changes in 2.0.0.1 (Bandol Beta 1)
- Compiler
- New features
-
-
Added support for ARRAY OF language construct. See the Runtime chapter for more information about this.
-
Added support for the X# Runtime assemblies when compiling in the VO or Vulcan dialects.
-
Added support for the "Pseudo" function ARGCOUNT() that returns the # of declared parameters in a function/method compiled with clipper calling convention.
-
Added a new warning number for assigning values to a foreach local variable. Assigning to USING and FIXED locals will generate an error.
-
- Optimizations
-
-
Optimized the code generation for Clipper calling convention functions/methods
-
The /cf and /norun compiler options are no longer supported
-
The preprocessor no longer strips white space. This should result in better error messages when compiling code that uses the preprocessor.
-
Some parser errors are now more descriptive
-
Changed the method that is used to determine if we compile against CLR2 or CLR4. The compiler checks at the location either system.dll or mscorlib.dll. When this location is in a path that contains "v2", "2.", "v3" or "3." then we assume we are compiling for CLR2. A path that contains "V4" or "4." is considered CLR4. The /clr commandline option for the compiler is NOT supported.
-
The preprocessor now generates an error when it detects recursive #include files.
-
- Bug fixes
-
-
Fixed a problem when using the [CallerMemberAttribute] on parameters when compiling in Vulcan or VO Dialect
-
Abstract properties should no longer generate a warning about a body
-
You can now correctly use ENUM values as array indexes.
-
Fixed a problem for Properties with PUBLIC GET and PRIVATE SET accessors.
-
Fixed an issue where assigning an Interface to a USUAL required a cast to Object
-
Fixed an issue where IIF expressions with literal types were returning the wrong type (the L or U suffix was ignored)
-
Fixed an issue where the declaration LOCAL x[10] was not compiled correctly. This now compiles into a local VO Array with 10 elements.
-
- Visual Studio Integration
-
-
Build 1.2.1 introduced a problem that could cause output files to be locked by the intellisense engine. This has been fixed
-
The editor parser had problems with nested types. This has been fixed
-
Enum members were not included in code completion for enums inside X# projects
-
Some improvements in the code reformatting
-
Added option on the Tools/Options for the editor to include keywords in the "All tokens" completion list
-
-
-
Fixed a problem where assemblies that could not be loaded to retrieve meta information would be retried 'for ever'
-
Fixed a problem with retrieving type information from assemblies that contained both managed and unmanaged code.
-
Added some properties for referenced assemblies to the IDE Properties window
-
Fixed a problem with assembly references and the Windows Forms editor, introduced in one of the latest Visual Studio 2017 updates
-
When enabling XML output on the Project Properties window an incorrect filename was shown for assemblies that contain a '.'in the assembly name.
-
The editor parser now has better support for parameters of type REF and OUT
-
Added support for 'Embed Interop Types' in the property windows for Assembly References and COM references
-
Fixed a problem where the codemodel was sometimes locking output DLLs for Project references
-
- Build System
-
-
Fixed a problem with the naming of the XML documentation file.
-
- Runtime
-
-
Added XSharp.Core.DLL, XSharp.VO.DLL and XSharp.Macrocompiler.DLL. Most runtime functions are implemented and supported. See the X# Runtime chapter for more information
-
- VO XPorter
-
-
SDK related options have been removed. They will be moved to a new tool later.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Visual-Studio-Integration.xml b/docs/Help_Spanish/Topics/Visual-Studio-Integration.xml
deleted file mode 100644
index e256047295..0000000000
--- a/docs/Help_Spanish/Topics/Visual-Studio-Integration.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- Using X# in Visual Studio
-
-
- Using X# in Visual Studio
-
- XSharp comes with two options for development environments:
-
-
Chris Pyrgas has adjusted his existing IDE to support XSharp (it is now called XIDE, and compiled in XSharp!).
-
We supply Visual Studio integration for Visual Studio 2017 and later. If you do not have Visual Studio, you can download a (free!) community edition from Visual Studio from the web:
-
- https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs.aspx
- The Visual Studio integration is still a work progress. What is supported in this version is:
-
-
Edit;
-
Compile;
-
Debug;
-
Source control;
-
Windows Forms Editor;
-
WPF Editor;
-
Resource editor;
-
Settings editor.
-
-
- Known issues:
-
-
Some of the intellisense features are not supported yet.
-
There are no editors for VO Binary entities yet.
-
No support yet for .Net Core, .Net Standard, Portable class libraries and shared projects.
-
-
-
diff --git a/docs/Help_Spanish/Topics/WORD.xml b/docs/Help_Spanish/Topics/WORD.xml
deleted file mode 100644
index 1696c6adde..0000000000
--- a/docs/Help_Spanish/Topics/WORD.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- WORD
-
- WORD
-
-
-
- WORD
-
- The WORD keyword denotes an integral type that stores unsigned 16-bit values with values ranging from 0 to 65535.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/Who-is-the-X-team.xml b/docs/Help_Spanish/Topics/Who-is-the-X-team.xml
deleted file mode 100644
index c0ab21f630..0000000000
--- a/docs/Help_Spanish/Topics/Who-is-the-X-team.xml
+++ /dev/null
@@ -1,89 +0,0 @@
-
-
-
- Who is who in the X# team
-
-
- Who is who in the X# team
-
- The founders of the X# project started the X# project in the summer of 2015.
- They have ample experience with the xBase language. They all worked on the Visual Objects and/or Vulcan.NET development teams, and some of them have created third-party additions to Visual Objects and/or Vulcan.NET or created tools for VO and Vulcan developers.
-
- They are in alphabetical order:
-
-
-
-
- Name
-
-
- Country
-
-
- Email
-
-
- Role in the X# development team
-
-
-
-
- Fabrice Foray
-
-
- France
-
-
- fabrice@xsharp.eu
-
-
- Visual Studio integration, examples, tutorials
-
-
-
-
- Nikos Kokkalis
-
-
- Greece
-
-
- nikos@xsharp.eu
-
-
- (Macro) Compiler
-
-
-
-
- Chris Pyrgas
-
-
- Greece
-
-
- chris@xsharp.eu
-
-
- Support, tools, examples, tutorials, runtime
-
-
-
-
- Robert van der Hulst
-
-
- The Netherlands
-
-
- robert@xsharp.eu
-
-
- Management, Compiler, Runtime, Visual Studio integration, Documentation
-
-
-
-
- If you are interested in participating in the development of X#, please contact us and let us know what your area of expertise is. There are plenty of things to do!
-
-
diff --git a/docs/Help_Spanish/Topics/Workarea-Events.xml b/docs/Help_Spanish/Topics/Workarea-Events.xml
deleted file mode 100644
index ab0734780a..0000000000
--- a/docs/Help_Spanish/Topics/Workarea-Events.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- Workarea Events
-
-
- Workarea Events
-
- In build 2.08, we have added the option to register an event handler that receives workarea events. This can be used to monitor access to workareas and for example write this information to a log file.
-
- There are two ways to install this event handler:
-
-
You create a function/ method that implements the DbNotifyEventHandler delegate:
PUBLICDELEGATE XSharp.DbNotifyEventHandler(osender AS XSharp.RDD.IRDD, e AS XSharp.DBNotifyEventArgs) ASVOID
-
You create a class that implements the IDbnotify interface, which only has a method named Notify() with the same prototype as the delegate from 1)
-
- Important
-
-
Your event handler should do as little as possible if you don't want to slow down the whole RDD system.
-
Do not manipulate any workareas from within your event handler to avoid recursion.
-
Unregister your event handler as soon as possible.
-
If you use an object for event handling, you are responsible yourself to manage the life time of this object. Also, be sure to unregister the object before it runs out of scope.
-
In some cases (operations that work on more than one workarea, such as DbCommitAll() , DbUnLockAll() ), the event handler will not always receive a sender parameter. Be prepared for that!
-
The events are sent from the CoreDb level. So if a method inside an RDD calls another method inside that RDD (for example, CreateOrder() might call GoTop() after creating the order), you will not see that second event, only the events related to the method that was called from the CoreDb() level, so the events related to the Ordercreation in this example.
-
- Examples
-
- If you use approach 1, you need to add the event handler to CoreDb.Notify, like in the following example:
-
- FUNCTION NotifyRDDOperations(oRDD AS XSharp.RDD.IRdd, oEvent AS XSharp.DbNotifyEventArgs) ASVOID IF oRDD != NULL ? oRDD:Alias, oEvent:Type:ToString(), oEvent:Data ELSE ? "(no area)",oEvent:Type:ToString(), oEvent:Data ENDIF RETURN
FUNCTION Start() ASVOID CoreDb.Notify += NotifyRDDOperations ? DbCreate("Test", {{"FLD1" , "C" , 10 , 0} }) // This will trigger a notification CoreDb.Notify -= NotifyRDDOperations// Do not forget to unregister! WAIT RETURN
- The parameters to the function are:
- oRDDThe RDD for which the event is triggered. This may be NULL for events that involve multiple workareas, such as DbUnlockAll()
- oEventAn event handler object that has 2 properties
- TypeA Value of the DbNotificationType enum
- DataAn object that has additional information about the event, such as the fieldname for a PieldPut and the recordnumber for a Append or Delete event..
-
- For the second approach you create a class. You can register the class with the DbRegisterClient() function and unregister the class with the DbUnRegisterClient function
- The method in the class will get the same arguments as the event handler function:
- CLASS Notifier IMPLEMENTS IDbnotify METHOD Notify(oRDD AS XSharp.RDD.IRdd, oEvent AS XSharp.DbNotifyEventArgs) ASVOID IF oRDD != NULL ? oRDD:Alias, oEvent:Type:ToString(), oEvent:Data ELSE ? "(no area)",oEvent:Type:ToString(), oEvent:Data ENDIF RETURN ENDCLASS
FUNCTION Start() ASVOID LOCAL oNot AS Notifier oNot := Notifier{} DbRegisterClient(oNot) ? DbCreate("Test", {{"FLD1" , "C" , 10 , 0} }) // This will trigger a notification DbUnRegisterClient(oNot) // Do not forget to unregister! WAIT RETURN
- See Also
- DbNotificationType
- DbRegisterClient()
- DbUnRegisterClient
- DbNotifyEventHandler
- IDbnotify
-
-
-
diff --git a/docs/Help_Spanish/Topics/Workarea_Operators.xml b/docs/Help_Spanish/Topics/Workarea_Operators.xml
deleted file mode 100644
index be42fdbb49..0000000000
--- a/docs/Help_Spanish/Topics/Workarea_Operators.xml
+++ /dev/null
@@ -1,70 +0,0 @@
-
-
-
- Workarea
-
- _FIELD
- ->
- ALIAS
- alias operator
- dynamic memory variable
- FIELD
- operator
- workarea
-
-
-
- Workarea
-
- X# uses the following Workarea operators:
-
-
- Field "LastName" in the "Customer" workarea.
- Field "FirstName" in the current workarea. Field "Salary" in the current workarea. The dynamic memory variable "Name" (public or private). The field City in workarea 1. Allowed single letter aliases are A .. J.
Note that FIELD and _FIELD are synonyms. Keywords that appear directly after the -> operator are seen as identifier and not keyword.
-
-
-
-
- . (Dot)
-
-
- Customer.LastName
-
-
- In the VFP dialect we also support the DOT (".") syntax for aliased operations. Please note that this is ambiguous because the compiler cannot detect at compile time if CUSTOMER is a workarea or for example a MEMVAR. If there is a local variable with the name CUSTOMER then this will access the LASTNAME property of the CUSTOMER local variable.
- In all other cases, this will produce code that looks for either a CUSTOMER workarea or memory variable at runtime. Keywords that appear directly after the "." operator are seen as identifier and not keyword.
-
-
-
-
- . (Dot)
-
-
- M.Name
-
-
- In the VFP dialect, we also support the DOT (".") syntax for memvar access. This is also ambiguous because NAME can be both a local variable or a dynamic memory variable "NAME" (public or private). However, the compiler will be able to detect the local variable at compile time, and when this is not found, it will access the dynamic memory variable.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/X-Compiler-Errors-and-Warnings.xml b/docs/Help_Spanish/Topics/X-Compiler-Errors-and-Warnings.xml
deleted file mode 100644
index d6126d04d2..0000000000
--- a/docs/Help_Spanish/Topics/X-Compiler-Errors-and-Warnings.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- X# Compiler Errors and Warnings
-
-
- X# Compiler Errors and Warnings
-
- The complete list of X# Compiler errors and warnings is not included in this "book like" documentation but can be found in the CHM, Visual Studio Help and/or Webhelp.
- The compiler warnings with numbers < 9000 are "standard" Roslyn (C#) compiler errors.
- The compiler warnings with numbers > 9000 are specific X# compiler errors.
-
-
diff --git a/docs/Help_Spanish/Topics/X-Compiler-Errors.xml b/docs/Help_Spanish/Topics/X-Compiler-Errors.xml
deleted file mode 100644
index b82fb6c3b5..0000000000
--- a/docs/Help_Spanish/Topics/X-Compiler-Errors.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- X# Compiler Errors and Warnings
-
-
- X# Compiler Errors and Warnings
-
- On the following pages you will find descriptions of the most common compiler errors and warnings
- The compiler errors with numbers < 9000 are "standard" Roslyn (C#) compiler errors and warnings
- The compiler errors with numbers > 9000 are specific for X#.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/X-Compiler-Options-By-Category.xml b/docs/Help_Spanish/Topics/X-Compiler-Options-By-Category.xml
deleted file mode 100644
index fd7db5e623..0000000000
--- a/docs/Help_Spanish/Topics/X-Compiler-Options-By-Category.xml
+++ /dev/null
@@ -1,1003 +0,0 @@
-
-
-
- X# Compiler Options By Category
-
- compiler options
- options
- -usenativeversion
-
-
-
- X# Compiler Options By Category
-
- The following compiler options are sorted by category. For an alphabetical list, see: X# Compiler Options Listed Alphabetically
- Dialect support
-
-
-
- Option
-
-
- Purpose
-
-
-
-
- -dialect
-
-
- Specifies the dialect to use when compiling. The following values are supported: Core, VO, Vulcan, dBase, FoxPro, Xbase++ and Harbour. Work on the VO and Vulcan dialects has started.
-
-
-
- XBase Compatibility
-
-
-
- Option
-
-
- Purpose
-
-
-
-
- -allowdot
-
-
- Allow the DOT (.) character as operator for instance members
-
-
-
-
- -allowoldstyleassignments
-
-
- Allow assignments with a single Equals operator (=)
-
-
-
-
- -az
-
-
- Specifies that arrays are zero-based rather than one-based
-
-
-
-
- -cs
-
-
- Specifies that the compiler should use case-sensitive type names
-
-
-
-
- -d
-
-
- Instruct the compiler to emit debugging information. (short for /debug)
-
-
-
-
- -enforceoverride
-
-
- Enforce the use of the OVERRIDE keyword to override methods from parent classes in subclasses
-
-
-
-
- -enforceself
-
-
- Enforce the use of SELF: to access fields, properties and methods inside a class
-
-
-
-
- -fovf
-
-
- Specifies that exceptions will be raised on invalid floating point operations
-
-
-
-
- -fox1
-
-
- Classes are assumed to inherit from the Custom class
-
-
-
-
- -fox2
-
-
- Compatible FoxPro Array support
-
-
-
-
- -i
-
-
- Specifies a directory to add to the #include file search path
-
-
-
-
- -initlocals
-
-
- Initialize all local variables
-
-
-
-
- -ins
-
-
- Use implicit namespace lookup mechanism
-
-
-
-
- -lb
-
-
- Specifies that the compiler should generate late bound calls when necessary
-
-
-
-
- -memvar
-
-
- Enables support for memory variables
-
-
-
-
- -modernsyntax
-
-
- Disable certain legacy compiler options
-
-
-
-
- -namedargs
-
-
- Specifies whether to allow named arguments in the parser or not.
-
-
-
-
- -noinit
-
-
- Suppress generation of empty $Init1() and $Exit() functions
-
-
-
-
- -norun
-
-
- Obsolete compiler option in X#, inherited from Vulcan. To achieve this simply remove the references to the runtime DLLs and compile in the Core dialect
-
-
-
-
- -nostddefs
-
-
- Suppresses preprocessor definitions in XSharpDefs.xh
-
-
-
-
- -ns
-
-
- Specify the default namespace for the output assembly
-
-
-
-
- -ovf
-
-
- Specifies that exceptions will be raised on integer overflows
-
-
-
-
- -showincludes
-
-
- Lists #include files in compiler output
-
-
-
-
- -snk
-
-
- Signs assembly with strong name key pair
-
-
-
-
- -undeclared
-
-
- Enables support for undeclared variables
-
-
-
-
- -vo1
-
-
- Use Init and Axit methods in stead of Constructors and Destructors
-
-
-
-
- -vo2
-
-
- Initialize STRING variables, fields and DIM arrays to empty strings
-
- Automatically generate Clipper calling convention constructors for classes without constructor
-
-
-
-
- -w
-
-
- This option is not supported; use -NoWarn in stead
-
-
-
-
- -wx
-
-
- Treats all warnings as errors (alias for -warnaserror)
-
-
-
-
- -xpp1
-
-
- All classes inherit from the Abstract class
-
-
-
- Optimization
-
-
-
- Option
-
-
- Purpose
-
-
-
-
- -filealign
-
-
- Specifies the size of sections in the output file.
-
-
-
-
- -optimize
-
-
- Enables/disables optimizations.
-
-
-
- Output files
-
-
-
- Option
-
-
- Purpose
-
-
-
-
- -doc
-
-
- Specifies an XML file where processed documentation comments are to be written.
-
-
-
-
- -modulename
-
-
- Specify the name of the source module.
-
-
-
-
- -out
-
-
- Specifies the output file.
-
-
-
-
- -pathmap
-
-
- Specify a mapping for source path names output by the compiler.
-
-
-
-
- -pdb
-
-
- Specifies the file name and location of the .pdb file.
-
-
-
-
- -platform
-
-
- Specify the output platform.
-
-
-
-
- -preferreduilang
-
-
- Specify a language for compiler output.
-
-
-
-
- -target
-
-
- Specifies the format of the output file using one of five options: /target:appcontainerexe, /target:exe, /target:library, /target:module, /target:winexe, or /target:winmdobj.
-
-
-
-
- -touchedfiles
-
-
- Specify filename that will be updated with list of files read and written by the compiler
-
-
-
- .NET Assemblies
-
-
-
- Option
-
-
- Purpose
-
-
-
-
- -analyzer
-
-
- Run the analyzers from this assembly (Short form: /a)
-
-
-
-
- -additionalfile
-
-
- Names additional files that do not directly affect code generation but may be used by analyzers for producing errors or warnings.
-
-
-
-
- -addmodule
-
-
- Specifies one or more modules to be part of this assembly.
-
-
-
-
- -delaysign
-
-
- Instructs the compiler to add the public key but to leave the assembly unsigned.
-
-
-
-
- -keycontainer
-
-
- Specifies the name of the cryptographic key container.
-
-
-
-
- -keyfile
-
-
- Specifies the filename containing the cryptographic key.
-
-
-
-
- -lib
-
-
- Specifies the location of assemblies referenced by means of /reference.
-
-
-
-
- -nostdlib
-
-
- Instructs the compiler not to import the standard library (mscorlib.dll).
-
-
-
-
- -reference
-
-
- Imports metadata from a file that contains an assembly.
-
-
-
- Debugging / Error checking
-
-
-
- Option
-
-
- Purpose
-
-
-
-
- -ast
-
-
- Dump the abstract syntax tree for each source file (.ast extension)
-
-
-
-
- -checked
-
-
- Specifies whether integer arithmetic that overflows the bounds of the data type will cause an exception at run time.
-
-
-
-
- -debug
-
-
- Instruct the compiler to emit debugging information.
-
-
-
-
- -errorendlocation
-
-
- Output line and column of the end location of each error
-
-
-
-
- -errorreport
-
-
- Sets error reporting behavior.
-
-
-
-
- -fullpaths
-
-
- Specifies the absolute path to the file in compiler output.
-
-
-
-
- -lexonly
-
-
- Tells the compiler to only lex the source code.
-
-
-
-
- -nowarn
-
-
- Suppresses the compiler's generation of specified warnings.
-
-
-
-
- -parseonly
-
-
- This compiler option tells the compiler to lex and parse the code.
-
-
-
-
- -ruleset
-
-
- Specify a rule set file that disables specific diagnostics.
-
-
-
-
- -warn
-
-
- Sets the warning level.
-
-
-
-
- -warnaserror
-
-
- Promotes warnings to errors.
-
-
-
-
- -wx
-
-
- This is an alias for the -warnaserror option
-
-
-
- Preprocessor
-
-
-
- Option
-
-
- Purpose
-
-
-
-
- -define
-
-
- Defines preprocessor symbols.
-
-
-
-
- -i
-
-
- Specifies a directory to add to the #include file search path
-
-
-
-
- -ppo
-
-
- Writes preprocessor output to file
-
-
-
-
- -nostddef
-
-
- Suppresses preprocessor definitions in XSharpDefs.xh
-
-
-
-
- -showdefs
-
-
- Show the defines that are added from the header files and their usage
-
-
-
-
- -showincludes
-
-
- Lists #include files in compiler output
-
-
-
-
- -verbose
-
-
- Shows includes, source file names, defines and more. on the console
-
-
-
- Resources
-
-
-
- Option
-
-
- Purpose
-
-
-
-
- -link
-
-
- Makes COM type information in specified assemblies available to the project.
-
-
-
-
- -linkresource
-
-
- Creates a link to a managed resource.
-
-
-
-
- -resource
-
-
- Embeds a .NET Framework resource into the output file.
-
-
-
-
- -usenativeversion
-
-
- Prefer native resource (if any) over resources generated from managed assembly properties
-
-
-
-
- -win32icon
-
-
- Specifies an .ico file to insert into the output file.
-
-
-
-
- -win32res
-
-
- Specifies a Win32 resource to insert into the output file.
-
- Dump the abstract syntax tree for each source file (.ast extension)
-
-
-
-
- -az
-
-
- Specifies that arrays are zero-based rather than one-based
-
-
-
-
- -baseaddress
-
-
- Specifies the preferred base address at which to load a DLL.
-
-
-
-
- -checked
-
-
- Specifies whether integer arithmetic that overflows the bounds of the data type will cause an exception at run time.
-
-
-
-
- -checksumalgorithm
-
-
- Specify the algorithm for calculating the source file checksum stored in PDB. Supported values are: SHA1 (default) or SHA256.
-
-
-
-
- -codepage
-
-
- Specifies the code page to use for all source code files in the compilation.
-
-
-
-
- -cs
-
-
- Specifies that the compiler should use case-sensitive type names
-
-
-
-
- -debug -d
-
-
- Instruct the compiler to emit debugging information.
-
-
-
-
- -define
-
-
- Defines preprocessor symbols.
-
-
-
-
- -dialect
-
-
- Specifies the dialect to use when compiling. The following values are supported: Core, VO, Vulcan, dBase, FoxPro, Xbase++ and Harbour. Work on the VO and Vulcan dialects has started.
-
-
-
-
- -delaysign
-
-
- Instructs the compiler to add the public key but to leave the assembly unsigned.
-
-
-
-
- -doc
-
-
- Specifies an XML file where processed documentation comments are to be written.
-
-
-
-
- -enforceoverride
-
-
- Enforce the use of the OVERRIDE keyword to override methods from parent classes in subclasses
-
-
-
-
- -enforceself
-
-
- Enforce the use of SELF: to access fields, properties and methods inside a class
-
-
-
-
- -errorendlocation
-
-
- Output line and column of the end location of each error
-
-
-
-
- -errorreport
-
-
- Sets error reporting behavior.
-
-
-
-
- -filealign
-
-
- Specifies the size of sections in the output file.
-
-
-
-
- -fox1
-
-
- Assume classes inherit from Custom class. This also controls the code generation for properties.
-
-
-
-
- -fox2
-
-
- Compatible FoxPro Array support
-
-
-
-
- -fovf
-
-
- Specifies that exceptions will be raised on invalid floating point operations (duplicate of -ovf)
-
-
-
-
- -fullpaths
-
-
- Specifies the absolute path to the file in compiler output.
-
-
-
-
- -help
-
-
- Lists compiler options to stdout.
-
-
-
-
- -highentropyva
-
-
- Specifies that the executable file supports address space layout randomization (ASLR).
-
-
-
-
- -i
-
-
- Specifies a directory to add to the #include file search path
-
-
-
-
- -initlocals
-
-
- Initialize all local variables
-
-
-
-
- -ins
-
-
- Use implicit namespace lookup mechanism
-
-
-
-
- -keycontainer
-
-
- Specifies the name of the cryptographic key container.
-
-
-
-
- -keyfile
-
-
- Specifies the filename containing the cryptographic key.
-
-
-
-
- -lb
-
-
- Specifies that the compiler should generate late bound calls when necessary
-
-
-
-
- -langversion
-
-
- Specify language version mode: core, VO, Vulcan, Harbour, FoxPro, dBase
-
-
-
-
- -lexonly
-
-
- Tells the compiler to only lex the source code.
-
-
-
-
- -lib
-
-
- Specifies the location of assemblies referenced by means of /reference.
-
-
-
-
- -link
-
-
- Makes COM type information in specified assemblies available to the project.
-
-
-
-
- -linkresource
-
-
- Creates a link to a managed resource.
-
-
-
-
- -main
-
-
- Specifies the location of the Main method.
-
-
-
-
- -memvar
-
-
- Enable support for memory variables
-
-
-
-
- -modernsyntax
-
-
- Disable certain legacy compiler options
-
-
-
-
- -modulename
-
-
- Specify the name of the source module
-
-
-
-
- -namedargs
-
-
- Specifies whether to allow named arguments in the parser or not.
-
-
-
-
- -nostddefs
-
-
- Suppresses preprocessor definitions in XSharpDefs.xh
-
-
-
-
- -ns
-
-
- Specify the default namespace for the output assembly
-
-
-
-
- -noconfig
-
-
- Instructs the compiler not to compile with xsc.rsp.
-
-
-
-
- -noinit
-
-
- Suppress generation of empty $Init1() and $Exit() functions
-
-
-
-
- -nologo
-
-
- Suppresses compiler banner information.
-
-
-
-
- -norun
-
-
- Obsolete compiler option in X#, inherited from Vulcan. To achieve this simply remove the references to the runtime DLLs and compile in the Core dialect
-
-
-
-
- -nostdlib
-
-
- Instructs the compiler not to import the standard library (mscorlib.dll).
-
-
-
-
- -nowarn
-
-
- Suppresses the compiler's generation of specified warnings.
-
-
-
-
- -optimize
-
-
- Enables/disables optimizations.
-
-
-
-
- -ovf
-
-
- Specifies that exceptions will be raised on overflows (duplicate of -fovf)
-
-
-
-
- -out
-
-
- Specifies the output file.
-
-
-
-
- -parallel
-
-
- Specifies whether to use concurrent build (+).
-
-
-
-
- -parseonly
-
-
- Tells the compiler to only lex and parse the source code.
-
-
-
-
- -pathmap
-
-
- Specify a mapping for source path names output by the compiler.
-
-
-
-
- -pdb
-
-
- Specifies the file name and location of the .pdb file.
-
-
-
-
- -platform
-
-
- Specify the output platform.
-
-
-
-
- -ppo
-
-
- Writes preprocessor output to file
-
-
-
-
- -preferreduilang
-
-
- Specify a language for compiler output.
-
-
-
-
- -recurse
-
-
- Searches subdirectories for source files to compile.
-
-
-
-
- -reference
-
-
- Imports metadata from a file that contains an assembly.
-
-
-
-
- -resource
-
-
- Embeds a .NET Framework resource into the output file.
-
-
-
-
- -ruleset
-
-
- Specify a rule set file that disables specific diagnostics.
-
-
-
-
- -s
-
-
- Syntax check only
-
-
-
-
- -shared
-
-
- Use the shared compiler
-
-
-
-
- -showdefs
-
-
- Show the defines that are added from the header files and their usage
-
-
-
-
- -showincludes
-
-
- Lists #include files in compiler output
-
-
-
-
- -snk
-
-
- Signs assembly with strong name key pair
-
-
-
-
- -subsystemversion
-
-
- Specifies the minimum version of the subsystem that the executable file can use.
-
-
-
-
- -target
-
-
- Specifies the format of the output file using one of five options: /target:appcontainerexe, /target:exe, /target:library, /target:module, /target:winexe, or /target:winmdobj.
-
-
-
-
- -touchedfiles
-
-
- Specify filename that will be updated with list of files read and written by the compiler
-
-
-
-
- -undeclared
-
-
- Enables the support for undeclared memory variables
-
-
-
-
- -unsafe
-
-
- Enables compilation of code that uses the unsafe keyword.
-
-
-
-
- -usenativeversion
-
-
- Prefer native resource (if any) over resources generated from managed assembly properties
-
-
-
-
- -utf8output
-
-
- Displays compiler output using UTF-8 encoding.
-
-
-
-
- -vo1
-
-
- Use Init and Axit methods in stead of Constructors and Destructors
-
-
-
-
- -vo2
-
-
- Initialize STRING variables, fields and DIM arrays to empty strings
-
-
-
-
- -vo3
-
-
- Treats All Methods As VIRTUAL
-
-
-
-
- -vo4
-
-
- Allows implicit numeric conversions
-
-
-
-
- -vo5
-
-
- Implicit CLIPPER Calling Convention for Zero-Argument Functions
-
-
-
-
- -vo6
-
-
- Resolves typed function pointers to PTR
-
-
-
-
- -vo7
-
-
- Allows compatible implicit casts and conversions
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XBase-Types.xml b/docs/Help_Spanish/Topics/XBase-Types.xml
deleted file mode 100644
index 8280038b38..0000000000
--- a/docs/Help_Spanish/Topics/XBase-Types.xml
+++ /dev/null
@@ -1,256 +0,0 @@
-
-
-
- XBase Types
-
-
- XBase Types
-
-
- The table below shows the type mapping between XBase types in X#.
- All types in the namespace XSharp are implemented in XSharp.VO.DLL and are only supported when NOT compiling in the Core dialect.
-
-
-
-
- XBase Type
-
-
- Implemented in type
-
-
-
-
- ARRAY
-
-
- XSharp.__Array
-
-
-
-
- ARRAY OF <t>
-
-
- XSharp.__ArrayBase <T>
-
-
-
-
- BINARY
-
-
- XSharp.__Binary
-
-
-
-
- BYTE
-
-
- System.Byte
-
-
-
-
- CHAR
-
-
- System.Char
-
-
-
-
- CODEBLOCK
-
-
- XSharp.CodeBlock
-
-
-
-
- _CODEBLOCK
-
-
- XSharp._CodeBlock
-
-
-
-
- DATE
-
-
- XSharp.__VODate
-
-
-
-
- CURRENCY
-
-
- XSharp.__Currency
-
-
-
-
- DATETIME
-
-
- System.DateTime
-
-
-
-
- DECIMAL
-
-
- System.Decimal
-
-
-
-
- DWORD
-
-
- System.UInt32
-
-
-
-
- DYNAMIC
-
-
- System.Dynamic
-
-
-
-
- FLOAT
-
-
- XSharp.__VOFloat
-
-
-
-
- INT / LONG / LONGINT
-
-
- System.Int32
-
-
-
-
- INT64
-
-
- System.Int64
-
-
-
-
- LOGIC
-
-
- System.Boolean or XSharp.__WinBool
-
-
-
-
- OBJECT
-
-
- System.Object
-
-
-
-
- PSZ
-
-
- XSharp.__Psz
-
-
-
-
- PTR
-
-
- System.IntPtr
-
-
-
-
- REAL4
-
-
- System.Float
-
-
-
-
- REAL8
-
-
- System.Double
-
-
-
-
- SHORT / SHORTINT
-
-
- System.Int16
-
-
-
-
- STRING
-
-
- System.String
-
-
-
-
- SYMBOL
-
-
- XSharp.__Symbol
-
-
-
-
- UINT64
-
-
- System.UInt64
-
-
-
-
- USUAL
-
-
- XSharp.__Usual
-
-
-
-
- VOID
-
-
- System.Void
-
-
-
-
- WORD
-
-
- System.UInt16
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XML-Documentation-Comments.xml b/docs/Help_Spanish/Topics/XML-Documentation-Comments.xml
deleted file mode 100644
index 9285d7fa9e..0000000000
--- a/docs/Help_Spanish/Topics/XML-Documentation-Comments.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- XML Documentation Comments
-
-
- XML Documentation Comments
-
- In X#, you can create documentation for your code by including XML elements in special comment fields (indicated by triple slashes) in the source code directly before the code block to which the comments refer, for example.
-
- /// <summary> /// This class performs an important function. /// </summary> CLASS MyClass . . ENDCLASS
- When you compile with the -doc option, the compiler will search for all XML tags in the source code and create an XML documentation file. To create the final documentation based on the compiler-generated file, you can create a custom tool or use a tool such Sandcastle.
-
- To refer to XML elements (for example, your function processes specific XML elements that you want to describe in an XML documentation comment), you can use the standard quoting mechanism (< and >). To refer to generic identifiers in code reference (cref) elements, you can use either the escape characters (for example, cref="List<T>") or braces (cref="List{T}"). As a special case, the compiler parses the braces as angle brackets to make the documentation comment less cumbersome to author when referring to generic identifiers.
-
- Since we use the same documentation engine that C# does, we refer to the C# documentation for the list of allowed documentation tags.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XPorter.xml b/docs/Help_Spanish/Topics/XPorter.xml
deleted file mode 100644
index 2fffed8b66..0000000000
--- a/docs/Help_Spanish/Topics/XPorter.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XPorter
-
- XPorter
-
-
-
- XPorter
-
- Enter topic text here.
-
-
diff --git a/docs/Help_Spanish/Topics/XS0006.xml b/docs/Help_Spanish/Topics/XS0006.xml
deleted file mode 100644
index 011f28cf27..0000000000
--- a/docs/Help_Spanish/Topics/XS0006.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- XS0006
-
- XS0006
-
-
-
- Error XS0006
-
- Metadata file 'dll_name' could not be found
-
- The program was compiled and explicitly passed the name of a file that contained metadata; however, the .dll was not found. For more information, see /reference (X# Compiler Options).
-
-
diff --git a/docs/Help_Spanish/Topics/XS0009.XML b/docs/Help_Spanish/Topics/XS0009.XML
deleted file mode 100644
index 14fc56ed75..0000000000
--- a/docs/Help_Spanish/Topics/XS0009.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0009
-
- XS0009
-
-
-
- Error XS0009
-
- Metadata file '{0}' could not be opened -- {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0012.XML b/docs/Help_Spanish/Topics/XS0012.XML
deleted file mode 100644
index 68be8b9488..0000000000
--- a/docs/Help_Spanish/Topics/XS0012.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0012
-
- XS0012
-
-
-
- Error XS0012
-
- The type '{0}' is defined in an assembly that is not referenced. You must add a reference to assembly '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0016.xml b/docs/Help_Spanish/Topics/XS0016.xml
deleted file mode 100644
index 6a59179eef..0000000000
--- a/docs/Help_Spanish/Topics/XS0016.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- XS0016
-
- XS0016
-
-
-
- Error XS0016
-
- Could not write to output file 'file' — 'reason'
-
- The compiler could not write to an output file. Check the path to the file to make sure it exists. If a previously built file is already at the location, make sure it is writeable, and that no process currently has a lock on the file. For example,make sure your executable is not running when you attempt to build.
-
-
diff --git a/docs/Help_Spanish/Topics/XS0017.XML b/docs/Help_Spanish/Topics/XS0017.XML
deleted file mode 100644
index 5e928b8137..0000000000
--- a/docs/Help_Spanish/Topics/XS0017.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0017
-
- XS0017
-
-
-
- Error XS0017
-
- Program has more than one entry point defined. Compile with /main to specify the type that contains the entry point.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0019.xml b/docs/Help_Spanish/Topics/XS0019.xml
deleted file mode 100644
index 416ceb6820..0000000000
--- a/docs/Help_Spanish/Topics/XS0019.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- XS0019
-
- XS0019
-
-
-
- Error XS0019
-
- Operator 'operator' cannot be applied to operands of type 'type' and 'type'
-
- A binary operator is applied to data types that do not support it. For example, you cannot use the || operator on strings, you cannot use + , - , < , or > operators on bool variables, and you cannot use the == operator with a struct type unless the type explicitly overloads that operator.
-
- If you encounter this error with a class type, it is because the class does not overload the operator. For more information, see Overloadable Operators.
- Example
-
- In the following example, XS0019 is generated in two places because bool in X# is not convertible to int. XS0019 also is generated when the subtraction operator is applied to a string. The addition operator (+) can be used with string operands because that operator is overloaded by the String class to perform string concatenation.
-
-
-
-
- Example
-
- In the following example, conditional logic must be specified outside the ConditionalAttribute. You can pass only one predefined symbol to the ConditionalAttribute.
- The following sample generates XS0019.
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0020.XML b/docs/Help_Spanish/Topics/XS0020.XML
deleted file mode 100644
index e70a4dfc90..0000000000
--- a/docs/Help_Spanish/Topics/XS0020.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0020
-
- XS0020
-
-
-
- Error XS0020
-
- Division by constant zero
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0021.XML b/docs/Help_Spanish/Topics/XS0021.XML
deleted file mode 100644
index 89b42f200e..0000000000
--- a/docs/Help_Spanish/Topics/XS0021.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0021
-
- XS0021
-
-
-
- Error XS0021
-
- Cannot apply indexing with [] to an expression of type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0022.XML b/docs/Help_Spanish/Topics/XS0022.XML
deleted file mode 100644
index fc6fa692a3..0000000000
--- a/docs/Help_Spanish/Topics/XS0022.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0022
-
- XS0022
-
-
-
- Error XS0022
-
- Wrong number of indices inside []; expected {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0023.XML b/docs/Help_Spanish/Topics/XS0023.XML
deleted file mode 100644
index 860db2f922..0000000000
--- a/docs/Help_Spanish/Topics/XS0023.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0023
-
- XS0023
-
-
-
- Error XS0023
-
- Operator '{0}' cannot be applied to operand of type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0026.XML b/docs/Help_Spanish/Topics/XS0026.XML
deleted file mode 100644
index a6d04df2ba..0000000000
--- a/docs/Help_Spanish/Topics/XS0026.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0026
-
- XS0026
-
-
-
- Error XS0026
-
- Keyword 'SELF' is not valid in a static property, static method, or static field initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0027.XML b/docs/Help_Spanish/Topics/XS0027.XML
deleted file mode 100644
index 3e8047be5a..0000000000
--- a/docs/Help_Spanish/Topics/XS0027.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0027
-
- XS0027
-
-
-
- Error XS0027
-
- Keyword 'SELF' is not available in the current context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0028.XML b/docs/Help_Spanish/Topics/XS0028.XML
deleted file mode 100644
index 23a780e86b..0000000000
--- a/docs/Help_Spanish/Topics/XS0028.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0028
-
- XS0028
-
-
-
- Warning XS0028
-
- '{0}' has the wrong signature to be an entry point
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0029.xml b/docs/Help_Spanish/Topics/XS0029.xml
deleted file mode 100644
index 09076fc5cd..0000000000
--- a/docs/Help_Spanish/Topics/XS0029.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- XS0029
-
- XS0029
-
-
-
- Error XS0029
-
- Cannot implicitly convert type 'type' to 'type'
-
- The compiler requires an explicit conversion. For example, you may need to cast an r-value to be the same type as an l-value. Or, you must provide conversion routines to support certain operator overloads.
-
- Conversions must occur when assigning a variable of one type to a variable of a different type. When making an assignment between variables of different types, the compiler must convert the type on the right-hand side of the assignment operator to the type on the left-hand side of the assignment operator. Take the following the code:
-
-
-
- i = lng; makes an assignment, but the data types of the variables on the left and right-hand side of the assignment operator don't match. Before making the assignment the compiler is implicitly converting the variable lng, which is of type long, to an int. This is implicit because no code explicitly instructed the compiler to perform this conversion. The problem with this code is that this is considered a narrowing conversion, and the compiler does not allow implicit narrowing conversions because there could be a potential loss of data.
-
- A narrowing conversion exists when converting to a data type that occupies less storage space in memory than the data type we are converting from. For example, converting a long to an int would be considered a narrowing conversion. A long occupies 8 bytes of memory while an int occupies 4 bytes. To see how data loss can occur, consider the following sample:
-
-
-
-
- The variable lng now contains a value that cannot be stored in the variable i because it is too large. If we were to convert this value to an int type we would be losing some of our data and the converted value would not be the same as the value before the conversion.
-
- A widening conversion would be the opposite of a narrowing conversion. With widening conversions, we are converting to a data type that occupies more storage space in memory than the data type we are converting from. Here is an example of a widening conversion:
-
-
-
-
- Notice the difference between this code sample and the first. This time the variable lng is on the left-hand side of the assignment operator, so it is the target of our assignment. Before the assignment can be made, the compiler must implicitly convert the variable i, which is of type int, to type long. This is a widening conversion since we are converting from a type that occupies 4 bytes of memory (an int) to a type that occupies 8 bytes of memory (a long). Implicit widening conversions are allowed because there is no potential loss of data. Any value that can be stored in an int can also be stored in a long.
-
- We know that implicit narrowing conversions are not allowed, so to be able to compile this code we need to explicitly convert the data type. Explicit conversions are done using casting. Casting is the term used in X# to describe converting one data type to another. To get the code to compile we would need to use the following syntax:
-
-
-
- The third line of code tells the compiler to explicitly convert the variable lng, which is of type long, to an int before making the assignment. Remember that with a narrowing conversion, there is a potential loss of data. Narrowing conversions should be used with caution and even though the code will compile you may get unexpected results at run-time.
-
- This discussion has only been for value types. When working with value types you work directly with the data stored in the variable. However, the .NET Framework also has reference types. When working with reference types you are working with a reference to a variable, not the actual data. Examples of reference types would be classes, interfaces and arrays. You cannot implicitly or explicitly convert one reference type to another unless the compiler allows the specific conversion or the appropriate conversion operators are implemented.
-
- The following sample generates XS0029:
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0030.XML b/docs/Help_Spanish/Topics/XS0030.XML
deleted file mode 100644
index fe0c930ca1..0000000000
--- a/docs/Help_Spanish/Topics/XS0030.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0030
-
- XS0030
-
-
-
- Error XS0030
-
- Cannot convert type '{0}' to '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0031.XML b/docs/Help_Spanish/Topics/XS0031.XML
deleted file mode 100644
index 1fca8c3776..0000000000
--- a/docs/Help_Spanish/Topics/XS0031.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0031
-
- XS0031
-
-
-
- Error XS0031
-
- Constant value '{0}' cannot be converted to a '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0034.xml b/docs/Help_Spanish/Topics/XS0034.xml
deleted file mode 100644
index 65161846c3..0000000000
--- a/docs/Help_Spanish/Topics/XS0034.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0034
-
- XS0034
-
-
-
- Error XS0034
-
- Operator 'operator' is ambiguous on operands of type 'type1' and 'type2'
-
- An operator was used on two objects and the compiler found more than one conversion. Because conversions have to be unique, you either have to make a cast or to make one of the conversions explicit. For more information, see Conversion Operators.
-
- The following sample generates XS0034:
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0035.XML b/docs/Help_Spanish/Topics/XS0035.XML
deleted file mode 100644
index de90a60f15..0000000000
--- a/docs/Help_Spanish/Topics/XS0035.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0035
-
- XS0035
-
-
-
- Error XS0035
-
- Operator '{0}' is ambiguous on an operand of type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0036.XML b/docs/Help_Spanish/Topics/XS0036.XML
deleted file mode 100644
index 98467b2ba8..0000000000
--- a/docs/Help_Spanish/Topics/XS0036.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0036
-
- XS0036
-
-
-
- Error XS0036
-
- An out parameter cannot have the In attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0037.XML b/docs/Help_Spanish/Topics/XS0037.XML
deleted file mode 100644
index d6c9dc92af..0000000000
--- a/docs/Help_Spanish/Topics/XS0037.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0037
-
- XS0037
-
-
-
- Error XS0037
-
- Cannot convert null to '{0}' because it is a non-nullable value type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0039.xml b/docs/Help_Spanish/Topics/XS0039.xml
deleted file mode 100644
index 0c63c933e3..0000000000
--- a/docs/Help_Spanish/Topics/XS0039.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS0039
-
- XS0039
-
-
-
- Error XS0039
-
- Cannot convert type 'type1' to 'type2' via a reference conversion, boxing conversion, unboxing conversion, wrapping conversion, or null type conversion
-
- A conversion with the as operator is allowed by inheritance, reference conversions, and boxing conversions. For more information, see Conversion Operators.
-
- Example
-
- The following example generates XS0039.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0041.XML b/docs/Help_Spanish/Topics/XS0041.XML
deleted file mode 100644
index dd0c32c2f3..0000000000
--- a/docs/Help_Spanish/Topics/XS0041.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0041
-
- XS0041
-
-
-
- Error XS0041
-
- Unexpected error writing debug information -- '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0050.xml b/docs/Help_Spanish/Topics/XS0050.xml
deleted file mode 100644
index 20c7b4c51c..0000000000
--- a/docs/Help_Spanish/Topics/XS0050.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0050
-
- XS0050
-
-
-
- Warning XS0050
-
- Inconsistent accessibility: return type 'type' is less accessible than method 'method'
-
- The return type and each of the types referenced in the formal parameter list of a method must be at least as accessible as the method itself. For more information, see Access Modifiers.
- Example
-
- The following sample generates XS0050 because no accessiblity modifier is supplied for MyClass and its accessibility therefore defaults to private.
-
- // XS0050.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0051.xml b/docs/Help_Spanish/Topics/XS0051.xml
deleted file mode 100644
index 27d422a7b9..0000000000
--- a/docs/Help_Spanish/Topics/XS0051.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0051
-
- XS0051
-
-
-
- Warning XS0051
-
- Inconsistent accessibility: parameter type 'type' is less accessible than method 'method'
-
- The return type and each of the types referenced in the formal parameter list of a method must be at least as accessible as the method itself. Make sure the types used in method signatures are not accidentally private due to the omission of the public modifier. For more information, see Access Modifiers.
- Example
-
- The following sample generates XS0051:
-
-
- // XS0051.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0052.xml b/docs/Help_Spanish/Topics/XS0052.xml
deleted file mode 100644
index 8880f4ca00..0000000000
--- a/docs/Help_Spanish/Topics/XS0052.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0052
-
- XS0052
-
-
-
- Warning XS0052
-
- Inconsistent accessibility: field type 'type' is less accessible than field 'field'
-
- The type of a field cannot be less accessible than the field itself because all public constructs must return a publicly accessible object.
- Example
-
- The following sample generates XS0052:
-
-
- // XS0052.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0053.XML b/docs/Help_Spanish/Topics/XS0053.XML
deleted file mode 100644
index c2952eed36..0000000000
--- a/docs/Help_Spanish/Topics/XS0053.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0053
-
- XS0053
-
-
-
- Warning XS0053
-
- Inconsistent accessibility: property type '{1}' is less accessible than property '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0054.XML b/docs/Help_Spanish/Topics/XS0054.XML
deleted file mode 100644
index 642e5ac555..0000000000
--- a/docs/Help_Spanish/Topics/XS0054.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0054
-
- XS0054
-
-
-
- Warning XS0054
-
- Inconsistent accessibility: indexer return type '{1}' is less accessible than indexer '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0055.XML b/docs/Help_Spanish/Topics/XS0055.XML
deleted file mode 100644
index 9fddc63d88..0000000000
--- a/docs/Help_Spanish/Topics/XS0055.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0055
-
- XS0055
-
-
-
- Warning XS0055
-
- Inconsistent accessibility: parameter type '{1}' is less accessible than indexer '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0056.XML b/docs/Help_Spanish/Topics/XS0056.XML
deleted file mode 100644
index d8e6c43168..0000000000
--- a/docs/Help_Spanish/Topics/XS0056.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0056
-
- XS0056
-
-
-
- Warning XS0056
-
- Inconsistent accessibility: return type '{1}' is less accessible than operator '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0057.XML b/docs/Help_Spanish/Topics/XS0057.XML
deleted file mode 100644
index ddfc8f0d6e..0000000000
--- a/docs/Help_Spanish/Topics/XS0057.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0057
-
- XS0057
-
-
-
- Warning XS0057
-
- Inconsistent accessibility: parameter type '{1}' is less accessible than operator '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0058.XML b/docs/Help_Spanish/Topics/XS0058.XML
deleted file mode 100644
index c3e2c557e0..0000000000
--- a/docs/Help_Spanish/Topics/XS0058.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0058
-
- XS0058
-
-
-
- Warning XS0058
-
- Inconsistent accessibility: return type '{1}' is less accessible than delegate '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0059.XML b/docs/Help_Spanish/Topics/XS0059.XML
deleted file mode 100644
index 064a33a4a9..0000000000
--- a/docs/Help_Spanish/Topics/XS0059.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0059
-
- XS0059
-
-
-
- Warning XS0059
-
- Inconsistent accessibility: parameter type '{1}' is less accessible than delegate '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0060.XML b/docs/Help_Spanish/Topics/XS0060.XML
deleted file mode 100644
index 20ef70e772..0000000000
--- a/docs/Help_Spanish/Topics/XS0060.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0060
-
- XS0060
-
-
-
- Warning XS0060
-
- Inconsistent accessibility: base class '{1}' is less accessible than class '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0061.XML b/docs/Help_Spanish/Topics/XS0061.XML
deleted file mode 100644
index d5a2aee652..0000000000
--- a/docs/Help_Spanish/Topics/XS0061.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0061
-
- XS0061
-
-
-
- Warning XS0061
-
- Inconsistent accessibility: base interface '{1}' is less accessible than interface '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0065.XML b/docs/Help_Spanish/Topics/XS0065.XML
deleted file mode 100644
index fef299f684..0000000000
--- a/docs/Help_Spanish/Topics/XS0065.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0065
-
- XS0065
-
-
-
- Error XS0065
-
- '{0}': event property must have both add and remove accessors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0066.XML b/docs/Help_Spanish/Topics/XS0066.XML
deleted file mode 100644
index 4e5f301391..0000000000
--- a/docs/Help_Spanish/Topics/XS0066.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0066
-
- XS0066
-
-
-
- Error XS0066
-
- '{0}': event must be of a delegate type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0067.XML b/docs/Help_Spanish/Topics/XS0067.XML
deleted file mode 100644
index e893b65993..0000000000
--- a/docs/Help_Spanish/Topics/XS0067.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0067
-
- XS0067
-
-
-
- Warning XS0067
-
- The event '{0}' is never used
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0068.XML b/docs/Help_Spanish/Topics/XS0068.XML
deleted file mode 100644
index 7b3f703eb9..0000000000
--- a/docs/Help_Spanish/Topics/XS0068.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0068
-
- XS0068
-
-
-
- Error XS0068
-
- '{0}': event in interface cannot have initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0069.XML b/docs/Help_Spanish/Topics/XS0069.XML
deleted file mode 100644
index cec489c210..0000000000
--- a/docs/Help_Spanish/Topics/XS0069.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0069
-
- XS0069
-
-
-
- Error XS0069
-
- An event in an interface cannot have add or remove accessors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0070.XML b/docs/Help_Spanish/Topics/XS0070.XML
deleted file mode 100644
index deb03ce1e7..0000000000
--- a/docs/Help_Spanish/Topics/XS0070.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0070
-
- XS0070
-
-
-
- Error XS0070
-
- The event '{0}' can only appear on the left hand side of += or -= (except when used from within the type '{1}')
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0071.xml b/docs/Help_Spanish/Topics/XS0071.xml
deleted file mode 100644
index ec5480cb80..0000000000
--- a/docs/Help_Spanish/Topics/XS0071.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0071
-
- XS0071
-
-
-
- Error XS0071
-
- An explicit interface implementation of an event must use event accessor syntax
-
- When explicitly implementing an event that was declared in an interface, you must use manually provide the add and remove event accessors that are typically provided by the compiler. The accessor code can connect the interface event to another event in your class (shown later in this topic), or to its own delegate type. For more information, see How to: Implement Interface Events.
- Example
-
- The following sample generates XS0071.
-
-
- // XS0071.prg
}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0072.XML b/docs/Help_Spanish/Topics/XS0072.XML
deleted file mode 100644
index ac14ebdb20..0000000000
--- a/docs/Help_Spanish/Topics/XS0072.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0072
-
- XS0072
-
-
-
- Error XS0072
-
- '{0}': cannot override; '{1}' is not an event
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0073.XML b/docs/Help_Spanish/Topics/XS0073.XML
deleted file mode 100644
index b71e9b22d5..0000000000
--- a/docs/Help_Spanish/Topics/XS0073.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0073
-
- XS0073
-
-
-
- Error XS0073
-
- An add or remove accessor must have a body
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0074.XML b/docs/Help_Spanish/Topics/XS0074.XML
deleted file mode 100644
index 6bb8d7e3f0..0000000000
--- a/docs/Help_Spanish/Topics/XS0074.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0074
-
- XS0074
-
-
-
- Error XS0074
-
- '{0}': abstract event cannot have initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0075.XML b/docs/Help_Spanish/Topics/XS0075.XML
deleted file mode 100644
index 48e0798c44..0000000000
--- a/docs/Help_Spanish/Topics/XS0075.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0075
-
- XS0075
-
-
-
- Error XS0075
-
- To cast a negative value, you must enclose the value in parentheses.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0076.XML b/docs/Help_Spanish/Topics/XS0076.XML
deleted file mode 100644
index ac73b5e0ef..0000000000
--- a/docs/Help_Spanish/Topics/XS0076.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0076
-
- XS0076
-
-
-
- Error XS0076
-
- The enumerator name '{0}' is reserved and cannot be used
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0077.XML b/docs/Help_Spanish/Topics/XS0077.XML
deleted file mode 100644
index 3b265e6ded..0000000000
--- a/docs/Help_Spanish/Topics/XS0077.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0077
-
- XS0077
-
-
-
- Error XS0077
-
- The as operator must be used with a reference type or nullable type ('{0}' is a non-nullable value type)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0078.XML b/docs/Help_Spanish/Topics/XS0078.XML
deleted file mode 100644
index 79509f8bd1..0000000000
--- a/docs/Help_Spanish/Topics/XS0078.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0078
-
- XS0078
-
-
-
- Warning XS0078
-
- The 'l' suffix is easily confused with the digit '1' -- use 'L' for clarity
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0079.XML b/docs/Help_Spanish/Topics/XS0079.XML
deleted file mode 100644
index 886a2a55a3..0000000000
--- a/docs/Help_Spanish/Topics/XS0079.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0079
-
- XS0079
-
-
-
- Error XS0079
-
- The event '{0}' can only appear on the left hand side of += or -=
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0080.XML b/docs/Help_Spanish/Topics/XS0080.XML
deleted file mode 100644
index 37366fdb90..0000000000
--- a/docs/Help_Spanish/Topics/XS0080.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0080
-
- XS0080
-
-
-
- Error XS0080
-
- Constraints are not allowed on non-generic declarations
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0081.XML b/docs/Help_Spanish/Topics/XS0081.XML
deleted file mode 100644
index 9b46706449..0000000000
--- a/docs/Help_Spanish/Topics/XS0081.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0081
-
- XS0081
-
-
-
- Error XS0081
-
- Type parameter declaration must be an identifier not a type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0082.XML b/docs/Help_Spanish/Topics/XS0082.XML
deleted file mode 100644
index 4cd841d109..0000000000
--- a/docs/Help_Spanish/Topics/XS0082.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0082
-
- XS0082
-
-
-
- Error XS0082
-
- Type '{1}' already reserves a member called '{0}' with the same parameter types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0100.XML b/docs/Help_Spanish/Topics/XS0100.XML
deleted file mode 100644
index 7d4065d494..0000000000
--- a/docs/Help_Spanish/Topics/XS0100.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0100
-
- XS0100
-
-
-
- Error XS0100
-
- The parameter name '{0}' is a duplicate
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0101.XML b/docs/Help_Spanish/Topics/XS0101.XML
deleted file mode 100644
index bf64d102ac..0000000000
--- a/docs/Help_Spanish/Topics/XS0101.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0101
-
- XS0101
-
-
-
- Error XS0101
-
- The namespace '{1}' already contains a definition for '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0102.XML b/docs/Help_Spanish/Topics/XS0102.XML
deleted file mode 100644
index b0e3f90ec0..0000000000
--- a/docs/Help_Spanish/Topics/XS0102.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0102
-
- XS0102
-
-
-
- Error XS0102
-
- The type '{0}' already contains a definition for '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0103.xml b/docs/Help_Spanish/Topics/XS0103.xml
deleted file mode 100644
index e05d8736dc..0000000000
--- a/docs/Help_Spanish/Topics/XS0103.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- XS0103
-
- XS0103
-
-
-
- Error XS0103
-
- The name 'identifier' does not exist in the current context
-
- An attempt was made to use a name that does not exist in the class, namespace, or scope. Check the spelling of the name and check your using directives and assembly references to make sure that the name that you are trying to use is available.
-
- This error frequently occurs if you declare a variable in a loop or a try or if block and then attempt to access it from an enclosing code block or a separate code block, as shown in the following example.
-
-
- // XS0103.prg
-
- The following example resolves the error.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0104.XML b/docs/Help_Spanish/Topics/XS0104.XML
deleted file mode 100644
index 3710d9fb5b..0000000000
--- a/docs/Help_Spanish/Topics/XS0104.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0104
-
- XS0104
-
-
-
- Error XS0104
-
- '{0}' is an ambiguous reference between '{1}' and '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0105.XML b/docs/Help_Spanish/Topics/XS0105.XML
deleted file mode 100644
index 9ce454af0c..0000000000
--- a/docs/Help_Spanish/Topics/XS0105.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0105
-
- XS0105
-
-
-
- Warning XS0105
-
- The using directive for '{0}' appeared previously in this namespace
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0106.xml b/docs/Help_Spanish/Topics/XS0106.xml
deleted file mode 100644
index e08046dbfc..0000000000
--- a/docs/Help_Spanish/Topics/XS0106.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- XS0106
-
- XS0106
-
-
-
- Error XS0106
-
- The modifier 'modifier' is not valid for this item
-
- A class or interface member was marked with an invalid access modifier. The following examples describe some of these invalid modifiers:
-
-
-
The static and public modifiers are not permitted on interface methods.
-
The public keyword is not allowed on an explicit interface declaration. In this case, remove the public keyword from the explicit interface declaration.
-
The abstract keyword is not allowed on an explicit interface declaration because an explicit interface implementation can never be overridden.
-
-
- In prior releases of Visual Studio, the static modifier was not permitted on a class, but static classes are allowed starting with Microsoft Visual Studio 2005.
-
- For more information, see Interfaces
- Example
-
- The following sample generates XS0106.
-
-
- // XS0106.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0107.XML b/docs/Help_Spanish/Topics/XS0107.XML
deleted file mode 100644
index 1b2c39d014..0000000000
--- a/docs/Help_Spanish/Topics/XS0107.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0107
-
- XS0107
-
-
-
- Error XS0107
-
- More than one protection modifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0108.xml b/docs/Help_Spanish/Topics/XS0108.xml
deleted file mode 100644
index 07f77f694b..0000000000
--- a/docs/Help_Spanish/Topics/XS0108.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- XS0108
-
- XS0108
-
-
-
- Warning XS0108
-
- 'member1' hides inherited member 'member2'. Use the new keyword if hiding was intended.
-
- please check the compiler option /VO3 Virtual Instance Methods or add the keyword virtual to your methods.
- Bby default METHODs and PROPERTIEs in .Net are not VIRTUAL, meaning that you cannot override a method of a base class by redefining it in a child class, like we do in VO, this instead creates a completely new method, from the CLR's point of view. In order to allow a (base) method to be overwritten , you must explicitly mark it with the VIRTUAL keyword. Or, you van simply enable the “All instance methods virtual” project option, which tells the compiler to make all methods VIRTUAL by default, for compatibility with VO. Both ways should get rid of the warning.
-
-
diff --git a/docs/Help_Spanish/Topics/XS0109.XML b/docs/Help_Spanish/Topics/XS0109.XML
deleted file mode 100644
index d2574fb144..0000000000
--- a/docs/Help_Spanish/Topics/XS0109.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0109
-
- XS0109
-
-
-
- Warning XS0109
-
- The member '{0}' does not hide an inherited member. The new keyword is not required.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0110.XML b/docs/Help_Spanish/Topics/XS0110.XML
deleted file mode 100644
index 903a171b59..0000000000
--- a/docs/Help_Spanish/Topics/XS0110.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0110
-
- XS0110
-
-
-
- Error XS0110
-
- The evaluation of the constant value for '{0}' involves a circular definition
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0111.XML b/docs/Help_Spanish/Topics/XS0111.XML
deleted file mode 100644
index a82190f5b2..0000000000
--- a/docs/Help_Spanish/Topics/XS0111.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0111
-
- XS0111
-
-
-
- Error XS0111
-
- Type '{1}' already defines a member called '{0}' with the same parameter types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0112.XML b/docs/Help_Spanish/Topics/XS0112.XML
deleted file mode 100644
index 077a16ec82..0000000000
--- a/docs/Help_Spanish/Topics/XS0112.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0112
-
- XS0112
-
-
-
- Error XS0112
-
- A static member '{0}' cannot be marked as override, virtual, or abstract
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0113.XML b/docs/Help_Spanish/Topics/XS0113.XML
deleted file mode 100644
index 546d61a8a9..0000000000
--- a/docs/Help_Spanish/Topics/XS0113.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0113
-
- XS0113
-
-
-
- Error XS0113
-
- A member '{0}' marked as override cannot be marked as new or virtual
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0114.XML b/docs/Help_Spanish/Topics/XS0114.XML
deleted file mode 100644
index 1ed4ffe200..0000000000
--- a/docs/Help_Spanish/Topics/XS0114.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0114
-
- XS0114
-
-
-
- Warning XS0114
-
- '{0}' hides inherited member '{1}'. To make the current member override that implementation, add the override keyword. Otherwise add the new keyword.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0115.xml b/docs/Help_Spanish/Topics/XS0115.xml
deleted file mode 100644
index 79b5a6dc6d..0000000000
--- a/docs/Help_Spanish/Topics/XS0115.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- XS0115
-
- XS0115
-
-
-
- Error XS0115
-
- 'function' : no suitable method found to override
-
- A method was marked as an override, but the compiler found no method to override. For more information, see override, and Knowing When to Use Override and New Keywords.
- Example
-
- The following sample generates XS0115. You can resolve XS0115 in one of two ways:
-
-
-
Remove the override keyword from the method in MyClass2.
-
Use MyClass1 as a base class for MyClass2.
-
-
-
- // XS0115.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0116.xml b/docs/Help_Spanish/Topics/XS0116.xml
deleted file mode 100644
index 82d6d5ebfd..0000000000
--- a/docs/Help_Spanish/Topics/XS0116.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0116
-
- XS0116
-
-
-
- Error XS0116
-
- A namespace does not directly contain members such as fields or methods
-
- Inside a namespace, the compiler only accepts classes, structures, unions, enumerations, interfaces, and delegates. This error is often generated by developers from a C/C++ background who forget that in X#, methods and variables must be declared and defined within a struct or class. For more information, see General Structure of a X# Program.
- Example
-
- The following sample generates XS0116:
-
-
- // XS0116.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0117.XML b/docs/Help_Spanish/Topics/XS0117.XML
deleted file mode 100644
index 410c9ef22a..0000000000
--- a/docs/Help_Spanish/Topics/XS0117.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0117
-
- XS0117
-
-
-
- Error XS0117
-
- '{0}' does not contain a definition for '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0118.XML b/docs/Help_Spanish/Topics/XS0118.XML
deleted file mode 100644
index 1d0d6fb092..0000000000
--- a/docs/Help_Spanish/Topics/XS0118.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0118
-
- XS0118
-
-
-
- Error XS0118
-
- '{0}' is a {1} but is used like a {2}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0119.XML b/docs/Help_Spanish/Topics/XS0119.XML
deleted file mode 100644
index edc3dbe046..0000000000
--- a/docs/Help_Spanish/Topics/XS0119.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0119
-
- XS0119
-
-
-
- Error XS0119
-
- '{0}' is a {1}, which is not valid in the given context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0120.xml b/docs/Help_Spanish/Topics/XS0120.xml
deleted file mode 100644
index d9a187d265..0000000000
--- a/docs/Help_Spanish/Topics/XS0120.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- XS0120
-
- XS0120
-
-
-
- Error XS0120
-
- An object reference is required for the nonstatic field, method, or property 'member'
-
- In order to use a non-static field, method, or property, you must first create an object instance. For more information about static methods, see Static Classes and Static Class Members. For more information about creating instances of classes, see Instance Constructors.
-
- The following sample generates XS0120:
-
-
- // XS0120_1.prg
-
-
- XS0120 will also be generated if there is a call to a non-static method from a static method, as follows:
-
-
- // XS0120_2.prg // XS0120 expected
-
- Similarly, a static method cannot call an instance method unless you explicitly give it an instance of the class, as follows:
-
-
- // XS0120_3.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0121.XML b/docs/Help_Spanish/Topics/XS0121.XML
deleted file mode 100644
index 75e26d00e9..0000000000
--- a/docs/Help_Spanish/Topics/XS0121.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0121
-
- XS0121
-
-
-
- Error XS0121
-
- The call is ambiguous between the following methods or properties: '{0}' and '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0122.XML b/docs/Help_Spanish/Topics/XS0122.XML
deleted file mode 100644
index 4f8318d46a..0000000000
--- a/docs/Help_Spanish/Topics/XS0122.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0122
-
- XS0122
-
-
-
- Error XS0122
-
- '{0}' is inaccessible due to its protection level
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0123.XML b/docs/Help_Spanish/Topics/XS0123.XML
deleted file mode 100644
index b242ed88f7..0000000000
--- a/docs/Help_Spanish/Topics/XS0123.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0123
-
- XS0123
-
-
-
- Error XS0123
-
- No overload for '{0}' matches delegate '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0126.XML b/docs/Help_Spanish/Topics/XS0126.XML
deleted file mode 100644
index 192433ae53..0000000000
--- a/docs/Help_Spanish/Topics/XS0126.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0126
-
- XS0126
-
-
-
- Error XS0126
-
- An object of a type convertible to '{0}' is required
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0127.XML b/docs/Help_Spanish/Topics/XS0127.XML
deleted file mode 100644
index 25e27fade9..0000000000
--- a/docs/Help_Spanish/Topics/XS0127.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0127
-
- XS0127
-
-
-
- Error XS0127
-
- Since '{0}' returns void, a return keyword must not be followed by an object expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0128.XML b/docs/Help_Spanish/Topics/XS0128.XML
deleted file mode 100644
index 1f449031ea..0000000000
--- a/docs/Help_Spanish/Topics/XS0128.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0128
-
- XS0128
-
-
-
- Error XS0128
-
- A local variable named '{0}' is already defined in this scope
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0131.XML b/docs/Help_Spanish/Topics/XS0131.XML
deleted file mode 100644
index f36952d3df..0000000000
--- a/docs/Help_Spanish/Topics/XS0131.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0131
-
- XS0131
-
-
-
- Error XS0131
-
- The left-hand side of an assignment must be a variable, property or indexer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0132.XML b/docs/Help_Spanish/Topics/XS0132.XML
deleted file mode 100644
index 1f725c3d7e..0000000000
--- a/docs/Help_Spanish/Topics/XS0132.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0132
-
- XS0132
-
-
-
- Error XS0132
-
- '{0}': a static constructor must be parameterless
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0133.XML b/docs/Help_Spanish/Topics/XS0133.XML
deleted file mode 100644
index 655b8d03d2..0000000000
--- a/docs/Help_Spanish/Topics/XS0133.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0133
-
- XS0133
-
-
-
- Error XS0133
-
- The expression being assigned to '{0}' must be constant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0134.xml b/docs/Help_Spanish/Topics/XS0134.xml
deleted file mode 100644
index bebeb368b7..0000000000
--- a/docs/Help_Spanish/Topics/XS0134.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS0134
-
- XS0134
-
-
-
- Error XS0134
-
- 'variable' is of type 'type'. A const field of a reference type other than string can only be initialized with null.
-
- A constant-expression is an expression that can be fully evaluated at compile-time. Because the only way to create a non-null value of a reference-type is to apply the new operator, and because the new operator is not permitted in a constant-expression, the only possible value for constants of reference-types other than string is null.
-
- If you encounter this error by trying to create a const string array, the solution is to make the array readonly, and initialize it in the constructor.
- Example
-
- The following example generates XS0134.
-
-
- // XS0134.prg // compile with: /target:library
-
-
diff --git a/docs/Help_Spanish/Topics/XS0136.XML b/docs/Help_Spanish/Topics/XS0136.XML
deleted file mode 100644
index 6e85951969..0000000000
--- a/docs/Help_Spanish/Topics/XS0136.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0136
-
- XS0136
-
-
-
- Error XS0136
-
- A local or parameter named '{0}' cannot be declared in this scope because that name is used in an enclosing local scope to define a local or parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0138.XML b/docs/Help_Spanish/Topics/XS0138.XML
deleted file mode 100644
index b9e7b1b34e..0000000000
--- a/docs/Help_Spanish/Topics/XS0138.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0138
-
- XS0138
-
-
-
- Error XS0138
-
- A 'using namespace' directive can only be applied to namespaces; '{0}' is a type not a namespace. Consider a 'using static' directive instead
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0139.XML b/docs/Help_Spanish/Topics/XS0139.XML
deleted file mode 100644
index 4fe607b20e..0000000000
--- a/docs/Help_Spanish/Topics/XS0139.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0139
-
- XS0139
-
-
-
- Error XS0139
-
- No enclosing loop out of which to break or continue
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0140.XML b/docs/Help_Spanish/Topics/XS0140.XML
deleted file mode 100644
index 51be236381..0000000000
--- a/docs/Help_Spanish/Topics/XS0140.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0140
-
- XS0140
-
-
-
- Error XS0140
-
- The label '{0}' is a duplicate
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0143.XML b/docs/Help_Spanish/Topics/XS0143.XML
deleted file mode 100644
index ff8799e94a..0000000000
--- a/docs/Help_Spanish/Topics/XS0143.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0143
-
- XS0143
-
-
-
- Error XS0143
-
- The type '{0}' has no constructors defined
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0144.XML b/docs/Help_Spanish/Topics/XS0144.XML
deleted file mode 100644
index 38517f03d6..0000000000
--- a/docs/Help_Spanish/Topics/XS0144.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0144
-
- XS0144
-
-
-
- Error XS0144
-
- Cannot create an instance of the abstract class or interface '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0145.XML b/docs/Help_Spanish/Topics/XS0145.XML
deleted file mode 100644
index 754bce9483..0000000000
--- a/docs/Help_Spanish/Topics/XS0145.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0145
-
- XS0145
-
-
-
- Error XS0145
-
- A const field requires a value to be provided
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0146.XML b/docs/Help_Spanish/Topics/XS0146.XML
deleted file mode 100644
index ecdfab5054..0000000000
--- a/docs/Help_Spanish/Topics/XS0146.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0146
-
- XS0146
-
-
-
- Error XS0146
-
- Circular base class dependency involving '{0}' and '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0148.XML b/docs/Help_Spanish/Topics/XS0148.XML
deleted file mode 100644
index 9051ebf7b8..0000000000
--- a/docs/Help_Spanish/Topics/XS0148.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0148
-
- XS0148
-
-
-
- Error XS0148
-
- The delegate '{0}' does not have a valid constructor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0149.XML b/docs/Help_Spanish/Topics/XS0149.XML
deleted file mode 100644
index 1c2f7977da..0000000000
--- a/docs/Help_Spanish/Topics/XS0149.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0149
-
- XS0149
-
-
-
- Error XS0149
-
- Method name expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0150.XML b/docs/Help_Spanish/Topics/XS0150.XML
deleted file mode 100644
index 445745a6e0..0000000000
--- a/docs/Help_Spanish/Topics/XS0150.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0150
-
- XS0150
-
-
-
- Error XS0150
-
- A constant value is expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0151.xml b/docs/Help_Spanish/Topics/XS0151.xml
deleted file mode 100644
index 4a0528aa48..0000000000
--- a/docs/Help_Spanish/Topics/XS0151.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS0151
-
- XS0151
-
-
-
- Error XS0151
-
- A value of an integral type expected
-
- A variable was used in a situation where an integral data type was required. For more information, see Types.
- Example
-
- This error can occur when there is no conversion or if the available implicit conversions result in an ambiguous situation. The following sample generates XS0151.
-
-
- // XS0151.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0152.XML b/docs/Help_Spanish/Topics/XS0152.XML
deleted file mode 100644
index 5908138152..0000000000
--- a/docs/Help_Spanish/Topics/XS0152.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0152
-
- XS0152
-
-
-
- Error XS0152
-
- The switch statement contains multiple cases with the label value '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0153.XML b/docs/Help_Spanish/Topics/XS0153.XML
deleted file mode 100644
index 583d2da5c1..0000000000
--- a/docs/Help_Spanish/Topics/XS0153.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0153
-
- XS0153
-
-
-
- Error XS0153
-
- A goto case is only valid inside a switch statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0154.XML b/docs/Help_Spanish/Topics/XS0154.XML
deleted file mode 100644
index 20840df855..0000000000
--- a/docs/Help_Spanish/Topics/XS0154.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0154
-
- XS0154
-
-
-
- Error XS0154
-
- The property or indexer '{0}' cannot be used in this context because it lacks the get accessor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0155.XML b/docs/Help_Spanish/Topics/XS0155.XML
deleted file mode 100644
index 5440d90290..0000000000
--- a/docs/Help_Spanish/Topics/XS0155.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0155
-
- XS0155
-
-
-
- Error XS0155
-
- The type caught or thrown must be derived from System.Exception
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0156.XML b/docs/Help_Spanish/Topics/XS0156.XML
deleted file mode 100644
index f5cd3a8920..0000000000
--- a/docs/Help_Spanish/Topics/XS0156.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0156
-
- XS0156
-
-
-
- Error XS0156
-
- A throw statement with no arguments is not allowed outside of a catch clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0157.XML b/docs/Help_Spanish/Topics/XS0157.XML
deleted file mode 100644
index 28156eb1ca..0000000000
--- a/docs/Help_Spanish/Topics/XS0157.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0157
-
- XS0157
-
-
-
- Error XS0157
-
- Control cannot leave the body of a finally clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0158.XML b/docs/Help_Spanish/Topics/XS0158.XML
deleted file mode 100644
index ed7aad0ee8..0000000000
--- a/docs/Help_Spanish/Topics/XS0158.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0158
-
- XS0158
-
-
-
- Error XS0158
-
- The label '{0}' shadows another label by the same name in a contained scope
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0159.XML b/docs/Help_Spanish/Topics/XS0159.XML
deleted file mode 100644
index 01123c41b7..0000000000
--- a/docs/Help_Spanish/Topics/XS0159.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0159
-
- XS0159
-
-
-
- Error XS0159
-
- No such label '{0}' within the scope of the goto statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0160.XML b/docs/Help_Spanish/Topics/XS0160.XML
deleted file mode 100644
index fad19432ff..0000000000
--- a/docs/Help_Spanish/Topics/XS0160.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0160
-
- XS0160
-
-
-
- Error XS0160
-
- A previous catch clause already catches all exceptions of this or of a super type ('{0}')
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0161.XML b/docs/Help_Spanish/Topics/XS0161.XML
deleted file mode 100644
index 8d7fcb8ddb..0000000000
--- a/docs/Help_Spanish/Topics/XS0161.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0161
-
- XS0161
-
-
-
- Error XS0161
-
- '{0}': not all code paths return a value
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0162.XML b/docs/Help_Spanish/Topics/XS0162.XML
deleted file mode 100644
index 1454b34baf..0000000000
--- a/docs/Help_Spanish/Topics/XS0162.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0162
-
- XS0162
-
-
-
- Warning XS0162
-
- Unreachable code detected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0163.xml b/docs/Help_Spanish/Topics/XS0163.xml
deleted file mode 100644
index ec5fd6f74b..0000000000
--- a/docs/Help_Spanish/Topics/XS0163.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS0163
-
- XS0163
-
-
-
- Error XS0163
-
- Control cannot fall through from one case label ('label') to another
-
- When a switch statement contains more than one switch section, you must explicitly terminate each section, including the last one, by using one of the following keywords:
-
-
-
return
-
goto
-
break
-
throw
-
continue
-
-
- If you want to implement "fall through" behavior from one section to the next, use goto case #. For more information and examples, see switch.
-
- The following sample generates XS0163.
-
-
- // XS0163.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0164.XML b/docs/Help_Spanish/Topics/XS0164.XML
deleted file mode 100644
index 54c491c264..0000000000
--- a/docs/Help_Spanish/Topics/XS0164.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0164
-
- XS0164
-
-
-
- Warning XS0164
-
- This label has not been referenced
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0165.xml b/docs/Help_Spanish/Topics/XS0165.xml
deleted file mode 100644
index 2e9599e9df..0000000000
--- a/docs/Help_Spanish/Topics/XS0165.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- XS0165
-
- XS0165
-
-
-
- Warning XS0165
-
- Use of unassigned local variable 'name'
-
- The X# compiler does not allow the use of uninitialized variables. If the compiler detects the use of a variable that might not have been initialized, it generates compiler error XS0165. For more information, see Fields. Note that this error is generated when the compiler encounters a construct that might result in the use of an unassigned variable, even if your particular code does not. This avoids the necessity of overly-complex rules for definite assignment.
- Example
-
- The following sample generates XS0165:
-
-
- // XS0165.prg
-
-
- Example
-
- Compiler error XS0165 can occur in recursive delegate definitions. You can avoid the error by defining the delegate in two statements so that the variable is not used before it is initialized. The following example demonstrates the error and the resolution.
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0168.XML b/docs/Help_Spanish/Topics/XS0168.XML
deleted file mode 100644
index 9298c33434..0000000000
--- a/docs/Help_Spanish/Topics/XS0168.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0168
-
- XS0168
-
-
-
- Warning XS0168
-
- The variable '{0}' is declared but never used
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0169.XML b/docs/Help_Spanish/Topics/XS0169.XML
deleted file mode 100644
index 55d6c692ad..0000000000
--- a/docs/Help_Spanish/Topics/XS0169.XML
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- XS0169
-
- XS0169
-
-
-
- Warning XS0169
-
- The field '{0}' is never used
-
- This warning will be shown when you declare a private field or method and you are never using that inside the class where it is defined.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0170.XML b/docs/Help_Spanish/Topics/XS0170.XML
deleted file mode 100644
index 183f1930f8..0000000000
--- a/docs/Help_Spanish/Topics/XS0170.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0170
-
- XS0170
-
-
-
- Warning XS0170
-
- Use of possibly unassigned field '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0171.XML b/docs/Help_Spanish/Topics/XS0171.XML
deleted file mode 100644
index dfb1a27e95..0000000000
--- a/docs/Help_Spanish/Topics/XS0171.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0171
-
- XS0171
-
-
-
- Warning XS0171
-
- Field '{0}' must be fully assigned before control is returned to the caller
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0172.XML b/docs/Help_Spanish/Topics/XS0172.XML
deleted file mode 100644
index c570d1fcbf..0000000000
--- a/docs/Help_Spanish/Topics/XS0172.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0172
-
- XS0172
-
-
-
- Error XS0172
-
- Type of conditional expression cannot be determined because '{0}' and '{1}' implicitly convert to one another
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0173.xml b/docs/Help_Spanish/Topics/XS0173.xml
deleted file mode 100644
index 5b2253d5d9..0000000000
--- a/docs/Help_Spanish/Topics/XS0173.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- XS0173
-
- XS0173
-
-
-
- Error XS0173
-
- Type of conditional expression cannot be determined because there is no implicit conversion between 'class1' and 'class2'
-
- Conversions between classes are useful when you want objects of different classes to work with the same code. However, two classes that work together cannot have mutual and redundant conversions, or no implicit conversions. The types of class1 and class2 are determined independently, and the more general type is selected as the type of the conditional expression. For more information about how types are determined, see Conditional operator cannot cast implicitly.
-
- To resolve XS0173, verify that there is one and only one implicit conversion between class1 and class2, regardless of which direction the conversion is in and regardless of which class the conversion is in. For more information, see Implicit Numeric Conversions Table and Conversion Operators.
- Example
-
- The following sample generates XS0173:
-
-
- // XS0173.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0174.XML b/docs/Help_Spanish/Topics/XS0174.XML
deleted file mode 100644
index 577557eb42..0000000000
--- a/docs/Help_Spanish/Topics/XS0174.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0174
-
- XS0174
-
-
-
- Error XS0174
-
- A base class is required for a 'SUPER' reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0175.XML b/docs/Help_Spanish/Topics/XS0175.XML
deleted file mode 100644
index cec03cf986..0000000000
--- a/docs/Help_Spanish/Topics/XS0175.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0175
-
- XS0175
-
-
-
- Error XS0175
-
- Use of keyword 'SUPER' is not valid in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0176.XML b/docs/Help_Spanish/Topics/XS0176.XML
deleted file mode 100644
index bae08b8075..0000000000
--- a/docs/Help_Spanish/Topics/XS0176.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0176
-
- XS0176
-
-
-
- Error XS0176
-
- Member '{0}' cannot be accessed with an instance reference; qualify it with a type name instead
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0177.XML b/docs/Help_Spanish/Topics/XS0177.XML
deleted file mode 100644
index f2bebb7b63..0000000000
--- a/docs/Help_Spanish/Topics/XS0177.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0177
-
- XS0177
-
-
-
- Error XS0177
-
- The out parameter '{0}' must be assigned to before control leaves the current method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0178.xml b/docs/Help_Spanish/Topics/XS0178.xml
deleted file mode 100644
index ae2fcae903..0000000000
--- a/docs/Help_Spanish/Topics/XS0178.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS0178
-
- XS0178
-
-
-
- Error XS0178
-
- Invalid rank specifier: expected ',' or ']'
-
- An array initialization was ill-formed. For example, when specifying the array dimensions, you can specify the following:
-
-
-
A number in brackets
-
Empty brackets
-
A comma enclosed in brackets
-
-
- For more information, see Arrays and the X# specification (X# Language Specification) section on array initializers.
- Example
-
- The following sample generates XS0178.
-
-
- // XS0178.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0179.XML b/docs/Help_Spanish/Topics/XS0179.XML
deleted file mode 100644
index 49f770c6a9..0000000000
--- a/docs/Help_Spanish/Topics/XS0179.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0179
-
- XS0179
-
-
-
- Error XS0179
-
- '{0}' cannot be extern and declare a body
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0180.XML b/docs/Help_Spanish/Topics/XS0180.XML
deleted file mode 100644
index 01f7549605..0000000000
--- a/docs/Help_Spanish/Topics/XS0180.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0180
-
- XS0180
-
-
-
- Error XS0180
-
- '{0}' cannot be both extern and abstract
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0181.XML b/docs/Help_Spanish/Topics/XS0181.XML
deleted file mode 100644
index 7350d4536f..0000000000
--- a/docs/Help_Spanish/Topics/XS0181.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0181
-
- XS0181
-
-
-
- Error XS0181
-
- Attribute constructor parameter '{0}' has type '{1}', which is not a valid attribute parameter type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0182.XML b/docs/Help_Spanish/Topics/XS0182.XML
deleted file mode 100644
index 59e0dac57f..0000000000
--- a/docs/Help_Spanish/Topics/XS0182.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0182
-
- XS0182
-
-
-
- Error XS0182
-
- An attribute argument must be a constant expression, typeof expression or array creation expression of an attribute parameter type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0183.XML b/docs/Help_Spanish/Topics/XS0183.XML
deleted file mode 100644
index 57494829c9..0000000000
--- a/docs/Help_Spanish/Topics/XS0183.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0183
-
- XS0183
-
-
-
- Warning XS0183
-
- The given expression is always of the provided ('{0}') type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0184.XML b/docs/Help_Spanish/Topics/XS0184.XML
deleted file mode 100644
index 53d5e49314..0000000000
--- a/docs/Help_Spanish/Topics/XS0184.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0184
-
- XS0184
-
-
-
- Warning XS0184
-
- The given expression is never of the provided ('{0}') type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0185.XML b/docs/Help_Spanish/Topics/XS0185.XML
deleted file mode 100644
index 7519d37ae7..0000000000
--- a/docs/Help_Spanish/Topics/XS0185.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0185
-
- XS0185
-
-
-
- Error XS0185
-
- '{0}' is not a reference type as required by the lock statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0186.XML b/docs/Help_Spanish/Topics/XS0186.XML
deleted file mode 100644
index 86e8325adc..0000000000
--- a/docs/Help_Spanish/Topics/XS0186.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0186
-
- XS0186
-
-
-
- Error XS0186
-
- Use of null is not valid in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0188.xml b/docs/Help_Spanish/Topics/XS0188.xml
deleted file mode 100644
index 0cd3a8ea31..0000000000
--- a/docs/Help_Spanish/Topics/XS0188.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- XS0188
-
- XS0188
-
-
-
- Warning XS0188
-
- The 'this' object cannot be used before all of its fields are assigned to
-
- All fields in a struct have to be assigned by a constructor before the constructor can call a method in the struct.
-
- If you see this error when trying to initialize a property in a struct constructor, the solution is to change the constructor parameter to specify the backing field instead of the property itself. Auto-implemented properties should be avoided in structs because they have no backing field and therefore cannot be initialized in any way from the constructor.
-
- For more information, see Using Structs.
- Example
-
- The following sample generates XS0188:
-
-
- // XS0188.prg // compile with: /t:library
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0190.XML b/docs/Help_Spanish/Topics/XS0190.XML
deleted file mode 100644
index beb9d00f3c..0000000000
--- a/docs/Help_Spanish/Topics/XS0190.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0190
-
- XS0190
-
-
-
- Error XS0190
-
- The __arglist construct is valid only within a variable argument method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0191.XML b/docs/Help_Spanish/Topics/XS0191.XML
deleted file mode 100644
index 68e896d05a..0000000000
--- a/docs/Help_Spanish/Topics/XS0191.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0191
-
- XS0191
-
-
-
- Error XS0191
-
- A readonly field cannot be assigned to (except in a constructor or a variable initializer)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0192.XML b/docs/Help_Spanish/Topics/XS0192.XML
deleted file mode 100644
index 0951d0227f..0000000000
--- a/docs/Help_Spanish/Topics/XS0192.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0192
-
- XS0192
-
-
-
- Error XS0192
-
- A readonly field cannot be passed ref or out (except in a constructor)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0193.XML b/docs/Help_Spanish/Topics/XS0193.XML
deleted file mode 100644
index f6c4ab601e..0000000000
--- a/docs/Help_Spanish/Topics/XS0193.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0193
-
- XS0193
-
-
-
- Error XS0193
-
- The * or -> operator must be applied to a pointer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0196.XML b/docs/Help_Spanish/Topics/XS0196.XML
deleted file mode 100644
index a7b5c39e79..0000000000
--- a/docs/Help_Spanish/Topics/XS0196.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0196
-
- XS0196
-
-
-
- Error XS0196
-
- A pointer must be indexed by only one value
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0197.XML b/docs/Help_Spanish/Topics/XS0197.XML
deleted file mode 100644
index 125257fc9b..0000000000
--- a/docs/Help_Spanish/Topics/XS0197.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0197
-
- XS0197
-
-
-
- Warning XS0197
-
- Passing '{0}' as ref or out or taking its address may cause a runtime exception because it is a field of a marshal-by-reference class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0198.XML b/docs/Help_Spanish/Topics/XS0198.XML
deleted file mode 100644
index 6f17419825..0000000000
--- a/docs/Help_Spanish/Topics/XS0198.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0198
-
- XS0198
-
-
-
- Error XS0198
-
- A static readonly field cannot be assigned to (except in a static constructor or a variable initializer)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0199.XML b/docs/Help_Spanish/Topics/XS0199.XML
deleted file mode 100644
index b85c266cc9..0000000000
--- a/docs/Help_Spanish/Topics/XS0199.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0199
-
- XS0199
-
-
-
- Error XS0199
-
- A static readonly field cannot be passed ref or out (except in a static constructor)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0200.XML b/docs/Help_Spanish/Topics/XS0200.XML
deleted file mode 100644
index f9f639bf86..0000000000
--- a/docs/Help_Spanish/Topics/XS0200.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0200
-
- XS0200
-
-
-
- Error XS0200
-
- Property or indexer '{0}' cannot be assigned to -- it is read only
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0201.xml b/docs/Help_Spanish/Topics/XS0201.xml
deleted file mode 100644
index db7b6567d8..0000000000
--- a/docs/Help_Spanish/Topics/XS0201.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XS0201
-
- XS0201
-
-
-
- Error XS0201
-
- Only assignment, call, increment, decrement, and new object expressions can be used as a statement
-
- The compiler generates an error when it encounters an invalid statement. An invalid statement is any line or series of lines ending in a semicolon that does not represent an assignment (=), method call (), new, -- or ++ operation. For more information, see Statements, Expressions, and Operators.
-
- Example
-
- The following sample generates XS0201 because 2 * 3 is an expression, not a statement. To make the code compile, try assigning the value of the expression to a variable.
-
-
- // XS0201.prg
-
- Example
-
- The following sample generates XS0201 because checked by itself is not a statement, even though it is parameterized by an increment operation.
-
-
- // XS0201_b.prg // compile with: /target:library
-
-
diff --git a/docs/Help_Spanish/Topics/XS0202.XML b/docs/Help_Spanish/Topics/XS0202.XML
deleted file mode 100644
index f1928eff75..0000000000
--- a/docs/Help_Spanish/Topics/XS0202.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0202
-
- XS0202
-
-
-
- Error XS0202
-
- foreach requires that the return type '{0}' of '{1}' must have a suitable public MoveNext method and public Current property
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0204.XML b/docs/Help_Spanish/Topics/XS0204.XML
deleted file mode 100644
index dea59858ed..0000000000
--- a/docs/Help_Spanish/Topics/XS0204.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0204
-
- XS0204
-
-
-
- Error XS0204
-
- Only 65534 locals, including those generated by the compiler, are allowed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0205.XML b/docs/Help_Spanish/Topics/XS0205.XML
deleted file mode 100644
index be77b6bf91..0000000000
--- a/docs/Help_Spanish/Topics/XS0205.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0205
-
- XS0205
-
-
-
- Error XS0205
-
- Cannot call an abstract base member: '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0206.XML b/docs/Help_Spanish/Topics/XS0206.XML
deleted file mode 100644
index 1abb4476f1..0000000000
--- a/docs/Help_Spanish/Topics/XS0206.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0206
-
- XS0206
-
-
-
- Error XS0206
-
- A property or indexer may not be passed as an out or ref parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0208.XML b/docs/Help_Spanish/Topics/XS0208.XML
deleted file mode 100644
index a5d4e454f6..0000000000
--- a/docs/Help_Spanish/Topics/XS0208.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0208
-
- XS0208
-
-
-
- Error XS0208
-
- Cannot take the address of, get the size of, or declare a pointer to a managed type ('{0}')
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0209.XML b/docs/Help_Spanish/Topics/XS0209.XML
deleted file mode 100644
index e9248d8548..0000000000
--- a/docs/Help_Spanish/Topics/XS0209.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0209
-
- XS0209
-
-
-
- Error XS0209
-
- The type of a local declared in a fixed statement must be a pointer type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0210.XML b/docs/Help_Spanish/Topics/XS0210.XML
deleted file mode 100644
index 3d7912a295..0000000000
--- a/docs/Help_Spanish/Topics/XS0210.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0210
-
- XS0210
-
-
-
- Error XS0210
-
- You must provide an initializer in a fixed or using statement declaration
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0211.XML b/docs/Help_Spanish/Topics/XS0211.XML
deleted file mode 100644
index 267ed21c4a..0000000000
--- a/docs/Help_Spanish/Topics/XS0211.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0211
-
-XS0211
-
-
-
- Error XS0211
-
- Cannot take the address of the given expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0212.XML b/docs/Help_Spanish/Topics/XS0212.XML
deleted file mode 100644
index 335380fd53..0000000000
--- a/docs/Help_Spanish/Topics/XS0212.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0212
-
-XS0212
-
-
-
- Error XS0212
-
- You can only take the address of an unfixed expression inside of a fixed statement initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0213.XML b/docs/Help_Spanish/Topics/XS0213.XML
deleted file mode 100644
index 6f49cef9b3..0000000000
--- a/docs/Help_Spanish/Topics/XS0213.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0213
-
-XS0213
-
-
-
- Error XS0213
-
- You cannot use the fixed statement to take the address of an already fixed expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0214.XML b/docs/Help_Spanish/Topics/XS0214.XML
deleted file mode 100644
index 276b2b2dbd..0000000000
--- a/docs/Help_Spanish/Topics/XS0214.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0214
-
-XS0214
-
-
-
- Error XS0214
-
- Pointers and fixed size buffers may only be used in an unsafe context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0215.XML b/docs/Help_Spanish/Topics/XS0215.XML
deleted file mode 100644
index d77fad9d55..0000000000
--- a/docs/Help_Spanish/Topics/XS0215.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0215
-
-XS0215
-
-
-
- Error XS0215
-
- The return type of operator True or False must be bool
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0216.XML b/docs/Help_Spanish/Topics/XS0216.XML
deleted file mode 100644
index 5289105e79..0000000000
--- a/docs/Help_Spanish/Topics/XS0216.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0216
-
- XS0216
-
-
-
- Warning XS0216
-
- The operator '{0}' requires a matching operator '{1}' to also be defined
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0217.XML b/docs/Help_Spanish/Topics/XS0217.XML
deleted file mode 100644
index 93c0837203..0000000000
--- a/docs/Help_Spanish/Topics/XS0217.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0217
-
-XS0217
-
-
-
- Error XS0217
-
- In order to be applicable as a short circuit operator a user-defined logical operator ('{0}') must have the same return type and parameter types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0218.XML b/docs/Help_Spanish/Topics/XS0218.XML
deleted file mode 100644
index 0ee8a083bf..0000000000
--- a/docs/Help_Spanish/Topics/XS0218.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0218
-
-XS0218
-
-
-
- Error XS0218
-
- In order for '{0}' to be applicable as a short circuit operator, its declaring type '{1}' must define operator true and operator false
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0219.XML b/docs/Help_Spanish/Topics/XS0219.XML
deleted file mode 100644
index d78a44a726..0000000000
--- a/docs/Help_Spanish/Topics/XS0219.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0219
-
- XS0219
-
-
-
- Warning XS0219
-
- The variable '{0}' is assigned but its value is never used
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0220.XML b/docs/Help_Spanish/Topics/XS0220.XML
deleted file mode 100644
index a037001527..0000000000
--- a/docs/Help_Spanish/Topics/XS0220.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0220
-
-XS0220
-
-
-
- Error XS0220
-
- The operation overflows at compile time in checked mode
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0221.XML b/docs/Help_Spanish/Topics/XS0221.XML
deleted file mode 100644
index 1a2c002125..0000000000
--- a/docs/Help_Spanish/Topics/XS0221.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0221
-
-XS0221
-
-
-
- Error XS0221
-
- Constant value '{0}' cannot be converted to a '{1}' (use 'unchecked' syntax to override)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0224.XML b/docs/Help_Spanish/Topics/XS0224.XML
deleted file mode 100644
index 696322417e..0000000000
--- a/docs/Help_Spanish/Topics/XS0224.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0224
-
-XS0224
-
-
-
- Error XS0224
-
- A method with vararg cannot be generic, be in a generic type, or have a params parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0225.XML b/docs/Help_Spanish/Topics/XS0225.XML
deleted file mode 100644
index 2b9cf6ec0e..0000000000
--- a/docs/Help_Spanish/Topics/XS0225.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0225
-
-XS0225
-
-
-
- Error XS0225
-
- The params parameter must be a single dimensional array
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0226.XML b/docs/Help_Spanish/Topics/XS0226.XML
deleted file mode 100644
index e46d1fd975..0000000000
--- a/docs/Help_Spanish/Topics/XS0226.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0226
-
-XS0226
-
-
-
- Error XS0226
-
- An __arglist expression may only appear inside of a call or new expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0227.XML b/docs/Help_Spanish/Topics/XS0227.XML
deleted file mode 100644
index ff12ae7136..0000000000
--- a/docs/Help_Spanish/Topics/XS0227.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0227
-
-XS0227
-
-
-
- Error XS0227
-
- Unsafe code may only appear if compiling with /unsafe
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0229.xml b/docs/Help_Spanish/Topics/XS0229.xml
deleted file mode 100644
index f428026551..0000000000
--- a/docs/Help_Spanish/Topics/XS0229.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0229
-
- XS0229
-
-
-
- Error XS0229
-
- Ambiguity between 'member1' and 'member2'
-
- Members of different interfaces have the same name. If you want to keep the same names, you must qualify the names. For more information, see Interfaces.
- Note
- In some cases, this ambiguity can be resolved by providing an explicit prefix to the identifier via a using alias.
- Example
-
- The following example generates XS0229:
-
- // XS0229.prg
FUNCTION Start AS VOID RETURN FUNCTION Test(x AS IListCounter) AS VOID x:Count := 1 // Try one of the following lines instead: // ((IList)x):Count := 1 // or // ((Icounter)x):Count := 1 RETURN
INTERFACE IList PROPERTY Count AS LONG GET SET METHOD Counter AS VOID END INTERFACE
INTERFACE ICounter PROPERTY Count AS REAL8 GET SET END INTERFACE
INTERFACE IListCounter INHERIT Ilist, ICounter END INTERFACE
-
-
diff --git a/docs/Help_Spanish/Topics/XS0230.XML b/docs/Help_Spanish/Topics/XS0230.XML
deleted file mode 100644
index b239277cef..0000000000
--- a/docs/Help_Spanish/Topics/XS0230.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0230
-
-XS0230
-
-
-
- Error XS0230
-
- Type and identifier are both required in a foreach statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0231.XML b/docs/Help_Spanish/Topics/XS0231.XML
deleted file mode 100644
index 504f7491b7..0000000000
--- a/docs/Help_Spanish/Topics/XS0231.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0231
-
-XS0231
-
-
-
- Error XS0231
-
- A params parameter must be the last parameter in a formal parameter list
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0233.xml b/docs/Help_Spanish/Topics/XS0233.xml
deleted file mode 100644
index af8a3ee305..0000000000
--- a/docs/Help_Spanish/Topics/XS0233.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0233
-
- XS0233
-
-
-
- Warning XS0233
-
- 'identifier' does not have a predefined size, therefore sizeof can only be used in an unsafe context (consider using System.Runtime.InteropServices.Marshal.SizeOf)
-
- The sizeof operator can only be used for types that are compile-time constants. If you are getting this error, make sure that the size of the identifier can be determined at compile time. If it cannot, then use SizeOf instead of sizeof.
- Example
-
- The following example generates XS0233:
-
-
- // XS0233.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0234.xml b/docs/Help_Spanish/Topics/XS0234.xml
deleted file mode 100644
index b43e8697a9..0000000000
--- a/docs/Help_Spanish/Topics/XS0234.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XS0234
-
- -reference
- XS0234
-
-
-
- Error XS0234
-
- The type or namespace name 'name' does not exist in the namespace 'namespace' (are you missing an assembly reference?)
-
- A type was expected. Possible causes for this error include the following:
-
-
-
An assembly that contains the definition of a type was not referenced in the compilation; use /reference (Import Metadata) to specify the assembly
-
You passed a variable name to the typeof operator.
-
You tried to reference an assembly that is not part of your target .NET Framework profile. For more information, see Troubleshooting .NET Framework Targeting Errors.
-
-
- If you see this error after moving code from one development machine to another, make sure that the project on the new machine has the correct references, and that the versions of the assemblies are the same as on the old machine. You can also use the Object Browser to inspect an assembly and verify whether it contains the types that you expect it to contain.
-
- The following sample generates XS0234:
-
-
- // XS0234.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0236.XML b/docs/Help_Spanish/Topics/XS0236.XML
deleted file mode 100644
index f0cb20c0d4..0000000000
--- a/docs/Help_Spanish/Topics/XS0236.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0236
-
-XS0236
-
-
-
- Error XS0236
-
- A field initializer cannot reference the non-static field, method, or property '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0238.XML b/docs/Help_Spanish/Topics/XS0238.XML
deleted file mode 100644
index c5a0b2ae3e..0000000000
--- a/docs/Help_Spanish/Topics/XS0238.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0238
-
- XS0238
-
-
-
- Warning XS0238
-
- '{0}' cannot be sealed because it is not an override
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0239.XML b/docs/Help_Spanish/Topics/XS0239.XML
deleted file mode 100644
index 89511f3e1c..0000000000
--- a/docs/Help_Spanish/Topics/XS0239.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0239
-
-XS0239
-
-
-
- Error XS0239
-
- '{0}': cannot override inherited member '{1}' because it is sealed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0242.XML b/docs/Help_Spanish/Topics/XS0242.XML
deleted file mode 100644
index d90de7ff1f..0000000000
--- a/docs/Help_Spanish/Topics/XS0242.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0242
-
-XS0242
-
-
-
- Error XS0242
-
- The operation in question is undefined on void pointers
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0243.XML b/docs/Help_Spanish/Topics/XS0243.XML
deleted file mode 100644
index fc19fd3b72..0000000000
--- a/docs/Help_Spanish/Topics/XS0243.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0243
-
-XS0243
-
-
-
- Error XS0243
-
- The Conditional attribute is not valid on '{0}' because it is an override method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0244.XML b/docs/Help_Spanish/Topics/XS0244.XML
deleted file mode 100644
index ccb5a32a34..0000000000
--- a/docs/Help_Spanish/Topics/XS0244.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0244
-
-XS0244
-
-
-
- Error XS0244
-
- Neither 'is' nor 'as' is valid on pointer types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0245.XML b/docs/Help_Spanish/Topics/XS0245.XML
deleted file mode 100644
index 5a94081b3a..0000000000
--- a/docs/Help_Spanish/Topics/XS0245.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0245
-
-XS0245
-
-
-
- Error XS0245
-
- Destructors and object.Finalize cannot be called directly. Consider calling IDisposable.Dispose if available.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0246.xml b/docs/Help_Spanish/Topics/XS0246.xml
deleted file mode 100644
index b4049ba1d8..0000000000
--- a/docs/Help_Spanish/Topics/XS0246.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-
- XS0246
-
- XS0246
-
-
-
- Error XS0246
-
- The type or namespace name 'type/namespace' could not be found (are you missing a using directive or an assembly reference?)
-
- A type or namespace that is used in the program was not found. You might have forgotten to reference (/reference) the assembly that contains the type, or you might not have added the required using directive. Or, there might be an issue with the assembly you are trying to reference.
-
- The following situations cause compiler error XS0246.
-
-
-
Did you misspell the name of the type or namespace? Without the correct name, the compiler cannot find the definition for the type or namespace. This often occurs because the casing used in the name of the type is not correct. For example, Dataset ds; generates XS0246 because the s in Dataset must be capitalized.
-
If the error is for a namespace name, did you add a reference (/reference) to the assembly that contains the namespace? For example, your code might contain the directive using Accessibility. However, if your project does not reference the assembly Accessibility.dll, error XS0246 is reported. For more information, see Managing references in a project
-
If the error is for a type name, did you include the proper using directive, or, alternatively, fully qualify the name of the type? Consider the following declaration: DataSet ds. To use the DataSet type, you need two things. First, you need a reference to the assembly that contains the definition for the DataSet type. Second, you need a using directive for the namespace where DataSet is located. For example, because DataSet is located in the System.Data namespace, you need the following directive at the beginning of your code: using System.Data.
-
The using directive is not required. However, if you omit the directive, you must fully qualify the DataSet type when referring to it. Full qualification means that you specify both the namespace and the type each time you refer to the type in your code. If you omit the using directive in the previous example, you must write System.Data.DataSet ds to declare ds instead of DataSet ds.
-
Did you use a variable or some other language element where a type was expected? For example, in an is statement, if you use a Type object instead of an actual type, you get error XS0246.
-
Did you use a using alias directive without fully qualifying the type name? A using alias directive does not use the using directives in the source code file to resolve types. The following example generates XS0246 because the type List<int> is not fully qualified. The using directive for System.Collections.Generic does not prevent the error.
-
-
-
-
-
-
- If you get this error in code that was previously working, first look for missing or unresolved references in Solution Explorer. Do you need to re-install a NuGetpackage? For information about how the build system searches for references, see Resolving file references in team build. If all references seem to be correct, look in your source control history to see what has changed in your .xsproj file and/or your local source file.
-
- If you haven’t successfully accessed the reference yet, use the Object Browser to inspect the assembly that is supposed to contain this namespace and verify that the namespace is present. If you verify with Object Browser that the assembly contains the namespace, try removing the “using” directive for the namespace and see what else breaks. The root problem may be with some other type in another assembly.
-
- The following example generates XS0246 because a necessary using directive is missing.
-
-
- // XS0246.prg
-
- The following example causes XS0246 because an object of type Type was used where an actual type was expected.
-
-
- // XS0246b.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0247.XML b/docs/Help_Spanish/Topics/XS0247.XML
deleted file mode 100644
index ed948aff0d..0000000000
--- a/docs/Help_Spanish/Topics/XS0247.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0247
-
-XS0247
-
-
-
- Error XS0247
-
- Cannot use a negative size with stackalloc
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0248.XML b/docs/Help_Spanish/Topics/XS0248.XML
deleted file mode 100644
index 891da1d995..0000000000
--- a/docs/Help_Spanish/Topics/XS0248.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0248
-
-XS0248
-
-
-
- Error XS0248
-
- Cannot create an array with a negative size
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0249.XML b/docs/Help_Spanish/Topics/XS0249.XML
deleted file mode 100644
index df83f54c05..0000000000
--- a/docs/Help_Spanish/Topics/XS0249.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0249
-
-XS0249
-
-
-
- Error XS0249
-
- Do not override object.Finalize. Instead, provide a destructor.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0250.XML b/docs/Help_Spanish/Topics/XS0250.XML
deleted file mode 100644
index 6ccbc6cce6..0000000000
--- a/docs/Help_Spanish/Topics/XS0250.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0250
-
-XS0250
-
-
-
- Error XS0250
-
- Do not directly call your base class Finalize method. It is called automatically from your destructor.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0251.XML b/docs/Help_Spanish/Topics/XS0251.XML
deleted file mode 100644
index 3cc1645de5..0000000000
--- a/docs/Help_Spanish/Topics/XS0251.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0251
-
- XS0251
-
-
-
- Warning XS0251
-
- Indexing an array with a negative index (array indices always start at zero)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0252.XML b/docs/Help_Spanish/Topics/XS0252.XML
deleted file mode 100644
index a0432aaa27..0000000000
--- a/docs/Help_Spanish/Topics/XS0252.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0252
-
- XS0252
-
-
-
- Warning XS0252
-
- Possible unintended reference comparison; to get a value comparison, cast the left hand side to type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0253.XML b/docs/Help_Spanish/Topics/XS0253.XML
deleted file mode 100644
index 01710ab046..0000000000
--- a/docs/Help_Spanish/Topics/XS0253.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0253
-
- XS0253
-
-
-
- Warning XS0253
-
- Possible unintended reference comparison; to get a value comparison, cast the right hand side to type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0254.XML b/docs/Help_Spanish/Topics/XS0254.XML
deleted file mode 100644
index 6bf07988fc..0000000000
--- a/docs/Help_Spanish/Topics/XS0254.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0254
-
-XS0254
-
-
-
- Error XS0254
-
- The right hand side of a fixed statement assignment may not be a cast expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0255.XML b/docs/Help_Spanish/Topics/XS0255.XML
deleted file mode 100644
index 6a95652090..0000000000
--- a/docs/Help_Spanish/Topics/XS0255.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0255
-
-XS0255
-
-
-
- Error XS0255
-
- stackalloc may not be used in a catch or finally block
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0257.XML b/docs/Help_Spanish/Topics/XS0257.XML
deleted file mode 100644
index 864b6c531c..0000000000
--- a/docs/Help_Spanish/Topics/XS0257.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0257
-
-XS0257
-
-
-
- Error XS0257
-
- An ellipsis parameter (...) must be the last parameter in a formal parameter list
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0260.xml b/docs/Help_Spanish/Topics/XS0260.xml
deleted file mode 100644
index ab24d77c20..0000000000
--- a/docs/Help_Spanish/Topics/XS0260.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0260
-
- XS0260
-
-
-
- Error XS0260
-
- Missing partial modifier on declaration of type 'type'; another partial declaration of this type exists
-
- This error indicates that you have declared multiple classes that have the same name. In addition, at least one but not all of the declarations contains the partial modifier. If you want to define a class in several parts, you must declare each part by using the keyword partial.
-
- This error also occurs if you declare a class and accidentally give it the same name as a partial class that's declared elsewhere in the same namespace.
-
- The following sample generates XS0260:
-
-
- // XS0260.prg // You must mark both parts of the definition of class C
-
-
diff --git a/docs/Help_Spanish/Topics/XS0261.XML b/docs/Help_Spanish/Topics/XS0261.XML
deleted file mode 100644
index 59ca6d3f69..0000000000
--- a/docs/Help_Spanish/Topics/XS0261.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0261
-
-XS0261
-
-
-
- Error XS0261
-
- Partial declarations of '{0}' must be all classes, all structs, or all interfaces
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0262.XML b/docs/Help_Spanish/Topics/XS0262.XML
deleted file mode 100644
index 4d996c5953..0000000000
--- a/docs/Help_Spanish/Topics/XS0262.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0262
-
-XS0262
-
-
-
- Error XS0262
-
- Partial declarations of '{0}' have conflicting accessibility modifiers
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0263.XML b/docs/Help_Spanish/Topics/XS0263.XML
deleted file mode 100644
index a67eb20415..0000000000
--- a/docs/Help_Spanish/Topics/XS0263.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0263
-
-XS0263
-
-
-
- Error XS0263
-
- Partial declarations of '{0}' must not specify different base classes
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0264.XML b/docs/Help_Spanish/Topics/XS0264.XML
deleted file mode 100644
index 3270c4218c..0000000000
--- a/docs/Help_Spanish/Topics/XS0264.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0264
-
-XS0264
-
-
-
- Error XS0264
-
- Partial declarations of '{0}' must have the same type parameter names in the same order
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0265.XML b/docs/Help_Spanish/Topics/XS0265.XML
deleted file mode 100644
index c80845d781..0000000000
--- a/docs/Help_Spanish/Topics/XS0265.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0265
-
-XS0265
-
-
-
- Error XS0265
-
- Partial declarations of '{0}' have inconsistent constraints for type parameter '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0266.xml b/docs/Help_Spanish/Topics/XS0266.xml
deleted file mode 100644
index 294bacf818..0000000000
--- a/docs/Help_Spanish/Topics/XS0266.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0266
-
- XS0266
-
-
-
- Error XS0266
-
- Cannot implicitly convert type 'type1' to 'type2'. An explicit conversion exists (are you missing a cast?)
-
- This error occurs when your code tries to convert between two types that cannot be implicitly converted, but where an explicit conversion is available. For more information, see Casting and Type Conversions.
-
- The following code shows an examples that generates XS0266 and how to avoid the error
-
-
- FUNCTION Start() LOCAL r8 := 1.234 asREAL8 LOCAL i ASINT i := R8 // this will produce error XS0266 i := (INT) r8 // this prevents the error because there is an explicit cast
- You can suppress this error for numeric conversions with the compiler option /vo11 (for assignments from larger types to smaller types or for assignments from fractional types to integral types). For assignments between signed and unsigned numbers the error can be suppressed with /vo4
-
-
diff --git a/docs/Help_Spanish/Topics/XS0267.XML b/docs/Help_Spanish/Topics/XS0267.XML
deleted file mode 100644
index 2aa8dd3e1a..0000000000
--- a/docs/Help_Spanish/Topics/XS0267.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0267
-
-XS0267
-
-
-
- Error XS0267
-
- The 'partial' modifier can only appear immediately before 'class', 'struct', 'interface', or 'void'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0268.XML b/docs/Help_Spanish/Topics/XS0268.XML
deleted file mode 100644
index e4e84c7f54..0000000000
--- a/docs/Help_Spanish/Topics/XS0268.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0268
-
-XS0268
-
-
-
- Error XS0268
-
- Imported type '{0}' is invalid. It contains a circular base class dependency.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0269.xml b/docs/Help_Spanish/Topics/XS0269.xml
deleted file mode 100644
index 632e0240bb..0000000000
--- a/docs/Help_Spanish/Topics/XS0269.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- XS0269
-
- XS0269
-
-
-
- Warning XS0269
-
- Use of unassigned out parameter 'parameter'
-
- The compiler could not verify that the out parameter was assigned a value before it was used; its value may be undefined when assigned. Be sure to assign a value to out parameters in the called method before accessing the value. If you need to use the value of the variable passed in, use a ref parameter instead. For more information, see Passing Parameters.
- Example
-
- The following sample generates XS0269:
-
-
- // XS0269.prg
- Example
-
- This could also occur if the initialization of a variable occurs in a try block, which the compiler is unable to verify will execute successfully:
-
-
- // XS0269b.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0270.xml b/docs/Help_Spanish/Topics/XS0270.xml
deleted file mode 100644
index e64718ef3f..0000000000
--- a/docs/Help_Spanish/Topics/XS0270.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0270
-
- XS0270
-
-
-
- Error XS0270
-
- Array size cannot be specified in a variable declaration (try initializing with a 'new' expression)
-
- This error occurs when a size is specified as part of an array declaration. To resolve, use the new Operator expression.
-
- The following example generates XS0270:
-
-
- // XS0270.prg // compile with: /t:module
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0271.XML b/docs/Help_Spanish/Topics/XS0271.XML
deleted file mode 100644
index d37e0420cf..0000000000
--- a/docs/Help_Spanish/Topics/XS0271.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0271
-
-XS0271
-
-
-
- Error XS0271
-
- The property or indexer '{0}' cannot be used in this context because the get accessor is inaccessible
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0272.XML b/docs/Help_Spanish/Topics/XS0272.XML
deleted file mode 100644
index a123ac3b0c..0000000000
--- a/docs/Help_Spanish/Topics/XS0272.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0272
-
-XS0272
-
-
-
- Error XS0272
-
- The property or indexer '{0}' cannot be used in this context because the set accessor is inaccessible
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0273.XML b/docs/Help_Spanish/Topics/XS0273.XML
deleted file mode 100644
index c70787ac34..0000000000
--- a/docs/Help_Spanish/Topics/XS0273.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0273
-
-XS0273
-
-
-
- Error XS0273
-
- The accessibility modifier of the '{0}' accessor must be more restrictive than the property or indexer '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0274.XML b/docs/Help_Spanish/Topics/XS0274.XML
deleted file mode 100644
index 197335976a..0000000000
--- a/docs/Help_Spanish/Topics/XS0274.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0274
-
-XS0274
-
-
-
- Error XS0274
-
- Cannot specify accessibility modifiers for both accessors of the property or indexer '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0275.XML b/docs/Help_Spanish/Topics/XS0275.XML
deleted file mode 100644
index c5a2c9bec2..0000000000
--- a/docs/Help_Spanish/Topics/XS0275.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0275
-
-XS0275
-
-
-
- Error XS0275
-
- '{0}': accessibility modifiers may not be used on accessors in an interface
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0276.XML b/docs/Help_Spanish/Topics/XS0276.XML
deleted file mode 100644
index 0ad827bec0..0000000000
--- a/docs/Help_Spanish/Topics/XS0276.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0276
-
-XS0276
-
-
-
- Error XS0276
-
- '{0}': accessibility modifiers on accessors may only be used if the property or indexer has both a get and a set accessor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0277.XML b/docs/Help_Spanish/Topics/XS0277.XML
deleted file mode 100644
index 00aa188517..0000000000
--- a/docs/Help_Spanish/Topics/XS0277.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0277
-
-XS0277
-
-
-
- Error XS0277
-
- '{0}' does not implement interface member '{1}'. '{2}' is not public.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0278.XML b/docs/Help_Spanish/Topics/XS0278.XML
deleted file mode 100644
index bae6521ee9..0000000000
--- a/docs/Help_Spanish/Topics/XS0278.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0278
-
- XS0278
-
-
-
- Warning XS0278
-
- '{0}' does not implement the '{1}' pattern. '{2}' is ambiguous with '{3}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0279.XML b/docs/Help_Spanish/Topics/XS0279.XML
deleted file mode 100644
index f10a64c1f9..0000000000
--- a/docs/Help_Spanish/Topics/XS0279.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0279
-
- XS0279
-
-
-
- Warning XS0279
-
- '{0}' does not implement the '{1}' pattern. '{2}' is either static or not public.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0280.XML b/docs/Help_Spanish/Topics/XS0280.XML
deleted file mode 100644
index 6b2d6cda16..0000000000
--- a/docs/Help_Spanish/Topics/XS0280.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0280
-
- XS0280
-
-
-
- Warning XS0280
-
- '{0}' does not implement the '{1}' pattern. '{2}' has the wrong signature.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0281.XML b/docs/Help_Spanish/Topics/XS0281.XML
deleted file mode 100644
index fe169700d7..0000000000
--- a/docs/Help_Spanish/Topics/XS0281.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0281
-
-XS0281
-
-
-
- Error XS0281
-
- Friend access was granted by '{0}', but the public key of the output assembly does not match that specified by the attribute in the granting assembly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0282.XML b/docs/Help_Spanish/Topics/XS0282.XML
deleted file mode 100644
index 5f1a1e1eed..0000000000
--- a/docs/Help_Spanish/Topics/XS0282.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0282
-
- XS0282
-
-
-
- Warning XS0282
-
- There is no defined ordering between fields in multiple declarations of partial struct '{0}'. To specify an ordering, all instance fields must be in the same declaration.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0283.XML b/docs/Help_Spanish/Topics/XS0283.XML
deleted file mode 100644
index 11be735028..0000000000
--- a/docs/Help_Spanish/Topics/XS0283.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0283
-
-XS0283
-
-
-
- Error XS0283
-
- The type '{0}' cannot be declared const
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0304.xml b/docs/Help_Spanish/Topics/XS0304.xml
deleted file mode 100644
index bbe10821ee..0000000000
--- a/docs/Help_Spanish/Topics/XS0304.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
- XS0304
-
- XS0304
-
-
-
- Error XS0304
-
- Cannot create an instance of the variable type 'type' because it does not have the new() constraint
-
- When you implement a generic class, and you want to use the new keyword to create a new instance of any type that is supplied for a type parameter T, you must apply the new() constraint to T in the class declaration, as shown in the following example.
-
-
- class C<T> where T : new()
-
-
- The new() constraint enforces type safety by guaranteeing that any concrete type that is supplied for T has a default, parameterless constructor. XS0304 occurs if you attempt to use the new operator in the body of the class to create an instance of type parameter T when T does not specify the new() constraint. On the client side, if code attempts to instantiate the generic class with a type that has no default constructor, that code will generate Compiler Error XS0310.
-
- The following example generates XS0304.
-
-
- // XS0304.prg
-
- The new operator also is not allowed in methods of the class.
-
-
- // Compile with: /target:library.
-
-
- To avoid the error, declare the class by using the new() constraint, as shown in the following example.
-
-
- // Compile with: /target:library.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0305.XML b/docs/Help_Spanish/Topics/XS0305.XML
deleted file mode 100644
index 59fead40de..0000000000
--- a/docs/Help_Spanish/Topics/XS0305.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0305
-
-XS0305
-
-
-
- Error XS0305
-
- Using the generic {1} '{0}' requires {2} type arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0306.XML b/docs/Help_Spanish/Topics/XS0306.XML
deleted file mode 100644
index 0bd4e466b5..0000000000
--- a/docs/Help_Spanish/Topics/XS0306.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0306
-
-XS0306
-
-
-
- Error XS0306
-
- The type '{0}' may not be used as a type argument
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0307.XML b/docs/Help_Spanish/Topics/XS0307.XML
deleted file mode 100644
index e3d0875aee..0000000000
--- a/docs/Help_Spanish/Topics/XS0307.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0307
-
-XS0307
-
-
-
- Error XS0307
-
- The {1} '{0}' cannot be used with type arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0308.XML b/docs/Help_Spanish/Topics/XS0308.XML
deleted file mode 100644
index 1686376350..0000000000
--- a/docs/Help_Spanish/Topics/XS0308.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0308
-
-XS0308
-
-
-
- Error XS0308
-
- The non-generic {1} '{0}' cannot be used with type arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0310.xml b/docs/Help_Spanish/Topics/XS0310.xml
deleted file mode 100644
index dfb0dda806..0000000000
--- a/docs/Help_Spanish/Topics/XS0310.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- XS0310
-
- XS0310
-
-
-
- Error XS0310
-
- The type 'typename' must be a non-abstract type with a public parameterless constructor in order to use it as parameter 'parameter' in the generic type or method 'generic'
-
- The generic type or method defines a new constraint in its where clause, so any type must have a public parameterless constructor in order to be used as a type argument for that generic type or method. To avoid this error, make sure that the type has the correct constructor, or modify the constraint clause of the generic type or method.
- Example
-
- The following sample generates XS0310:
// XS0310.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0311.xml b/docs/Help_Spanish/Topics/XS0311.xml
deleted file mode 100644
index 78f61ee65c..0000000000
--- a/docs/Help_Spanish/Topics/XS0311.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- XS0311
-
- XS0311
-
-
-
- Error XS0311
-
- The type 'type1' cannot be used as type parameter 'T' in the generic type or method '<name>'. There is no implicit reference conversion from 'type1' to 'type2'.
-
- When a constraint is applied to a generic type parameter, an implicit identity or reference conversion must exist from the concrete argument to the type of the constraint.
- To correct this error
-
-
Change the argument you are using to create the class.
-
If you own the class, you can remove the constraint or else do something to enable an implicit reference or identity conversion. For example, you can make the second type inherit from the first.
-
- Example
-
-
- // XS0311.prg
-
- If this error occurs when trying to use a value-type argument, notice that an implicit numeric conversion, for example from short to int, does not satisfy a generic type parameter.
-
-
diff --git a/docs/Help_Spanish/Topics/XS0312.XML b/docs/Help_Spanish/Topics/XS0312.XML
deleted file mode 100644
index 314096d43e..0000000000
--- a/docs/Help_Spanish/Topics/XS0312.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0312
-
-XS0312
-
-
-
- Error XS0312
-
- The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not satisfy the constraint of '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0313.XML b/docs/Help_Spanish/Topics/XS0313.XML
deleted file mode 100644
index d1130da71f..0000000000
--- a/docs/Help_Spanish/Topics/XS0313.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0313
-
-XS0313
-
-
-
- Error XS0313
-
- The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not satisfy the constraint of '{1}'. Nullable types can not satisfy any interface constraints.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0314.XML b/docs/Help_Spanish/Topics/XS0314.XML
deleted file mode 100644
index 04f721e3a0..0000000000
--- a/docs/Help_Spanish/Topics/XS0314.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0314
-
-XS0314
-
-
-
- Error XS0314
-
- The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no boxing conversion or type parameter conversion from '{3}' to '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0315.XML b/docs/Help_Spanish/Topics/XS0315.XML
deleted file mode 100644
index 57ab2d1e3d..0000000000
--- a/docs/Help_Spanish/Topics/XS0315.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0315
-
-XS0315
-
-
-
- Error XS0315
-
- The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no boxing conversion from '{3}' to '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0316.XML b/docs/Help_Spanish/Topics/XS0316.XML
deleted file mode 100644
index 1479a86e0e..0000000000
--- a/docs/Help_Spanish/Topics/XS0316.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0316
-
-XS0316
-
-
-
- Error XS0316
-
- The parameter name '{0}' conflicts with an automatically-generated parameter name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0400.XML b/docs/Help_Spanish/Topics/XS0400.XML
deleted file mode 100644
index 8850bdcd86..0000000000
--- a/docs/Help_Spanish/Topics/XS0400.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0400
-
-XS0400
-
-
-
- Error XS0400
-
- The type or namespace name '{0}' could not be found in the global namespace (are you missing an assembly reference?)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0401.XML b/docs/Help_Spanish/Topics/XS0401.XML
deleted file mode 100644
index 1151e76691..0000000000
--- a/docs/Help_Spanish/Topics/XS0401.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0401
-
-XS0401
-
-
-
- Error XS0401
-
- The new() constraint must be the last constraint specified
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0402.XML b/docs/Help_Spanish/Topics/XS0402.XML
deleted file mode 100644
index 396293c12b..0000000000
--- a/docs/Help_Spanish/Topics/XS0402.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0402
-
- XS0402
-
-
-
- Warning XS0402
-
- '{0}': an entry point cannot be generic or in a generic type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0403.XML b/docs/Help_Spanish/Topics/XS0403.XML
deleted file mode 100644
index ecac4a9e99..0000000000
--- a/docs/Help_Spanish/Topics/XS0403.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0403
-
-XS0403
-
-
-
- Error XS0403
-
- Cannot convert null to type parameter '{0}' because it could be a non-nullable value type. Consider using 'default({0})' instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0404.XML b/docs/Help_Spanish/Topics/XS0404.XML
deleted file mode 100644
index 2b3028119a..0000000000
--- a/docs/Help_Spanish/Topics/XS0404.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0404
-
-XS0404
-
-
-
- Error XS0404
-
- Cannot apply attribute class '{0}' because it is generic
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0405.XML b/docs/Help_Spanish/Topics/XS0405.XML
deleted file mode 100644
index 64bf125470..0000000000
--- a/docs/Help_Spanish/Topics/XS0405.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0405
-
-XS0405
-
-
-
- Error XS0405
-
- Duplicate constraint '{0}' for type parameter '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0406.XML b/docs/Help_Spanish/Topics/XS0406.XML
deleted file mode 100644
index 71ceacb9de..0000000000
--- a/docs/Help_Spanish/Topics/XS0406.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0406
-
-XS0406
-
-
-
- Error XS0406
-
- The class type constraint '{0}' must come before any other constraints
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0407.XML b/docs/Help_Spanish/Topics/XS0407.XML
deleted file mode 100644
index a56ce44889..0000000000
--- a/docs/Help_Spanish/Topics/XS0407.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0407
-
-XS0407
-
-
-
- Error XS0407
-
- '{1} {0}' has the wrong return type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0409.XML b/docs/Help_Spanish/Topics/XS0409.XML
deleted file mode 100644
index 496db7da29..0000000000
--- a/docs/Help_Spanish/Topics/XS0409.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0409
-
-XS0409
-
-
-
- Error XS0409
-
- A constraint clause has already been specified for type parameter '{0}'. All of the constraints for a type parameter must be specified in a single where clause.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0411.XML b/docs/Help_Spanish/Topics/XS0411.XML
deleted file mode 100644
index 87478ea5d9..0000000000
--- a/docs/Help_Spanish/Topics/XS0411.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0411
-
-XS0411
-
-
-
- Error XS0411
-
- The type arguments for method '{0}' cannot be inferred from the usage. Try specifying the type arguments explicitly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0412.XML b/docs/Help_Spanish/Topics/XS0412.XML
deleted file mode 100644
index 099fa30eb4..0000000000
--- a/docs/Help_Spanish/Topics/XS0412.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0412
-
-XS0412
-
-
-
- Error XS0412
-
- '{0}': a parameter or local variable cannot have the same name as a method type parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0413.xml b/docs/Help_Spanish/Topics/XS0413.xml
deleted file mode 100644
index 0e77fca1cd..0000000000
--- a/docs/Help_Spanish/Topics/XS0413.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- XS0413
-
- XS0413
-
-
-
- Error XS0413
-
- The type parameter 'type parameter' cannot be used with the 'as' operator because it does not have a class type constraint nor a 'class' constraint
-
- This error occurs if a generic type uses the as operator, but that generic type does not have a class type constraint. The as operator is only allowed with reference types, so the type parameter must be constrained to guarantee that it is not a value type. To avoid this error, use a class type constraint or a reference type constraint.
-
- This is because the as operator could return null, which is not a possible value for a value type, and the type parameter must be treated as a value type unless it is a class type constraint or a reference type constraint.
- Example
-
- The following sample generates XS0413.
-
-
- // XS0413.prg // compile with: /target:library
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0414.XML b/docs/Help_Spanish/Topics/XS0414.XML
deleted file mode 100644
index c5745fc452..0000000000
--- a/docs/Help_Spanish/Topics/XS0414.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0414
-
- XS0414
-
-
-
- Warning XS0414
-
- The field '{0}' is assigned but its value is never used
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0415.XML b/docs/Help_Spanish/Topics/XS0415.XML
deleted file mode 100644
index 07552e487b..0000000000
--- a/docs/Help_Spanish/Topics/XS0415.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0415
-
-XS0415
-
-
-
- Error XS0415
-
- The '{0}' attribute is valid only on an indexer that is not an explicit interface member declaration
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0416.XML b/docs/Help_Spanish/Topics/XS0416.XML
deleted file mode 100644
index 89c31d5ac5..0000000000
--- a/docs/Help_Spanish/Topics/XS0416.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0416
-
-XS0416
-
-
-
- Error XS0416
-
- '{0}': an attribute argument cannot use type parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0417.xml b/docs/Help_Spanish/Topics/XS0417.xml
deleted file mode 100644
index c56ab2b16b..0000000000
--- a/docs/Help_Spanish/Topics/XS0417.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS0417
-
- XS0417
-
-
-
- Error XS0417
-
- 'identifier': cannot provide arguments when creating an instance of a variable type
-
- This error occurs if a call to the new operator on a type parameter has arguments. The only constructor that can be called by using the new operator on an unknown parameter type is a constructor that has no arguments. If you need to call another constructor, consider using a class type constraint or interface constraint.
- Example
-
- The following example generates XS0417:
-
-
- // XS0417
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0418.XML b/docs/Help_Spanish/Topics/XS0418.XML
deleted file mode 100644
index 45764564ea..0000000000
--- a/docs/Help_Spanish/Topics/XS0418.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0418
-
-XS0418
-
-
-
- Error XS0418
-
- '{0}': an abstract class cannot be sealed or static
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0419.XML b/docs/Help_Spanish/Topics/XS0419.XML
deleted file mode 100644
index 23e9e1b45f..0000000000
--- a/docs/Help_Spanish/Topics/XS0419.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0419
-
- XS0419
-
-
-
- Warning XS0419
-
- Ambiguous reference in cref attribute: '{0}'. Assuming '{1}', but could have also matched other overloads including '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0420.xml b/docs/Help_Spanish/Topics/XS0420.xml
deleted file mode 100644
index 23c7ad006a..0000000000
--- a/docs/Help_Spanish/Topics/XS0420.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0420
-
- XS0420
-
-
-
- Error XS0420
-
- 'identifier': a reference to a volatile field will not be treated as volatile
-
- A volatile field should not normally be passed using a ref or out parameter, since it will not be treated as volatile within the scope of the function. There are exceptions to this, such as when calling an interlocked API. As with any warning, you may use the #pragma warning to disable this warning in those rare cases where you are intentionally using a volatile field as a reference parameter.
-
- The following sample generates XS0420:
-
-
- // XS0420.prg // compile with: /W:1
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0423.XML b/docs/Help_Spanish/Topics/XS0423.XML
deleted file mode 100644
index 901a32182c..0000000000
--- a/docs/Help_Spanish/Topics/XS0423.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0423
-
-XS0423
-
-
-
- Error XS0423
-
- Since '{1}' has the ComImport attribute, '{0}' must be extern or abstract
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0424.XML b/docs/Help_Spanish/Topics/XS0424.XML
deleted file mode 100644
index cd5eb14196..0000000000
--- a/docs/Help_Spanish/Topics/XS0424.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0424
-
-XS0424
-
-
-
- Error XS0424
-
- '{0}': a class with the ComImport attribute cannot specify a base class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0425.XML b/docs/Help_Spanish/Topics/XS0425.XML
deleted file mode 100644
index 2f466a3012..0000000000
--- a/docs/Help_Spanish/Topics/XS0425.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0425
-
-XS0425
-
-
-
- Error XS0425
-
- The constraints for type parameter '{0}' of method '{1}' must match the constraints for type parameter '{2}' of interface method '{3}'. Consider using an explicit interface implementation instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0426.XML b/docs/Help_Spanish/Topics/XS0426.XML
deleted file mode 100644
index e2d1e306a4..0000000000
--- a/docs/Help_Spanish/Topics/XS0426.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0426
-
-XS0426
-
-
-
- Error XS0426
-
- The type name '{0}' does not exist in the type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0428.XML b/docs/Help_Spanish/Topics/XS0428.XML
deleted file mode 100644
index 7bb53c8e0b..0000000000
--- a/docs/Help_Spanish/Topics/XS0428.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0428
-
-XS0428
-
-
-
- Error XS0428
-
- '{0}' is a method and cannot be converted to '{1}'. Did you forget the parenthesis?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0430.XML b/docs/Help_Spanish/Topics/XS0430.XML
deleted file mode 100644
index b6d7d23541..0000000000
--- a/docs/Help_Spanish/Topics/XS0430.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0430
-
-XS0430
-
-
-
- Error XS0430
-
- The extern alias '{0}' was not specified in a /reference option
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0431.XML b/docs/Help_Spanish/Topics/XS0431.XML
deleted file mode 100644
index 36e6edf517..0000000000
--- a/docs/Help_Spanish/Topics/XS0431.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0431
-
-XS0431
-
-
-
- Error XS0431
-
- Cannot use alias '{0}' with '::' since the alias references a type. Use '.' instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0432.XML b/docs/Help_Spanish/Topics/XS0432.XML
deleted file mode 100644
index 934df7e605..0000000000
--- a/docs/Help_Spanish/Topics/XS0432.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0432
-
-XS0432
-
-
-
- Error XS0432
-
- Alias '{0}' not found
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0433.xml b/docs/Help_Spanish/Topics/XS0433.xml
deleted file mode 100644
index 37e1020042..0000000000
--- a/docs/Help_Spanish/Topics/XS0433.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
- XS0433
-
- XS0433
-
-
-
- Error XS0433
-
- The type TypeName1 exists in both TypeName2 and TypeName3
-
- Two different assemblies referenced in your application contain the same namespace and type, which produces ambiguity.
-
- To resolve this error, use the alias feature of the /reference (X# Compiler Options) compiler option or do not reference one of your assemblies.
- Example
-
- This code creates the DLL with the first copy of the ambiguous type.
-
-
- // XS0433_1.prg // compile with: /target:library
-
- Example
-
- This code creates the DLL with the second copy of the ambiguous type.
-
-
- // XS0433_2.prg // compile with: /target:library
-
- Example
-
- The following example generates XS0433.
-
-
- // XS0433_3.prg // compile with: /reference:XS0433_1.dll /reference:XS0433_2.dll
-
- Example
-
- The following example shows how you can use the alias feature of the /reference compiler option to resolve this XS0433 error.
-
-
- // XS0433_4.prg // compile with: /reference:XS0433_1.dll /reference:TypeBindConflicts=XS0433_2.dll
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0434.XML b/docs/Help_Spanish/Topics/XS0434.XML
deleted file mode 100644
index ef039b7732..0000000000
--- a/docs/Help_Spanish/Topics/XS0434.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0434
-
-XS0434
-
-
-
- Error XS0434
-
- The namespace '{1}' in '{0}' conflicts with the type '{3}' in '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0435.XML b/docs/Help_Spanish/Topics/XS0435.XML
deleted file mode 100644
index 5da3335607..0000000000
--- a/docs/Help_Spanish/Topics/XS0435.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0435
-
- XS0435
-
-
-
- Warning XS0435
-
- The namespace '{1}' in '{0}' conflicts with the imported type '{3}' in '{2}'. Using the namespace defined in '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0436.XML b/docs/Help_Spanish/Topics/XS0436.XML
deleted file mode 100644
index fb23be2ded..0000000000
--- a/docs/Help_Spanish/Topics/XS0436.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0436
-
- XS0436
-
-
-
- Warning XS0436
-
- The type '{1}' in '{0}' conflicts with the imported type '{3}' in '{2}'. Using the type defined in '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0437.XML b/docs/Help_Spanish/Topics/XS0437.XML
deleted file mode 100644
index 4875a7ccb6..0000000000
--- a/docs/Help_Spanish/Topics/XS0437.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0437
-
- XS0437
-
-
-
- Warning XS0437
-
- The type '{1}' in '{0}' conflicts with the imported namespace '{3}' in '{2}'. Using the type defined in '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0438.XML b/docs/Help_Spanish/Topics/XS0438.XML
deleted file mode 100644
index f18116daa9..0000000000
--- a/docs/Help_Spanish/Topics/XS0438.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0438
-
-XS0438
-
-
-
- Error XS0438
-
- The type '{1}' in '{0}' conflicts with the namespace '{3}' in '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0439.XML b/docs/Help_Spanish/Topics/XS0439.XML
deleted file mode 100644
index 9b02fefbd2..0000000000
--- a/docs/Help_Spanish/Topics/XS0439.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0439
-
-XS0439
-
-
-
- Error XS0439
-
- An extern alias declaration must precede all other elements defined in the namespace
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0440.XML b/docs/Help_Spanish/Topics/XS0440.XML
deleted file mode 100644
index 19ef966f7a..0000000000
--- a/docs/Help_Spanish/Topics/XS0440.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0440
-
- XS0440
-
-
-
- Warning XS0440
-
- Defining an alias named 'global' is ill-advised since 'global::' always references the global namespace and not an alias
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0441.XML b/docs/Help_Spanish/Topics/XS0441.XML
deleted file mode 100644
index 82c3efe865..0000000000
--- a/docs/Help_Spanish/Topics/XS0441.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0441
-
-XS0441
-
-
-
- Error XS0441
-
- '{0}': a class cannot be both static and sealed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0442.XML b/docs/Help_Spanish/Topics/XS0442.XML
deleted file mode 100644
index 4d052c88fe..0000000000
--- a/docs/Help_Spanish/Topics/XS0442.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0442
-
-XS0442
-
-
-
- Error XS0442
-
- '{0}': abstract properties cannot have private accessors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0443.XML b/docs/Help_Spanish/Topics/XS0443.XML
deleted file mode 100644
index 041bc8d69f..0000000000
--- a/docs/Help_Spanish/Topics/XS0443.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0443
-
-XS0443
-
-
-
- Error XS0443
-
- Syntax error; value expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0445.xml b/docs/Help_Spanish/Topics/XS0445.xml
deleted file mode 100644
index faf2712a3b..0000000000
--- a/docs/Help_Spanish/Topics/XS0445.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0445
-
- XS0445
-
-
-
- Error XS0445
-
- Cannot modify the result of an unboxing conversion
-
- The result of an unboxing conversion is a temporary variable. The compiler prevents you from modifying such variables because any modification would go away when the temporary variable goes away. To fix this, declare a new value-type variable to store the intermediate expression, and assign the result of the unboxing conversion to that variable.
-
- The following code generates XS0455.
-
-
- // XS0445.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0446.xml b/docs/Help_Spanish/Topics/XS0446.xml
deleted file mode 100644
index f848da1b04..0000000000
--- a/docs/Help_Spanish/Topics/XS0446.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0446
-
- XS0446
-
-
-
- Error XS0446
-
- Foreach cannot operate on a 'Method or Delegate'. Did you intend to invoke the 'Method or Delegate'?
-
- This error is caused by specifying a method without parentheses or an anonymous method without parentheses in the part of the foreach statement where you would normally put a collection class. Note that it is valid, though unusual, to put a method call in that location, if the method returns a collection class.
- Example
-
- The following code will generate XS0446.
-
-
- // XS0446.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0448.XML b/docs/Help_Spanish/Topics/XS0448.XML
deleted file mode 100644
index 2a57de9ee9..0000000000
--- a/docs/Help_Spanish/Topics/XS0448.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0448
-
-XS0448
-
-
-
- Error XS0448
-
- The return type for ++ or -- operator must match the parameter type or be derived from the parameter type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0449.XML b/docs/Help_Spanish/Topics/XS0449.XML
deleted file mode 100644
index 7d5611cf9d..0000000000
--- a/docs/Help_Spanish/Topics/XS0449.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0449
-
-XS0449
-
-
-
- Error XS0449
-
- The 'class' or 'struct' constraint must come before any other constraints
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0450.XML b/docs/Help_Spanish/Topics/XS0450.XML
deleted file mode 100644
index 4241595216..0000000000
--- a/docs/Help_Spanish/Topics/XS0450.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0450
-
-XS0450
-
-
-
- Error XS0450
-
- '{0}': cannot specify both a constraint class and the 'class' or 'struct' constraint
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0451.XML b/docs/Help_Spanish/Topics/XS0451.XML
deleted file mode 100644
index 0317b1e5cc..0000000000
--- a/docs/Help_Spanish/Topics/XS0451.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0451
-
-XS0451
-
-
-
- Error XS0451
-
- The 'new()' constraint cannot be used with the 'struct' constraint
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0452.XML b/docs/Help_Spanish/Topics/XS0452.XML
deleted file mode 100644
index 61d0d29feb..0000000000
--- a/docs/Help_Spanish/Topics/XS0452.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0452
-
-XS0452
-
-
-
- Error XS0452
-
- The type '{2}' must be a reference type in order to use it as parameter '{1}' in the generic type or method '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0453.XML b/docs/Help_Spanish/Topics/XS0453.XML
deleted file mode 100644
index 0f18c6340e..0000000000
--- a/docs/Help_Spanish/Topics/XS0453.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0453
-
-XS0453
-
-
-
- Error XS0453
-
- The type '{2}' must be a non-nullable value type in order to use it as parameter '{1}' in the generic type or method '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0454.XML b/docs/Help_Spanish/Topics/XS0454.XML
deleted file mode 100644
index 09d5ce8017..0000000000
--- a/docs/Help_Spanish/Topics/XS0454.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0454
-
-XS0454
-
-
-
- Error XS0454
-
- Circular constraint dependency involving '{0}' and '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0455.XML b/docs/Help_Spanish/Topics/XS0455.XML
deleted file mode 100644
index 2152fdb093..0000000000
--- a/docs/Help_Spanish/Topics/XS0455.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0455
-
-XS0455
-
-
-
- Error XS0455
-
- Type parameter '{0}' inherits conflicting constraints '{1}' and '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0456.XML b/docs/Help_Spanish/Topics/XS0456.XML
deleted file mode 100644
index c3ff90787d..0000000000
--- a/docs/Help_Spanish/Topics/XS0456.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0456
-
-XS0456
-
-
-
- Error XS0456
-
- Type parameter '{1}' has the 'struct' constraint so '{1}' cannot be used as a constraint for '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0457.XML b/docs/Help_Spanish/Topics/XS0457.XML
deleted file mode 100644
index 20312d2103..0000000000
--- a/docs/Help_Spanish/Topics/XS0457.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0457
-
-XS0457
-
-
-
- Error XS0457
-
- Ambiguous user defined conversions '{0}' and '{1}' when converting from '{2}' to '{3}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0458.XML b/docs/Help_Spanish/Topics/XS0458.XML
deleted file mode 100644
index 8a4938f12a..0000000000
--- a/docs/Help_Spanish/Topics/XS0458.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0458
-
- XS0458
-
-
-
- Warning XS0458
-
- The result of the expression is always 'null' of type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0459.XML b/docs/Help_Spanish/Topics/XS0459.XML
deleted file mode 100644
index 6f79e347ee..0000000000
--- a/docs/Help_Spanish/Topics/XS0459.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0459
-
-XS0459
-
-
-
- Error XS0459
-
- Cannot take the address of a read-only local variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0460.XML b/docs/Help_Spanish/Topics/XS0460.XML
deleted file mode 100644
index 636b23d5bb..0000000000
--- a/docs/Help_Spanish/Topics/XS0460.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0460
-
-XS0460
-
-
-
- Error XS0460
-
- Constraints for override and explicit interface implementation methods are inherited from the base method, so they cannot be specified directly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0462.XML b/docs/Help_Spanish/Topics/XS0462.XML
deleted file mode 100644
index a5a892e889..0000000000
--- a/docs/Help_Spanish/Topics/XS0462.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0462
-
-XS0462
-
-
-
- Error XS0462
-
- The inherited members '{0}' and '{1}' have the same signature in type '{2}', so they cannot be overridden
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0463.XML b/docs/Help_Spanish/Topics/XS0463.XML
deleted file mode 100644
index ad7de19519..0000000000
--- a/docs/Help_Spanish/Topics/XS0463.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0463
-
-XS0463
-
-
-
- Error XS0463
-
- Evaluation of the decimal constant expression failed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0464.XML b/docs/Help_Spanish/Topics/XS0464.XML
deleted file mode 100644
index 3cbc812908..0000000000
--- a/docs/Help_Spanish/Topics/XS0464.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0464
-
- XS0464
-
-
-
- Warning XS0464
-
- Comparing with null of type '{0}' always produces 'false'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0465.xml b/docs/Help_Spanish/Topics/XS0465.xml
deleted file mode 100644
index f1f7deee4d..0000000000
--- a/docs/Help_Spanish/Topics/XS0465.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS0465
-
- XS0465
-
-
-
- Error XS0465
-
- Introducing a 'Finalize' method can interfere with destructor invocation. Did you intend to declare a destructor?
-
- This warning occurs when you create a class with a method whose signature is public virtual void Finalize.
-
- If such a class is used as a base class and if the deriving class defines a destructor, the destructor will override the base class Finalize method, not Finalize.
- Example
-
- The following sample generates XS0465.
-
-
- // XS0465.prg // compile with: /target:library
-
-
diff --git a/docs/Help_Spanish/Topics/XS0466.XML b/docs/Help_Spanish/Topics/XS0466.XML
deleted file mode 100644
index 2ef039c033..0000000000
--- a/docs/Help_Spanish/Topics/XS0466.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0466
-
-XS0466
-
-
-
- Error XS0466
-
- '{0}' should not have a params parameter since '{1}' does not
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0469.XML b/docs/Help_Spanish/Topics/XS0469.XML
deleted file mode 100644
index 7bbff26414..0000000000
--- a/docs/Help_Spanish/Topics/XS0469.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0469
-
- XS0469
-
-
-
- Warning XS0469
-
- The 'goto case' value is not implicitly convertible to type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0470.XML b/docs/Help_Spanish/Topics/XS0470.XML
deleted file mode 100644
index 5af6e60955..0000000000
--- a/docs/Help_Spanish/Topics/XS0470.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0470
-
-XS0470
-
-
-
- Error XS0470
-
- Method '{0}' cannot implement interface accessor '{1}' for type '{2}'. Use an explicit interface implementation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0472.XML b/docs/Help_Spanish/Topics/XS0472.XML
deleted file mode 100644
index 976b4e84ab..0000000000
--- a/docs/Help_Spanish/Topics/XS0472.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0472
-
- XS0472
-
-
-
- Warning XS0472
-
- The result of the expression is always '{0}' since a value of type '{1}' is never equal to 'null' of type '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0473.XML b/docs/Help_Spanish/Topics/XS0473.XML
deleted file mode 100644
index 7430e9d6d8..0000000000
--- a/docs/Help_Spanish/Topics/XS0473.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0473
-
- XS0473
-
-
-
- Warning XS0473
-
- Explicit interface implementation '{0}' matches more than one interface member. Which interface member is actually chosen is implementation-dependent. Consider using a non-explicit implementation instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0500.XML b/docs/Help_Spanish/Topics/XS0500.XML
deleted file mode 100644
index 6140700edf..0000000000
--- a/docs/Help_Spanish/Topics/XS0500.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0500
-
-XS0500
-
-
-
- Error XS0500
-
- '{0}' cannot declare a body because it is marked abstract
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0501.XML b/docs/Help_Spanish/Topics/XS0501.XML
deleted file mode 100644
index 85993c4615..0000000000
--- a/docs/Help_Spanish/Topics/XS0501.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0501
-
-XS0501
-
-
-
- Error XS0501
-
- '{0}' must declare a body because it is not marked abstract, extern, or partial
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0502.XML b/docs/Help_Spanish/Topics/XS0502.XML
deleted file mode 100644
index 4fb2fb973a..0000000000
--- a/docs/Help_Spanish/Topics/XS0502.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0502
-
-XS0502
-
-
-
- Error XS0502
-
- '{0}' cannot be both abstract and sealed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0503.XML b/docs/Help_Spanish/Topics/XS0503.XML
deleted file mode 100644
index 12c4f880a3..0000000000
--- a/docs/Help_Spanish/Topics/XS0503.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0503
-
-XS0503
-
-
-
- Error XS0503
-
- The abstract method '{0}' cannot be marked virtual
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0504.xml b/docs/Help_Spanish/Topics/XS0504.xml
deleted file mode 100644
index a79a057947..0000000000
--- a/docs/Help_Spanish/Topics/XS0504.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0504
-
- XS0504
-
-
-
- Error XS0504
-
- The constant 'variable' cannot be marked static
-
- If a variable is const, it is also static. If you want a const and static variable, just declare that variable as const; if all you want is a static variable, just mark it static.
-
- The following sample generates XS0504:
-
-
- // XS0504.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0505.XML b/docs/Help_Spanish/Topics/XS0505.XML
deleted file mode 100644
index 1adcd12733..0000000000
--- a/docs/Help_Spanish/Topics/XS0505.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0505
-
-XS0505
-
-
-
- Error XS0505
-
- '{0}': cannot override because '{1}' is not a function
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0506.XML b/docs/Help_Spanish/Topics/XS0506.XML
deleted file mode 100644
index 4601eb2b9b..0000000000
--- a/docs/Help_Spanish/Topics/XS0506.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0506
-
-XS0506
-
-
-
- Error XS0506
-
- '{0}': cannot override inherited member '{1}' because it is not marked virtual, abstract, or override
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0507.xml b/docs/Help_Spanish/Topics/XS0507.xml
deleted file mode 100644
index 04420eb71e..0000000000
--- a/docs/Help_Spanish/Topics/XS0507.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- XS0507
-
- XS0507
-
-
-
- Error XS0507
-
- 'function1' : cannot change access modifiers when overriding 'access' inherited member 'function2'
-
- An attempt was made to change the access specification in a method override.
- Example
-
- The following sample generates XS0507.
-
-
- // XS0507.prg
-
- Example
-
- XS0507 can also occur if a class attempts to override a method marked as protected internal defined in referenced metadata. In this situation, the overriding method should be marked as protected.
-
-
- // XS0507_b.prg // compile with: /target:library
-
- Example
-
- The following sample generates XS0507.
-
-
- // XS0507_c.prg // compile with: /reference:XS0507_b.dll public class cly : clx
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0508.XML b/docs/Help_Spanish/Topics/XS0508.XML
deleted file mode 100644
index 0375d86f5c..0000000000
--- a/docs/Help_Spanish/Topics/XS0508.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0508
-
-XS0508
-
-
-
- Error XS0508
-
- '{0}': return type must be '{2}' to match overridden member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0509.XML b/docs/Help_Spanish/Topics/XS0509.XML
deleted file mode 100644
index c6d36981a9..0000000000
--- a/docs/Help_Spanish/Topics/XS0509.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0509
-
-XS0509
-
-
-
- Error XS0509
-
- '{0}': cannot derive from sealed type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0513.XML b/docs/Help_Spanish/Topics/XS0513.XML
deleted file mode 100644
index b535c6135f..0000000000
--- a/docs/Help_Spanish/Topics/XS0513.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0513
-
-XS0513
-
-
-
- Error XS0513
-
- '{0}' is abstract but it is contained in non-abstract class '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0514.XML b/docs/Help_Spanish/Topics/XS0514.XML
deleted file mode 100644
index 3f9cdfd2ca..0000000000
--- a/docs/Help_Spanish/Topics/XS0514.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0514
-
-XS0514
-
-
-
- Error XS0514
-
- '{0}': static constructor cannot have an explicit 'SELF' or 'SUPER' constructor call
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0515.XML b/docs/Help_Spanish/Topics/XS0515.XML
deleted file mode 100644
index 6c446ad7e7..0000000000
--- a/docs/Help_Spanish/Topics/XS0515.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0515
-
-XS0515
-
-
-
- Error XS0515
-
- '{0}': access modifiers are not allowed on static constructors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0516.XML b/docs/Help_Spanish/Topics/XS0516.XML
deleted file mode 100644
index cf4671bbfc..0000000000
--- a/docs/Help_Spanish/Topics/XS0516.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0516
-
-XS0516
-
-
-
- Error XS0516
-
- Constructor '{0}' cannot call itself
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0517.XML b/docs/Help_Spanish/Topics/XS0517.XML
deleted file mode 100644
index 629902e8d8..0000000000
--- a/docs/Help_Spanish/Topics/XS0517.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0517
-
-XS0517
-
-
-
- Error XS0517
-
- '{0}' has no base class and cannot call a base constructor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0518.xml b/docs/Help_Spanish/Topics/XS0518.xml
deleted file mode 100644
index cd4220dad5..0000000000
--- a/docs/Help_Spanish/Topics/XS0518.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS0518
-
- XS0518
-
-
-
- Error XS0518
-
- Predefined type 'type' is not defined or imported
-
- The main cause for this problem is that the project is not importing mscorlib.dll, which defines the entire System namespace. This can be caused by one of the following:
-
-
-
The /nostdlib option from the command line compiler has been specified. The /nostdlib option prevents the import of mscorlib.dll. Use this option if you want to define or create a user-specific System namespace.
-
An incorrect mscorlib.dll is referenced.
-
A corrupt Visual Studio .NET or .NET Framework common language runtime installation exists.
-
Residual components from an earlier installation that are incompatible with the latest installation remain.
-
-
- To resolve this problem, take one of the following actions:
-
-
-
Do not specify the /nostdlib option from the command line compiler.
-
Make sure that the project refers to the correct mscorlib.dll.
-
Reinstall the .NET Framework common language runtime (if the previous solutions do not solve the problem).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0522.XML b/docs/Help_Spanish/Topics/XS0522.XML
deleted file mode 100644
index 24ca0d7a9f..0000000000
--- a/docs/Help_Spanish/Topics/XS0522.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0522
-
-XS0522
-
-
-
- Error XS0522
-
- '{0}': structs cannot call base class constructors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0523.xml b/docs/Help_Spanish/Topics/XS0523.xml
deleted file mode 100644
index 562d11610c..0000000000
--- a/docs/Help_Spanish/Topics/XS0523.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0523
-
- XS0523
-
-
-
- Error XS0523
-
- Struct member 'struct2 field' of type 'struct1' causes a cycle in the struct layout
-
- The definitions of two structs include recursive references. Change the struct definitions such that each does not define itself on the other. This limitation applies only to structs, since structs are value types. If using recursive references, declare your types as classes.
-
- The following sample generates XS0523:
-
-
- // XS0523.prg // compile with: /target:library
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0524.XML b/docs/Help_Spanish/Topics/XS0524.XML
deleted file mode 100644
index cc6e2a2e97..0000000000
--- a/docs/Help_Spanish/Topics/XS0524.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0524
-
-XS0524
-
-
-
- Error XS0524
-
- '{0}': interfaces cannot declare types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0525.XML b/docs/Help_Spanish/Topics/XS0525.XML
deleted file mode 100644
index b35e39089e..0000000000
--- a/docs/Help_Spanish/Topics/XS0525.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0525
-
-XS0525
-
-
-
- Error XS0525
-
- Interfaces cannot contain fields
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0526.XML b/docs/Help_Spanish/Topics/XS0526.XML
deleted file mode 100644
index 34bc0465aa..0000000000
--- a/docs/Help_Spanish/Topics/XS0526.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0526
-
-XS0526
-
-
-
- Error XS0526
-
- Interfaces cannot contain constructors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0527.XML b/docs/Help_Spanish/Topics/XS0527.XML
deleted file mode 100644
index 0c9947c83b..0000000000
--- a/docs/Help_Spanish/Topics/XS0527.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0527
-
-XS0527
-
-
-
- Error XS0527
-
- Type '{0}' in interface list is not an interface
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0528.XML b/docs/Help_Spanish/Topics/XS0528.XML
deleted file mode 100644
index 18a7c6e6a9..0000000000
--- a/docs/Help_Spanish/Topics/XS0528.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0528
-
-XS0528
-
-
-
- Error XS0528
-
- '{0}' is already listed in interface list
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0529.XML b/docs/Help_Spanish/Topics/XS0529.XML
deleted file mode 100644
index 9bd0ef0887..0000000000
--- a/docs/Help_Spanish/Topics/XS0529.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0529
-
-XS0529
-
-
-
- Error XS0529
-
- Inherited interface '{1}' causes a cycle in the interface hierarchy of '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0531.XML b/docs/Help_Spanish/Topics/XS0531.XML
deleted file mode 100644
index e2bc7c3d0c..0000000000
--- a/docs/Help_Spanish/Topics/XS0531.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0531
-
-XS0531
-
-
-
- Error XS0531
-
- '{0}': interface members cannot have a definition
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0533.XML b/docs/Help_Spanish/Topics/XS0533.XML
deleted file mode 100644
index f3904f4101..0000000000
--- a/docs/Help_Spanish/Topics/XS0533.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0533
-
-XS0533
-
-
-
- Error XS0533
-
- '{0}' hides inherited abstract member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0534.XML b/docs/Help_Spanish/Topics/XS0534.XML
deleted file mode 100644
index 0dae635aa1..0000000000
--- a/docs/Help_Spanish/Topics/XS0534.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0534
-
-XS0534
-
-
-
- Error XS0534
-
- '{0}' does not implement inherited abstract member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0535.XML b/docs/Help_Spanish/Topics/XS0535.XML
deleted file mode 100644
index 3b15c1e6f3..0000000000
--- a/docs/Help_Spanish/Topics/XS0535.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0535
-
-XS0535
-
-
-
- Error XS0535
-
- '{0}' does not implement interface member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0537.XML b/docs/Help_Spanish/Topics/XS0537.XML
deleted file mode 100644
index ec7a00d9fe..0000000000
--- a/docs/Help_Spanish/Topics/XS0537.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0537
-
-XS0537
-
-
-
- Error XS0537
-
- The class System.Object cannot have a base class or implement an interface
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0538.XML b/docs/Help_Spanish/Topics/XS0538.XML
deleted file mode 100644
index 923575b56d..0000000000
--- a/docs/Help_Spanish/Topics/XS0538.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0538
-
-XS0538
-
-
-
- Error XS0538
-
- '{0}' in explicit interface declaration is not an interface
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0539.XML b/docs/Help_Spanish/Topics/XS0539.XML
deleted file mode 100644
index 9e2c076f38..0000000000
--- a/docs/Help_Spanish/Topics/XS0539.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0539
-
-XS0539
-
-
-
- Error XS0539
-
- '{0}' in explicit interface declaration is not a member of interface
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0540.XML b/docs/Help_Spanish/Topics/XS0540.XML
deleted file mode 100644
index ebd64c127c..0000000000
--- a/docs/Help_Spanish/Topics/XS0540.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0540
-
-XS0540
-
-
-
- Error XS0540
-
- '{0}': containing type does not implement interface '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0541.XML b/docs/Help_Spanish/Topics/XS0541.XML
deleted file mode 100644
index f25f36a022..0000000000
--- a/docs/Help_Spanish/Topics/XS0541.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0541
-
-XS0541
-
-
-
- Error XS0541
-
- '{0}': explicit interface declaration can only be declared in a class or struct
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0542.XML b/docs/Help_Spanish/Topics/XS0542.XML
deleted file mode 100644
index 590787ee2b..0000000000
--- a/docs/Help_Spanish/Topics/XS0542.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0542
-
- XS0542
-
-
-
- Warning XS0542
-
- '{0}': member names cannot be the same as their enclosing type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0543.XML b/docs/Help_Spanish/Topics/XS0543.XML
deleted file mode 100644
index 0293a631a3..0000000000
--- a/docs/Help_Spanish/Topics/XS0543.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0543
-
-XS0543
-
-
-
- Error XS0543
-
- '{0}': the enumerator value is too large to fit in its type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0544.XML b/docs/Help_Spanish/Topics/XS0544.XML
deleted file mode 100644
index f03f7589c9..0000000000
--- a/docs/Help_Spanish/Topics/XS0544.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0544
-
-XS0544
-
-
-
- Error XS0544
-
- '{0}': cannot override because '{1}' is not a property
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0545.xml b/docs/Help_Spanish/Topics/XS0545.xml
deleted file mode 100644
index 5c55223877..0000000000
--- a/docs/Help_Spanish/Topics/XS0545.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- XS0545
-
- XS0545
-
-
-
- Error XS0545
-
- 'function' : cannot override because 'property' does not have an overridable get accessor
-
- A try was made to define an override for a property accessor when the base class has no such definition to override. You can resolve this error by:
-
-
-
Adding a set accessor in the base class.
-
Removing the set accessor from the derived class.
-
Hiding the base class property by adding the new keyword to a property in a derived class.
-
Making the base class property virtual.
-
-
- For more information, see Using Properties.
- Example
-
- The following sample generates XS0545.
-
-
- // XS0545.prg // compile with: /target:library
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0546.XML b/docs/Help_Spanish/Topics/XS0546.XML
deleted file mode 100644
index dc43c6a148..0000000000
--- a/docs/Help_Spanish/Topics/XS0546.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0546
-
-XS0546
-
-
-
- Error XS0546
-
- '{0}': cannot override because '{1}' does not have an overridable set accessor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0547.XML b/docs/Help_Spanish/Topics/XS0547.XML
deleted file mode 100644
index 64f8f19507..0000000000
--- a/docs/Help_Spanish/Topics/XS0547.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0547
-
-XS0547
-
-
-
- Error XS0547
-
- '{0}': property or indexer cannot have void type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0548.XML b/docs/Help_Spanish/Topics/XS0548.XML
deleted file mode 100644
index 3b2f036c11..0000000000
--- a/docs/Help_Spanish/Topics/XS0548.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0548
-
-XS0548
-
-
-
- Error XS0548
-
- '{0}': property or indexer must have at least one accessor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0549.XML b/docs/Help_Spanish/Topics/XS0549.XML
deleted file mode 100644
index 91ebf78f46..0000000000
--- a/docs/Help_Spanish/Topics/XS0549.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0549
-
- XS0549
-
-
-
- Warning XS0549
-
- '{0}' is a new virtual member in sealed class '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0550.XML b/docs/Help_Spanish/Topics/XS0550.XML
deleted file mode 100644
index e68542c325..0000000000
--- a/docs/Help_Spanish/Topics/XS0550.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0550
-
-XS0550
-
-
-
- Error XS0550
-
- '{0}' adds an accessor not found in interface member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0551.XML b/docs/Help_Spanish/Topics/XS0551.XML
deleted file mode 100644
index a6bdb02ce3..0000000000
--- a/docs/Help_Spanish/Topics/XS0551.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0551
-
-XS0551
-
-
-
- Error XS0551
-
- Explicit interface implementation '{0}' is missing accessor '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0552.xml b/docs/Help_Spanish/Topics/XS0552.xml
deleted file mode 100644
index 84b211d77c..0000000000
--- a/docs/Help_Spanish/Topics/XS0552.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0552
-
- XS0552
-
-
-
- Error XS0552
-
- 'conversion routine' : user defined conversion to/from interface
-
- You cannot create a user-defined conversion to or from an interface. If you need the conversion routine, resolve this error by making the interface a class or derive a class from the interface.
-
- The following sample generates XS0552:
-
-
- // XS0552.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0553.XML b/docs/Help_Spanish/Topics/XS0553.XML
deleted file mode 100644
index 2312299913..0000000000
--- a/docs/Help_Spanish/Topics/XS0553.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0553
-
- XS0553
-
-
-
- Warning XS0553
-
- '{0}': user-defined conversions to or from a base class are not allowed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0554.XML b/docs/Help_Spanish/Topics/XS0554.XML
deleted file mode 100644
index 32ff4cae14..0000000000
--- a/docs/Help_Spanish/Topics/XS0554.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0554
-
- XS0554
-
-
-
- Warning XS0554
-
- '{0}': user-defined conversions to or from a derived class are not allowed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0555.XML b/docs/Help_Spanish/Topics/XS0555.XML
deleted file mode 100644
index fd1b9d73df..0000000000
--- a/docs/Help_Spanish/Topics/XS0555.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0555
-
-XS0555
-
-
-
- Error XS0555
-
- User-defined operator cannot take an object of the enclosing type and convert to an object of the enclosing type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0556.XML b/docs/Help_Spanish/Topics/XS0556.XML
deleted file mode 100644
index fbd8ff4388..0000000000
--- a/docs/Help_Spanish/Topics/XS0556.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0556
-
-XS0556
-
-
-
- Error XS0556
-
- User-defined conversion must convert to or from the enclosing type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0557.XML b/docs/Help_Spanish/Topics/XS0557.XML
deleted file mode 100644
index d146ae843e..0000000000
--- a/docs/Help_Spanish/Topics/XS0557.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0557
-
-XS0557
-
-
-
- Error XS0557
-
- Duplicate user-defined conversion in type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0558.XML b/docs/Help_Spanish/Topics/XS0558.XML
deleted file mode 100644
index cecf8ad070..0000000000
--- a/docs/Help_Spanish/Topics/XS0558.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0558
-
-XS0558
-
-
-
- Error XS0558
-
- User-defined operator '{0}' must be declared static and public
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0559.XML b/docs/Help_Spanish/Topics/XS0559.XML
deleted file mode 100644
index 149eebb75e..0000000000
--- a/docs/Help_Spanish/Topics/XS0559.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0559
-
-XS0559
-
-
-
- Error XS0559
-
- The parameter type for ++ or -- operator must be the containing type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0562.XML b/docs/Help_Spanish/Topics/XS0562.XML
deleted file mode 100644
index bfb70a15c3..0000000000
--- a/docs/Help_Spanish/Topics/XS0562.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0562
-
-XS0562
-
-
-
- Error XS0562
-
- The parameter of a unary operator must be the containing type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0563.xml b/docs/Help_Spanish/Topics/XS0563.xml
deleted file mode 100644
index c7cce9c7f5..0000000000
--- a/docs/Help_Spanish/Topics/XS0563.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0563
-
- XS0563
-
-
-
- Error XS0563
-
- One of the parameters of a binary operator must be the containing type
-
- The method declaration for an operator overload must follow certain guidelines.
- Example
-
- The following sample generates XS0563:
-
-
- // XS0563.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0564.XML b/docs/Help_Spanish/Topics/XS0564.XML
deleted file mode 100644
index 6d07b008a7..0000000000
--- a/docs/Help_Spanish/Topics/XS0564.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0564
-
-XS0564
-
-
-
- Error XS0564
-
- The first operand of an overloaded shift operator must have the same type as the containing type, and the type of the second operand must be int
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0567.XML b/docs/Help_Spanish/Topics/XS0567.XML
deleted file mode 100644
index c3175c6de7..0000000000
--- a/docs/Help_Spanish/Topics/XS0567.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0567
-
-XS0567
-
-
-
- Error XS0567
-
- Interfaces cannot contain operators
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0568.XML b/docs/Help_Spanish/Topics/XS0568.XML
deleted file mode 100644
index bb6e4ddc2d..0000000000
--- a/docs/Help_Spanish/Topics/XS0568.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0568
-
-XS0568
-
-
-
- Error XS0568
-
- Structs cannot contain explicit parameterless constructors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0569.XML b/docs/Help_Spanish/Topics/XS0569.XML
deleted file mode 100644
index bf5e9c5a39..0000000000
--- a/docs/Help_Spanish/Topics/XS0569.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0569
-
-XS0569
-
-
-
- Error XS0569
-
- '{0}': cannot override '{1}' because it is not supported by the language
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0570.xml b/docs/Help_Spanish/Topics/XS0570.xml
deleted file mode 100644
index 6ee9ecfa93..0000000000
--- a/docs/Help_Spanish/Topics/XS0570.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XS0570
-
- XS0570
-
-
-
- Error XS0570
-
- Property, indexer, or event 'name' is not supported by the language; try directly calling accessor method 'name!'
-
- This error occurs when using imported metadata that was generated by another compiler. Your code attempted to use a class member that the compiler cannot process.
- Example
-
- The following C++ program uses an attribute, RequiredAttributeAttribute, which may not be consumed by other languages.
-
-
- // CPP0570.cpp // compile with: /clr /LD
-
- Example
-
- The following sample generates XS0570.
-
-
- // XS0570.prg // compile with: /reference:CPP0570.dll
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0571.xml b/docs/Help_Spanish/Topics/XS0571.xml
deleted file mode 100644
index 06c16db6ff..0000000000
--- a/docs/Help_Spanish/Topics/XS0571.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0571
-
- XS0571
-
-
-
- Warning XS0571
-
- 'function' : cannot explicitly call operator or accessor
-
- Certain operators have internal names. For example, op_Increment is the internal name of the ++ operator. You should not use or explicitly call such method names.
-
- The following sample generates XS0571:
-
-
- // XS0571.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0572.XML b/docs/Help_Spanish/Topics/XS0572.XML
deleted file mode 100644
index 582bc99184..0000000000
--- a/docs/Help_Spanish/Topics/XS0572.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0572
-
-XS0572
-
-
-
- Error XS0572
-
- '{0}': cannot reference a type through an expression; try '{1}' instead
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0573.XML b/docs/Help_Spanish/Topics/XS0573.XML
deleted file mode 100644
index 57c1b8296b..0000000000
--- a/docs/Help_Spanish/Topics/XS0573.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0573
-
-XS0573
-
-
-
- Error XS0573
-
- '{0}': cannot have instance property or field initializers in structs
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0574.XML b/docs/Help_Spanish/Topics/XS0574.XML
deleted file mode 100644
index 896d056ca5..0000000000
--- a/docs/Help_Spanish/Topics/XS0574.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0574
-
-XS0574
-
-
-
- Error XS0574
-
- Name of destructor must match name of class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0575.XML b/docs/Help_Spanish/Topics/XS0575.XML
deleted file mode 100644
index 38f4f59c57..0000000000
--- a/docs/Help_Spanish/Topics/XS0575.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0575
-
-XS0575
-
-
-
- Error XS0575
-
- Only class types can contain destructors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0576.XML b/docs/Help_Spanish/Topics/XS0576.XML
deleted file mode 100644
index b5e1a56922..0000000000
--- a/docs/Help_Spanish/Topics/XS0576.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0576
-
-XS0576
-
-
-
- Error XS0576
-
- Namespace '{1}' contains a definition conflicting with alias '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0577.XML b/docs/Help_Spanish/Topics/XS0577.XML
deleted file mode 100644
index 90af2d274a..0000000000
--- a/docs/Help_Spanish/Topics/XS0577.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0577
-
-XS0577
-
-
-
- Error XS0577
-
- The Conditional attribute is not valid on '{0}' because it is a constructor, destructor, operator, or explicit interface implementation
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0578.XML b/docs/Help_Spanish/Topics/XS0578.XML
deleted file mode 100644
index 2e1e607136..0000000000
--- a/docs/Help_Spanish/Topics/XS0578.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0578
-
-XS0578
-
-
-
- Error XS0578
-
- The Conditional attribute is not valid on '{0}' because its return type is not void
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0579.xml b/docs/Help_Spanish/Topics/XS0579.xml
deleted file mode 100644
index 8eded0dd1a..0000000000
--- a/docs/Help_Spanish/Topics/XS0579.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0579
-
- XS0579
-
-
-
- Error XS0579
-
- Duplicate 'attribute' attribute
-
- It is not possible to specify the same attribute more than once unless the attribute specifies AllowMultiple=true in its AttributeUsage.
- Example
-
- The following example generates XS0579.
-
-
- // XS0579.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0582.XML b/docs/Help_Spanish/Topics/XS0582.XML
deleted file mode 100644
index 5dcd7c43e7..0000000000
--- a/docs/Help_Spanish/Topics/XS0582.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0582
-
-XS0582
-
-
-
- Error XS0582
-
- The Conditional attribute is not valid on interface members
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0590.XML b/docs/Help_Spanish/Topics/XS0590.XML
deleted file mode 100644
index ac2cd14001..0000000000
--- a/docs/Help_Spanish/Topics/XS0590.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0590
-
-XS0590
-
-
-
- Error XS0590
-
- User-defined operators cannot return void
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0591.XML b/docs/Help_Spanish/Topics/XS0591.XML
deleted file mode 100644
index e78865f2b3..0000000000
--- a/docs/Help_Spanish/Topics/XS0591.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0591
-
-XS0591
-
-
-
- Error XS0591
-
- Invalid value for argument to '{0}' attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0592.xml b/docs/Help_Spanish/Topics/XS0592.xml
deleted file mode 100644
index 8dfa39f6c3..0000000000
--- a/docs/Help_Spanish/Topics/XS0592.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0592
-
- XS0592
-
-
-
- Error XS0592
-
- Attribute 'attribute' is not valid on this declaration type. It is valid on 'type' declarations only.
-
- When you define an attribute, you define what constructs it can be applied to by specifying an AttributeTargets value. In the following example, the MyAttribute attribute can be applied to interfaces only, because the AttributeUsage attribute specifies AttributeTargets.Iterface. The error is generated because the attribute is applied to a class (class A).
- Example
-
- The following sample generates XS0592:
-
-
- // XS0592.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0594.XML b/docs/Help_Spanish/Topics/XS0594.XML
deleted file mode 100644
index 711bda4162..0000000000
--- a/docs/Help_Spanish/Topics/XS0594.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0594
-
-XS0594
-
-
-
- Error XS0594
-
- Floating-point constant is outside the range of type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0595.XML b/docs/Help_Spanish/Topics/XS0595.XML
deleted file mode 100644
index 73973d3985..0000000000
--- a/docs/Help_Spanish/Topics/XS0595.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0595
-
-XS0595
-
-
-
- Error XS0595
-
- Invalid real literal.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0596.XML b/docs/Help_Spanish/Topics/XS0596.XML
deleted file mode 100644
index 4ea34ebe99..0000000000
--- a/docs/Help_Spanish/Topics/XS0596.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0596
-
-XS0596
-
-
-
- Error XS0596
-
- The Guid attribute must be specified with the ComImport attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0599.XML b/docs/Help_Spanish/Topics/XS0599.XML
deleted file mode 100644
index 0f07747067..0000000000
--- a/docs/Help_Spanish/Topics/XS0599.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0599
-
-XS0599
-
-
-
- Error XS0599
-
- Invalid value for named attribute argument '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0601.XML b/docs/Help_Spanish/Topics/XS0601.XML
deleted file mode 100644
index e01cd887e5..0000000000
--- a/docs/Help_Spanish/Topics/XS0601.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0601
-
-XS0601
-
-
-
- Error XS0601
-
- The DllImport attribute must be specified on a method marked 'static' and 'extern'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0610.XML b/docs/Help_Spanish/Topics/XS0610.XML
deleted file mode 100644
index 80337d7f72..0000000000
--- a/docs/Help_Spanish/Topics/XS0610.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0610
-
-XS0610
-
-
-
- Error XS0610
-
- Field or property cannot be of type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0611.XML b/docs/Help_Spanish/Topics/XS0611.XML
deleted file mode 100644
index b38dd5ad8d..0000000000
--- a/docs/Help_Spanish/Topics/XS0611.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0611
-
-XS0611
-
-
-
- Error XS0611
-
- Array elements cannot be of type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0612.XML b/docs/Help_Spanish/Topics/XS0612.XML
deleted file mode 100644
index 17a655643c..0000000000
--- a/docs/Help_Spanish/Topics/XS0612.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0612
-
- XS0612
-
-
-
- Warning XS0612
-
- '{0}' is obsolete
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0613.xml b/docs/Help_Spanish/Topics/XS0613.xml
deleted file mode 100644
index daf08efc77..0000000000
--- a/docs/Help_Spanish/Topics/XS0613.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- XS0613
-
-
- Error XS0613
-
- Static class '{0}' cannot derive from type '{1}'. Static classes must derive from object.
- This error message appears when you inherit a static class from another class.
- To solve this you must either:
-
-
CLASS MyClass ENDCLASS
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0616.xml b/docs/Help_Spanish/Topics/XS0616.xml
deleted file mode 100644
index f9487305ca..0000000000
--- a/docs/Help_Spanish/Topics/XS0616.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS0616
-
- XS0616
-
-
-
- Error XS0616
-
- 'class' is not an attribute class
-
- An attempt was made to use a non-attribute class in an attribute block. All the attribute types need to be inherited from System.Attribute.
- Example
-
- The following sample generates XS0616.
-
-
- // XS0616.prg // compile with: /target:library
-
-
- Example
-
- The following sample shows how you might define an attribute:
-
-
- // CreateAttrib.prg // compile with: /target:library
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0617.XML b/docs/Help_Spanish/Topics/XS0617.XML
deleted file mode 100644
index 3ed7d21fc7..0000000000
--- a/docs/Help_Spanish/Topics/XS0617.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0617
-
-XS0617
-
-
-
- Error XS0617
-
- '{0}' is not a valid named attribute argument. Named attribute arguments must be fields which are not readonly, static, or const, or read-write properties which are public and not static.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0618.xml b/docs/Help_Spanish/Topics/XS0618.xml
deleted file mode 100644
index a8cb2c0028..0000000000
--- a/docs/Help_Spanish/Topics/XS0618.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- XS0618
-
- XS0618
-
-
-
- Warning XS0618
-
- 'member' is obsolete: 'text'
-
- A class member was marked with the Obsolete attribute, such that a warning will be issued when the class member is referenced. For more information, see Common Attributes.
-
- The following sample generates XS0618:
-
-
- // XS0618.prg // compile with: /W:2
-
-
diff --git a/docs/Help_Spanish/Topics/XS0619.XML b/docs/Help_Spanish/Topics/XS0619.XML
deleted file mode 100644
index 29aaa0d682..0000000000
--- a/docs/Help_Spanish/Topics/XS0619.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0619
-
-XS0619
-
-
-
- Error XS0619
-
- '{0}' is obsolete: '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0620.XML b/docs/Help_Spanish/Topics/XS0620.XML
deleted file mode 100644
index f7a1aa390b..0000000000
--- a/docs/Help_Spanish/Topics/XS0620.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0620
-
-XS0620
-
-
-
- Error XS0620
-
- Indexers cannot have void type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0621.XML b/docs/Help_Spanish/Topics/XS0621.XML
deleted file mode 100644
index 4a169bc4fb..0000000000
--- a/docs/Help_Spanish/Topics/XS0621.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0621
-
-XS0621
-
-
-
- Error XS0621
-
- '{0}': virtual or abstract members cannot be private
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0622.XML b/docs/Help_Spanish/Topics/XS0622.XML
deleted file mode 100644
index eb84f09a85..0000000000
--- a/docs/Help_Spanish/Topics/XS0622.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0622
-
-XS0622
-
-
-
- Error XS0622
-
- Can only use array initializer expressions to assign to array types. Try using a new expression instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0623.XML b/docs/Help_Spanish/Topics/XS0623.XML
deleted file mode 100644
index 7139a45784..0000000000
--- a/docs/Help_Spanish/Topics/XS0623.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0623
-
-XS0623
-
-
-
- Error XS0623
-
- Array initializers can only be used in a variable or field initializer. Try using a new expression instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0625.XML b/docs/Help_Spanish/Topics/XS0625.XML
deleted file mode 100644
index 8e3b788462..0000000000
--- a/docs/Help_Spanish/Topics/XS0625.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0625
-
-XS0625
-
-
-
- Error XS0625
-
- '{0}': instance field types marked with StructLayout(LayoutKind.Explicit) must have a FieldOffset attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0626.XML b/docs/Help_Spanish/Topics/XS0626.XML
deleted file mode 100644
index 6ff1bf126a..0000000000
--- a/docs/Help_Spanish/Topics/XS0626.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0626
-
- XS0626
-
-
-
- Warning XS0626
-
- Method, operator, or accessor '{0}' is marked external and has no attributes on it. Consider adding a DllImport attribute to specify the external implementation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0628.xml b/docs/Help_Spanish/Topics/XS0628.xml
deleted file mode 100644
index 7f77d6205a..0000000000
--- a/docs/Help_Spanish/Topics/XS0628.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0628
-
- XS0628
-
-
-
- Warning XS0628
-
- '{0}': new protected member declared in sealed class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0629.xml b/docs/Help_Spanish/Topics/XS0629.xml
deleted file mode 100644
index ba8d8e8317..0000000000
--- a/docs/Help_Spanish/Topics/XS0629.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0629
-
-XS0629
-
-
-
- Error XS0629
-
- Conditional member '{0}' cannot implement interface member '{1}' in type '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0630.XML b/docs/Help_Spanish/Topics/XS0630.XML
deleted file mode 100644
index 8c9262cf33..0000000000
--- a/docs/Help_Spanish/Topics/XS0630.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS0630
-
-XS0630
-
-
-
- Error XS0630
-
- '{0}' cannot implement interface member '{1}' in type '{2}' because it has an __arglist parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0631.xml b/docs/Help_Spanish/Topics/XS0631.xml
deleted file mode 100644
index f412f4e85e..0000000000
--- a/docs/Help_Spanish/Topics/XS0631.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0631
-
-XS0631
-
-
-
- Error XS0631
-
- ref and out are not valid in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0633.xml b/docs/Help_Spanish/Topics/XS0633.xml
deleted file mode 100644
index a0a1f49151..0000000000
--- a/docs/Help_Spanish/Topics/XS0633.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0633
-
-XS0633
-
-
-
- Error XS0633
-
- The argument to the '{0}' attribute must be a valid identifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0636.xml b/docs/Help_Spanish/Topics/XS0636.xml
deleted file mode 100644
index e279a163ab..0000000000
--- a/docs/Help_Spanish/Topics/XS0636.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0636
-
-XS0636
-
-
-
- Error XS0636
-
- The FieldOffset attribute can only be placed on members of types marked with the StructLayout(LayoutKind.Explicit)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0637.xml b/docs/Help_Spanish/Topics/XS0637.xml
deleted file mode 100644
index e3acd047dc..0000000000
--- a/docs/Help_Spanish/Topics/XS0637.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0637
-
-XS0637
-
-
-
- Error XS0637
-
- The FieldOffset attribute is not allowed on static or const fields
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0641.xml b/docs/Help_Spanish/Topics/XS0641.xml
deleted file mode 100644
index bd8370b354..0000000000
--- a/docs/Help_Spanish/Topics/XS0641.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0641
-
-XS0641
-
-
-
- Error XS0641
-
- Attribute '{0}' is only valid on classes derived from System.Attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0642.xml b/docs/Help_Spanish/Topics/XS0642.xml
deleted file mode 100644
index b0a52614d4..0000000000
--- a/docs/Help_Spanish/Topics/XS0642.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0642
-
- XS0642
-
-
-
- Warning XS0642
-
- Possible mistaken empty statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0643.xml b/docs/Help_Spanish/Topics/XS0643.xml
deleted file mode 100644
index d26e61e80f..0000000000
--- a/docs/Help_Spanish/Topics/XS0643.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0643
-
-XS0643
-
-
-
- Error XS0643
-
- '{0}' duplicate named attribute argument
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0644.xml b/docs/Help_Spanish/Topics/XS0644.xml
deleted file mode 100644
index 7b5e7143a5..0000000000
--- a/docs/Help_Spanish/Topics/XS0644.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0644
-
-XS0644
-
-
-
- Error XS0644
-
- '{0}' cannot derive from special class '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0646.xml b/docs/Help_Spanish/Topics/XS0646.xml
deleted file mode 100644
index 035ecdcef0..0000000000
--- a/docs/Help_Spanish/Topics/XS0646.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0646
-
-XS0646
-
-
-
- Error XS0646
-
- Cannot specify the DefaultMember attribute on a type containing an indexer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0648.xml b/docs/Help_Spanish/Topics/XS0648.xml
deleted file mode 100644
index 421197cb7d..0000000000
--- a/docs/Help_Spanish/Topics/XS0648.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0648
-
-XS0648
-
-
-
- Error XS0648
-
- '{0}' is a type not supported by the language
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0649.xml b/docs/Help_Spanish/Topics/XS0649.xml
deleted file mode 100644
index 51e242b35b..0000000000
--- a/docs/Help_Spanish/Topics/XS0649.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0649
-
- XS0649
-
-
-
- Warning XS0649
-
- Field '{0}' is never assigned to, and will always have its default value {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0650.xml b/docs/Help_Spanish/Topics/XS0650.xml
deleted file mode 100644
index ff343bb6a4..0000000000
--- a/docs/Help_Spanish/Topics/XS0650.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS0650
-
- XS0650
-
-
-
- Error XS0650
-
- Bad array declarator: To declare a managed array the rank specifier precedes the variable's identifier. To declare a fixed size buffer field, use the fixed keyword before the field type.
-
- An array was declared incorrectly. In X#, unlike in C and C++, the square brackets follow the type, not the variable name. Also, realize that the syntax for a fixed size buffer differs from that of an array.
- Example
-
- The following example code generates XS0650.
-
-
- // XS0650.prg
-
- Example
-
- The following example shows how to use the fixed keyword when you create a fixed size buffer:
-
-
- // This code must appear in an unsafe block.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0652.xml b/docs/Help_Spanish/Topics/XS0652.xml
deleted file mode 100644
index 849ed5cc71..0000000000
--- a/docs/Help_Spanish/Topics/XS0652.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0652
-
- XS0652
-
-
-
- Warning XS0652
-
- Comparison to integral constant is useless; the constant is outside the range of type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0653.xml b/docs/Help_Spanish/Topics/XS0653.xml
deleted file mode 100644
index a4026e8cc5..0000000000
--- a/docs/Help_Spanish/Topics/XS0653.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0653
-
-XS0653
-
-
-
- Error XS0653
-
- Cannot apply attribute class '{0}' because it is abstract
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0655.xml b/docs/Help_Spanish/Topics/XS0655.xml
deleted file mode 100644
index 488740bd10..0000000000
--- a/docs/Help_Spanish/Topics/XS0655.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0655
-
-XS0655
-
-
-
- Error XS0655
-
- '{0}' is not a valid named attribute argument because it is not a valid attribute parameter type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0656.xml b/docs/Help_Spanish/Topics/XS0656.xml
deleted file mode 100644
index 27e67c3f30..0000000000
--- a/docs/Help_Spanish/Topics/XS0656.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0656
-
-XS0656
-
-
-
- Error XS0656
-
- Missing compiler required member '{0}.{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0657.xml b/docs/Help_Spanish/Topics/XS0657.xml
deleted file mode 100644
index 0807196eb2..0000000000
--- a/docs/Help_Spanish/Topics/XS0657.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0657
-
- XS0657
-
-
-
- Warning XS0657
-
- '{0}' is not a valid attribute location for this declaration. Valid attribute locations for this declaration are '{1}'. All attributes in this block will be ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0658.xml b/docs/Help_Spanish/Topics/XS0658.xml
deleted file mode 100644
index 2a20384c00..0000000000
--- a/docs/Help_Spanish/Topics/XS0658.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0658
-
- XS0658
-
-
-
- Warning XS0658
-
- '{0}' is not a recognized attribute location. All attributes in this block will be ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0659.xml b/docs/Help_Spanish/Topics/XS0659.xml
deleted file mode 100644
index d32caddaae..0000000000
--- a/docs/Help_Spanish/Topics/XS0659.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0659
-
- XS0659
-
-
-
- Warning XS0659
-
- '{0}' overrides Object.Equals(object o) but does not override Object.GetHashCode()
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0660.xml b/docs/Help_Spanish/Topics/XS0660.xml
deleted file mode 100644
index d6675e95cb..0000000000
--- a/docs/Help_Spanish/Topics/XS0660.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0660
-
- XS0660
-
-
-
- Warning XS0660
-
- '{0}' defines operator == or operator != but does not override Object.Equals(object o)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0661.xml b/docs/Help_Spanish/Topics/XS0661.xml
deleted file mode 100644
index 9e61cade0d..0000000000
--- a/docs/Help_Spanish/Topics/XS0661.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0661
-
- XS0661
-
-
-
- Warning XS0661
-
- '{0}' defines operator == or operator != but does not override Object.GetHashCode()
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0662.xml b/docs/Help_Spanish/Topics/XS0662.xml
deleted file mode 100644
index 71063a562b..0000000000
--- a/docs/Help_Spanish/Topics/XS0662.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0662
-
-XS0662
-
-
-
- Error XS0662
-
- Cannot specify only Out attribute on a ref parameter. Use both In and Out attributes, or neither.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0663.xml b/docs/Help_Spanish/Topics/XS0663.xml
deleted file mode 100644
index e900dae4a1..0000000000
--- a/docs/Help_Spanish/Topics/XS0663.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0663
-
-XS0663
-
-
-
- Error XS0663
-
- '{0}' cannot define overloaded methods that differ only on ref and out
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0664.xml b/docs/Help_Spanish/Topics/XS0664.xml
deleted file mode 100644
index 15f3f9d098..0000000000
--- a/docs/Help_Spanish/Topics/XS0664.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0664
-
-XS0664
-
-
-
- Error XS0664
-
- Literal of type double cannot be implicitly converted to type '{1}'; use an '{0}' suffix to create a literal of this type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0665.xml b/docs/Help_Spanish/Topics/XS0665.xml
deleted file mode 100644
index f2ec573ff9..0000000000
--- a/docs/Help_Spanish/Topics/XS0665.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0665
-
- XS0665
-
-
-
- Warning XS0665
-
- Assignment in conditional expression is always constant; did you mean to use == instead of := ?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0666.xml b/docs/Help_Spanish/Topics/XS0666.xml
deleted file mode 100644
index 3a7e17ea83..0000000000
--- a/docs/Help_Spanish/Topics/XS0666.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0666
-
- XS0666
-
-
-
- Warning XS0666
-
- '{0}': new protected member declared in struct
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0668.xml b/docs/Help_Spanish/Topics/XS0668.xml
deleted file mode 100644
index 60b631d97f..0000000000
--- a/docs/Help_Spanish/Topics/XS0668.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0668
-
-XS0668
-
-
-
- Error XS0668
-
- Two indexers have different names; the IndexerName attribute must be used with the same name on every indexer within a type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0669.xml b/docs/Help_Spanish/Topics/XS0669.xml
deleted file mode 100644
index 3c78f8963c..0000000000
--- a/docs/Help_Spanish/Topics/XS0669.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0669
-
-XS0669
-
-
-
- Error XS0669
-
- A class with the ComImport attribute cannot have a user-defined constructor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0670.xml b/docs/Help_Spanish/Topics/XS0670.xml
deleted file mode 100644
index 4ae3a85e2f..0000000000
--- a/docs/Help_Spanish/Topics/XS0670.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0670
-
-XS0670
-
-
-
- Error XS0670
-
- Field cannot have void type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0672.xml b/docs/Help_Spanish/Topics/XS0672.xml
deleted file mode 100644
index c51a04dee6..0000000000
--- a/docs/Help_Spanish/Topics/XS0672.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0672
-
- XS0672
-
-
-
- Warning XS0672
-
- Member '{0}' overrides obsolete member '{1}'. Add the Obsolete attribute to '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0673.xml b/docs/Help_Spanish/Topics/XS0673.xml
deleted file mode 100644
index 0c49a4bb4d..0000000000
--- a/docs/Help_Spanish/Topics/XS0673.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0673
-
-XS0673
-
-
-
- Error XS0673
-
- System.Void cannot be used from X# -- use typeof(void) to get the void type object
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0674.xml b/docs/Help_Spanish/Topics/XS0674.xml
deleted file mode 100644
index 3a1407542a..0000000000
--- a/docs/Help_Spanish/Topics/XS0674.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0674
-
-XS0674
-
-
-
- Error XS0674
-
- Do not use 'System.ParamArrayAttribute'. Use the 'params' keyword instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0675.xml b/docs/Help_Spanish/Topics/XS0675.xml
deleted file mode 100644
index dbeed9e216..0000000000
--- a/docs/Help_Spanish/Topics/XS0675.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS0675
-
- XS0675
-
-
-
- Warning XS0675
-
- Bitwise-or operator used on a sign-extended operand; consider casting to a smaller unsigned type first
-
- The compiler implicitly widened and sign-extended a variable, and then used the resulting value in a bitwise OR operation. This can result in unexpected behavior.
-
- The following sample generates XS0675:
-
-
- // XS0675.prg // compile with: /W:3
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0677.xml b/docs/Help_Spanish/Topics/XS0677.xml
deleted file mode 100644
index 2b50597886..0000000000
--- a/docs/Help_Spanish/Topics/XS0677.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0677
-
-XS0677
-
-
-
- Error XS0677
-
- '{0}': a volatile field cannot be of the type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0678.xml b/docs/Help_Spanish/Topics/XS0678.xml
deleted file mode 100644
index 0b382344a4..0000000000
--- a/docs/Help_Spanish/Topics/XS0678.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0678
-
-XS0678
-
-
-
- Error XS0678
-
- '{0}': a field cannot be both volatile and readonly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0681.xml b/docs/Help_Spanish/Topics/XS0681.xml
deleted file mode 100644
index d2d5ac52d1..0000000000
--- a/docs/Help_Spanish/Topics/XS0681.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0681
-
-XS0681
-
-
-
- Error XS0681
-
- The modifier 'abstract' is not valid on fields. Try using a property instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0682.xml b/docs/Help_Spanish/Topics/XS0682.xml
deleted file mode 100644
index ef9ba5c28a..0000000000
--- a/docs/Help_Spanish/Topics/XS0682.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0682
-
-XS0682
-
-
-
- Error XS0682
-
- '{0}' cannot implement '{1}' because it is not supported by the language
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0683.xml b/docs/Help_Spanish/Topics/XS0683.xml
deleted file mode 100644
index 780094fa67..0000000000
--- a/docs/Help_Spanish/Topics/XS0683.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0683
-
-XS0683
-
-
-
- Error XS0683
-
- '{0}' explicit method implementation cannot implement '{1}' because it is an accessor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0684.xml b/docs/Help_Spanish/Topics/XS0684.xml
deleted file mode 100644
index ec55cf5b67..0000000000
--- a/docs/Help_Spanish/Topics/XS0684.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0684
-
- XS0684
-
-
-
- Warning XS0684
-
- '{0}' interface marked with 'CoClassAttribute' not marked with 'ComImportAttribute'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0685.xml b/docs/Help_Spanish/Topics/XS0685.xml
deleted file mode 100644
index 82c3ba17d7..0000000000
--- a/docs/Help_Spanish/Topics/XS0685.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0685
-
-XS0685
-
-
-
- Error XS0685
-
- Conditional member '{0}' cannot have an out parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0686.xml b/docs/Help_Spanish/Topics/XS0686.xml
deleted file mode 100644
index d0f9359fe8..0000000000
--- a/docs/Help_Spanish/Topics/XS0686.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- XS0686
-
- XS0686
-
-
-
- Error XS0686
-
- Accessor 'accessor' cannot implement interface member 'member' for type 'type'. Use an explicit interface implementation.
-
- Suggested: This error can occur when implementing an interface that contains method names which conflict with the auto-generated methods associated with a property or event. The get/set methods for properties are generated as get_property and set_property, and the add/remove methods for events are generated as add_event and remove_event. If an interface contains either of these methods, a conflict occurs. To avoid this error, implement the methods using an explicit interface implementation. To do this, specify the function as:
-
-
-
-
- Example
-
- The following sample generates XS0686:
-
-
- // XS0686.prg
-
- Example
-
- This error can also occur when declaring events. The event construct automatically generates the add_``event and remove_``event methods, which could conflict with the methods of the same name in an interface, as in the following sample:
-
-
- // XS0686b.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0687.xml b/docs/Help_Spanish/Topics/XS0687.xml
deleted file mode 100644
index b853df9453..0000000000
--- a/docs/Help_Spanish/Topics/XS0687.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0687
-
-XS0687
-
-
-
- Error XS0687
-
- The namespace alias qualifier '::' always resolves to a type or namespace so is illegal here. Consider using '.' instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0689.xml b/docs/Help_Spanish/Topics/XS0689.xml
deleted file mode 100644
index c8685b39b4..0000000000
--- a/docs/Help_Spanish/Topics/XS0689.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0689
-
-XS0689
-
-
-
- Error XS0689
-
- Cannot derive from '{0}' because it is a type parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0692.xml b/docs/Help_Spanish/Topics/XS0692.xml
deleted file mode 100644
index c7ed9286b4..0000000000
--- a/docs/Help_Spanish/Topics/XS0692.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0692
-
-XS0692
-
-
-
- Error XS0692
-
- Duplicate type parameter '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0693.xml b/docs/Help_Spanish/Topics/XS0693.xml
deleted file mode 100644
index e3b3675e18..0000000000
--- a/docs/Help_Spanish/Topics/XS0693.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0693
-
- XS0693
-
-
-
- Warning XS0693
-
- Type parameter '{0}' has the same name as the type parameter from outer type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0694.xml b/docs/Help_Spanish/Topics/XS0694.xml
deleted file mode 100644
index 000da30fe9..0000000000
--- a/docs/Help_Spanish/Topics/XS0694.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0694
-
-XS0694
-
-
-
- Error XS0694
-
- Type parameter '{0}' has the same name as the containing type, or method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0695.xml b/docs/Help_Spanish/Topics/XS0695.xml
deleted file mode 100644
index d054a708be..0000000000
--- a/docs/Help_Spanish/Topics/XS0695.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0695
-
-XS0695
-
-
-
- Error XS0695
-
- '{0}' cannot implement both '{1}' and '{2}' because they may unify for some type parameter substitutions
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0698.xml b/docs/Help_Spanish/Topics/XS0698.xml
deleted file mode 100644
index fc668ebcdb..0000000000
--- a/docs/Help_Spanish/Topics/XS0698.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0698
-
-XS0698
-
-
-
- Error XS0698
-
- A generic type cannot derive from '{0}' because it is an attribute class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0699.xml b/docs/Help_Spanish/Topics/XS0699.xml
deleted file mode 100644
index 46757c4c86..0000000000
--- a/docs/Help_Spanish/Topics/XS0699.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0699
-
-XS0699
-
-
-
- Error XS0699
-
- '{1}' does not define type parameter '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0701.xml b/docs/Help_Spanish/Topics/XS0701.xml
deleted file mode 100644
index c3e442823f..0000000000
--- a/docs/Help_Spanish/Topics/XS0701.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0701
-
-XS0701
-
-
-
- Error XS0701
-
- '{0}' is not a valid constraint. A type used as a constraint must be an interface, a non-sealed class or a type parameter.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0702.xml b/docs/Help_Spanish/Topics/XS0702.xml
deleted file mode 100644
index 145c23667b..0000000000
--- a/docs/Help_Spanish/Topics/XS0702.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS0702
-
- XS0702
-
-
-
- Error XS0702
-
- Constraint cannot be special class 'identifier'
-
- The following types may not be used as constraints: System.Object,``System.Array, System.Delegate, System.Enum, or System.ValueType.
- Example
-
- The following sample generates XS0702:
-
-
- // XS0702.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0703.xml b/docs/Help_Spanish/Topics/XS0703.xml
deleted file mode 100644
index 85d96f4cd0..0000000000
--- a/docs/Help_Spanish/Topics/XS0703.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS0703
-
- XS0703
-
-
-
- Error XS0703
-
- Inconsistent accessibility: constraint type 'identifier' is less accessible than 'identifier'
-
- A constraint may not force the generic parameter to be less accessible than the generic class itself. In the following example, while the generic class C<T> is declared public, the constraint attempts to force T to implement an internal interface. Even if this were allowed, only clients with internal access would be able to create the parameter for the class, so in effect, the class could be used only by clients with internal access.
-
- To get rid of this error, make sure the access level of the generic class is not less restrictive than any classes or interfaces that appear in the bounds.
-
- The following sample generates XS0703:
-
-
- // XS0703.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0704.xml b/docs/Help_Spanish/Topics/XS0704.xml
deleted file mode 100644
index 25ad72955c..0000000000
--- a/docs/Help_Spanish/Topics/XS0704.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0704
-
-XS0704
-
-
-
- Error XS0704
-
- Cannot do member lookup in '{0}' because it is a type parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0706.xml b/docs/Help_Spanish/Topics/XS0706.xml
deleted file mode 100644
index f81b4d2c2f..0000000000
--- a/docs/Help_Spanish/Topics/XS0706.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0706
-
-XS0706
-
-
-
- Error XS0706
-
- Invalid constraint type. A type used as a constraint must be an interface, a non-sealed class or a type parameter.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0708.xml b/docs/Help_Spanish/Topics/XS0708.xml
deleted file mode 100644
index ec9cb68375..0000000000
--- a/docs/Help_Spanish/Topics/XS0708.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0708
-
-XS0708
-
-
-
- Error XS0708
-
- '{0}': cannot declare instance members in a static class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0709.xml b/docs/Help_Spanish/Topics/XS0709.xml
deleted file mode 100644
index 6e70144cc8..0000000000
--- a/docs/Help_Spanish/Topics/XS0709.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0709
-
-XS0709
-
-
-
- Error XS0709
-
- '{1}': cannot derive from static class '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0710.xml b/docs/Help_Spanish/Topics/XS0710.xml
deleted file mode 100644
index 36bd275e5b..0000000000
--- a/docs/Help_Spanish/Topics/XS0710.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0710
-
-XS0710
-
-
-
- Error XS0710
-
- Static classes cannot have instance constructors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0711.xml b/docs/Help_Spanish/Topics/XS0711.xml
deleted file mode 100644
index 6d4593ae9a..0000000000
--- a/docs/Help_Spanish/Topics/XS0711.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0711
-
-XS0711
-
-
-
- Error XS0711
-
- Static classes cannot contain destructors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0712.xml b/docs/Help_Spanish/Topics/XS0712.xml
deleted file mode 100644
index 6f365a9902..0000000000
--- a/docs/Help_Spanish/Topics/XS0712.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0712
-
-XS0712
-
-
-
- Error XS0712
-
- Cannot create an instance of the static class '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0713.xml b/docs/Help_Spanish/Topics/XS0713.xml
deleted file mode 100644
index 11fc4d7201..0000000000
--- a/docs/Help_Spanish/Topics/XS0713.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0713
-
- XS0713
-
-
-
- Warning XS0713
-
- Static class '{0}' cannot derive from type '{1}'. Static classes must derive from object.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0714.xml b/docs/Help_Spanish/Topics/XS0714.xml
deleted file mode 100644
index c29eda1c2c..0000000000
--- a/docs/Help_Spanish/Topics/XS0714.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0714
-
-XS0714
-
-
-
- Error XS0714
-
- '{0}': static classes cannot implement interfaces
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0715.xml b/docs/Help_Spanish/Topics/XS0715.xml
deleted file mode 100644
index cadf305f44..0000000000
--- a/docs/Help_Spanish/Topics/XS0715.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0715
-
-XS0715
-
-
-
- Error XS0715
-
- '{0}': static classes cannot contain user-defined operators
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0716.xml b/docs/Help_Spanish/Topics/XS0716.xml
deleted file mode 100644
index 03f60e5951..0000000000
--- a/docs/Help_Spanish/Topics/XS0716.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0716
-
-XS0716
-
-
-
- Error XS0716
-
- Cannot convert to static type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0717.xml b/docs/Help_Spanish/Topics/XS0717.xml
deleted file mode 100644
index 3fc54c5b28..0000000000
--- a/docs/Help_Spanish/Topics/XS0717.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0717
-
-XS0717
-
-
-
- Error XS0717
-
- '{0}': static classes cannot be used as constraints
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0718.xml b/docs/Help_Spanish/Topics/XS0718.xml
deleted file mode 100644
index 16313b7832..0000000000
--- a/docs/Help_Spanish/Topics/XS0718.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0718
-
-XS0718
-
-
-
- Error XS0718
-
- '{0}': static types cannot be used as type arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0719.xml b/docs/Help_Spanish/Topics/XS0719.xml
deleted file mode 100644
index cce5f699a1..0000000000
--- a/docs/Help_Spanish/Topics/XS0719.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0719
-
-XS0719
-
-
-
- Error XS0719
-
- '{0}': array elements cannot be of static type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0720.xml b/docs/Help_Spanish/Topics/XS0720.xml
deleted file mode 100644
index 6a699e17e8..0000000000
--- a/docs/Help_Spanish/Topics/XS0720.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0720
-
-XS0720
-
-
-
- Error XS0720
-
- '{0}': cannot declare indexers in a static class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0721.xml b/docs/Help_Spanish/Topics/XS0721.xml
deleted file mode 100644
index 995168a56a..0000000000
--- a/docs/Help_Spanish/Topics/XS0721.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0721
-
-XS0721
-
-
-
- Error XS0721
-
- '{0}': static types cannot be used as parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0722.xml b/docs/Help_Spanish/Topics/XS0722.xml
deleted file mode 100644
index b0f88f9066..0000000000
--- a/docs/Help_Spanish/Topics/XS0722.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0722
-
-XS0722
-
-
-
- Error XS0722
-
- '{0}': static types cannot be used as return types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0723.xml b/docs/Help_Spanish/Topics/XS0723.xml
deleted file mode 100644
index f8636b3525..0000000000
--- a/docs/Help_Spanish/Topics/XS0723.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0723
-
-XS0723
-
-
-
- Error XS0723
-
- Cannot declare a variable of static type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0724.xml b/docs/Help_Spanish/Topics/XS0724.xml
deleted file mode 100644
index 661c42f156..0000000000
--- a/docs/Help_Spanish/Topics/XS0724.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0724
-
-XS0724
-
-
-
- Error XS0724
-
- A throw statement with no arguments is not allowed in a finally clause that is nested inside the nearest enclosing catch clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0726.xml b/docs/Help_Spanish/Topics/XS0726.xml
deleted file mode 100644
index 9d6e7b5599..0000000000
--- a/docs/Help_Spanish/Topics/XS0726.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0726
-
-XS0726
-
-
-
- Error XS0726
-
- '{0}' is not a valid format specifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0728.xml b/docs/Help_Spanish/Topics/XS0728.xml
deleted file mode 100644
index d79f22f314..0000000000
--- a/docs/Help_Spanish/Topics/XS0728.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0728
-
- XS0728
-
-
-
- Warning XS0728
-
- Possibly incorrect assignment to local '{0}' which is the argument to a using or lock statement. The Dispose call or unlocking will happen on the original value of the local.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0729.xml b/docs/Help_Spanish/Topics/XS0729.xml
deleted file mode 100644
index 5abab56550..0000000000
--- a/docs/Help_Spanish/Topics/XS0729.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0729
-
-XS0729
-
-
-
- Error XS0729
-
- Type '{0}' is defined in this assembly, but a type forwarder is specified for it
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0730.xml b/docs/Help_Spanish/Topics/XS0730.xml
deleted file mode 100644
index cc45089f3a..0000000000
--- a/docs/Help_Spanish/Topics/XS0730.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0730
-
-XS0730
-
-
-
- Error XS0730
-
- Cannot forward type '{0}' because it is a nested type of '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0731.xml b/docs/Help_Spanish/Topics/XS0731.xml
deleted file mode 100644
index b4c8dfbc7e..0000000000
--- a/docs/Help_Spanish/Topics/XS0731.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- XS0731
-
- XS0731
-
-
-
- Error XS0731
-
- The type forwarder for type 'type' in assembly 'assembly' causes a cycle
-
- This error can only occur with improperly formed imported metadata. It cannot occur with only X# source.
- Example
-
- The following sample generates XS0731. The example consists of three files:
-
-
-
Circular.IL
-
Circular2.IL
-
XS0731.prg
-
-
- First compile the .IL files as libraries, and then compile the .prg code referencing the two files.
-
-
- // Circular.il // compile with: /DLL /out=Circular.dll
-
-
-
- // Circular2.il // compile with: /DLL /out=Circular2.dll
-
-
-
- // XS0731.prg // compile with: /reference:circular.dll /reference:circular2.dll
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0734.xml b/docs/Help_Spanish/Topics/XS0734.xml
deleted file mode 100644
index aa34242adf..0000000000
--- a/docs/Help_Spanish/Topics/XS0734.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0734
-
-XS0734
-
-
-
- Error XS0734
-
- The /moduleassemblyname option may only be specified when building a target type of 'module'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0735.xml b/docs/Help_Spanish/Topics/XS0735.xml
deleted file mode 100644
index 2220083c05..0000000000
--- a/docs/Help_Spanish/Topics/XS0735.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0735
-
-XS0735
-
-
-
- Error XS0735
-
- Invalid type specified as an argument for TypeForwardedTo attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0736.xml b/docs/Help_Spanish/Topics/XS0736.xml
deleted file mode 100644
index a441a83549..0000000000
--- a/docs/Help_Spanish/Topics/XS0736.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0736
-
-XS0736
-
-
-
- Error XS0736
-
- '{0}' does not implement interface member '{1}'. '{2}' cannot implement an interface member because it is static.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0737.xml b/docs/Help_Spanish/Topics/XS0737.xml
deleted file mode 100644
index 6502031cf8..0000000000
--- a/docs/Help_Spanish/Topics/XS0737.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0737
-
-XS0737
-
-
-
- Error XS0737
-
- '{0}' does not implement interface member '{1}'. '{2}' cannot implement an interface member because it is not public.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0738.xml b/docs/Help_Spanish/Topics/XS0738.xml
deleted file mode 100644
index 9be6145940..0000000000
--- a/docs/Help_Spanish/Topics/XS0738.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0738
-
-XS0738
-
-
-
- Error XS0738
-
- '{0}' does not implement interface member '{1}'. '{2}' cannot implement '{1}' because it does not have the matching return type of '{3}' or because the name does not match exactly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0739.xml b/docs/Help_Spanish/Topics/XS0739.xml
deleted file mode 100644
index 7923f9bb51..0000000000
--- a/docs/Help_Spanish/Topics/XS0739.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0739
-
-XS0739
-
-
-
- Error XS0739
-
- '{0}' duplicate TypeForwardedToAttribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0742.xml b/docs/Help_Spanish/Topics/XS0742.xml
deleted file mode 100644
index 936eb6b885..0000000000
--- a/docs/Help_Spanish/Topics/XS0742.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0742
-
-XS0742
-
-
-
- Error XS0742
-
- A query body must end with a select clause or a group clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0743.xml b/docs/Help_Spanish/Topics/XS0743.xml
deleted file mode 100644
index 66596ad21c..0000000000
--- a/docs/Help_Spanish/Topics/XS0743.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0743
-
-XS0743
-
-
-
- Error XS0743
-
- Expected contextual keyword 'on'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0744.xml b/docs/Help_Spanish/Topics/XS0744.xml
deleted file mode 100644
index 6ad42093b3..0000000000
--- a/docs/Help_Spanish/Topics/XS0744.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0744
-
-XS0744
-
-
-
- Error XS0744
-
- Expected contextual keyword 'equals'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0745.xml b/docs/Help_Spanish/Topics/XS0745.xml
deleted file mode 100644
index 63808f9d8d..0000000000
--- a/docs/Help_Spanish/Topics/XS0745.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0745
-
-XS0745
-
-
-
- Error XS0745
-
- Expected contextual keyword 'by'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0746.xml b/docs/Help_Spanish/Topics/XS0746.xml
deleted file mode 100644
index 0dc6ea25b5..0000000000
--- a/docs/Help_Spanish/Topics/XS0746.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0746
-
-XS0746
-
-
-
- Error XS0746
-
- Invalid anonymous type member declarator. Anonymous type members must be declared with a member assignment, simple name or member access.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0747.xml b/docs/Help_Spanish/Topics/XS0747.xml
deleted file mode 100644
index e8310746dd..0000000000
--- a/docs/Help_Spanish/Topics/XS0747.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0747
-
-XS0747
-
-
-
- Error XS0747
-
- Invalid initializer member declarator
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0748.xml b/docs/Help_Spanish/Topics/XS0748.xml
deleted file mode 100644
index 64108473df..0000000000
--- a/docs/Help_Spanish/Topics/XS0748.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0748
-
-XS0748
-
-
-
- Error XS0748
-
- Inconsistent lambda parameter usage; parameter types must be all explicit or all implicit
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0750.xml b/docs/Help_Spanish/Topics/XS0750.xml
deleted file mode 100644
index 60232d8335..0000000000
--- a/docs/Help_Spanish/Topics/XS0750.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0750
-
-XS0750
-
-
-
- Error XS0750
-
- A partial method cannot have access modifiers or the virtual, abstract, override, new, sealed, or extern modifiers
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0751.xml b/docs/Help_Spanish/Topics/XS0751.xml
deleted file mode 100644
index 67b13bbacc..0000000000
--- a/docs/Help_Spanish/Topics/XS0751.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0751
-
-XS0751
-
-
-
- Error XS0751
-
- A partial method must be declared within a partial class or partial struct
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0752.xml b/docs/Help_Spanish/Topics/XS0752.xml
deleted file mode 100644
index 8a6bdedd6a..0000000000
--- a/docs/Help_Spanish/Topics/XS0752.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0752
-
-XS0752
-
-
-
- Error XS0752
-
- A partial method cannot have out parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0753.xml b/docs/Help_Spanish/Topics/XS0753.xml
deleted file mode 100644
index 61cb187e50..0000000000
--- a/docs/Help_Spanish/Topics/XS0753.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0753
-
-XS0753
-
-
-
- Error XS0753
-
- Only methods, classes, structs, or interfaces may be partial
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0754.xml b/docs/Help_Spanish/Topics/XS0754.xml
deleted file mode 100644
index 8daea666ad..0000000000
--- a/docs/Help_Spanish/Topics/XS0754.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0754
-
-XS0754
-
-
-
- Error XS0754
-
- A partial method may not explicitly implement an interface method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0755.xml b/docs/Help_Spanish/Topics/XS0755.xml
deleted file mode 100644
index 9b560f9119..0000000000
--- a/docs/Help_Spanish/Topics/XS0755.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0755
-
-XS0755
-
-
-
- Error XS0755
-
- Both partial method declarations must be extension methods or neither may be an extension method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0756.xml b/docs/Help_Spanish/Topics/XS0756.xml
deleted file mode 100644
index 9470562a15..0000000000
--- a/docs/Help_Spanish/Topics/XS0756.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0756
-
-XS0756
-
-
-
- Error XS0756
-
- A partial method may not have multiple defining declarations
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0757.xml b/docs/Help_Spanish/Topics/XS0757.xml
deleted file mode 100644
index d24f8c1c83..0000000000
--- a/docs/Help_Spanish/Topics/XS0757.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0757
-
-XS0757
-
-
-
- Error XS0757
-
- A partial method may not have multiple implementing declarations
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0758.xml b/docs/Help_Spanish/Topics/XS0758.xml
deleted file mode 100644
index f6f20ded4e..0000000000
--- a/docs/Help_Spanish/Topics/XS0758.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0758
-
-XS0758
-
-
-
- Error XS0758
-
- Both partial method declarations must use a params parameter or neither may use a params parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0759.xml b/docs/Help_Spanish/Topics/XS0759.xml
deleted file mode 100644
index 582ebedb68..0000000000
--- a/docs/Help_Spanish/Topics/XS0759.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0759
-
-XS0759
-
-
-
- Error XS0759
-
- No defining declaration found for implementing declaration of partial method '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0761.xml b/docs/Help_Spanish/Topics/XS0761.xml
deleted file mode 100644
index a706fdec57..0000000000
--- a/docs/Help_Spanish/Topics/XS0761.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0761
-
-XS0761
-
-
-
- Error XS0761
-
- Partial method declarations of '{0}' have inconsistent type parameter constraints
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0762.xml b/docs/Help_Spanish/Topics/XS0762.xml
deleted file mode 100644
index 873411413f..0000000000
--- a/docs/Help_Spanish/Topics/XS0762.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0762
-
-XS0762
-
-
-
- Error XS0762
-
- Cannot create delegate from method '{0}' because it is a partial method without an implementing declaration
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0763.xml b/docs/Help_Spanish/Topics/XS0763.xml
deleted file mode 100644
index 424922c2f0..0000000000
--- a/docs/Help_Spanish/Topics/XS0763.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0763
-
-XS0763
-
-
-
- Error XS0763
-
- Both partial method declarations must be static or neither may be static
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0764.xml b/docs/Help_Spanish/Topics/XS0764.xml
deleted file mode 100644
index 88618bdf0b..0000000000
--- a/docs/Help_Spanish/Topics/XS0764.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0764
-
-XS0764
-
-
-
- Error XS0764
-
- Both partial method declarations must be unsafe or neither may be unsafe
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0765.xml b/docs/Help_Spanish/Topics/XS0765.xml
deleted file mode 100644
index d9d51ddbff..0000000000
--- a/docs/Help_Spanish/Topics/XS0765.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0765
-
-XS0765
-
-
-
- Error XS0765
-
- Partial methods with only a defining declaration or removed conditional methods cannot be used in expression trees
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0766.xml b/docs/Help_Spanish/Topics/XS0766.xml
deleted file mode 100644
index 0b2c25703b..0000000000
--- a/docs/Help_Spanish/Topics/XS0766.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0766
-
-XS0766
-
-
-
- Error XS0766
-
- Partial methods must have a void return type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0767.xml b/docs/Help_Spanish/Topics/XS0767.xml
deleted file mode 100644
index f623ad166a..0000000000
--- a/docs/Help_Spanish/Topics/XS0767.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0767
-
-XS0767
-
-
-
- Error XS0767
-
- Cannot inherit interface '{0}' with the specified type parameters because it causes method '{1}' to contain overloads which differ only on ref and out
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0768.xml b/docs/Help_Spanish/Topics/XS0768.xml
deleted file mode 100644
index dada32bfe0..0000000000
--- a/docs/Help_Spanish/Topics/XS0768.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0768
-
-XS0768
-
-
-
- Error XS0768
-
- Constructor '{0}' cannot call itself through another constructor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0809.xml b/docs/Help_Spanish/Topics/XS0809.xml
deleted file mode 100644
index 09071723eb..0000000000
--- a/docs/Help_Spanish/Topics/XS0809.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0809
-
- XS0809
-
-
-
- Warning XS0809
-
- Obsolete member '{0}' overrides non-obsolete member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0811.xml b/docs/Help_Spanish/Topics/XS0811.xml
deleted file mode 100644
index c56867c95c..0000000000
--- a/docs/Help_Spanish/Topics/XS0811.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0811
-
- XS0811
-
-
-
- Warning XS0811
-
- The fully qualified name for '{0}' is too long for debug information. Compile without '/debug' option.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0815.xml b/docs/Help_Spanish/Topics/XS0815.xml
deleted file mode 100644
index cf304055f7..0000000000
--- a/docs/Help_Spanish/Topics/XS0815.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0815
-
-XS0815
-
-
-
- Error XS0815
-
- Cannot assign {0} to an implicitly-typed variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0818.xml b/docs/Help_Spanish/Topics/XS0818.xml
deleted file mode 100644
index 0566f833b8..0000000000
--- a/docs/Help_Spanish/Topics/XS0818.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0818
-
-XS0818
-
-
-
- Error XS0818
-
- Implicitly-typed variables must be initialized
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0819.xml b/docs/Help_Spanish/Topics/XS0819.xml
deleted file mode 100644
index c77cff0328..0000000000
--- a/docs/Help_Spanish/Topics/XS0819.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0819
-
-XS0819
-
-
-
- Error XS0819
-
- Implicitly-typed variables cannot have multiple declarators
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0820.xml b/docs/Help_Spanish/Topics/XS0820.xml
deleted file mode 100644
index 3ab867c2a3..0000000000
--- a/docs/Help_Spanish/Topics/XS0820.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0820
-
-XS0820
-
-
-
- Error XS0820
-
- Cannot initialize an implicitly-typed variable with an array initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0821.xml b/docs/Help_Spanish/Topics/XS0821.xml
deleted file mode 100644
index 6d00948b18..0000000000
--- a/docs/Help_Spanish/Topics/XS0821.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0821
-
-XS0821
-
-
-
- Error XS0821
-
- Implicitly-typed local variables cannot be fixed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0822.xml b/docs/Help_Spanish/Topics/XS0822.xml
deleted file mode 100644
index 413e4d5a48..0000000000
--- a/docs/Help_Spanish/Topics/XS0822.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0822
-
-XS0822
-
-
-
- Error XS0822
-
- Implicitly-typed variables cannot be constant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0824.xml b/docs/Help_Spanish/Topics/XS0824.xml
deleted file mode 100644
index e201b50dfa..0000000000
--- a/docs/Help_Spanish/Topics/XS0824.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS0824
-
- XS0824
-
-
-
- Warning XS0824
-
- Constructor '{0}' is marked external
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0825.xml b/docs/Help_Spanish/Topics/XS0825.xml
deleted file mode 100644
index e493845e9a..0000000000
--- a/docs/Help_Spanish/Topics/XS0825.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0825
-
-XS0825
-
-
-
- Error XS0825
-
- The contextual keyword 'var' may only appear within a local variable declaration or in script code
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0826.xml b/docs/Help_Spanish/Topics/XS0826.xml
deleted file mode 100644
index 9a945e410c..0000000000
--- a/docs/Help_Spanish/Topics/XS0826.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- XS0826
-
- XS0826
-
-
-
- Error XS0826
-
- No best type found for implicitly typed array.
-
- Array elements must all be the same type or implicitly convertible to the same type according to the type inference rules used by the compiler. The best type must be one of the types present in the array expression. Elements will not be converted to a new type such as object. For an implicitly typed array, the compiler must infer the array type based on the type of elements assigned to it.
-
- To correct this error
-
-
-
Give the array an explicit type.
-
Give all array elements the same type.
-
Provide explicit casts on those elements that might be causing the problem.
-
- Example
-
- The following code generates XS0826 because the array elements are not all the same type, and the compiler's type inference logic does not find a single best type:
-
-
- // XS0826.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0828.xml b/docs/Help_Spanish/Topics/XS0828.xml
deleted file mode 100644
index e40032ca4e..0000000000
--- a/docs/Help_Spanish/Topics/XS0828.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0828
-
-XS0828
-
-
-
- Error XS0828
-
- Cannot assign {0} to anonymous type property
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0831.xml b/docs/Help_Spanish/Topics/XS0831.xml
deleted file mode 100644
index 5f8d2bd047..0000000000
--- a/docs/Help_Spanish/Topics/XS0831.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0831
-
-XS0831
-
-
-
- Error XS0831
-
- An expression tree may not contain a base access
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0832.xml b/docs/Help_Spanish/Topics/XS0832.xml
deleted file mode 100644
index 3081496424..0000000000
--- a/docs/Help_Spanish/Topics/XS0832.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0832
-
-XS0832
-
-
-
- Error XS0832
-
- An expression tree may not contain an assignment operator
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0833.xml b/docs/Help_Spanish/Topics/XS0833.xml
deleted file mode 100644
index 482e69b896..0000000000
--- a/docs/Help_Spanish/Topics/XS0833.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0833
-
-XS0833
-
-
-
- Error XS0833
-
- An anonymous type cannot have multiple properties with the same name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0834.xml b/docs/Help_Spanish/Topics/XS0834.xml
deleted file mode 100644
index 683a02f054..0000000000
--- a/docs/Help_Spanish/Topics/XS0834.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- XS0834
-
- XS0834
-
-
-
- Error XS0834
-
- A lambda expression must have an expression body to be converted to an expression tree.
-
- Lambdas that are translated to expression trees must be expression lambdas; statement lambdas and anonymous methods can only be converted to delegate types.
-
- To correct this error
-
-
-
Remove the statement from the lambda expression.
-
- Example
-
- The following example generates XS0834:
-
-
- // XS0834.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0835.xml b/docs/Help_Spanish/Topics/XS0835.xml
deleted file mode 100644
index 1c8fad147d..0000000000
--- a/docs/Help_Spanish/Topics/XS0835.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0835
-
-XS0835
-
-
-
- Error XS0835
-
- Cannot convert lambda to an expression tree whose type argument '{0}' is not a delegate type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0836.xml b/docs/Help_Spanish/Topics/XS0836.xml
deleted file mode 100644
index f29a11e2dc..0000000000
--- a/docs/Help_Spanish/Topics/XS0836.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0836
-
-XS0836
-
-
-
- Error XS0836
-
- Cannot use anonymous type in a constant expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0837.xml b/docs/Help_Spanish/Topics/XS0837.xml
deleted file mode 100644
index 68afdbb39d..0000000000
--- a/docs/Help_Spanish/Topics/XS0837.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0837
-
-XS0837
-
-
-
- Error XS0837
-
- The first operand of an 'is' or 'as' operator may not be a lambda expression, anonymous method, or method group.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0838.xml b/docs/Help_Spanish/Topics/XS0838.xml
deleted file mode 100644
index d072d49dc4..0000000000
--- a/docs/Help_Spanish/Topics/XS0838.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0838
-
-XS0838
-
-
-
- Error XS0838
-
- An expression tree may not contain a multidimensional array initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0839.xml b/docs/Help_Spanish/Topics/XS0839.xml
deleted file mode 100644
index 45d4a47af3..0000000000
--- a/docs/Help_Spanish/Topics/XS0839.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0839
-
-XS0839
-
-
-
- Error XS0839
-
- Argument missing
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0841.xml b/docs/Help_Spanish/Topics/XS0841.xml
deleted file mode 100644
index 66a324dc65..0000000000
--- a/docs/Help_Spanish/Topics/XS0841.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0841
-
-XS0841
-
-
-
- Error XS0841
-
- Cannot use local variable '{0}' before it is declared
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0842.xml b/docs/Help_Spanish/Topics/XS0842.xml
deleted file mode 100644
index 07de50d537..0000000000
--- a/docs/Help_Spanish/Topics/XS0842.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0842
-
-XS0842
-
-
-
- Error XS0842
-
- '{0}': Auto-implemented properties cannot be used inside a type marked with StructLayout(LayoutKind.Explicit)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0843.xml b/docs/Help_Spanish/Topics/XS0843.xml
deleted file mode 100644
index 34337379e2..0000000000
--- a/docs/Help_Spanish/Topics/XS0843.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- XS0843
-
- XS0843
-
-
-
- Error XS0843
-
- Backing field for automatically implemented property 'name' must be fully assigned before control is returned to the caller. Consider calling the default constructor from a constructor initializer.
-
- To assign a value to an automatically-implemented property from a constructor, you must first invoke the default constructor to create the object.
- To correct this error
-
-
-
Add a call to the default constructor in a constructor initializer as shown in the following example. Note the use of : this(). For more information, see this.
-
- Example
-
- The following code generates XS0843:
-
-
- // XS0843.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS0844.xml b/docs/Help_Spanish/Topics/XS0844.xml
deleted file mode 100644
index c09a2eb924..0000000000
--- a/docs/Help_Spanish/Topics/XS0844.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0844
-
-XS0844
-
-
-
- Error XS0844
-
- Cannot use local variable '{0}' before it is declared. The declaration of the local variable hides the field '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0845.xml b/docs/Help_Spanish/Topics/XS0845.xml
deleted file mode 100644
index ff33fb6115..0000000000
--- a/docs/Help_Spanish/Topics/XS0845.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- XS0845
-
- XS0845
-
-
-
- Error XS0845
-
- An expression tree lambda may not contain a coalescing operator with a null literal left-hand side.
-
- Because null by itself does not have a type, the null coalescing operator cannot operate on it.
- To correct this error
-
-
-
Cast the null literal to an object.
-
- Example
-
- The following code generates XS0845:
-
-
- // XS0845.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0846.xml b/docs/Help_Spanish/Topics/XS0846.xml
deleted file mode 100644
index b7ab1c6214..0000000000
--- a/docs/Help_Spanish/Topics/XS0846.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0846
-
-XS0846
-
-
-
- Error XS0846
-
- A nested array initializer is expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0847.xml b/docs/Help_Spanish/Topics/XS0847.xml
deleted file mode 100644
index 079437c682..0000000000
--- a/docs/Help_Spanish/Topics/XS0847.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0847
-
-XS0847
-
-
-
- Error XS0847
-
- An array initializer of length '{0}' is expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0851.xml b/docs/Help_Spanish/Topics/XS0851.xml
deleted file mode 100644
index 75ccf945ef..0000000000
--- a/docs/Help_Spanish/Topics/XS0851.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0851
-
-XS0851
-
-
-
- Error XS0851
-
- Cannot define overloaded constructor '{0}' because it differs from another constructor only on ref and out
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0853.xml b/docs/Help_Spanish/Topics/XS0853.xml
deleted file mode 100644
index 9297bc729b..0000000000
--- a/docs/Help_Spanish/Topics/XS0853.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0853
-
-XS0853
-
-
-
- Error XS0853
-
- An expression tree may not contain a named argument specification
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0854.xml b/docs/Help_Spanish/Topics/XS0854.xml
deleted file mode 100644
index 38efe0fb69..0000000000
--- a/docs/Help_Spanish/Topics/XS0854.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0854
-
-XS0854
-
-
-
- Error XS0854
-
- An expression tree may not contain a call or invocation that uses optional arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0855.xml b/docs/Help_Spanish/Topics/XS0855.xml
deleted file mode 100644
index e2e2786c5c..0000000000
--- a/docs/Help_Spanish/Topics/XS0855.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0855
-
-XS0855
-
-
-
- Error XS0855
-
- An expression tree may not contain an indexed property
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0856.xml b/docs/Help_Spanish/Topics/XS0856.xml
deleted file mode 100644
index 4c5e811daa..0000000000
--- a/docs/Help_Spanish/Topics/XS0856.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0856
-
-XS0856
-
-
-
- Error XS0856
-
- Indexed property '{0}' has non-optional arguments which must be provided
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS0857.xml b/docs/Help_Spanish/Topics/XS0857.xml
deleted file mode 100644
index 85251c998d..0000000000
--- a/docs/Help_Spanish/Topics/XS0857.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS0857
-
-XS0857
-
-
-
- Error XS0857
-
- Indexed property '{0}' must have all arguments optional
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1001.xml b/docs/Help_Spanish/Topics/XS1001.xml
deleted file mode 100644
index 11c8786230..0000000000
--- a/docs/Help_Spanish/Topics/XS1001.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- XS1001
-
- XS1001
-
-
-
- Error XS1001
-
- Identifier expected
-
- You did not supply an identifier. An identifier is the name of a class, struct, namespace, method, variable and so on that you provide.
-
- The following example declares a simple class but does not give the class a name:
-
-
- //XS1001.prg
-
-
- Parameter names are required even if the compiler doesn't use them, for example, in an interface definition. These parameters are required so that programmers who are consuming the interface know something about the what the parameters mean.
-
-
- // XS1001-2.prg // compile with: /target:library
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1002.xml b/docs/Help_Spanish/Topics/XS1002.xml
deleted file mode 100644
index bc542b6170..0000000000
--- a/docs/Help_Spanish/Topics/XS1002.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1002
-
-XS1002
-
-
-
- Error XS1002
-
- ; expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1003.xml b/docs/Help_Spanish/Topics/XS1003.xml
deleted file mode 100644
index 39510a96bd..0000000000
--- a/docs/Help_Spanish/Topics/XS1003.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1003
-
-XS1003
-
-
-
- Error XS1003
-
- Syntax error, '{0}' expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1004.xml b/docs/Help_Spanish/Topics/XS1004.xml
deleted file mode 100644
index d5586d1708..0000000000
--- a/docs/Help_Spanish/Topics/XS1004.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1004
-
-XS1004
-
-
-
- Error XS1004
-
- Duplicate '{0}' modifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1007.xml b/docs/Help_Spanish/Topics/XS1007.xml
deleted file mode 100644
index cd92c36e56..0000000000
--- a/docs/Help_Spanish/Topics/XS1007.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1007
-
-XS1007
-
-
-
- Error XS1007
-
- Property accessor already defined
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1008.xml b/docs/Help_Spanish/Topics/XS1008.xml
deleted file mode 100644
index c8ff11a7fa..0000000000
--- a/docs/Help_Spanish/Topics/XS1008.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1008
-
-XS1008
-
-
-
- Error XS1008
-
- Type byte, sbyte, short, ushort, int, uint, long, or ulong expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1009.xml b/docs/Help_Spanish/Topics/XS1009.xml
deleted file mode 100644
index 183dd657da..0000000000
--- a/docs/Help_Spanish/Topics/XS1009.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- XS1009
-
- XS1009
-
-
-
- Error XS1009
-
- Unrecognized escape sequence
-
- An unexpected character follows a backslash (\) in a string. The compiler expects one of the valid escape characters. For more information, see Character Escapes.
-
- The following sample generates XS1009.
-
-
- // XS1009-a.prg
-
- A common cause of this error is using the backslash character in a file name, as the following example shows.
-
-
-
-
- To resolve this error, use "\\" or the @-quoted string literal, as the following example shows.
-
-
- // XS1009-b.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1010.xml b/docs/Help_Spanish/Topics/XS1010.xml
deleted file mode 100644
index c111568d76..0000000000
--- a/docs/Help_Spanish/Topics/XS1010.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1010
-
-XS1010
-
-
-
- Error XS1010
-
- Newline in constant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1011.xml b/docs/Help_Spanish/Topics/XS1011.xml
deleted file mode 100644
index 559f1e568b..0000000000
--- a/docs/Help_Spanish/Topics/XS1011.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1011
-
-XS1011
-
-
-
- Error XS1011
-
- Empty character literal
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1012.xml b/docs/Help_Spanish/Topics/XS1012.xml
deleted file mode 100644
index 3415fef6bf..0000000000
--- a/docs/Help_Spanish/Topics/XS1012.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1012
-
-XS1012
-
-
-
- Error XS1012
-
- Too many characters in character literal
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1013.xml b/docs/Help_Spanish/Topics/XS1013.xml
deleted file mode 100644
index 64babbeaf9..0000000000
--- a/docs/Help_Spanish/Topics/XS1013.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1013
-
-XS1013
-
-
-
- Error XS1013
-
- Invalid number
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1014.xml b/docs/Help_Spanish/Topics/XS1014.xml
deleted file mode 100644
index 77d101e676..0000000000
--- a/docs/Help_Spanish/Topics/XS1014.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1014
-
-XS1014
-
-
-
- Error XS1014
-
- A get or set accessor expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1015.xml b/docs/Help_Spanish/Topics/XS1015.xml
deleted file mode 100644
index d082f99f02..0000000000
--- a/docs/Help_Spanish/Topics/XS1015.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1015
-
-XS1015
-
-
-
- Error XS1015
-
- An object, string, or class type expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1016.xml b/docs/Help_Spanish/Topics/XS1016.xml
deleted file mode 100644
index e70f5f28db..0000000000
--- a/docs/Help_Spanish/Topics/XS1016.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1016
-
-XS1016
-
-
-
- Error XS1016
-
- Named attribute argument expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1017.xml b/docs/Help_Spanish/Topics/XS1017.xml
deleted file mode 100644
index 043b533c86..0000000000
--- a/docs/Help_Spanish/Topics/XS1017.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1017
-
-XS1017
-
-
-
- Error XS1017
-
- Catch clauses cannot follow the general catch clause of a try statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1018.xml b/docs/Help_Spanish/Topics/XS1018.xml
deleted file mode 100644
index f556f0d688..0000000000
--- a/docs/Help_Spanish/Topics/XS1018.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS1018
-
- XS1018
-
-
-
- Error XS1018
-
- Keyword 'SELF' or 'SUPER' expected
-
- The compiler encountered an incomplete constructor declaration.
- Example
-
- The following example generates XS1018, and suggests several ways to resolve the error:
-
-
- // XS1018.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1019.xml b/docs/Help_Spanish/Topics/XS1019.xml
deleted file mode 100644
index a07dda9a3d..0000000000
--- a/docs/Help_Spanish/Topics/XS1019.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XS1019
-
- XS1019
-
-
-
- Error XS1019
-
- Overloadable unary operator expected
-
- Something that looks like an overloaded unary operator has been declared, but the operator is missing or is in the wrong location in the signature.
-
- A unary operator is an operator that operates on a single operand. For example, ++ is a unary operator. You can overload some unary operators by using the operator keyword and specifying a single parameter of the type that the operator operates on. For example, if you want to overload the operator ++ for a user-defined class Temperature so that you can write Temperature++, you can define it in this way:
-
-
-
-
-
- When you receive this error, you have declared something that looks like an overloaded unary operator, except that the operator itself is missing or is in the wrong location in the signature. If you remove the ++ from the signature in the previous example, you will generate XS1019.
-
- The following code generates XS1019:
-
-
- // XS1019.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1020.xml b/docs/Help_Spanish/Topics/XS1020.xml
deleted file mode 100644
index 8e157aa571..0000000000
--- a/docs/Help_Spanish/Topics/XS1020.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1020
-
-XS1020
-
-
-
- Error XS1020
-
- Overloadable binary operator expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1021.xml b/docs/Help_Spanish/Topics/XS1021.xml
deleted file mode 100644
index 24f209c0b6..0000000000
--- a/docs/Help_Spanish/Topics/XS1021.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1021
-
-XS1021
-
-
-
- Error XS1021
-
- Integral constant is too large
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1022.xml b/docs/Help_Spanish/Topics/XS1022.xml
deleted file mode 100644
index f24995936c..0000000000
--- a/docs/Help_Spanish/Topics/XS1022.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1022
-
-XS1022
-
-
-
- Error XS1022
-
- Type or namespace definition, or end-of-file expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1023.xml b/docs/Help_Spanish/Topics/XS1023.xml
deleted file mode 100644
index f0113a980f..0000000000
--- a/docs/Help_Spanish/Topics/XS1023.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1023
-
-XS1023
-
-
-
- Error XS1023
-
- Embedded statement cannot be a declaration or labeled statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1024.xml b/docs/Help_Spanish/Topics/XS1024.xml
deleted file mode 100644
index 1ac25f2806..0000000000
--- a/docs/Help_Spanish/Topics/XS1024.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1024
-
-XS1024
-
-
-
- Error XS1024
-
- Preprocessor directive expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1025.xml b/docs/Help_Spanish/Topics/XS1025.xml
deleted file mode 100644
index 16d5562bc4..0000000000
--- a/docs/Help_Spanish/Topics/XS1025.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1025
-
-XS1025
-
-
-
- Error XS1025
-
- Single-line comment or end-of-line expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1026.xml b/docs/Help_Spanish/Topics/XS1026.xml
deleted file mode 100644
index 882f300f4a..0000000000
--- a/docs/Help_Spanish/Topics/XS1026.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS1026
-
- XS1026
-
-
-
- Error XS1026
-
- ) expected
-
- An incomplete statement was found.
-
- The following example generates XS1026:
-
-
- // XS1026.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1027.xml b/docs/Help_Spanish/Topics/XS1027.xml
deleted file mode 100644
index cd583231c5..0000000000
--- a/docs/Help_Spanish/Topics/XS1027.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1027
-
-XS1027
-
-
-
- Error XS1027
-
- #endif directive expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1028.xml b/docs/Help_Spanish/Topics/XS1028.xml
deleted file mode 100644
index a33b22e982..0000000000
--- a/docs/Help_Spanish/Topics/XS1028.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1028
-
-XS1028
-
-
-
- Error XS1028
-
- Unexpected preprocessor directive
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1029.xml b/docs/Help_Spanish/Topics/XS1029.xml
deleted file mode 100644
index aa088f7df1..0000000000
--- a/docs/Help_Spanish/Topics/XS1029.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- XS1029
-
- XS1029
-
-
-
- Error XS1029
-
- #error: 'text'
-
- Displays the text of an error defined with the #error directive.
-
- The following sample shows how to create a user-defined error:
-
-
- // XS1029.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS1030.xml b/docs/Help_Spanish/Topics/XS1030.xml
deleted file mode 100644
index 5a0d99fccb..0000000000
--- a/docs/Help_Spanish/Topics/XS1030.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1030
-
- XS1030
-
-
-
- Warning XS1030
-
- #warning: '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1031.xml b/docs/Help_Spanish/Topics/XS1031.xml
deleted file mode 100644
index 76d866381b..0000000000
--- a/docs/Help_Spanish/Topics/XS1031.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1031
-
-XS1031
-
-
-
- Error XS1031
-
- Type expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1032.xml b/docs/Help_Spanish/Topics/XS1032.xml
deleted file mode 100644
index 52c95e1b47..0000000000
--- a/docs/Help_Spanish/Topics/XS1032.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1032
-
-XS1032
-
-
-
- Error XS1032
-
- Cannot define/undefine preprocessor symbols after first token in file
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1035.xml b/docs/Help_Spanish/Topics/XS1035.xml
deleted file mode 100644
index 32f70c5003..0000000000
--- a/docs/Help_Spanish/Topics/XS1035.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1035
-
-XS1035
-
-
-
- Error XS1035
-
- End-of-file found, '*/' expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1037.xml b/docs/Help_Spanish/Topics/XS1037.xml
deleted file mode 100644
index 56a936bdb8..0000000000
--- a/docs/Help_Spanish/Topics/XS1037.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1037
-
-XS1037
-
-
-
- Error XS1037
-
- Overloadable operator expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1038.xml b/docs/Help_Spanish/Topics/XS1038.xml
deleted file mode 100644
index d71b2a2166..0000000000
--- a/docs/Help_Spanish/Topics/XS1038.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1038
-
-XS1038
-
-
-
- Error XS1038
-
- #endregion directive expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1039.xml b/docs/Help_Spanish/Topics/XS1039.xml
deleted file mode 100644
index 4eb94a291f..0000000000
--- a/docs/Help_Spanish/Topics/XS1039.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1039
-
-XS1039
-
-
-
- Error XS1039
-
- Unterminated string literal
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1040.xml b/docs/Help_Spanish/Topics/XS1040.xml
deleted file mode 100644
index 2302600b01..0000000000
--- a/docs/Help_Spanish/Topics/XS1040.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1040
-
-XS1040
-
-
-
- Error XS1040
-
- Preprocessor directives must appear as the first non-whitespace character on a line
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1041.xml b/docs/Help_Spanish/Topics/XS1041.xml
deleted file mode 100644
index 3d465c3351..0000000000
--- a/docs/Help_Spanish/Topics/XS1041.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1041
-
-XS1041
-
-
-
- Error XS1041
-
- Identifier expected; '{1}' is a keyword
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1043.xml b/docs/Help_Spanish/Topics/XS1043.xml
deleted file mode 100644
index f3091f8214..0000000000
--- a/docs/Help_Spanish/Topics/XS1043.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1043
-
-XS1043
-
-
-
- Error XS1043
-
- { or ; expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1044.xml b/docs/Help_Spanish/Topics/XS1044.xml
deleted file mode 100644
index 71c6a6b285..0000000000
--- a/docs/Help_Spanish/Topics/XS1044.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1044
-
-XS1044
-
-
-
- Error XS1044
-
- Cannot use more than one type in a for, using, fixed, or declaration statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1055.xml b/docs/Help_Spanish/Topics/XS1055.xml
deleted file mode 100644
index 09b9d95d8a..0000000000
--- a/docs/Help_Spanish/Topics/XS1055.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1055
-
-XS1055
-
-
-
- Error XS1055
-
- An add or remove accessor expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1056.xml b/docs/Help_Spanish/Topics/XS1056.xml
deleted file mode 100644
index 1a07ca09ad..0000000000
--- a/docs/Help_Spanish/Topics/XS1056.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1056
-
-XS1056
-
-
-
- Error XS1056
-
- Unexpected character '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1057.xml b/docs/Help_Spanish/Topics/XS1057.xml
deleted file mode 100644
index 9bd32e192b..0000000000
--- a/docs/Help_Spanish/Topics/XS1057.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1057
-
- XS1057
-
-
-
- Warning XS1057
-
- '{0}': static classes cannot contain protected members
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1058.xml b/docs/Help_Spanish/Topics/XS1058.xml
deleted file mode 100644
index af84c76b89..0000000000
--- a/docs/Help_Spanish/Topics/XS1058.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS1058
-
- XS1058
-
-
-
- Warning XS1058
-
- A previous catch clause already catches all exceptions. All exceptions thrown will be wrapped in a System.Runtime.CompilerServices.RuntimeWrappedException
-
- This attribute causes XS1058 if a catch() block has no specified exception type after a catch (System.Exception e) block. The warning advises that the catch() block will not catch any exceptions.
-
- A catch() block after a catch (System.Exception e) block can catch non-CLS exceptions if the RuntimeCompatibilityAttribute is set to false in the AssemblyInfo.prg file: [assembly: RuntimeCompatibilityAttribute(WrapNonExceptionThrows = false)]. If this attribute is not set explicitly to false, all thrown non-CLS exceptions are wrapped as Exceptions and the catch (System.Exception e) block catches them. For more information, see How to: Catch a non-CLS Exception.
- Example
-
- The following example generates XS1058.
-
-
- // XS1058.prg // XS1058 expected
-
-
diff --git a/docs/Help_Spanish/Topics/XS1059.xml b/docs/Help_Spanish/Topics/XS1059.xml
deleted file mode 100644
index 76b239ebce..0000000000
--- a/docs/Help_Spanish/Topics/XS1059.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1059
-
-XS1059
-
-
-
- Error XS1059
-
- The operand of an increment or decrement operator must be a variable, property or indexer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1061.xml b/docs/Help_Spanish/Topics/XS1061.xml
deleted file mode 100644
index 955bc1c42e..0000000000
--- a/docs/Help_Spanish/Topics/XS1061.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS1061
-
- XS1061
-
-
-
- Error XS1061
-
- 'type' does not contain a definition for 'member' and no extension method 'name' accepting a first argument of type 'type' could be found (are you missing a using directive or an assembly reference?).
-
- This error occurs when you try to call a method or access a class member that does not exist.
- Example
-
- The following example generates XS1061 because TestClass1 does not have a DisplaySomething method. It does have a method that is called WriteSomething. Perhaps that is what the author of this source code meant to write.
-
-
- // XS1061.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1062.xml b/docs/Help_Spanish/Topics/XS1062.xml
deleted file mode 100644
index d22e4cba90..0000000000
--- a/docs/Help_Spanish/Topics/XS1062.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1062
-
- XS1062
-
-
-
- Warning XS1062
-
- The best overloaded Add method '{0}' for the collection initializer element is obsolete. {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1063.xml b/docs/Help_Spanish/Topics/XS1063.xml
deleted file mode 100644
index 9c9f39bf6e..0000000000
--- a/docs/Help_Spanish/Topics/XS1063.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1063
-
-XS1063
-
-
-
- Error XS1063
-
- The best overloaded Add method '{0}' for the collection initializer element is obsolete. {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1064.xml b/docs/Help_Spanish/Topics/XS1064.xml
deleted file mode 100644
index 9cd49606b4..0000000000
--- a/docs/Help_Spanish/Topics/XS1064.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1064
-
- XS1064
-
-
-
- Warning XS1064
-
- The best overloaded Add method '{0}' for the collection initializer element is obsolete.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1065.xml b/docs/Help_Spanish/Topics/XS1065.xml
deleted file mode 100644
index ce38d6fc34..0000000000
--- a/docs/Help_Spanish/Topics/XS1065.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1065
-
-XS1065
-
-
-
- Error XS1065
-
- Default values are not valid in this context.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1066.xml b/docs/Help_Spanish/Topics/XS1066.xml
deleted file mode 100644
index 558dc80dbb..0000000000
--- a/docs/Help_Spanish/Topics/XS1066.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1066
-
- XS1066
-
-
-
- Warning XS1066
-
- The default value specified for parameter '{0}' will have no effect because it applies to a member that is used in contexts that do not allow optional arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1067.xml b/docs/Help_Spanish/Topics/XS1067.xml
deleted file mode 100644
index 3c12c895c9..0000000000
--- a/docs/Help_Spanish/Topics/XS1067.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1067
-
-XS1067
-
-
-
- Error XS1067
-
- Partial declarations of '{0}' must have the same type parameter names and variance modifiers in the same order
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1068.xml b/docs/Help_Spanish/Topics/XS1068.xml
deleted file mode 100644
index 37d249880d..0000000000
--- a/docs/Help_Spanish/Topics/XS1068.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1068
-
-XS1068
-
-
-
- Error XS1068
-
- The type name '{0}' could not be found in the global namespace. This type has been forwarded to assembly '{1}' Consider adding a reference to that assembly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1069.xml b/docs/Help_Spanish/Topics/XS1069.xml
deleted file mode 100644
index e3228292f9..0000000000
--- a/docs/Help_Spanish/Topics/XS1069.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1069
-
-XS1069
-
-
-
- Error XS1069
-
- The type name '{0}' could not be found in the namespace '{1}'. This type has been forwarded to assembly '{2}' Consider adding a reference to that assembly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1070.xml b/docs/Help_Spanish/Topics/XS1070.xml
deleted file mode 100644
index a4b8003d7a..0000000000
--- a/docs/Help_Spanish/Topics/XS1070.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1070
-
-XS1070
-
-
-
- Error XS1070
-
- The type name '{0}' could not be found. This type has been forwarded to assembly '{1}'. Consider adding a reference to that assembly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1072.xml b/docs/Help_Spanish/Topics/XS1072.xml
deleted file mode 100644
index 0b10f3dfe6..0000000000
--- a/docs/Help_Spanish/Topics/XS1072.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1072
-
- XS1072
-
-
-
- Warning XS1072
-
- Expected identifier or numeric literal.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1073.xml b/docs/Help_Spanish/Topics/XS1073.xml
deleted file mode 100644
index 2ec0e1fe64..0000000000
--- a/docs/Help_Spanish/Topics/XS1073.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1073
-
-XS1073
-
-
-
- Error XS1073
-
- Unexpected token '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1100.xml b/docs/Help_Spanish/Topics/XS1100.xml
deleted file mode 100644
index 7bc12deacb..0000000000
--- a/docs/Help_Spanish/Topics/XS1100.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1100
-
-XS1100
-
-
-
- Error XS1100
-
- Method '{0}' has a parameter modifier 'SELF' which is not on the first parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1101.xml b/docs/Help_Spanish/Topics/XS1101.xml
deleted file mode 100644
index 536340cdae..0000000000
--- a/docs/Help_Spanish/Topics/XS1101.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1101
-
-XS1101
-
-
-
- Error XS1101
-
- The parameter modifier 'ref' cannot be used with 'SELF'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1102.xml b/docs/Help_Spanish/Topics/XS1102.xml
deleted file mode 100644
index 16ce0b4796..0000000000
--- a/docs/Help_Spanish/Topics/XS1102.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1102
-
-XS1102
-
-
-
- Error XS1102
-
- The parameter modifier 'out' cannot be used with 'SELF'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1103.xml b/docs/Help_Spanish/Topics/XS1103.xml
deleted file mode 100644
index ac38f6d2b7..0000000000
--- a/docs/Help_Spanish/Topics/XS1103.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1103
-
-XS1103
-
-
-
- Error XS1103
-
- The first parameter of an extension method cannot be of type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1104.xml b/docs/Help_Spanish/Topics/XS1104.xml
deleted file mode 100644
index 5ca632dcfe..0000000000
--- a/docs/Help_Spanish/Topics/XS1104.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1104
-
-XS1104
-
-
-
- Error XS1104
-
- A parameter array cannot be used with 'SELF' modifier on an extension method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1105.xml b/docs/Help_Spanish/Topics/XS1105.xml
deleted file mode 100644
index bfbf602ec3..0000000000
--- a/docs/Help_Spanish/Topics/XS1105.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1105
-
-XS1105
-
-
-
- Error XS1105
-
- Extension method must be static
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1106.xml b/docs/Help_Spanish/Topics/XS1106.xml
deleted file mode 100644
index cf974c0843..0000000000
--- a/docs/Help_Spanish/Topics/XS1106.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1106
-
-XS1106
-
-
-
- Error XS1106
-
- Extension method must be defined in a non-generic static class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1107.xml b/docs/Help_Spanish/Topics/XS1107.xml
deleted file mode 100644
index dd2c2de736..0000000000
--- a/docs/Help_Spanish/Topics/XS1107.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1107
-
-XS1107
-
-
-
- Error XS1107
-
- A parameter can only have one '{0}' modifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1108.xml b/docs/Help_Spanish/Topics/XS1108.xml
deleted file mode 100644
index 2bd8f0753d..0000000000
--- a/docs/Help_Spanish/Topics/XS1108.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1108
-
-XS1108
-
-
-
- Error XS1108
-
- A parameter cannot have all the specified modifiers; there are too many modifiers on the parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1109.xml b/docs/Help_Spanish/Topics/XS1109.xml
deleted file mode 100644
index cf7ae9f05a..0000000000
--- a/docs/Help_Spanish/Topics/XS1109.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1109
-
-XS1109
-
-
-
- Error XS1109
-
- Extension methods must be defined in a top level static class; {0} is a nested class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1110.xml b/docs/Help_Spanish/Topics/XS1110.xml
deleted file mode 100644
index 42ede51e1b..0000000000
--- a/docs/Help_Spanish/Topics/XS1110.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1110
-
-XS1110
-
-
-
- Error XS1110
-
- Cannot define a new extension method because the compiler required type '{0}' cannot be found. Are you missing a reference to System.Core.dll?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1112.xml b/docs/Help_Spanish/Topics/XS1112.xml
deleted file mode 100644
index d6bf66ff48..0000000000
--- a/docs/Help_Spanish/Topics/XS1112.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- XS1112
-
- XS1112
-
-
-
- Error XS1112
-
- Do not use 'System.Runtime.CompilerServices.ExtensionAttribute'. Use the 'this' keyword instead.
-
- This error is generated when the ExtensionAttribute is used on a non-static class that contains extension methods. If this attribute is used on a static class, another error, such as XS0708: "Cannot declare instance members in a static class," might occur.
-
- In X#, extension methods must be defined in a static class and the first parameter of the method is modified with the this keyword. Do not use the attribute at all in the source code. For more information, see Extension Methods.
- To correct this error
-
-
-
Remove the attribute and apply the this modifier to the first parameter of the method.
-
- Example
-
- The following example generates XS1112:
-
-
- // XS1112.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS1113.xml b/docs/Help_Spanish/Topics/XS1113.xml
deleted file mode 100644
index d59e959b95..0000000000
--- a/docs/Help_Spanish/Topics/XS1113.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1113
-
-XS1113
-
-
-
- Error XS1113
-
- Extension method '{0}' defined on value type '{1}' cannot be used to create delegates
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1501.xml b/docs/Help_Spanish/Topics/XS1501.xml
deleted file mode 100644
index 765255d771..0000000000
--- a/docs/Help_Spanish/Topics/XS1501.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS1501
-
- XS1501
-
-
-
- Error XS1501
-
- No overload for method 'method' takes 'number' arguments
-
- A call was made to a class method, but no definition of the method takes the specified number of arguments.
- Example
-
- The following sample generates XS1501.
-
-
- //XS1501.PRG
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1503.xml b/docs/Help_Spanish/Topics/XS1503.xml
deleted file mode 100644
index 95455fcd09..0000000000
--- a/docs/Help_Spanish/Topics/XS1503.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1503
-
-XS1503
-
-
-
- Error XS1503
-
- Argument {0}: cannot convert from '{1}' to '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1504.xml b/docs/Help_Spanish/Topics/XS1504.xml
deleted file mode 100644
index 1a75b9f05c..0000000000
--- a/docs/Help_Spanish/Topics/XS1504.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1504
-
-XS1504
-
-
-
- Error XS1504
-
- Source file '{0}' could not be opened -- {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1507.xml b/docs/Help_Spanish/Topics/XS1507.xml
deleted file mode 100644
index 4ca1c1c3d3..0000000000
--- a/docs/Help_Spanish/Topics/XS1507.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1507
-
-XS1507
-
-
-
- Error XS1507
-
- Cannot link resource files when building a module
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1508.xml b/docs/Help_Spanish/Topics/XS1508.xml
deleted file mode 100644
index c188ad47ac..0000000000
--- a/docs/Help_Spanish/Topics/XS1508.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1508
-
-XS1508
-
-
-
- Error XS1508
-
- Resource identifier '{0}' has already been used in this assembly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1509.xml b/docs/Help_Spanish/Topics/XS1509.xml
deleted file mode 100644
index 6aef873de8..0000000000
--- a/docs/Help_Spanish/Topics/XS1509.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1509
-
-XS1509
-
-
-
- Error XS1509
-
- The referenced file '{0}' is not an assembly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1510.xml b/docs/Help_Spanish/Topics/XS1510.xml
deleted file mode 100644
index 3433d60f38..0000000000
--- a/docs/Help_Spanish/Topics/XS1510.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1510
-
-XS1510
-
-
-
- Error XS1510
-
- A ref or out argument must be an assignable variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1511.xml b/docs/Help_Spanish/Topics/XS1511.xml
deleted file mode 100644
index d2b7c12247..0000000000
--- a/docs/Help_Spanish/Topics/XS1511.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1511
-
-XS1511
-
-
-
- Error XS1511
-
- Keyword 'SUPER' is not available in a static method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1512.xml b/docs/Help_Spanish/Topics/XS1512.xml
deleted file mode 100644
index f120ff9707..0000000000
--- a/docs/Help_Spanish/Topics/XS1512.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1512
-
-XS1512
-
-
-
- Error XS1512
-
- Keyword 'SUPER' is not available in the current context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1513.xml b/docs/Help_Spanish/Topics/XS1513.xml
deleted file mode 100644
index 88523e01dc..0000000000
--- a/docs/Help_Spanish/Topics/XS1513.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1513
-
-XS1513
-
-
-
- Error XS1513
-
- } expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1514.xml b/docs/Help_Spanish/Topics/XS1514.xml
deleted file mode 100644
index ae9e9321c2..0000000000
--- a/docs/Help_Spanish/Topics/XS1514.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1514
-
-XS1514
-
-
-
- Error XS1514
-
- { expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1515.xml b/docs/Help_Spanish/Topics/XS1515.xml
deleted file mode 100644
index fa72fb5147..0000000000
--- a/docs/Help_Spanish/Topics/XS1515.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1515
-
-XS1515
-
-
-
- Error XS1515
-
- 'in' expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1517.xml b/docs/Help_Spanish/Topics/XS1517.xml
deleted file mode 100644
index 9a8734f778..0000000000
--- a/docs/Help_Spanish/Topics/XS1517.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1517
-
-XS1517
-
-
-
- Error XS1517
-
- Invalid preprocessor expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1519.xml b/docs/Help_Spanish/Topics/XS1519.xml
deleted file mode 100644
index bccffd4fd6..0000000000
--- a/docs/Help_Spanish/Topics/XS1519.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS1519
-
- XS1519
-
-
-
- Error XS1519
-
- Invalid token 'token' in class, struct, or interface member declaration
-
- This error is generated whenever a token is encountered in a location where it does not belong. A token is a keyword; an identifier (the name of a class, struct, method, and so on); a string, character, or numeric literal value such as 108, "Hello", or 'A'; or an operator or punctuator such as == or ;.
-
- Any class, struct, or interface member declaration that contains invalid modifiers before the type will generate this error. To fix the error, remove the invalid modifiers.
- The following sample generates XS1519 in five places because tokens are placed in locations where they are not valid:
-
-
- // XS1519.prg // Generates XS1519 because a class name cannot be a number:
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1520.xml b/docs/Help_Spanish/Topics/XS1520.xml
deleted file mode 100644
index 6d0b99e721..0000000000
--- a/docs/Help_Spanish/Topics/XS1520.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1520
-
-XS1520
-
-
-
- Error XS1520
-
- Method must have a return type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1521.xml b/docs/Help_Spanish/Topics/XS1521.xml
deleted file mode 100644
index b51e0a0a89..0000000000
--- a/docs/Help_Spanish/Topics/XS1521.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1521
-
-XS1521
-
-
-
- Error XS1521
-
- Invalid base type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1522.xml b/docs/Help_Spanish/Topics/XS1522.xml
deleted file mode 100644
index 20e3ede699..0000000000
--- a/docs/Help_Spanish/Topics/XS1522.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1522
-
- XS1522
-
-
-
- Warning XS1522
-
- Empty switch block
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1524.xml b/docs/Help_Spanish/Topics/XS1524.xml
deleted file mode 100644
index 1ebb6c09ed..0000000000
--- a/docs/Help_Spanish/Topics/XS1524.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1524
-
-XS1524
-
-
-
- Error XS1524
-
- Expected catch or finally
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1525.xml b/docs/Help_Spanish/Topics/XS1525.xml
deleted file mode 100644
index c7c56388b9..0000000000
--- a/docs/Help_Spanish/Topics/XS1525.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1525
-
-XS1525
-
-
-
- Error XS1525
-
- Invalid expression term '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1526.xml b/docs/Help_Spanish/Topics/XS1526.xml
deleted file mode 100644
index c212e41db5..0000000000
--- a/docs/Help_Spanish/Topics/XS1526.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1526
-
-XS1526
-
-
-
- Error XS1526
-
- A new expression requires (), [], or {} after type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1527.xml b/docs/Help_Spanish/Topics/XS1527.xml
deleted file mode 100644
index 5bf3eb0a02..0000000000
--- a/docs/Help_Spanish/Topics/XS1527.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1527
-
-XS1527
-
-
-
- Error XS1527
-
- Elements defined in a namespace cannot be explicitly declared as private, protected, or protected internal
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1528.xml b/docs/Help_Spanish/Topics/XS1528.xml
deleted file mode 100644
index e45c75ef26..0000000000
--- a/docs/Help_Spanish/Topics/XS1528.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1528
-
-XS1528
-
-
-
- Error XS1528
-
- Expected ; or = (cannot specify constructor arguments in declaration)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1529.xml b/docs/Help_Spanish/Topics/XS1529.xml
deleted file mode 100644
index f13805a454..0000000000
--- a/docs/Help_Spanish/Topics/XS1529.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1529
-
-XS1529
-
-
-
- Error XS1529
-
- A using clause must precede all other elements defined in the namespace except extern alias declarations
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1534.xml b/docs/Help_Spanish/Topics/XS1534.xml
deleted file mode 100644
index 22e6e37b21..0000000000
--- a/docs/Help_Spanish/Topics/XS1534.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1534
-
-XS1534
-
-
-
- Error XS1534
-
- Overloaded binary operator '{0}' takes two parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1535.xml b/docs/Help_Spanish/Topics/XS1535.xml
deleted file mode 100644
index e8170f116c..0000000000
--- a/docs/Help_Spanish/Topics/XS1535.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1535
-
-XS1535
-
-
-
- Error XS1535
-
- Overloaded unary operator '{0}' takes one parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1536.xml b/docs/Help_Spanish/Topics/XS1536.xml
deleted file mode 100644
index 22a34b7650..0000000000
--- a/docs/Help_Spanish/Topics/XS1536.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1536
-
-XS1536
-
-
-
- Error XS1536
-
- Invalid parameter type 'void'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1537.xml b/docs/Help_Spanish/Topics/XS1537.xml
deleted file mode 100644
index de3cf55102..0000000000
--- a/docs/Help_Spanish/Topics/XS1537.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1537
-
-XS1537
-
-
-
- Error XS1537
-
- The using alias '{0}' appeared previously in this namespace
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1540.xml b/docs/Help_Spanish/Topics/XS1540.xml
deleted file mode 100644
index 8ab4cd4ec2..0000000000
--- a/docs/Help_Spanish/Topics/XS1540.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- XS1540
-
- XS1540
-
-
-
- Error XS1540
-
- Cannot access protected member 'member' via a qualifier of type 'type1'; the qualifier must be of type 'type2' (or derived from it)
-
- A derived class cannot access protected members of its base class through an instance of the base class. An instance of the base class declared in the derived class might, at run time, be an instance of another type that is derived from the same base but is not otherwise related to the derived class. Because protected members can be accessed only by derived types, any attempts to access protected members that might not be valid at run time are marked by the compiler as not valid.
-
- In the Employee class in the following example, emp2 and emp3 both have type Person at compile time, but emp2 has type Manager at run time. Because Employee is not derived from Manager, it cannot access the protected members of the base class, Person, through an instance of the Manager class. The compiler cannot determine what the run-time type of the two Person objects will be. Therefore, both the call from emp2 and the call from emp3 cause compiler error XS1540.
-
-
- // XS1540.PRG
-
-
diff --git a/docs/Help_Spanish/Topics/XS1542.xml b/docs/Help_Spanish/Topics/XS1542.xml
deleted file mode 100644
index 42252300fc..0000000000
--- a/docs/Help_Spanish/Topics/XS1542.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1542
-
-XS1542
-
-
-
- Error XS1542
-
- '{0}' cannot be added to this assembly because it already is an assembly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1545.xml b/docs/Help_Spanish/Topics/XS1545.xml
deleted file mode 100644
index 5c760b8dd5..0000000000
--- a/docs/Help_Spanish/Topics/XS1545.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1545
-
-XS1545
-
-
-
- Error XS1545
-
- Property, indexer, or event '{0}' is not supported by the language; try directly calling accessor methods '{1}' or '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1546.xml b/docs/Help_Spanish/Topics/XS1546.xml
deleted file mode 100644
index 4c0c3d66a7..0000000000
--- a/docs/Help_Spanish/Topics/XS1546.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- XS1546
-
- XS1546
-
-
-
- Error XS1546
-
- Property, indexer, or event 'property' is not supported by the language; try directly calling accessor method 'accessor'
-
- Your code is consuming an object that has a default indexed property and tried to use the indexed syntax. To resolve this error, call the property's accessor method. For more information on indexers and properties, see Indexers.
-
- The following sample generates XS1546.
- Example
-
- This code sample consists of a .cpp file, which compiles to a .dll, and a .prg file, which uses that .dll. The following code is for the .dll file, and defines a property to be accessed by the code in the .prg file.
-
-
- // CPP1546.cpp // compile with: /clr /LD using namespace System; public ref class MCPP { public: property int Prop [int,int] { int get( int i, int b ) { return i; } } };
-
- Example
-
- This is the X# file.
-
-
- // XS1546.prg // compile with: /r:CPP1546.dll
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1547.xml b/docs/Help_Spanish/Topics/XS1547.xml
deleted file mode 100644
index dfa322b265..0000000000
--- a/docs/Help_Spanish/Topics/XS1547.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1547
-
-XS1547
-
-
-
- Error XS1547
-
- Keyword 'void' cannot be used in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1551.xml b/docs/Help_Spanish/Topics/XS1551.xml
deleted file mode 100644
index 3861f468d1..0000000000
--- a/docs/Help_Spanish/Topics/XS1551.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1551
-
-XS1551
-
-
-
- Error XS1551
-
- Indexers must have at least one parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1552.xml b/docs/Help_Spanish/Topics/XS1552.xml
deleted file mode 100644
index aea7200ea9..0000000000
--- a/docs/Help_Spanish/Topics/XS1552.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1552
-
-XS1552
-
-
-
- Error XS1552
-
- Array type specifier, [], must appear before parameter name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1553.xml b/docs/Help_Spanish/Topics/XS1553.xml
deleted file mode 100644
index 8942a7acef..0000000000
--- a/docs/Help_Spanish/Topics/XS1553.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1553
-
-XS1553
-
-
-
- Error XS1553
-
- Declaration is not valid; use '{0} operator (...' instead
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1555.xml b/docs/Help_Spanish/Topics/XS1555.xml
deleted file mode 100644
index d6c8524ec1..0000000000
--- a/docs/Help_Spanish/Topics/XS1555.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1555
-
-XS1555
-
-
-
- Error XS1555
-
- Could not find '{0}' specified for Start method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1556.xml b/docs/Help_Spanish/Topics/XS1556.xml
deleted file mode 100644
index 83da7cbc55..0000000000
--- a/docs/Help_Spanish/Topics/XS1556.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1556
-
-XS1556
-
-
-
- Error XS1556
-
- '{0}' specified for Start method must be a valid non-generic class or struct
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1558.xml b/docs/Help_Spanish/Topics/XS1558.xml
deleted file mode 100644
index 0f4d5c5e89..0000000000
--- a/docs/Help_Spanish/Topics/XS1558.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1558
-
-XS1558
-
-
-
- Error XS1558
-
- '{0}' does not have a suitable static Start method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1562.xml b/docs/Help_Spanish/Topics/XS1562.xml
deleted file mode 100644
index b37a86a349..0000000000
--- a/docs/Help_Spanish/Topics/XS1562.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1562
-
-XS1562
-
-
-
- Error XS1562
-
- Outputs without source must have the /out option specified
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1564.xml b/docs/Help_Spanish/Topics/XS1564.xml
deleted file mode 100644
index f974ff3b5b..0000000000
--- a/docs/Help_Spanish/Topics/XS1564.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- XS1564
-
- XS1564
-
-
-
- Error XS1564
-
- Conflicting options specified: Win32 resource file; Win32 manifest.
-
- If you use the /Win32res compiler option, you must include the custom Win32 manifest (if it is required) in the resource file. You cannot provide a custom Win32 manifest separately from a Win32 resource file. Use the /win32manifest option only if you are not specifying a win32 resource file.
- To correct this error
-
-
-
Add the win32 manifest to the win32 resource file and remove the /win32manifest compiler option.
-
- Example
-
- The following example produces XS1564 if it is compiled with the /Win32res option and no manifest is included in the resource file.
-
-
- // XS1564.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1565.xml b/docs/Help_Spanish/Topics/XS1565.xml
deleted file mode 100644
index 35d1e2d35c..0000000000
--- a/docs/Help_Spanish/Topics/XS1565.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1565
-
-XS1565
-
-
-
- Error XS1565
-
- Conflicting options specified: Win32 resource file; Win32 icon
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1566.xml b/docs/Help_Spanish/Topics/XS1566.xml
deleted file mode 100644
index dcd5b00375..0000000000
--- a/docs/Help_Spanish/Topics/XS1566.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1566
-
-XS1566
-
-
-
- Error XS1566
-
- Error reading resource '{0}' -- '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1569.xml b/docs/Help_Spanish/Topics/XS1569.xml
deleted file mode 100644
index 419fdf8b22..0000000000
--- a/docs/Help_Spanish/Topics/XS1569.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1569
-
-XS1569
-
-
-
- Error XS1569
-
- Error writing to XML documentation file: {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1570.xml b/docs/Help_Spanish/Topics/XS1570.xml
deleted file mode 100644
index 5514fce53b..0000000000
--- a/docs/Help_Spanish/Topics/XS1570.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1570
-
- XS1570
-
-
-
- Warning XS1570
-
- XML comment has badly formed XML -- '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1571.xml b/docs/Help_Spanish/Topics/XS1571.xml
deleted file mode 100644
index f75d0166dc..0000000000
--- a/docs/Help_Spanish/Topics/XS1571.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1571
-
- XS1571
-
-
-
- Warning XS1571
-
- XML comment has a duplicate param tag for '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1572.xml b/docs/Help_Spanish/Topics/XS1572.xml
deleted file mode 100644
index 986d7df4b4..0000000000
--- a/docs/Help_Spanish/Topics/XS1572.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1572
-
- XS1572
-
-
-
- Warning XS1572
-
- XML comment has a param tag for '{0}', but there is no parameter by that name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1573.xml b/docs/Help_Spanish/Topics/XS1573.xml
deleted file mode 100644
index b524dfa8bf..0000000000
--- a/docs/Help_Spanish/Topics/XS1573.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1573
-
- XS1573
-
-
-
- Warning XS1573
-
- Parameter '{0}' has no matching param tag in the XML comment for '{1}' (but other parameters do)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1574.xml b/docs/Help_Spanish/Topics/XS1574.xml
deleted file mode 100644
index aa7459e66b..0000000000
--- a/docs/Help_Spanish/Topics/XS1574.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1574
-
- XS1574
-
-
-
- Warning XS1574
-
- XML comment has cref attribute '{0}' that could not be resolved
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1575.xml b/docs/Help_Spanish/Topics/XS1575.xml
deleted file mode 100644
index 61e1505e5e..0000000000
--- a/docs/Help_Spanish/Topics/XS1575.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1575
-
-XS1575
-
-
-
- Error XS1575
-
- A stackalloc expression requires [] after type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1576.xml b/docs/Help_Spanish/Topics/XS1576.xml
deleted file mode 100644
index 5800b24941..0000000000
--- a/docs/Help_Spanish/Topics/XS1576.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1576
-
-XS1576
-
-
-
- Error XS1576
-
- The line number specified for #line directive is missing or invalid
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1578.xml b/docs/Help_Spanish/Topics/XS1578.xml
deleted file mode 100644
index b458d17263..0000000000
--- a/docs/Help_Spanish/Topics/XS1578.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1578
-
-XS1578
-
-
-
- Error XS1578
-
- Quoted file name, single-line comment or end-of-line expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1579.xml b/docs/Help_Spanish/Topics/XS1579.xml
deleted file mode 100644
index 753c9b0924..0000000000
--- a/docs/Help_Spanish/Topics/XS1579.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- XS1579
-
- XS1579
-
-
-
- Error XS1579
-
- foreach statement cannot operate on variables of type 'type1' because 'type2' does not contain a public definition for 'identifier'
-
- To iterate through a collection using the foreach statement, the collection must meet the following requirements:
-
-
-
It must be an interface, class or struct.
-
It must include a public GetEnumerator method that returns a type.
-
The return type must contain a public property named Current, and a public method named MoveNext.
-
For more information, see How to: Access a Collection Class with foreach.
-
- Example
-
- In this sample, foreach is not able to iterate through the collection because there is no publicGetEnumerator method in MyCollection.
-
- The following sample generates XS1579.
-
-
- // XS1579.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1580.xml b/docs/Help_Spanish/Topics/XS1580.xml
deleted file mode 100644
index 30a28b26f1..0000000000
--- a/docs/Help_Spanish/Topics/XS1580.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1580
-
- XS1580
-
-
-
- Warning XS1580
-
- Invalid type for parameter {0} in XML comment cref attribute: '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1581.xml b/docs/Help_Spanish/Topics/XS1581.xml
deleted file mode 100644
index 41ebd629a0..0000000000
--- a/docs/Help_Spanish/Topics/XS1581.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1581
-
- XS1581
-
-
-
- Warning XS1581
-
- Invalid return type in XML comment cref attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1583.xml b/docs/Help_Spanish/Topics/XS1583.xml
deleted file mode 100644
index a8f9065a56..0000000000
--- a/docs/Help_Spanish/Topics/XS1583.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1583
-
-XS1583
-
-
-
- Error XS1583
-
- Error reading Win32 resources -- {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1584.xml b/docs/Help_Spanish/Topics/XS1584.xml
deleted file mode 100644
index 8cd58ddfcc..0000000000
--- a/docs/Help_Spanish/Topics/XS1584.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1584
-
- XS1584
-
-
-
- Warning XS1584
-
- XML comment has syntactically incorrect cref attribute '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1585.xml b/docs/Help_Spanish/Topics/XS1585.xml
deleted file mode 100644
index 3075575fe7..0000000000
--- a/docs/Help_Spanish/Topics/XS1585.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1585
-
-XS1585
-
-
-
- Error XS1585
-
- Member modifier '{0}' must precede the member type and name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1586.xml b/docs/Help_Spanish/Topics/XS1586.xml
deleted file mode 100644
index 565836ae0a..0000000000
--- a/docs/Help_Spanish/Topics/XS1586.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1586
-
-XS1586
-
-
-
- Error XS1586
-
- Array creation must have array size or array initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1587.xml b/docs/Help_Spanish/Topics/XS1587.xml
deleted file mode 100644
index 2d744d5556..0000000000
--- a/docs/Help_Spanish/Topics/XS1587.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1587
-
- XS1587
-
-
-
- Warning XS1587
-
- XML comment is not placed on a valid language element
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1589.xml b/docs/Help_Spanish/Topics/XS1589.xml
deleted file mode 100644
index f80051c814..0000000000
--- a/docs/Help_Spanish/Topics/XS1589.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1589
-
- XS1589
-
-
-
- Warning XS1589
-
- Unable to include XML fragment '{1}' of file '{0}' -- {2}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1590.xml b/docs/Help_Spanish/Topics/XS1590.xml
deleted file mode 100644
index 921e4ffc23..0000000000
--- a/docs/Help_Spanish/Topics/XS1590.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1590
-
- XS1590
-
-
-
- Warning XS1590
-
- Invalid XML include element -- {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1591.xml b/docs/Help_Spanish/Topics/XS1591.xml
deleted file mode 100644
index 1569078d3e..0000000000
--- a/docs/Help_Spanish/Topics/XS1591.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- XS1591
-
- XS1591
-
-
-
- Warning XS1591
-
- Missing XML comment for publicly visible type or member 'Type_or_Member'
-
- The /doc compiler option was specified, but one or more constructs did not have comments.
-
- The following sample generates XS1591:
-
-
- // XS1591.prg // compile with: /W:4 /doc:x.xml
-
-
diff --git a/docs/Help_Spanish/Topics/XS1592.xml b/docs/Help_Spanish/Topics/XS1592.xml
deleted file mode 100644
index 0854d2510c..0000000000
--- a/docs/Help_Spanish/Topics/XS1592.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1592
-
- XS1592
-
-
-
- Warning XS1592
-
- Badly formed XML in included comments file -- '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1593.xml b/docs/Help_Spanish/Topics/XS1593.xml
deleted file mode 100644
index 091963e8ce..0000000000
--- a/docs/Help_Spanish/Topics/XS1593.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1593
-
-XS1593
-
-
-
- Error XS1593
-
- Delegate '{0}' does not take {1} arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1597.xml b/docs/Help_Spanish/Topics/XS1597.xml
deleted file mode 100644
index 2ec04c5c85..0000000000
--- a/docs/Help_Spanish/Topics/XS1597.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1597
-
-XS1597
-
-
-
- Error XS1597
-
- Semicolon after method or accessor block is not valid
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1599.xml b/docs/Help_Spanish/Topics/XS1599.xml
deleted file mode 100644
index 8506e95e42..0000000000
--- a/docs/Help_Spanish/Topics/XS1599.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1599
-
-XS1599
-
-
-
- Error XS1599
-
- Method or delegate cannot return type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1600.xml b/docs/Help_Spanish/Topics/XS1600.xml
deleted file mode 100644
index d1199e1cdd..0000000000
--- a/docs/Help_Spanish/Topics/XS1600.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1600
-
-XS1600
-
-
-
- Error XS1600
-
- Compilation cancelled by user
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1601.xml b/docs/Help_Spanish/Topics/XS1601.xml
deleted file mode 100644
index 56dd830c75..0000000000
--- a/docs/Help_Spanish/Topics/XS1601.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1601
-
-XS1601
-
-
-
- Error XS1601
-
- Cannot make reference to variable of type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1604.xml b/docs/Help_Spanish/Topics/XS1604.xml
deleted file mode 100644
index d044bcfb53..0000000000
--- a/docs/Help_Spanish/Topics/XS1604.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1604
-
-XS1604
-
-
-
- Error XS1604
-
- Cannot assign to '{0}' because it is read-only
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1605.xml b/docs/Help_Spanish/Topics/XS1605.xml
deleted file mode 100644
index 2fcb446bc3..0000000000
--- a/docs/Help_Spanish/Topics/XS1605.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1605
-
-XS1605
-
-
-
- Error XS1605
-
- Cannot pass '{0}' as a ref or out argument because it is read-only
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1607.xml b/docs/Help_Spanish/Topics/XS1607.xml
deleted file mode 100644
index fd98b7f5e1..0000000000
--- a/docs/Help_Spanish/Topics/XS1607.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS1607
-
- XS1607
-
-
-
- Warning XS1607
-
- Assembly generation -- reason
-
- A warning was generated from the assembly-creation phase of the compilation.
-
- If you are building a 64-bit application on a 32-bit operating system, you must ensure that 64-bit versions of all referenced assemblies are installed on the target operating system.
- All x86-specific common language runtime (CLR) assemblies have 64-bit counterparts (every CLR assembly will exist on all operating systems). Therefore, you can safely ignore XS1607 for CLR assemblies.
-
- You can ignore this warning if you encounter it when you create a AssemblyInformationalVersionAttribute. The informational version is a string that attaches additional version information to an assembly; this information is not used at run time. Although you can specify any text, a warning message appears on compilation if the string is not in the format that is used by the assembly version number, or if it is in that format but contains wildcard characters. This warning is harmless.
-
- For more information, see Al.exe Tool Errors and Warnings.
-
-
diff --git a/docs/Help_Spanish/Topics/XS1608.xml b/docs/Help_Spanish/Topics/XS1608.xml
deleted file mode 100644
index 6975c4bc50..0000000000
--- a/docs/Help_Spanish/Topics/XS1608.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1608
-
-XS1608
-
-
-
- Error XS1608
-
- The RequiredAttribute attribute is not permitted on X# types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1609.xml b/docs/Help_Spanish/Topics/XS1609.xml
deleted file mode 100644
index 778010d602..0000000000
--- a/docs/Help_Spanish/Topics/XS1609.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1609
-
-XS1609
-
-
-
- Error XS1609
-
- Modifiers cannot be placed on event accessor declarations
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1611.xml b/docs/Help_Spanish/Topics/XS1611.xml
deleted file mode 100644
index 316ee297d1..0000000000
--- a/docs/Help_Spanish/Topics/XS1611.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1611
-
-XS1611
-
-
-
- Error XS1611
-
- The params parameter cannot be declared as ref or out
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1612.xml b/docs/Help_Spanish/Topics/XS1612.xml
deleted file mode 100644
index 58dd533f31..0000000000
--- a/docs/Help_Spanish/Topics/XS1612.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- XS1612
-
- XS1612
-
-
-
- Error XS1612
-
- Cannot modify the return value of 'expression' because it is not a variable
-
- An attempt was made to modify a value type that is produced as the result of an intermediate expression but is not stored in a variable. This error can occur when you attempt to directly modify a struct in a generic collection, as shown in the following example:
-
-
-
-
- To modify the struct, first assign it to a local variable, modify the variable, then assign the variable back to the item in the collection.
-
-
-
-
- This error occurs because value types are copied on assignment. When you retrieve a value type from a property or indexer, you are getting a copy of the object, not a reference to the object itself. The copy that is returned is not stored by the property or indexer because they are actually methods, not storage locations (variables). You must store the copy into a variable that you declare before you can modify it.
-
- The error does not occur with reference types because a property or indexer in that case returns a reference to an existing object, which is a storage location.
-
- If you are defining the class or struct, you can resolve this error by modifying your property declaration to provide access to the members of a struct. If you are writing client code, you can resolve the error by creating your own instance of the struct, modifying its fields, and then assigning the entire struct back to the property. As a third alternative, you can change your struct to a class.
- Example
-
- XS1612 also occurs when you attempt to access the member of a struct through a property on an enclosing class that is returning the entire struct, as shown in the following example:
-
-
- // XS1612.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1613.xml b/docs/Help_Spanish/Topics/XS1613.xml
deleted file mode 100644
index 43f18c864d..0000000000
--- a/docs/Help_Spanish/Topics/XS1613.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1613
-
-XS1613
-
-
-
- Error XS1613
-
- The managed coclass wrapper class '{0}' for interface '{1}' cannot be found (are you missing an assembly reference?)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1614.xml b/docs/Help_Spanish/Topics/XS1614.xml
deleted file mode 100644
index 50e7d45c3d..0000000000
--- a/docs/Help_Spanish/Topics/XS1614.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS1614
-
- XS1614
-
-
-
- Error XS1614
-
- 'name' is ambiguous; between 'attribute1' and 'attribute2'. use either '@attribute' or 'attributeAttribute'
-
- The compiler has encountered an ambiguous attribute specification.
-
- For convenience, the X# compiler allows you to specify ExampleAttribute as just [Example]. However, ambiguity arises if an attribute class named Example exists along with ExampleAttribute, because the compiler cannot tell if [Example] refers to the Example attribute or the ExampleAttribute attribute. To clarify, use [@Example] for the Example attribute and [ExampleAttribute] for ExampleAttribute.
-
- The following sample generates XS1614:
-
-
- // XS1614.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1615.xml b/docs/Help_Spanish/Topics/XS1615.xml
deleted file mode 100644
index 10495f7fd9..0000000000
--- a/docs/Help_Spanish/Topics/XS1615.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1615
-
-XS1615
-
-
-
- Error XS1615
-
- Argument {0} should not be passed with the '{1}' keyword
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1616.xml b/docs/Help_Spanish/Topics/XS1616.xml
deleted file mode 100644
index ca79d1863c..0000000000
--- a/docs/Help_Spanish/Topics/XS1616.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- XS1616
-
- XS1616
-
-
-
- Error XS1616
-
- Option 'option' overrides attribute 'attribute' given in a source file or added module
-
- This warning occurs if the assembly attributes AssemblyKeyFileAttribute or AssemblyKeyNameAttribute found in source conflict with the /keyfile or /keycontainer command line option or key file name or key container specified in the Project Properties.
-
- For the example below, assume you have a key file named XS1616.snk. This file could be generated with the command line:
-
-
- sn –k XS1616.snk
-
- The following sample generates XS1616:
-
-
- // XS1616.prg // compile with: /keyfile:XS1616.snk
-
-
diff --git a/docs/Help_Spanish/Topics/XS1617.xml b/docs/Help_Spanish/Topics/XS1617.xml
deleted file mode 100644
index 24a128b1d1..0000000000
--- a/docs/Help_Spanish/Topics/XS1617.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1617
-
-XS1617
-
-
-
- Error XS1617
-
- Invalid option '{0}' for /langversion; must be ISO-1, ISO-2, Default or an integer in range 1 to 6.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1618.xml b/docs/Help_Spanish/Topics/XS1618.xml
deleted file mode 100644
index 7d59888b83..0000000000
--- a/docs/Help_Spanish/Topics/XS1618.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1618
-
-XS1618
-
-
-
- Error XS1618
-
- Cannot create delegate with '{0}' because it or a method it overrides has a Conditional attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1619.xml b/docs/Help_Spanish/Topics/XS1619.xml
deleted file mode 100644
index cb9e273527..0000000000
--- a/docs/Help_Spanish/Topics/XS1619.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1619
-
-XS1619
-
-
-
- Error XS1619
-
- Cannot create temporary file -- {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1620.xml b/docs/Help_Spanish/Topics/XS1620.xml
deleted file mode 100644
index b83202360d..0000000000
--- a/docs/Help_Spanish/Topics/XS1620.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1620
-
-XS1620
-
-
-
- Error XS1620
-
- Argument {0} must be passed with the '{1}' keyword
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1621.xml b/docs/Help_Spanish/Topics/XS1621.xml
deleted file mode 100644
index 7f9500baf2..0000000000
--- a/docs/Help_Spanish/Topics/XS1621.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1621
-
-XS1621
-
-
-
- Error XS1621
-
- The yield statement cannot be used inside an anonymous method or lambda expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1622.xml b/docs/Help_Spanish/Topics/XS1622.xml
deleted file mode 100644
index e353f28077..0000000000
--- a/docs/Help_Spanish/Topics/XS1622.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1622
-
-XS1622
-
-
-
- Error XS1622
-
- Cannot return a value from an iterator. Use the yield return statement to return a value, or yield break to end the iteration.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1623.xml b/docs/Help_Spanish/Topics/XS1623.xml
deleted file mode 100644
index ecec948baa..0000000000
--- a/docs/Help_Spanish/Topics/XS1623.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1623
-
-XS1623
-
-
-
- Error XS1623
-
- Iterators cannot have ref or out parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1624.xml b/docs/Help_Spanish/Topics/XS1624.xml
deleted file mode 100644
index 140acca51a..0000000000
--- a/docs/Help_Spanish/Topics/XS1624.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1624
-
-XS1624
-
-
-
- Error XS1624
-
- The body of '{0}' cannot be an iterator block because '{1}' is not an iterator interface type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1625.xml b/docs/Help_Spanish/Topics/XS1625.xml
deleted file mode 100644
index 8ab94c9448..0000000000
--- a/docs/Help_Spanish/Topics/XS1625.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1625
-
-XS1625
-
-
-
- Error XS1625
-
- Cannot yield in the body of a finally clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1626.xml b/docs/Help_Spanish/Topics/XS1626.xml
deleted file mode 100644
index 9cadec986b..0000000000
--- a/docs/Help_Spanish/Topics/XS1626.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1626
-
-XS1626
-
-
-
- Error XS1626
-
- Cannot yield a value in the body of a try block with a catch clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1627.xml b/docs/Help_Spanish/Topics/XS1627.xml
deleted file mode 100644
index 50da89f55d..0000000000
--- a/docs/Help_Spanish/Topics/XS1627.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1627
-
-XS1627
-
-
-
- Error XS1627
-
- Expression expected after yield return
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1628.xml b/docs/Help_Spanish/Topics/XS1628.xml
deleted file mode 100644
index b7d7072194..0000000000
--- a/docs/Help_Spanish/Topics/XS1628.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1628
-
-XS1628
-
-
-
- Error XS1628
-
- Cannot use ref or out parameter '{0}' inside an anonymous method, lambda expression, or query expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1629.xml b/docs/Help_Spanish/Topics/XS1629.xml
deleted file mode 100644
index 886ed97f3d..0000000000
--- a/docs/Help_Spanish/Topics/XS1629.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1629
-
-XS1629
-
-
-
- Error XS1629
-
- Unsafe code may not appear in iterators
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1631.xml b/docs/Help_Spanish/Topics/XS1631.xml
deleted file mode 100644
index 0b2c423ceb..0000000000
--- a/docs/Help_Spanish/Topics/XS1631.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1631
-
-XS1631
-
-
-
- Error XS1631
-
- Cannot yield a value in the body of a catch clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1632.xml b/docs/Help_Spanish/Topics/XS1632.xml
deleted file mode 100644
index 5c63799bae..0000000000
--- a/docs/Help_Spanish/Topics/XS1632.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1632
-
-XS1632
-
-
-
- Error XS1632
-
- Control cannot leave the body of an anonymous method or lambda expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1633.xml b/docs/Help_Spanish/Topics/XS1633.xml
deleted file mode 100644
index fad3803bca..0000000000
--- a/docs/Help_Spanish/Topics/XS1633.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1633
-
- XS1633
-
-
-
- Warning XS1633
-
- Unrecognized #pragma directive
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1634.xml b/docs/Help_Spanish/Topics/XS1634.xml
deleted file mode 100644
index 5070ca4059..0000000000
--- a/docs/Help_Spanish/Topics/XS1634.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1634
-
- XS1634
-
-
-
- Warning XS1634
-
- Expected disable or restore
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1635.xml b/docs/Help_Spanish/Topics/XS1635.xml
deleted file mode 100644
index 7a420c8bba..0000000000
--- a/docs/Help_Spanish/Topics/XS1635.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1635
-
- XS1635
-
-
-
- Warning XS1635
-
- Cannot restore warning 'CS{0}' because it was disabled globally
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1636.xml b/docs/Help_Spanish/Topics/XS1636.xml
deleted file mode 100644
index dfd7e233f1..0000000000
--- a/docs/Help_Spanish/Topics/XS1636.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1636
-
-XS1636
-
-
-
- Error XS1636
-
- __arglist is not allowed in the parameter list of iterators
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1637.xml b/docs/Help_Spanish/Topics/XS1637.xml
deleted file mode 100644
index 938ec7f67e..0000000000
--- a/docs/Help_Spanish/Topics/XS1637.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1637
-
-XS1637
-
-
-
- Error XS1637
-
- Iterators cannot have unsafe parameters or yield types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1639.xml b/docs/Help_Spanish/Topics/XS1639.xml
deleted file mode 100644
index 94924d06fd..0000000000
--- a/docs/Help_Spanish/Topics/XS1639.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1639
-
-XS1639
-
-
-
- Error XS1639
-
- The managed coclass wrapper class signature '{0}' for interface '{1}' is not a valid class name signature
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1640.xml b/docs/Help_Spanish/Topics/XS1640.xml
deleted file mode 100644
index 9ba37ae51c..0000000000
--- a/docs/Help_Spanish/Topics/XS1640.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS1640
-
- XS1640
-
-
-
- Error XS1640
-
- foreach statement cannot operate on variables of type 'type' because it implements multiple instantiations of 'interface', try casting to a specific interface instantiation
-
- The type inherits from two or more instances of IEnumerator<T>, which means there is not a unique enumeration of the type that foreach could use. Specify the type of IEnumerator<T> or use another looping construct.
- Example
-
- The following sample generates XS1640:
-
-
- // XS1640.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1641.xml b/docs/Help_Spanish/Topics/XS1641.xml
deleted file mode 100644
index 61836cec53..0000000000
--- a/docs/Help_Spanish/Topics/XS1641.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1641
-
-XS1641
-
-
-
- Error XS1641
-
- A fixed size buffer field must have the array size specifier after the field name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1642.xml b/docs/Help_Spanish/Topics/XS1642.xml
deleted file mode 100644
index 23550f2084..0000000000
--- a/docs/Help_Spanish/Topics/XS1642.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1642
-
-XS1642
-
-
-
- Error XS1642
-
- Fixed size buffer fields may only be members of structs
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1643.xml b/docs/Help_Spanish/Topics/XS1643.xml
deleted file mode 100644
index d9e4954c05..0000000000
--- a/docs/Help_Spanish/Topics/XS1643.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1643
-
-XS1643
-
-
-
- Error XS1643
-
- Not all code paths return a value in {0} of type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1645.xml b/docs/Help_Spanish/Topics/XS1645.xml
deleted file mode 100644
index 774f633476..0000000000
--- a/docs/Help_Spanish/Topics/XS1645.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1645
-
- XS1645
-
-
-
- Warning XS1645
-
- Feature '{0}' is not part of the standardized ISO C# language specification, and may not be accepted by other compilers
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1646.xml b/docs/Help_Spanish/Topics/XS1646.xml
deleted file mode 100644
index 26d4c726c6..0000000000
--- a/docs/Help_Spanish/Topics/XS1646.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1646
-
-XS1646
-
-
-
- Error XS1646
-
- Keyword, identifier, or string expected after verbatim specifier: @
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1648.xml b/docs/Help_Spanish/Topics/XS1648.xml
deleted file mode 100644
index aa27148b63..0000000000
--- a/docs/Help_Spanish/Topics/XS1648.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1648
-
-XS1648
-
-
-
- Error XS1648
-
- Members of readonly field '{0}' cannot be modified (except in a constructor or a variable initializer)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1649.xml b/docs/Help_Spanish/Topics/XS1649.xml
deleted file mode 100644
index f9c0481012..0000000000
--- a/docs/Help_Spanish/Topics/XS1649.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1649
-
-XS1649
-
-
-
- Error XS1649
-
- Members of readonly field '{0}' cannot be passed ref or out (except in a constructor)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1650.xml b/docs/Help_Spanish/Topics/XS1650.xml
deleted file mode 100644
index 36975810fc..0000000000
--- a/docs/Help_Spanish/Topics/XS1650.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1650
-
-XS1650
-
-
-
- Error XS1650
-
- Fields of static readonly field '{0}' cannot be assigned to (except in a static constructor or a variable initializer)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1651.xml b/docs/Help_Spanish/Topics/XS1651.xml
deleted file mode 100644
index f03d5be80f..0000000000
--- a/docs/Help_Spanish/Topics/XS1651.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1651
-
-XS1651
-
-
-
- Error XS1651
-
- Fields of static readonly field '{0}' cannot be passed ref or out (except in a static constructor)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1654.xml b/docs/Help_Spanish/Topics/XS1654.xml
deleted file mode 100644
index fecf6ceb6d..0000000000
--- a/docs/Help_Spanish/Topics/XS1654.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1654
-
-XS1654
-
-
-
- Error XS1654
-
- Cannot modify members of '{0}' because it is a '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1655.xml b/docs/Help_Spanish/Topics/XS1655.xml
deleted file mode 100644
index 0c8719998e..0000000000
--- a/docs/Help_Spanish/Topics/XS1655.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1655
-
-XS1655
-
-
-
- Error XS1655
-
- Cannot pass fields of '{0}' as a ref or out argument because it is a '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1656.xml b/docs/Help_Spanish/Topics/XS1656.xml
deleted file mode 100644
index e6e92b7c6a..0000000000
--- a/docs/Help_Spanish/Topics/XS1656.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XS1656
-
- XS1656
-
-
-
- Warning XS1656
-
- Cannot assign to 'variable' because it is a 'read-only variable type'
-
- This error occurs when an assignment to variable occurs in a read-only context. Read-only contexts include foreach iteration variables, using variables, and fixed variables. To resolve this error, avoid assignments to a statement variable in using blocks, foreach statements, and fixed statements.
- Example
-
- The following example generates error XS1656 because it tries to replace complete elements of a collection inside a foreach loop. One way to work around the error is to change the foreach loop to a for loop. Another way, not shown here, is to modify the members of the existing element; this is possible with classes, but not with structs.
-
-
-
-
- Example
-
- The following sample demonstrates how XS1656 can be generated in other contexts besides a foreach loop:
-
-
- // XS1656.prg // compile with: /unsafe
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1657.xml b/docs/Help_Spanish/Topics/XS1657.xml
deleted file mode 100644
index 923995d482..0000000000
--- a/docs/Help_Spanish/Topics/XS1657.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1657
-
-XS1657
-
-
-
- Error XS1657
-
- Cannot pass '{0}' as a ref or out argument because it is a '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1658.xml b/docs/Help_Spanish/Topics/XS1658.xml
deleted file mode 100644
index da587b4fdb..0000000000
--- a/docs/Help_Spanish/Topics/XS1658.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS1658
-
- XS1658
-
-
-
- Warning XS1658
-
- 'warning text'. See also error 'error code'
-
- The compiler emits this warning when it overrides an error with a warning. For information about the problem, refer to the error mentioned. To find the appropriate error from within the Visual Studio IDE, use the index. For example, if the text above reads "See also error 'XS1037'," look for XS1037 in the index.
- Example
-
- The following example generates XS1658.
-
-
- // XS1658.prg // compile with: /doc:x.xml
-
-
diff --git a/docs/Help_Spanish/Topics/XS1660.xml b/docs/Help_Spanish/Topics/XS1660.xml
deleted file mode 100644
index 7fea3cbd18..0000000000
--- a/docs/Help_Spanish/Topics/XS1660.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1660
-
-XS1660
-
-
-
- Error XS1660
-
- Cannot convert {0} to type '{1}' because it is not a delegate type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1661.xml b/docs/Help_Spanish/Topics/XS1661.xml
deleted file mode 100644
index 8a0ccd1cf2..0000000000
--- a/docs/Help_Spanish/Topics/XS1661.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1661
-
-XS1661
-
-
-
- Error XS1661
-
- Cannot convert {0} to delegate type '{1}' because the parameter types do not match the delegate parameter types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1662.xml b/docs/Help_Spanish/Topics/XS1662.xml
deleted file mode 100644
index 387cf0d092..0000000000
--- a/docs/Help_Spanish/Topics/XS1662.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1662
-
-XS1662
-
-
-
- Error XS1662
-
- Cannot convert {0} to intended delegate type because some of the return types in the block are not implicitly convertible to the delegate return type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1663.xml b/docs/Help_Spanish/Topics/XS1663.xml
deleted file mode 100644
index 94a09bac4f..0000000000
--- a/docs/Help_Spanish/Topics/XS1663.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1663
-
-XS1663
-
-
-
- Error XS1663
-
- Fixed size buffer type must be one of the following: bool, byte, short, int, long, char, sbyte, ushort, uint, ulong, float or double (also ptr or vostruct in vo/vulcan dialect)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1664.xml b/docs/Help_Spanish/Topics/XS1664.xml
deleted file mode 100644
index 5e0babc2ae..0000000000
--- a/docs/Help_Spanish/Topics/XS1664.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1664
-
-XS1664
-
-
-
- Error XS1664
-
- Fixed size buffer of length {0} and type '{1}' is too big
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1665.xml b/docs/Help_Spanish/Topics/XS1665.xml
deleted file mode 100644
index ac729e33e9..0000000000
--- a/docs/Help_Spanish/Topics/XS1665.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1665
-
-XS1665
-
-
-
- Error XS1665
-
- Fixed size buffers must have a length greater than zero
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1666.xml b/docs/Help_Spanish/Topics/XS1666.xml
deleted file mode 100644
index 4c5420be35..0000000000
--- a/docs/Help_Spanish/Topics/XS1666.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1666
-
-XS1666
-
-
-
- Error XS1666
-
- You cannot use fixed size buffers contained in unfixed expressions. Try using the fixed statement.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1667.xml b/docs/Help_Spanish/Topics/XS1667.xml
deleted file mode 100644
index b2990e9e26..0000000000
--- a/docs/Help_Spanish/Topics/XS1667.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1667
-
-XS1667
-
-
-
- Error XS1667
-
- Attribute '{0}' is not valid on property or event accessors. It is only valid on '{1}' declarations.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1668.xml b/docs/Help_Spanish/Topics/XS1668.xml
deleted file mode 100644
index 0e6394d8f8..0000000000
--- a/docs/Help_Spanish/Topics/XS1668.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1668
-
- XS1668
-
-
-
- Warning XS1668
-
- Invalid search path '{0}' specified in '{1}' -- '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1669.xml b/docs/Help_Spanish/Topics/XS1669.xml
deleted file mode 100644
index deff33bba0..0000000000
--- a/docs/Help_Spanish/Topics/XS1669.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1669
-
-XS1669
-
-
-
- Error XS1669
-
- __arglist is not valid in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1670.xml b/docs/Help_Spanish/Topics/XS1670.xml
deleted file mode 100644
index 3791c1b3a9..0000000000
--- a/docs/Help_Spanish/Topics/XS1670.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1670
-
-XS1670
-
-
-
- Error XS1670
-
- params is not valid in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1671.xml b/docs/Help_Spanish/Topics/XS1671.xml
deleted file mode 100644
index df671a8c7c..0000000000
--- a/docs/Help_Spanish/Topics/XS1671.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1671
-
-XS1671
-
-
-
- Error XS1671
-
- A namespace declaration cannot have modifiers or attributes
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1672.xml b/docs/Help_Spanish/Topics/XS1672.xml
deleted file mode 100644
index de88cb2162..0000000000
--- a/docs/Help_Spanish/Topics/XS1672.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1672
-
-XS1672
-
-
-
- Error XS1672
-
- Invalid option '{0}' for /platform; must be anycpu, x86, Itanium or x64
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1673.xml b/docs/Help_Spanish/Topics/XS1673.xml
deleted file mode 100644
index 1a4480e7ad..0000000000
--- a/docs/Help_Spanish/Topics/XS1673.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1673
-
-XS1673
-
-
-
- Error XS1673
-
- Anonymous methods, lambda expressions, and query expressions inside structs cannot access instance members of 'SELF'. Consider copying 'SELF' to a local variable outside the anonymous method, lambda expression or query expression and using the local instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1674.xml b/docs/Help_Spanish/Topics/XS1674.xml
deleted file mode 100644
index ebd4add501..0000000000
--- a/docs/Help_Spanish/Topics/XS1674.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- XS1674
-
- XS1674
-
-
-
- Error XS1674
-
- 'T': type used in a using statement must be implicitly convertible to 'System.IDisposable'
-
- The using Statement is intended to be used to ensure the disposal of an object at the end of the using block, thus, only types which are disposable may be used in such a statement. For example, value types are not disposable, and type parameters which are not constrained to be classes may not be assumed to be disposable.
-
- Example
-
- The following sample generates XS1674.
-
-
- // XS1674.prg
-
- Example
-
- The following sample generates XS1674.
-
-
- // XS1674_b.prg
-
- Example
-
- The following case illustrates the need for a class type constraint to guarantee that an unknown type parameter is disposable. The following sample generates XS1674.
-
-
- // XS1674_c.prg // compile with: /target:library
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1676.xml b/docs/Help_Spanish/Topics/XS1676.xml
deleted file mode 100644
index e17162d6b8..0000000000
--- a/docs/Help_Spanish/Topics/XS1676.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1676
-
-XS1676
-
-
-
- Error XS1676
-
- Parameter {0} must be declared with the '{1}' keyword
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1677.xml b/docs/Help_Spanish/Topics/XS1677.xml
deleted file mode 100644
index 942dc2d96c..0000000000
--- a/docs/Help_Spanish/Topics/XS1677.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1677
-
-XS1677
-
-
-
- Error XS1677
-
- Parameter {0} should not be declared with the '{1}' keyword
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1678.xml b/docs/Help_Spanish/Topics/XS1678.xml
deleted file mode 100644
index e39611e227..0000000000
--- a/docs/Help_Spanish/Topics/XS1678.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1678
-
-XS1678
-
-
-
- Error XS1678
-
- Parameter {0} is declared as type '{1}{2}' but should be '{3}{4}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1679.xml b/docs/Help_Spanish/Topics/XS1679.xml
deleted file mode 100644
index 4eb0f7c125..0000000000
--- a/docs/Help_Spanish/Topics/XS1679.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1679
-
-XS1679
-
-
-
- Error XS1679
-
- Invalid extern alias for '/reference'; '{0}' is not a valid identifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1680.xml b/docs/Help_Spanish/Topics/XS1680.xml
deleted file mode 100644
index 3b29ea40f5..0000000000
--- a/docs/Help_Spanish/Topics/XS1680.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1680
-
-XS1680
-
-
-
- Error XS1680
-
- Invalid reference alias option: '{0}=' -- missing filename
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1681.xml b/docs/Help_Spanish/Topics/XS1681.xml
deleted file mode 100644
index ebdce7f3b9..0000000000
--- a/docs/Help_Spanish/Topics/XS1681.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1681
-
-XS1681
-
-
-
- Error XS1681
-
- You cannot redefine the global extern alias
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1685.xml b/docs/Help_Spanish/Topics/XS1685.xml
deleted file mode 100644
index b775d47801..0000000000
--- a/docs/Help_Spanish/Topics/XS1685.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- XS1685
-
- XS1685
-
-
-
- Warning XS1685
-
- The predefined type 'System.type name' is defined in multiple assemblies in the global alias; using definition from 'File Name'
-
- This error occurs when a predefined system type such as System.int32 is found in two assemblies. One way this can happen is if you are referencing mscorlib from two different places, such as trying to run the.Net Framework versions 1.0 and 1.1 side-by-side.
-
- The compiler will use the definition from only one of the assemblies. The compiler searches only global aliases, does not search libraries defined /reference. If you have specified /nostdlib, the compiler will search for Object, and in the future start all searches for predefined types in the file where it found Object.
-
-
diff --git a/docs/Help_Spanish/Topics/XS1686.xml b/docs/Help_Spanish/Topics/XS1686.xml
deleted file mode 100644
index 0813e05fa2..0000000000
--- a/docs/Help_Spanish/Topics/XS1686.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1686
-
-XS1686
-
-
-
- Error XS1686
-
- Local '{0}' or its members cannot have their address taken and be used inside an anonymous method or lambda expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1687.xml b/docs/Help_Spanish/Topics/XS1687.xml
deleted file mode 100644
index dedee0b491..0000000000
--- a/docs/Help_Spanish/Topics/XS1687.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1687
-
- XS1687
-
-
-
- Warning XS1687
-
- Source file has exceeded the limit of 16,707,565 lines representable in the PDB; debug information will be incorrect
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1688.xml b/docs/Help_Spanish/Topics/XS1688.xml
deleted file mode 100644
index b257cb55fe..0000000000
--- a/docs/Help_Spanish/Topics/XS1688.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1688
-
-XS1688
-
-
-
- Error XS1688
-
- Cannot convert anonymous method block without a parameter list to delegate type '{0}' because it has one or more out parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1689.xml b/docs/Help_Spanish/Topics/XS1689.xml
deleted file mode 100644
index 60e212ab1d..0000000000
--- a/docs/Help_Spanish/Topics/XS1689.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1689
-
-XS1689
-
-
-
- Error XS1689
-
- Attribute '{0}' is only valid on methods or attribute classes
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1690.xml b/docs/Help_Spanish/Topics/XS1690.xml
deleted file mode 100644
index 2d31f82f09..0000000000
--- a/docs/Help_Spanish/Topics/XS1690.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- XS1690
-
- XS1690
-
-
-
- Error XS1690
-
- Accessing a member on 'member' may cause a runtime exception because it is a field of a marshal-by-reference class
-
- This warning occurs when you try to call a method, property, or indexer on a member of a class that derives from MarshalByRefObject, and the member is a value type. Objects that inherit from MarshalByRefObject are typically intended to be marshaled by reference across an application domain. If any code ever attempts to directly access the value-type member of such an object across an application domain, a runtime exception will occur. To resolve the warning, first copy the member into a local variable and call the method on that variable.
-
- The following sample generates XS1690:
-
-
- // XS1690.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1692.xml b/docs/Help_Spanish/Topics/XS1692.xml
deleted file mode 100644
index 49b7f2f32d..0000000000
--- a/docs/Help_Spanish/Topics/XS1692.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1692
-
- XS1692
-
-
-
- Warning XS1692
-
- Invalid number
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1695.xml b/docs/Help_Spanish/Topics/XS1695.xml
deleted file mode 100644
index 7e2b2ce88e..0000000000
--- a/docs/Help_Spanish/Topics/XS1695.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1695
-
- XS1695
-
-
-
- Warning XS1695
-
- Invalid #pragma checksum syntax; should be #pragma checksum "filename" "{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}" "XXXX..."
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1696.xml b/docs/Help_Spanish/Topics/XS1696.xml
deleted file mode 100644
index e0ad031bbe..0000000000
--- a/docs/Help_Spanish/Topics/XS1696.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1696
-
- XS1696
-
-
-
- Warning XS1696
-
- Single-line comment or end-of-line expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1697.xml b/docs/Help_Spanish/Topics/XS1697.xml
deleted file mode 100644
index be597e1ebc..0000000000
--- a/docs/Help_Spanish/Topics/XS1697.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1697
-
- XS1697
-
-
-
- Warning XS1697
-
- Different checksum values given for '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1700.xml b/docs/Help_Spanish/Topics/XS1700.xml
deleted file mode 100644
index 5cee400b4b..0000000000
--- a/docs/Help_Spanish/Topics/XS1700.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS1700
-
- XS1700
-
-
-
- Warning XS1700
-
- Assembly reference Assembly Name is invalid and cannot be resolved
-
- This warning indicates that an attribute, such as InternalsVisibleToAttribute, was not specified correctly.
-
- For more information, see Friend Assemblies.
- Example
-
- The following sample generates XS1700.
-
-
- // XS1700.prg // compile with: /target:library
-
-
diff --git a/docs/Help_Spanish/Topics/XS1701.xml b/docs/Help_Spanish/Topics/XS1701.xml
deleted file mode 100644
index 298de63e66..0000000000
--- a/docs/Help_Spanish/Topics/XS1701.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- XS1701
-
- XS1701
-
-
-
- Warning XS1701
-
- Assuming assembly reference "Assembly Name #1" matches "Assembly Name #2", you may need to supply runtime policy
-
- The two assemblies differ in release and/or version number. For unification to occur, you must specify directives in the application's .config file, and you must provide the correct strong name of an assembly, as demonstrated in the following example code.
- Example
-
- The following multifile sample references an assembly using two different external aliases. This first sample builds the older version of the code that creates assembly XS1701_d.
-
-
- // XS1701_a.prg // compile with: /target:library /out:XS1701_d.dll /keyfile:mykey.snk
-
- Example
-
- This is the code that creates the newer version of assembly XS1701_d. Note that it compiles into a different directory than the older version, necessary since the output files have the same names.
-
-
- // XS1701_b.prg // compile with: /target:library /out:c:\\XS1701_d.dll /keyfile:mykey.snk
-
- Example
-
- This sample sets up the external aliases A1 and A2.
-
-
- // XS1701_c.prg // compile with: /target:library /reference:A2=c:\\XS1701_d.dll /reference:A1=XS1701_d.dll
-
- Example
-
- This sample calls methods using two different aliases of A. The following sample generates C1701.
-
-
- // XS1701_d.prg // compile with: /reference:c:\\XS1701_d.dll /reference:XS1701_c.dll // XS1701 expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1702.xml b/docs/Help_Spanish/Topics/XS1702.xml
deleted file mode 100644
index 59a27d9f6a..0000000000
--- a/docs/Help_Spanish/Topics/XS1702.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1702
-
- XS1702
-
-
-
- Warning XS1702
-
- Assuming assembly reference '{0}' used by '{1}' matches identity '{2}' of '{3}', you may need to supply runtime policy
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1703.xml b/docs/Help_Spanish/Topics/XS1703.xml
deleted file mode 100644
index f791519727..0000000000
--- a/docs/Help_Spanish/Topics/XS1703.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- XS1703
-
- XS1703
-
-
-
- Error XS1703
-
- An assembly with the same simple name 'name' has already been imported. Try removing one of the references or sign them to enable side-by-side.
-
- The compiler removes references that have the same path and file name, but it is possible that the same file exists in two places, or that you forgot to change the version number. This error points out that two references have the same assembly identity and thus the compiler has no way of distinguishing between them in metadata. Either remove one of the redundant references, or make the references unique somehow, such as by incrementing the assembly version number.
-
- The following code generates error XS1703.
- Example
-
- This code creates assembly A in the .\bin1 directory.
- Save this example in a file named XS1703a1.prg, and compile it with the following flags: /t:library /out:.\bin1\XS1703.dll /keyfile:key.snk
-
-
-
- Example
-
- This code creates a copy of assembly A in the .\bin2 directory.
- Save this example in a file named XS1703a2.prg, and compile it with the following flags: /t:library /out:.\bin2\XS1703.dll /keyfile:key.snk
-
- Example
-
- This code references the assembly A in the two prior modules.
- Save this example in a file named XS1703ref.prg, and compile it with the following flags: /t:library /r:A2=.\bin2\XS1703.dll /r:A1=.\bin1\XS1703.dll
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1704.xml b/docs/Help_Spanish/Topics/XS1704.xml
deleted file mode 100644
index 8833bfb88a..0000000000
--- a/docs/Help_Spanish/Topics/XS1704.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- XS1704
-
- XS1704
-
-
-
- Error XS1704
-
- An assembly with the same simple name 'Assembly Name' has already been imported. Try removing one of the references or sign them to enable side-by-side.
-
- This error points out that two references have the same assembly identity because the assemblies in question lack strong names, they were not signed, and thus the compiler has no way of distinguishing between them in metadata. Thus, the run time ignores the version and culture assembly name properties. The user should remove the redundant reference, rename one of the references, or provide a strong name for them.
- Example
-
- This sample creates an assembly and saves it to the root directory.
-
-
- // XS1704_a.prg // compile with: /target:library /out:c:\\XS1704.dll
-
- Example
-
- This sample creates an assembly with the same name as the previous sample, but saves it to a different location.
-
-
- // XS1704_b.prg // compile with: /target:library /out:XS1704.dll
-
- Example
-
- This sample attempts to reference both assemblies. The following sample generates XS1704.
-
-
- // XS1704_c.prg // compile with: /target:library /r:A2=XS1704.dll /r:A1=c:\\XS1704.dll // XS1704 expected
-
-
diff --git a/docs/Help_Spanish/Topics/XS1705.xml b/docs/Help_Spanish/Topics/XS1705.xml
deleted file mode 100644
index 3809dd64f2..0000000000
--- a/docs/Help_Spanish/Topics/XS1705.xml
+++ /dev/null
@@ -1,65 +0,0 @@
-
-
-
- XS1705
-
- XS1705
-
-
-
- Error XS1705
-
- Assembly 'AssemblyName1' uses 'TypeName' which has a higher version than referenced assembly 'AssemblyName2'
-
- You are accessing a type that has a higher version number than the version number in a referenced assembly. Typically, this error is caused by the accidental use of two versions of the same assembly.
-
- For example, suppose that you have two assemblies, Asmb1 and Asmb2. Assembly Asmb1 references version 1.0 of assembly Asmb2. Assembly Asmb1 also uses a class MyClass that was added to assembly Asmb2 in version 2.0. The compiler has unification rules for binding references, and a reference to MyClass in version 2.0 cannot be satisfied by version 1.0.
- Example
-
- The following more detailed example consists of four code modules:
-
-
-
Two DLLs that are identical except for a version attribute.
-
A third DLL that references the first two.
-
A client that references only version 1.0 of the identical DLLs, but accesses a class from version 2.0.
-
-
- The following code creates the first of the identical DLLs. For information about how to generate a key file, see /keyfile (X# Compiler Options).
-
-
- // XS1705a.prg
- Example
-
- The following code defines version 2.0 of the assembly, as specified by the AssemblyVersionAttribute attribute.
-
-
- // XS1705b.prg
-
- Example
-
- The following code references the two DLL versions that are defined in the preceding code. AssemblyA refers to the DLL created by XS1705a.prg (version 1.0). AssemblyB refers to the DLL created by XS1705b.prg (version 2.0). In ClassC, two methods are defined. The first, Return1A, returns an object of type Class1A, which is an alias for Class1 from version 1.0 of the DLL. The second, Return1B, returns an object of type Class1B, which is an alias for Class1 from version 2.0 of the DLL. The definition of Return1A creates a dependency on version 1.0; the definition of Return1B creates a dependency on version 2.0.
-
-
- // XS1705c.prg
-
-
- Example
-
- The following code generates compiler error XS1705. It references the DLL created by XS1705a.prg (version 1.0). However, in the Main method, the code accesses ClassC from XS1705c.prg. ClassC uses a type that is defined in XS1705b.prg (version 2.0). This causes compiler error XS1705 because the type has a version number for XS1705.dll that is higher than the referenced version of XS1705.dll.
-
-
- // XS1705d.prg
-
-
- You can resolve the error in one of the following ways:
-
-
-
Update the code so that all files use the same version of the DLL.
-
Add a reference to version 2.0 of the DLL to XS1705d.prg by using the following command to compile:
-
-
- xsc /reference:C:\\XS1705.dll /reference:XS1705.dll /reference:XS1705c.dll XS1705d.prg
-
- Although the program compiles when you use this command, it still does not run. To enable the program to run, you can provide an application configuration file that includes a <dependentAssembly> element that uses <assemblyIdentity> and <codeBase> child elements to specify the location of version 1.0 of the DLL. For more information about configuration files, see Configuring Apps.
-
-
diff --git a/docs/Help_Spanish/Topics/XS1708.xml b/docs/Help_Spanish/Topics/XS1708.xml
deleted file mode 100644
index 37f5a0ce3b..0000000000
--- a/docs/Help_Spanish/Topics/XS1708.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS1708
-
- XS1708
-
-
-
- Error XS1708
-
- Fixed size buffers can only be accessed through locals or fields
-
- A new feature in X# 2.0 is the ability to define an in-line array inside of a struct. Such arrays can only be accessed via local variables or fields, and may not be referenced as intermediate values on the left-hand side of an expression. Also, the arrays cannot be accessed by fields that are static or readonly.
-
- To resolve this error, define an array variable, and assign the in-line array to the variable. Or, remove the static or readonly modifier from the field representing the in-line array.
- Example
-
- The following sample generates XS1708.
-
-
- // XS1708.prg // compile with: /unsafe
-
-
diff --git a/docs/Help_Spanish/Topics/XS1710.xml b/docs/Help_Spanish/Topics/XS1710.xml
deleted file mode 100644
index e0b5125ef8..0000000000
--- a/docs/Help_Spanish/Topics/XS1710.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1710
-
- XS1710
-
-
-
- Warning XS1710
-
- XML comment has a duplicate typeparam tag for '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1711.xml b/docs/Help_Spanish/Topics/XS1711.xml
deleted file mode 100644
index 7290055cb5..0000000000
--- a/docs/Help_Spanish/Topics/XS1711.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1711
-
- XS1711
-
-
-
- Warning XS1711
-
- XML comment has a typeparam tag for '{0}', but there is no type parameter by that name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1712.xml b/docs/Help_Spanish/Topics/XS1712.xml
deleted file mode 100644
index 26d6026232..0000000000
--- a/docs/Help_Spanish/Topics/XS1712.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1712
-
- XS1712
-
-
-
- Warning XS1712
-
- Type parameter '{0}' has no matching typeparam tag in the XML comment on '{1}' (but other type parameters do)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1715.xml b/docs/Help_Spanish/Topics/XS1715.xml
deleted file mode 100644
index 4621d2100d..0000000000
--- a/docs/Help_Spanish/Topics/XS1715.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1715
-
-XS1715
-
-
-
- Error XS1715
-
- '{0}': type must be '{2}' to match overridden member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1716.xml b/docs/Help_Spanish/Topics/XS1716.xml
deleted file mode 100644
index e049f0e7e7..0000000000
--- a/docs/Help_Spanish/Topics/XS1716.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS1716
-
- XS1716
-
-
-
- Error XS1716
-
- Do not use 'System.Runtime.CompilerServices.FixedBuffer' attribute. Use the 'fixed' field modifier instead.
-
- This error arises in an unsafe code section that contains a fixed-size array declaration similar to a field declaration. Do not use this attribute. Instead, use the keyword fixed.
- Example
-
- The following example generates XS1716.
-
-
- // XS1716.prg // compile with: /unsafe
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1717.xml b/docs/Help_Spanish/Topics/XS1717.xml
deleted file mode 100644
index 0094cf4795..0000000000
--- a/docs/Help_Spanish/Topics/XS1717.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1717
-
- XS1717
-
-
-
- Warning XS1717
-
- Assignment made to same variable; did you mean to assign something else?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1718.xml b/docs/Help_Spanish/Topics/XS1718.xml
deleted file mode 100644
index e79f61a554..0000000000
--- a/docs/Help_Spanish/Topics/XS1718.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1718
-
- XS1718
-
-
-
- Warning XS1718
-
- Comparison made to same variable; did you mean to compare something else?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1719.xml b/docs/Help_Spanish/Topics/XS1719.xml
deleted file mode 100644
index 01eb010205..0000000000
--- a/docs/Help_Spanish/Topics/XS1719.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1719
-
-XS1719
-
-
-
- Error XS1719
-
- Error opening Win32 resource file '{0}' -- '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1720.xml b/docs/Help_Spanish/Topics/XS1720.xml
deleted file mode 100644
index 76224fad85..0000000000
--- a/docs/Help_Spanish/Topics/XS1720.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1720
-
- XS1720
-
-
-
- Warning XS1720
-
- Expression will always cause a System.NullReferenceException because the default value of '{0}' is null
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1721.xml b/docs/Help_Spanish/Topics/XS1721.xml
deleted file mode 100644
index f03cb48f9e..0000000000
--- a/docs/Help_Spanish/Topics/XS1721.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- XS1721
-
- XS1721
-
-
-
- Error XS1721
-
- Class 'class' cannot have multiple base classes: 'class_1' and 'class_2'
-
- The most common cause of this error message is attempting to use multiple inheritance. A class in X# may only inherit directly from one class. However, a class can implement any number of interfaces.
-
- Example
-
- The following example shows one way in which SC1721 is generated, and then shows two possible ways to avoid the error.
-
-
- // XS1721.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1722.xml b/docs/Help_Spanish/Topics/XS1722.xml
deleted file mode 100644
index b63aa035f9..0000000000
--- a/docs/Help_Spanish/Topics/XS1722.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1722
-
-XS1722
-
-
-
- Error XS1722
-
- Base class '{0}' must come before any interfaces
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1723.xml b/docs/Help_Spanish/Topics/XS1723.xml
deleted file mode 100644
index 5676a9b24a..0000000000
--- a/docs/Help_Spanish/Topics/XS1723.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1723
-
- XS1723
-
-
-
- Warning XS1723
-
- XML comment has cref attribute '{0}' that refers to a type parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1725.xml b/docs/Help_Spanish/Topics/XS1725.xml
deleted file mode 100644
index 4d4dafa6ad..0000000000
--- a/docs/Help_Spanish/Topics/XS1725.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1725
-
-XS1725
-
-
-
- Error XS1725
-
- Friend assembly reference '{0}' is invalid. InternalsVisibleTo declarations cannot have a version, culture, public key token, or processor architecture specified.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1726.xml b/docs/Help_Spanish/Topics/XS1726.xml
deleted file mode 100644
index 8484a57319..0000000000
--- a/docs/Help_Spanish/Topics/XS1726.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- XS1726
-
- XS1726
-
-
-
- Error XS1726
-
- Friend assembly reference 'reference' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
-
- A strong name signed assembly can only grant friend assembly access, made with the InternalsVisibleToAttribute, to other strongly signed assemblies.
-
- To resolve XS1726, either sign (give a strong name to) the assembly to which you want to grant friend access, or don't grant friend access.
-
- For more information, see Friend Assemblies.
- Example
-
- The following sample generates XS1726.
-
-
- // Save this code as XS1726.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1728.xml b/docs/Help_Spanish/Topics/XS1728.xml
deleted file mode 100644
index 7e185bf6ed..0000000000
--- a/docs/Help_Spanish/Topics/XS1728.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1728
-
-XS1728
-
-
-
- Error XS1728
-
- Cannot bind delegate to '{0}' because it is a member of 'System.Nullable'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1729.xml b/docs/Help_Spanish/Topics/XS1729.xml
deleted file mode 100644
index f3c7f0733f..0000000000
--- a/docs/Help_Spanish/Topics/XS1729.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XS1729
-
- XS1729
-
-
-
- Error XS1729
-
- 'type' does not contain a constructor that takes 'number' arguments.
-
- This error occurs when you either directly or indirectly invoke the constructor of a class but the compiler cannot find any constructors with the same number of parameters. In the following example, the test class has no constructors that take any arguments. It therefore has only a default constructor that takes zero arguments. Because in the second line in which the error is generated, the derived class declares no constructors of its own, the compiler provides a default constructor. That constructor invokes a parameterless constructor in the base class. Because the base class has no such constructor, XS1729 is generated.
-
- To correct this error
-
-
-
Adjust the number of parameters in the call to the constructor.
-
Modify the class to provide a constructor with the parameters you must call.
-
Provide a parameterless constructor in the base class.
-
- Example
-
- The following example generates XS1729:
-
-
- // XS1729.prg
-
-
diff --git a/docs/Help_Spanish/Topics/XS1730.xml b/docs/Help_Spanish/Topics/XS1730.xml
deleted file mode 100644
index 5462bc66ae..0000000000
--- a/docs/Help_Spanish/Topics/XS1730.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1730
-
-XS1730
-
-
-
- Error XS1730
-
- Assembly and module attributes must precede all other elements defined in a file except using clauses and extern alias declarations
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1733.xml b/docs/Help_Spanish/Topics/XS1733.xml
deleted file mode 100644
index b46d85c45c..0000000000
--- a/docs/Help_Spanish/Topics/XS1733.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1733
-
-XS1733
-
-
-
- Error XS1733
-
- Expected expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1734.xml b/docs/Help_Spanish/Topics/XS1734.xml
deleted file mode 100644
index c57c1b9c2f..0000000000
--- a/docs/Help_Spanish/Topics/XS1734.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1734
-
- XS1734
-
-
-
- Warning XS1734
-
- XML comment on '{1}' has a paramref tag for '{0}', but there is no parameter by that name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1735.xml b/docs/Help_Spanish/Topics/XS1735.xml
deleted file mode 100644
index 3cf558adb2..0000000000
--- a/docs/Help_Spanish/Topics/XS1735.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1735
-
- XS1735
-
-
-
- Warning XS1735
-
- XML comment on '{1}' has a typeparamref tag for '{0}', but there is no type parameter by that name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1736.xml b/docs/Help_Spanish/Topics/XS1736.xml
deleted file mode 100644
index 454d7a49d9..0000000000
--- a/docs/Help_Spanish/Topics/XS1736.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1736
-
-XS1736
-
-
-
- Error XS1736
-
- Default parameter value for '{0}' must be a compile-time constant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1737.xml b/docs/Help_Spanish/Topics/XS1737.xml
deleted file mode 100644
index 77ffa836c3..0000000000
--- a/docs/Help_Spanish/Topics/XS1737.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1737
-
-XS1737
-
-
-
- Error XS1737
-
- Optional parameters must appear after all required parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1738.xml b/docs/Help_Spanish/Topics/XS1738.xml
deleted file mode 100644
index 5a0d611caf..0000000000
--- a/docs/Help_Spanish/Topics/XS1738.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1738
-
-XS1738
-
-
-
- Error XS1738
-
- Named argument specifications must appear after all fixed arguments have been specified
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1739.xml b/docs/Help_Spanish/Topics/XS1739.xml
deleted file mode 100644
index 85b98b8f51..0000000000
--- a/docs/Help_Spanish/Topics/XS1739.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1739
-
-XS1739
-
-
-
- Error XS1739
-
- The best overload for '{0}' does not have a parameter named '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1740.xml b/docs/Help_Spanish/Topics/XS1740.xml
deleted file mode 100644
index 24404096dc..0000000000
--- a/docs/Help_Spanish/Topics/XS1740.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1740
-
-XS1740
-
-
-
- Error XS1740
-
- Named argument '{0}' cannot be specified multiple times
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1741.xml b/docs/Help_Spanish/Topics/XS1741.xml
deleted file mode 100644
index b90bc2cb70..0000000000
--- a/docs/Help_Spanish/Topics/XS1741.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1741
-
-XS1741
-
-
-
- Error XS1741
-
- A ref or out parameter cannot have a default value
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1742.xml b/docs/Help_Spanish/Topics/XS1742.xml
deleted file mode 100644
index 6f52c4352f..0000000000
--- a/docs/Help_Spanish/Topics/XS1742.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1742
-
-XS1742
-
-
-
- Error XS1742
-
- An array access may not have a named argument specifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1743.xml b/docs/Help_Spanish/Topics/XS1743.xml
deleted file mode 100644
index 9d5da6013d..0000000000
--- a/docs/Help_Spanish/Topics/XS1743.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1743
-
-XS1743
-
-
-
- Error XS1743
-
- Cannot specify a default value for the 'SELF' parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1744.xml b/docs/Help_Spanish/Topics/XS1744.xml
deleted file mode 100644
index d97426d73d..0000000000
--- a/docs/Help_Spanish/Topics/XS1744.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1744
-
-XS1744
-
-
-
- Error XS1744
-
- Named argument '{0}' specifies a parameter for which a positional argument has already been given
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1745.xml b/docs/Help_Spanish/Topics/XS1745.xml
deleted file mode 100644
index eaf873b132..0000000000
--- a/docs/Help_Spanish/Topics/XS1745.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1745
-
-XS1745
-
-
-
- Error XS1745
-
- Cannot specify default parameter value in conjunction with DefaultParameterAttribute or OptionalAttribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1746.xml b/docs/Help_Spanish/Topics/XS1746.xml
deleted file mode 100644
index 16ee631c8b..0000000000
--- a/docs/Help_Spanish/Topics/XS1746.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1746
-
-XS1746
-
-
-
- Error XS1746
-
- The delegate '{0}' does not have a parameter named '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1747.xml b/docs/Help_Spanish/Topics/XS1747.xml
deleted file mode 100644
index 3e99be6d12..0000000000
--- a/docs/Help_Spanish/Topics/XS1747.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1747
-
-XS1747
-
-
-
- Error XS1747
-
- Cannot embed interop types from assembly '{0}' because it is missing the '{1}' attribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1748.xml b/docs/Help_Spanish/Topics/XS1748.xml
deleted file mode 100644
index 12ecbc2040..0000000000
--- a/docs/Help_Spanish/Topics/XS1748.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1748
-
-XS1748
-
-
-
- Error XS1748
-
- Cannot find the interop type that matches the embedded interop type '{0}'. Are you missing an assembly reference?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1750.xml b/docs/Help_Spanish/Topics/XS1750.xml
deleted file mode 100644
index ac880d98cb..0000000000
--- a/docs/Help_Spanish/Topics/XS1750.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1750
-
-XS1750
-
-
-
- Error XS1750
-
- A value of type '{0}' cannot be used as a default parameter because there are no standard conversions to type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1751.xml b/docs/Help_Spanish/Topics/XS1751.xml
deleted file mode 100644
index a4583bd21b..0000000000
--- a/docs/Help_Spanish/Topics/XS1751.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1751
-
-XS1751
-
-
-
- Error XS1751
-
- Cannot specify a default value for a parameter array
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1752.xml b/docs/Help_Spanish/Topics/XS1752.xml
deleted file mode 100644
index 40568537be..0000000000
--- a/docs/Help_Spanish/Topics/XS1752.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1752
-
-XS1752
-
-
-
- Error XS1752
-
- Interop type '{0}' cannot be embedded. Use the applicable interface instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1754.xml b/docs/Help_Spanish/Topics/XS1754.xml
deleted file mode 100644
index 8efd21a814..0000000000
--- a/docs/Help_Spanish/Topics/XS1754.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1754
-
-XS1754
-
-
-
- Error XS1754
-
- Type '{0}' cannot be embedded because it is a nested type. Consider setting the 'Embed Interop Types' property to false.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1756.xml b/docs/Help_Spanish/Topics/XS1756.xml
deleted file mode 100644
index 06843cdfdc..0000000000
--- a/docs/Help_Spanish/Topics/XS1756.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1756
-
-XS1756
-
-
-
- Error XS1756
-
- Interop type '{0}' cannot be embedded because it is missing the required '{1}' attribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1757.xml b/docs/Help_Spanish/Topics/XS1757.xml
deleted file mode 100644
index 55d291edb5..0000000000
--- a/docs/Help_Spanish/Topics/XS1757.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1757
-
-XS1757
-
-
-
- Error XS1757
-
- Embedded interop struct '{0}' can contain only public instance fields.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1758.xml b/docs/Help_Spanish/Topics/XS1758.xml
deleted file mode 100644
index 53c988302c..0000000000
--- a/docs/Help_Spanish/Topics/XS1758.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1758
-
-XS1758
-
-
-
- Error XS1758
-
- Cannot embed interop type '{0}' found in both assembly '{1}' and '{2}'. Consider setting the 'Embed Interop Types' property to false.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1759.xml b/docs/Help_Spanish/Topics/XS1759.xml
deleted file mode 100644
index 0343959b13..0000000000
--- a/docs/Help_Spanish/Topics/XS1759.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1759
-
-XS1759
-
-
-
- Error XS1759
-
- Cannot embed interop types from assembly '{0}' because it is missing either the '{1}' attribute or the '{2}' attribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1760.xml b/docs/Help_Spanish/Topics/XS1760.xml
deleted file mode 100644
index f913a1c164..0000000000
--- a/docs/Help_Spanish/Topics/XS1760.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1760
-
-XS1760
-
-
-
- Error XS1760
-
- Assemblies '{0}' and '{1}' refer to the same metadata but only one is a linked reference (specified using /link option); consider removing one of the references.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1761.xml b/docs/Help_Spanish/Topics/XS1761.xml
deleted file mode 100644
index 6a6670eee8..0000000000
--- a/docs/Help_Spanish/Topics/XS1761.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1761
-
-XS1761
-
-
-
- Error XS1761
-
- Embedding the interop type '{0}' from assembly '{1}' causes a name clash in the current assembly. Consider setting the 'Embed Interop Types' property to false.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1762.xml b/docs/Help_Spanish/Topics/XS1762.xml
deleted file mode 100644
index 85f255b4d4..0000000000
--- a/docs/Help_Spanish/Topics/XS1762.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- XS1762
-
- XS1762
-
-
-
- Warning XS1762
-
- A reference was created to embedded interop assembly '<assembly1>' because of an indirect reference to that assembly from assembly '<assembly2>'. Consider changing the 'Embed Interop Types' property on either assembly.
-
- You have added a reference to an assembly (assembly1) that has the Embed Interop Types property set to True. This instructs the compiler to embed interop type information from that assembly. However, the compiler cannot embed interop type information from that assembly because another assembly that you have referenced (assembly2) also references that assembly (assembly1) and has the Embed Interop Types property set to False.
-
- Note
- Setting the Embed Interop Types property on an assembly reference to True is equivalent to referencing the assembly by using the /link option for the command-line compiler.
- To address this warning
-
-
-
To embed interop type information for both assemblies, set the Embed Interop Types property on all references to assembly1 to True. For more information about how to set that property, see Walkthrough: Embedding Types from Managed Assemblies.
-
To remove the warning, you can set the Embed Interop Types property of assembly1 to False. In this case, a primary interop assembly (PIA) provides interop type information.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1763.xml b/docs/Help_Spanish/Topics/XS1763.xml
deleted file mode 100644
index 5d26f847c5..0000000000
--- a/docs/Help_Spanish/Topics/XS1763.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1763
-
-XS1763
-
-
-
- Error XS1763
-
- '{0}' is of type '{1}'. A default parameter value of a reference type other than string can only be initialized with null
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1764.xml b/docs/Help_Spanish/Topics/XS1764.xml
deleted file mode 100644
index beef0d633c..0000000000
--- a/docs/Help_Spanish/Topics/XS1764.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1764
-
-XS1764
-
-
-
- Error XS1764
-
- Cannot use fixed local '{0}' inside an anonymous method, lambda expression, or query expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1766.xml b/docs/Help_Spanish/Topics/XS1766.xml
deleted file mode 100644
index 857a188124..0000000000
--- a/docs/Help_Spanish/Topics/XS1766.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1766
-
-XS1766
-
-
-
- Error XS1766
-
- Source interface '{0}' is missing method '{1}' which is required to embed event '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1767.xml b/docs/Help_Spanish/Topics/XS1767.xml
deleted file mode 100644
index 98f14b260f..0000000000
--- a/docs/Help_Spanish/Topics/XS1767.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1767
-
-XS1767
-
-
-
- Error XS1767
-
- Interface '{0}' has an invalid source interface which is required to embed event '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1768.xml b/docs/Help_Spanish/Topics/XS1768.xml
deleted file mode 100644
index 84aa9cda03..0000000000
--- a/docs/Help_Spanish/Topics/XS1768.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1768
-
-XS1768
-
-
-
- Error XS1768
-
- Type '{0}' cannot be embedded because it has a generic argument. Consider setting the 'Embed Interop Types' property to false.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1769.xml b/docs/Help_Spanish/Topics/XS1769.xml
deleted file mode 100644
index be2adc91a0..0000000000
--- a/docs/Help_Spanish/Topics/XS1769.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1769
-
-XS1769
-
-
-
- Error XS1769
-
- Type '{0}' from assembly '{1}' cannot be used across assembly boundaries because it has a generic type parameter that is an embedded interop type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1770.xml b/docs/Help_Spanish/Topics/XS1770.xml
deleted file mode 100644
index bc48e953a1..0000000000
--- a/docs/Help_Spanish/Topics/XS1770.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1770
-
-XS1770
-
-
-
- Error XS1770
-
- A value of type '{0}' cannot be used as default parameter for nullable parameter '{1}' because '{0}' is not a simple type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1773.xml b/docs/Help_Spanish/Topics/XS1773.xml
deleted file mode 100644
index 0203bc06c6..0000000000
--- a/docs/Help_Spanish/Topics/XS1773.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1773
-
-XS1773
-
-
-
- Error XS1773
-
- Invalid version {0} for /subsystemversion. The version must be 6.02 or greater for ARM or AppContainerExe, and 4.00 or greater otherwise
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1774.xml b/docs/Help_Spanish/Topics/XS1774.xml
deleted file mode 100644
index 8e7bfdd74c..0000000000
--- a/docs/Help_Spanish/Topics/XS1774.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1774
-
-XS1774
-
-
-
- Error XS1774
-
- Embedded interop method '{0}' contains a body.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1900.xml b/docs/Help_Spanish/Topics/XS1900.xml
deleted file mode 100644
index 4f7279921f..0000000000
--- a/docs/Help_Spanish/Topics/XS1900.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1900
-
-XS1900
-
-
-
- Error XS1900
-
- Warning level must be in the range 0-4
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1902.xml b/docs/Help_Spanish/Topics/XS1902.xml
deleted file mode 100644
index 747993a2c3..0000000000
--- a/docs/Help_Spanish/Topics/XS1902.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1902
-
-XS1902
-
-
-
- Error XS1902
-
- Invalid option '{0}' for /debug; must be full or pdbonly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1906.xml b/docs/Help_Spanish/Topics/XS1906.xml
deleted file mode 100644
index 2164efcafd..0000000000
--- a/docs/Help_Spanish/Topics/XS1906.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1906
-
-XS1906
-
-
-
- Error XS1906
-
- Invalid option '{0}'; Resource visibility must be either 'public' or 'private'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1908.xml b/docs/Help_Spanish/Topics/XS1908.xml
deleted file mode 100644
index 71fe1bae9d..0000000000
--- a/docs/Help_Spanish/Topics/XS1908.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1908
-
-XS1908
-
-
-
- Error XS1908
-
- The type of the argument to the DefaultParameterValue attribute must match the parameter type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1910.xml b/docs/Help_Spanish/Topics/XS1910.xml
deleted file mode 100644
index 202c621fc9..0000000000
--- a/docs/Help_Spanish/Topics/XS1910.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1910
-
-XS1910
-
-
-
- Error XS1910
-
- Argument of type '{0}' is not applicable for the DefaultParameterValue attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1912.xml b/docs/Help_Spanish/Topics/XS1912.xml
deleted file mode 100644
index 8101d7db74..0000000000
--- a/docs/Help_Spanish/Topics/XS1912.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1912
-
-XS1912
-
-
-
- Error XS1912
-
- Duplicate initialization of member '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1913.xml b/docs/Help_Spanish/Topics/XS1913.xml
deleted file mode 100644
index 9d1b06c513..0000000000
--- a/docs/Help_Spanish/Topics/XS1913.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1913
-
-XS1913
-
-
-
- Error XS1913
-
- Member '{0}' cannot be initialized. It is not a field or property.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1914.xml b/docs/Help_Spanish/Topics/XS1914.xml
deleted file mode 100644
index 4d68d0ba94..0000000000
--- a/docs/Help_Spanish/Topics/XS1914.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1914
-
-XS1914
-
-
-
- Error XS1914
-
- Static field or property '{0}' cannot be assigned in an object initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1917.xml b/docs/Help_Spanish/Topics/XS1917.xml
deleted file mode 100644
index 36313d80c0..0000000000
--- a/docs/Help_Spanish/Topics/XS1917.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1917
-
-XS1917
-
-
-
- Error XS1917
-
- Members of readonly field '{0}' of type '{1}' cannot be assigned with an object initializer because it is of a value type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1918.xml b/docs/Help_Spanish/Topics/XS1918.xml
deleted file mode 100644
index aab4b488c9..0000000000
--- a/docs/Help_Spanish/Topics/XS1918.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1918
-
-XS1918
-
-
-
- Error XS1918
-
- Members of property '{0}' of type '{1}' cannot be assigned with an object initializer because it is of a value type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1919.xml b/docs/Help_Spanish/Topics/XS1919.xml
deleted file mode 100644
index 788a47ed08..0000000000
--- a/docs/Help_Spanish/Topics/XS1919.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- XS1919
-
- XS1919
-
-
-
- Error XS1919
-
- Unsafe type 'type name' cannot be used in object creation.
-
- The new operator creates objects only on the managed heap. However, you can create objects in unmanaged memory indirectly by using the interoperability capabilities of the language to call native methods that return pointers.
-
- To correct this error
-
-
-
Use a safe type in the new object creation expression. For example, use char or int instead of char* or int*.
-
If you must create objects in unmanaged memory, use a Win32 or COM method or else write your own function in C or C++ and call it from X#.
-
- Example
-
- The following example generates XS1919 because a pointer type is unsafe:
-
-
- // XS1919.prg // Compile with: /unsafe
-
-
diff --git a/docs/Help_Spanish/Topics/XS1920.xml b/docs/Help_Spanish/Topics/XS1920.xml
deleted file mode 100644
index 441d273979..0000000000
--- a/docs/Help_Spanish/Topics/XS1920.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1920
-
-XS1920
-
-
-
- Error XS1920
-
- Element initializer cannot be empty
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1921.xml b/docs/Help_Spanish/Topics/XS1921.xml
deleted file mode 100644
index d1196659e0..0000000000
--- a/docs/Help_Spanish/Topics/XS1921.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS1921
-
- XS1921
-
-
-
- Error XS1921
-
- The best overloaded method match for 'method' has wrong signature for the initializer element. The initializable Add must be an accessible instance method.
-
- This error is generated when you try to use a collection initializer with a class that has no public non-static Add method. If the Add method is not accessible because of its protection level (private, protected, internal) then you will get XS0122, so that this error probably means that the method is defined as static.
-
- Example
-
- The following example generates XS1921:
-
-
- // XS1921.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1922.xml b/docs/Help_Spanish/Topics/XS1922.xml
deleted file mode 100644
index 00428a7e54..0000000000
--- a/docs/Help_Spanish/Topics/XS1922.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1922
-
-XS1922
-
-
-
- Error XS1922
-
- Cannot initialize type '{0}' with a collection initializer because it does not implement 'System.Collections.IEnumerable'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1926.xml b/docs/Help_Spanish/Topics/XS1926.xml
deleted file mode 100644
index faef73c102..0000000000
--- a/docs/Help_Spanish/Topics/XS1926.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS1926
-
- XS1926
-
-
-
- Error XS1926
-
- Error reading Win32 manifest file 'filename' -- 'error'.
-
- This error is generated when the following conditions are true:
-
-
-
The /win32manifest option is specified either on the command line or by right-clicking the Project icon in Solution Explorer, pointing to Add, clicking New Item, and then clicking Application Manifest File.
-
The file is either corrupted or missing.
-
- To correct this error
-
-
-
Remove the option.
-
Replace, repair, or regenerate the file.
-
- Example
-
- The following example generates XS1926 when it is compiled with a corrupted for missing win32 manifest file:
// XS1926.prg // Compile with: /win32manifest: ../../app.manifest
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1927.xml b/docs/Help_Spanish/Topics/XS1927.xml
deleted file mode 100644
index db1a6c5326..0000000000
--- a/docs/Help_Spanish/Topics/XS1927.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1927
-
- XS1927
-
-
-
- Warning XS1927
-
- Ignoring /win32manifest for module because it only applies to assemblies
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1928.xml b/docs/Help_Spanish/Topics/XS1928.xml
deleted file mode 100644
index b52f314770..0000000000
--- a/docs/Help_Spanish/Topics/XS1928.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1928
-
-XS1928
-
-
-
- Error XS1928
-
- '{0}' does not contain a definition for '{1}' and the best extension method overload '{2}' has some invalid arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1929.xml b/docs/Help_Spanish/Topics/XS1929.xml
deleted file mode 100644
index 8efc1202bc..0000000000
--- a/docs/Help_Spanish/Topics/XS1929.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1929
-
-XS1929
-
-
-
- Error XS1929
-
- '{0}' does not contain a definition for '{1}' and the best extension method overload '{2}' requires a receiver of type '{3}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1930.xml b/docs/Help_Spanish/Topics/XS1930.xml
deleted file mode 100644
index b9869dcd6b..0000000000
--- a/docs/Help_Spanish/Topics/XS1930.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1930
-
-XS1930
-
-
-
- Error XS1930
-
- The range variable '{0}' has already been declared
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1931.xml b/docs/Help_Spanish/Topics/XS1931.xml
deleted file mode 100644
index 87a8675082..0000000000
--- a/docs/Help_Spanish/Topics/XS1931.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1931
-
-XS1931
-
-
-
- Error XS1931
-
- The range variable '{0}' conflicts with a previous declaration of '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1932.xml b/docs/Help_Spanish/Topics/XS1932.xml
deleted file mode 100644
index 69d4755c78..0000000000
--- a/docs/Help_Spanish/Topics/XS1932.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1932
-
-XS1932
-
-
-
- Error XS1932
-
- Cannot assign {0} to a range variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1934.xml b/docs/Help_Spanish/Topics/XS1934.xml
deleted file mode 100644
index 04ae387049..0000000000
--- a/docs/Help_Spanish/Topics/XS1934.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1934
-
-XS1934
-
-
-
- Error XS1934
-
- Could not find an implementation of the query pattern for source type '{0}'. '{1}' not found. Consider explicitly specifying the type of the range variable '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1935.xml b/docs/Help_Spanish/Topics/XS1935.xml
deleted file mode 100644
index d9728f0e4d..0000000000
--- a/docs/Help_Spanish/Topics/XS1935.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1935
-
-XS1935
-
-
-
- Error XS1935
-
- Could not find an implementation of the query pattern for source type '{0}'. '{1}' not found. Are you missing a reference to 'System.Core.dll' or a using directive for 'System.Linq'?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1936.xml b/docs/Help_Spanish/Topics/XS1936.xml
deleted file mode 100644
index ecdf8802df..0000000000
--- a/docs/Help_Spanish/Topics/XS1936.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS1936
-
- XS1936
-
-
-
- Error XS1936
-
- Could not find an implementation of the query pattern for source type 'type'. 'method' not found.
-
- In order to query a source type, that type must implement the standard query operator methods that you are invoking in the query. The implementation can be either in the form of class members or extension methods that are brought into scope with the appropriate using directive.
-
- To correct this error
-
-
-
Make sure that you are querying a collection of objects, not an individual object.
-
Make sure that you have specified the necessary using directives.
-
- Example
-
- The following example produces XS1936:
-
-
- // XS1936.prg
-
- This error typically occurs when you accidentally try to query an object of some type instead of a collection of those objects.
-
-
diff --git a/docs/Help_Spanish/Topics/XS1937.xml b/docs/Help_Spanish/Topics/XS1937.xml
deleted file mode 100644
index a2b7fed52d..0000000000
--- a/docs/Help_Spanish/Topics/XS1937.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1937
-
-XS1937
-
-
-
- Error XS1937
-
- The name '{0}' is not in scope on the left side of 'equals'. Consider swapping the expressions on either side of 'equals'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1938.xml b/docs/Help_Spanish/Topics/XS1938.xml
deleted file mode 100644
index 64991cb99e..0000000000
--- a/docs/Help_Spanish/Topics/XS1938.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1938
-
-XS1938
-
-
-
- Error XS1938
-
- The name '{0}' is not in scope on the right side of 'equals'. Consider swapping the expressions on either side of 'equals'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1939.xml b/docs/Help_Spanish/Topics/XS1939.xml
deleted file mode 100644
index d406df457d..0000000000
--- a/docs/Help_Spanish/Topics/XS1939.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1939
-
-XS1939
-
-
-
- Error XS1939
-
- Cannot pass the range variable '{0}' as an out or ref parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1940.xml b/docs/Help_Spanish/Topics/XS1940.xml
deleted file mode 100644
index 67e157ca70..0000000000
--- a/docs/Help_Spanish/Topics/XS1940.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1940
-
-XS1940
-
-
-
- Error XS1940
-
- Multiple implementations of the query pattern were found for source type '{0}'. Ambiguous call to '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1941.xml b/docs/Help_Spanish/Topics/XS1941.xml
deleted file mode 100644
index 329d6debf0..0000000000
--- a/docs/Help_Spanish/Topics/XS1941.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XS1941
-
- XS1941
-
-
-
- Error XS1941
-
- The type of one of the expressions in the 'clause' clause is incorrect. Type inference failed in the call to 'method'.
-
- Type inference in query expressions flows from the type of the elements in the data source(s).
-
- To correct this error
-
-
-
If it is not immediately obvious why the error is occurring, examine the query carefully and trace the type of the result of each clause from the data source to the point where the error is occurring.
-
- Example
-
- The following code generates XS1941 because the equals operator is being asked to compare an int to a string.
-
-
- // XS1941.prg
-
- The method in which type inference fails is the method that the query clause is translated to at compile time.
-
-
diff --git a/docs/Help_Spanish/Topics/XS1942.xml b/docs/Help_Spanish/Topics/XS1942.xml
deleted file mode 100644
index c873501701..0000000000
--- a/docs/Help_Spanish/Topics/XS1942.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- XS1942
-
- XS1942
-
-
-
- Error XS1942
-
- The type of the expression in the 'clause' clause is incorrect. Type inference failed in the call to 'method'.
-
- This error is typically generated when the range variable has been given an incorrect explicit type.
-
- To correct this error
-
-
-
If the range variable is explicitly typed, make sure that the type is either the same as, or implicitly convertible from, the type of the elements in the collection it iterates. If the range variable is preceded with the var keyword, remove var.
-
- Example
-
- The following code generates XS1942:
-
-
- // XS1942.prg
- XS1942 is related to XS1949 because the use of var with a range variable causes the underlying Cast<T> operation to fail because var is not a type.
-
-
diff --git a/docs/Help_Spanish/Topics/XS1943.xml b/docs/Help_Spanish/Topics/XS1943.xml
deleted file mode 100644
index fbc5b8ec06..0000000000
--- a/docs/Help_Spanish/Topics/XS1943.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XS1943
-
- XS1943
-
-
-
- Error XS1943
-
- An expression of type 'type' is not allowed in a subsequent from clause in a query expression with source type 'type'. Type inference failed in the call to 'method'.
-
- All range variables must represent queryable types.
-
- To correct this error
-
-
-
Make sure that the type is a queryable type that implements IEnumerable, IEnumerable<T> or a derived interface, or any other type which has a query pattern defined for it.
-
If the type is a non-generic IEnumerable, provide an explicit type on the range variable.
-
- Example
-
- The following code generates XS1943:
-
-
- // XS1943.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1944.xml b/docs/Help_Spanish/Topics/XS1944.xml
deleted file mode 100644
index 76620bcb47..0000000000
--- a/docs/Help_Spanish/Topics/XS1944.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1944
-
-XS1944
-
-
-
- Error XS1944
-
- An expression tree may not contain an unsafe pointer operation
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1945.xml b/docs/Help_Spanish/Topics/XS1945.xml
deleted file mode 100644
index c477b84e01..0000000000
--- a/docs/Help_Spanish/Topics/XS1945.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1945
-
-XS1945
-
-
-
- Error XS1945
-
- An expression tree may not contain an anonymous method expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1946.xml b/docs/Help_Spanish/Topics/XS1946.xml
deleted file mode 100644
index 01c1c5658f..0000000000
--- a/docs/Help_Spanish/Topics/XS1946.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- XS1946
-
- XS1946
-
-
-
- Error XS1946
-
- An anonymous method expression cannot be converted to an expression tree.
-
- An anonymous method represents a set of statements but an expression tree must not contain a statement. Therefore an anonymous method cannot be represented by an expression tree.
-
- To correct this error
-
-
-
Change the anonymous method to a lambda expression.
-
- Example
-
- The following example generates XS1946:
-
-
- // XS1946.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1947.xml b/docs/Help_Spanish/Topics/XS1947.xml
deleted file mode 100644
index 46a79afe7b..0000000000
--- a/docs/Help_Spanish/Topics/XS1947.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1947
-
-XS1947
-
-
-
- Error XS1947
-
- Range variable '{0}' cannot be assigned to -- it is read only
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1948.xml b/docs/Help_Spanish/Topics/XS1948.xml
deleted file mode 100644
index 899e54391b..0000000000
--- a/docs/Help_Spanish/Topics/XS1948.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1948
-
-XS1948
-
-
-
- Error XS1948
-
- The range variable '{0}' cannot have the same name as a method type parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1949.xml b/docs/Help_Spanish/Topics/XS1949.xml
deleted file mode 100644
index ba78522321..0000000000
--- a/docs/Help_Spanish/Topics/XS1949.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1949
-
-XS1949
-
-
-
- Error XS1949
-
- The contextual keyword 'var' cannot be used in a range variable declaration
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1950.xml b/docs/Help_Spanish/Topics/XS1950.xml
deleted file mode 100644
index 7d20c5a026..0000000000
--- a/docs/Help_Spanish/Topics/XS1950.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1950
-
-XS1950
-
-
-
- Error XS1950
-
- The best overloaded Add method '{0}' for the collection initializer has some invalid arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1951.xml b/docs/Help_Spanish/Topics/XS1951.xml
deleted file mode 100644
index b239226fc1..0000000000
--- a/docs/Help_Spanish/Topics/XS1951.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1951
-
-XS1951
-
-
-
- Error XS1951
-
- An expression tree lambda may not contain an out or ref parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1952.xml b/docs/Help_Spanish/Topics/XS1952.xml
deleted file mode 100644
index f0ff2eb992..0000000000
--- a/docs/Help_Spanish/Topics/XS1952.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1952
-
-XS1952
-
-
-
- Error XS1952
-
- An expression tree lambda may not contain a method with variable arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1954.xml b/docs/Help_Spanish/Topics/XS1954.xml
deleted file mode 100644
index 6556fdaeb1..0000000000
--- a/docs/Help_Spanish/Topics/XS1954.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1954
-
-XS1954
-
-
-
- Error XS1954
-
- The best overloaded method match '{0}' for the collection initializer element cannot be used. Collection initializer 'Add' methods cannot have ref or out parameters.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1955.xml b/docs/Help_Spanish/Topics/XS1955.xml
deleted file mode 100644
index 4f27b62bdc..0000000000
--- a/docs/Help_Spanish/Topics/XS1955.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1955
-
-XS1955
-
-
-
- Error XS1955
-
- Non-invocable member '{0}' cannot be used like a method.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1956.xml b/docs/Help_Spanish/Topics/XS1956.xml
deleted file mode 100644
index d69a450423..0000000000
--- a/docs/Help_Spanish/Topics/XS1956.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS1956
-
- XS1956
-
-
-
- Warning XS1956
-
- Member 'name' implements interface member 'name' in type 'type'. There are multiple matches for the interface member at run-time. It is implementation dependent which method will be called.
-
- This warning can be generated when two interface methods are differentiated only by whether a particular parameter is marked with ref or with out. It is best to change your code to avoid this warning because it is not obvious or guaranteed which method is called at runtime.
-
- Although X# distinguishes between out and ref, the CLR sees them as the same. When deciding which method implements the interface, the CLR just picks one.
-
- To avoid this warning
-
-
-
Give the compiler some way to differentiate the methods. For example, you can give them different names or provide an additional parameter on one of them.
-
- Example
-
- The following code generates XS1956 because the two Test methods in Base differ only by the ref/out modifier on the first parameter.
-
-
- // XS1956.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1957.xml b/docs/Help_Spanish/Topics/XS1957.xml
deleted file mode 100644
index 1b4f83ce02..0000000000
--- a/docs/Help_Spanish/Topics/XS1957.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1957
-
- XS1957
-
-
-
- Warning XS1957
-
- Member '{1}' overrides '{0}'. There are multiple override candidates at run-time. It is implementation dependent which method will be called.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1958.xml b/docs/Help_Spanish/Topics/XS1958.xml
deleted file mode 100644
index 6994bcb64f..0000000000
--- a/docs/Help_Spanish/Topics/XS1958.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1958
-
-XS1958
-
-
-
- Error XS1958
-
- Object and collection initializer expressions may not be applied to a delegate creation expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1959.xml b/docs/Help_Spanish/Topics/XS1959.xml
deleted file mode 100644
index 857281cb7c..0000000000
--- a/docs/Help_Spanish/Topics/XS1959.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1959
-
-XS1959
-
-
-
- Error XS1959
-
- '{0}' is of type '{1}'. The type specified in a constant declaration must be sbyte, byte, short, ushort, int, uint, long, ulong, char, float, double, decimal, bool, string, an enum-type, or a reference-type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1960.xml b/docs/Help_Spanish/Topics/XS1960.xml
deleted file mode 100644
index c120a0b2b9..0000000000
--- a/docs/Help_Spanish/Topics/XS1960.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1960
-
-XS1960
-
-
-
- Error XS1960
-
- Invalid variance modifier. Only interface and delegate type parameters can be specified as variant.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1961.xml b/docs/Help_Spanish/Topics/XS1961.xml
deleted file mode 100644
index 271306e7c3..0000000000
--- a/docs/Help_Spanish/Topics/XS1961.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1961
-
-XS1961
-
-
-
- Error XS1961
-
- Invalid variance: The type parameter '{1}' must be {3} valid on '{0}'. '{1}' is {2}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1962.xml b/docs/Help_Spanish/Topics/XS1962.xml
deleted file mode 100644
index a086bae0ca..0000000000
--- a/docs/Help_Spanish/Topics/XS1962.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1962
-
-XS1962
-
-
-
- Error XS1962
-
- The typeof operator cannot be used on the dynamic type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1963.xml b/docs/Help_Spanish/Topics/XS1963.xml
deleted file mode 100644
index adfbf1f297..0000000000
--- a/docs/Help_Spanish/Topics/XS1963.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1963
-
-XS1963
-
-
-
- Error XS1963
-
- An expression tree may not contain a dynamic operation
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1964.xml b/docs/Help_Spanish/Topics/XS1964.xml
deleted file mode 100644
index 9075ab7ebe..0000000000
--- a/docs/Help_Spanish/Topics/XS1964.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1964
-
-XS1964
-
-
-
- Error XS1964
-
- '{0}': user-defined conversions to or from the dynamic type are not allowed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1965.xml b/docs/Help_Spanish/Topics/XS1965.xml
deleted file mode 100644
index 55f851937d..0000000000
--- a/docs/Help_Spanish/Topics/XS1965.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1965
-
-XS1965
-
-
-
- Error XS1965
-
- '{0}': cannot derive from the dynamic type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1966.xml b/docs/Help_Spanish/Topics/XS1966.xml
deleted file mode 100644
index 437f73db50..0000000000
--- a/docs/Help_Spanish/Topics/XS1966.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1966
-
-XS1966
-
-
-
- Error XS1966
-
- '{0}': cannot implement a dynamic interface '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1967.xml b/docs/Help_Spanish/Topics/XS1967.xml
deleted file mode 100644
index e8682a4141..0000000000
--- a/docs/Help_Spanish/Topics/XS1967.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1967
-
-XS1967
-
-
-
- Error XS1967
-
- Constraint cannot be the dynamic type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1968.xml b/docs/Help_Spanish/Topics/XS1968.xml
deleted file mode 100644
index 66e98949fd..0000000000
--- a/docs/Help_Spanish/Topics/XS1968.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1968
-
-XS1968
-
-
-
- Error XS1968
-
- Constraint cannot be a dynamic type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1969.xml b/docs/Help_Spanish/Topics/XS1969.xml
deleted file mode 100644
index 0a67f71812..0000000000
--- a/docs/Help_Spanish/Topics/XS1969.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1969
-
-XS1969
-
-
-
- Error XS1969
-
- One or more types required to compile a dynamic expression cannot be found. Are you missing a reference?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1970.xml b/docs/Help_Spanish/Topics/XS1970.xml
deleted file mode 100644
index a37ea23ae9..0000000000
--- a/docs/Help_Spanish/Topics/XS1970.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1970
-
-XS1970
-
-
-
- Error XS1970
-
- Do not use 'System.Runtime.CompilerServices.DynamicAttribute'. Use the 'dynamic' keyword instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1971.xml b/docs/Help_Spanish/Topics/XS1971.xml
deleted file mode 100644
index bcef107c1a..0000000000
--- a/docs/Help_Spanish/Topics/XS1971.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1971
-
-XS1971
-
-
-
- Error XS1971
-
- The call to method '{0}' needs to be dynamically dispatched, but cannot be because it is part of a base access expression. Consider casting the dynamic arguments or eliminating the base access.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1972.xml b/docs/Help_Spanish/Topics/XS1972.xml
deleted file mode 100644
index 9a9f1f250f..0000000000
--- a/docs/Help_Spanish/Topics/XS1972.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1972
-
-XS1972
-
-
-
- Error XS1972
-
- The indexer access needs to be dynamically dispatched, but cannot be because it is part of a base access expression. Consider casting the dynamic arguments or eliminating the base access.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1973.xml b/docs/Help_Spanish/Topics/XS1973.xml
deleted file mode 100644
index 9a50e54e23..0000000000
--- a/docs/Help_Spanish/Topics/XS1973.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1973
-
-XS1973
-
-
-
- Error XS1973
-
- '{0}' has no applicable method named '{1}' but appears to have an extension method by that name. Extension methods cannot be dynamically dispatched. Consider casting the dynamic arguments or calling the extension method without the extension method syntax.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1974.xml b/docs/Help_Spanish/Topics/XS1974.xml
deleted file mode 100644
index 86f45979be..0000000000
--- a/docs/Help_Spanish/Topics/XS1974.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1974
-
- XS1974
-
-
-
- Warning XS1974
-
- The dynamically dispatched call to method '{0}' may fail at runtime because one or more applicable overloads are conditional methods.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1975.xml b/docs/Help_Spanish/Topics/XS1975.xml
deleted file mode 100644
index e886eba6a3..0000000000
--- a/docs/Help_Spanish/Topics/XS1975.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1975
-
-XS1975
-
-
-
- Error XS1975
-
- The constructor call needs to be dynamically dispatched, but cannot be because it is part of a constructor initializer. Consider casting the dynamic arguments.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1976.xml b/docs/Help_Spanish/Topics/XS1976.xml
deleted file mode 100644
index 09e54c2c00..0000000000
--- a/docs/Help_Spanish/Topics/XS1976.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1976
-
-XS1976
-
-
-
- Error XS1976
-
- Cannot use a method group as an argument to a dynamically dispatched operation. Did you intend to invoke the method?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1977.xml b/docs/Help_Spanish/Topics/XS1977.xml
deleted file mode 100644
index 2924614d91..0000000000
--- a/docs/Help_Spanish/Topics/XS1977.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1977
-
-XS1977
-
-
-
- Error XS1977
-
- Cannot use a lambda expression as an argument to a dynamically dispatched operation without first casting it to a delegate or expression tree type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1978.xml b/docs/Help_Spanish/Topics/XS1978.xml
deleted file mode 100644
index 52b9258bca..0000000000
--- a/docs/Help_Spanish/Topics/XS1978.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1978
-
-XS1978
-
-
-
- Error XS1978
-
- Cannot use an expression of type '{0}' as an argument to a dynamically dispatched operation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1979.xml b/docs/Help_Spanish/Topics/XS1979.xml
deleted file mode 100644
index 81d1b4e8ec..0000000000
--- a/docs/Help_Spanish/Topics/XS1979.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1979
-
-XS1979
-
-
-
- Error XS1979
-
- Query expressions over source type 'dynamic' or with a join sequence of type 'dynamic' are not allowed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1980.xml b/docs/Help_Spanish/Topics/XS1980.xml
deleted file mode 100644
index 03a2a584cd..0000000000
--- a/docs/Help_Spanish/Topics/XS1980.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1980
-
-XS1980
-
-
-
- Error XS1980
-
- Cannot define a class or member that utilizes 'dynamic' because the compiler required type '{0}' cannot be found. Are you missing a reference?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1981.xml b/docs/Help_Spanish/Topics/XS1981.xml
deleted file mode 100644
index 0f62634964..0000000000
--- a/docs/Help_Spanish/Topics/XS1981.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1981
-
- XS1981
-
-
-
- Warning XS1981
-
- Using '{0}' to test compatibility with '{1}' is essentially identical to testing compatibility with '{2}' and will succeed for all non-null values
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1983.xml b/docs/Help_Spanish/Topics/XS1983.xml
deleted file mode 100644
index fdb1c34ce5..0000000000
--- a/docs/Help_Spanish/Topics/XS1983.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1983
-
-XS1983
-
-
-
- Error XS1983
-
- The return type of an async method must be void, Task or Task
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1984.xml b/docs/Help_Spanish/Topics/XS1984.xml
deleted file mode 100644
index 3faad4bdd3..0000000000
--- a/docs/Help_Spanish/Topics/XS1984.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1984
-
-XS1984
-
-
-
- Error XS1984
-
- Cannot await in the body of a finally clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1985.xml b/docs/Help_Spanish/Topics/XS1985.xml
deleted file mode 100644
index c886fd7a3a..0000000000
--- a/docs/Help_Spanish/Topics/XS1985.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1985
-
-XS1985
-
-
-
- Error XS1985
-
- Cannot await in a catch clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1986.xml b/docs/Help_Spanish/Topics/XS1986.xml
deleted file mode 100644
index cfe7708c0a..0000000000
--- a/docs/Help_Spanish/Topics/XS1986.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1986
-
-XS1986
-
-
-
- Error XS1986
-
- 'await' requires that the type {0} have a suitable GetAwaiter method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1988.xml b/docs/Help_Spanish/Topics/XS1988.xml
deleted file mode 100644
index 5c6e5e346a..0000000000
--- a/docs/Help_Spanish/Topics/XS1988.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1988
-
-XS1988
-
-
-
- Error XS1988
-
- Async methods cannot have ref or out parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1989.xml b/docs/Help_Spanish/Topics/XS1989.xml
deleted file mode 100644
index 3481fe5117..0000000000
--- a/docs/Help_Spanish/Topics/XS1989.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1989
-
-XS1989
-
-
-
- Error XS1989
-
- Async lambda expressions cannot be converted to expression trees
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1991.xml b/docs/Help_Spanish/Topics/XS1991.xml
deleted file mode 100644
index 126f50cc32..0000000000
--- a/docs/Help_Spanish/Topics/XS1991.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1991
-
-XS1991
-
-
-
- Error XS1991
-
- '{0}' cannot implement '{1}' because '{2}' is a Windows Runtime event and '{3}' is a regular .NET event.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1992.xml b/docs/Help_Spanish/Topics/XS1992.xml
deleted file mode 100644
index 76e2b3cb34..0000000000
--- a/docs/Help_Spanish/Topics/XS1992.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1992
-
-XS1992
-
-
-
- Error XS1992
-
- The 'await' operator can only be used when contained within a method or lambda expression marked with the 'async' modifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1994.xml b/docs/Help_Spanish/Topics/XS1994.xml
deleted file mode 100644
index f0151f2a01..0000000000
--- a/docs/Help_Spanish/Topics/XS1994.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1994
-
-XS1994
-
-
-
- Error XS1994
-
- The 'async' modifier can only be used in methods that have a body.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1995.xml b/docs/Help_Spanish/Topics/XS1995.xml
deleted file mode 100644
index db09129983..0000000000
--- a/docs/Help_Spanish/Topics/XS1995.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1995
-
-XS1995
-
-
-
- Error XS1995
-
- The 'await' operator may only be used in a query expression within the first collection expression of the initial 'from' clause or within the collection expression of a 'join' clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1996.xml b/docs/Help_Spanish/Topics/XS1996.xml
deleted file mode 100644
index 12e522db6f..0000000000
--- a/docs/Help_Spanish/Topics/XS1996.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1996
-
-XS1996
-
-
-
- Error XS1996
-
- Cannot await in the body of a lock statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1997.xml b/docs/Help_Spanish/Topics/XS1997.xml
deleted file mode 100644
index 6e816c2008..0000000000
--- a/docs/Help_Spanish/Topics/XS1997.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS1997
-
-XS1997
-
-
-
- Error XS1997
-
- Since '{0}' is an async method that returns 'Task', a return keyword must not be followed by an object expression. Did you intend to return 'Task'?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS1998.xml b/docs/Help_Spanish/Topics/XS1998.xml
deleted file mode 100644
index 28ec3eb43f..0000000000
--- a/docs/Help_Spanish/Topics/XS1998.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS1998
-
- XS1998
-
-
-
- Warning XS1998
-
- This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2001.xml b/docs/Help_Spanish/Topics/XS2001.xml
deleted file mode 100644
index af311a2696..0000000000
--- a/docs/Help_Spanish/Topics/XS2001.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2001
-
-XS2001
-
-
-
- Error XS2001
-
- Source file '{0}' could not be found.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2002.xml b/docs/Help_Spanish/Topics/XS2002.xml
deleted file mode 100644
index 08a0f8408b..0000000000
--- a/docs/Help_Spanish/Topics/XS2002.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS2002
-
- XS2002
-
-
-
- Warning XS2002
-
- Source file '{0}' specified multiple times
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2005.xml b/docs/Help_Spanish/Topics/XS2005.xml
deleted file mode 100644
index fffb94528c..0000000000
--- a/docs/Help_Spanish/Topics/XS2005.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2005
-
-XS2005
-
-
-
- Error XS2005
-
- Missing file specification for '{0}' option
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2006.xml b/docs/Help_Spanish/Topics/XS2006.xml
deleted file mode 100644
index 492ef18d56..0000000000
--- a/docs/Help_Spanish/Topics/XS2006.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2006
-
-XS2006
-
-
-
- Error XS2006
-
- Command-line syntax error: Missing '{0}' for '{1}' option
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2007.xml b/docs/Help_Spanish/Topics/XS2007.xml
deleted file mode 100644
index 42e17951f5..0000000000
--- a/docs/Help_Spanish/Topics/XS2007.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2007
-
-XS2007
-
-
-
- Error XS2007
-
- Unrecognized option: '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2008.xml b/docs/Help_Spanish/Topics/XS2008.xml
deleted file mode 100644
index f2c2a26a1c..0000000000
--- a/docs/Help_Spanish/Topics/XS2008.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS2008
-
- XS2008
-
-
-
- Warning XS2008
-
- No source files specified.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2011.xml b/docs/Help_Spanish/Topics/XS2011.xml
deleted file mode 100644
index 37f66a5f6d..0000000000
--- a/docs/Help_Spanish/Topics/XS2011.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2011
-
-XS2011
-
-
-
- Error XS2011
-
- Error opening response file '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2012.xml b/docs/Help_Spanish/Topics/XS2012.xml
deleted file mode 100644
index 3d0156c3f9..0000000000
--- a/docs/Help_Spanish/Topics/XS2012.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2012
-
-XS2012
-
-
-
- Error XS2012
-
- Cannot open '{0}' for writing -- '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2013.xml b/docs/Help_Spanish/Topics/XS2013.xml
deleted file mode 100644
index c7cab93957..0000000000
--- a/docs/Help_Spanish/Topics/XS2013.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2013
-
-XS2013
-
-
-
- Error XS2013
-
- Invalid image base number '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2015.xml b/docs/Help_Spanish/Topics/XS2015.xml
deleted file mode 100644
index a7050ed52a..0000000000
--- a/docs/Help_Spanish/Topics/XS2015.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2015
-
-XS2015
-
-
-
- Error XS2015
-
- '{0}' is a binary file instead of a text file
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2016.xml b/docs/Help_Spanish/Topics/XS2016.xml
deleted file mode 100644
index 8c397802ce..0000000000
--- a/docs/Help_Spanish/Topics/XS2016.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2016
-
-XS2016
-
-
-
- Error XS2016
-
- Code page '{0}' is invalid or not installed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2017.xml b/docs/Help_Spanish/Topics/XS2017.xml
deleted file mode 100644
index 7864f7289c..0000000000
--- a/docs/Help_Spanish/Topics/XS2017.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2017
-
-XS2017
-
-
-
- Error XS2017
-
- Cannot specify /main if building a module or library
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2019.xml b/docs/Help_Spanish/Topics/XS2019.xml
deleted file mode 100644
index b2bdb2b62c..0000000000
--- a/docs/Help_Spanish/Topics/XS2019.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2019
-
-XS2019
-
-
-
- Error XS2019
-
- Invalid target type for /target: must specify 'exe', 'winexe', 'library', or 'module'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2021.xml b/docs/Help_Spanish/Topics/XS2021.xml
deleted file mode 100644
index 6e7194fdce..0000000000
--- a/docs/Help_Spanish/Topics/XS2021.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2021
-
-XS2021
-
-
-
- Error XS2021
-
- File name '{0}' is empty, contains invalid characters, has a drive specification without an absolute path, or is too long
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2023.xml b/docs/Help_Spanish/Topics/XS2023.xml
deleted file mode 100644
index c866765778..0000000000
--- a/docs/Help_Spanish/Topics/XS2023.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS2023
-
- XS2023
-
-
-
- Warning XS2023
-
- Ignoring /noconfig option because it was specified in a response file
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2024.xml b/docs/Help_Spanish/Topics/XS2024.xml
deleted file mode 100644
index 2de230dc1b..0000000000
--- a/docs/Help_Spanish/Topics/XS2024.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2024
-
-XS2024
-
-
-
- Error XS2024
-
- Invalid file section alignment '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2029.xml b/docs/Help_Spanish/Topics/XS2029.xml
deleted file mode 100644
index 630a7a2a16..0000000000
--- a/docs/Help_Spanish/Topics/XS2029.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS2029
-
- XS2029
-
-
-
- Warning XS2029
-
- Invalid value for '/define'; '{0}' is not a valid identifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2033.xml b/docs/Help_Spanish/Topics/XS2033.xml
deleted file mode 100644
index 699c467b50..0000000000
--- a/docs/Help_Spanish/Topics/XS2033.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2033
-
-XS2033
-
-
-
- Error XS2033
-
- Cannot create short filename '{0}' when a long filename with the same short filename already exists
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2034.xml b/docs/Help_Spanish/Topics/XS2034.xml
deleted file mode 100644
index 3525f09f61..0000000000
--- a/docs/Help_Spanish/Topics/XS2034.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2034
-
-XS2034
-
-
-
- Error XS2034
-
- A /reference option that declares an extern alias can only have one filename. To specify multiple aliases or filenames, use multiple /reference options.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2035.xml b/docs/Help_Spanish/Topics/XS2035.xml
deleted file mode 100644
index 3a8073ccb9..0000000000
--- a/docs/Help_Spanish/Topics/XS2035.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2035
-
-XS2035
-
-
-
- Error XS2035
-
- Command-line syntax error: Missing ':' for '{0}' option
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2036.xml b/docs/Help_Spanish/Topics/XS2036.xml
deleted file mode 100644
index e068040f29..0000000000
--- a/docs/Help_Spanish/Topics/XS2036.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2036
-
-XS2036
-
-
-
- Error XS2036
-
- The /pdb option requires that the /debug option also be used
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2037.xml b/docs/Help_Spanish/Topics/XS2037.xml
deleted file mode 100644
index 36b4a2bb2a..0000000000
--- a/docs/Help_Spanish/Topics/XS2037.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2037
-
-XS2037
-
-
-
- Error XS2037
-
- An expression tree lambda may not contain a COM call with ref omitted on arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2038.xml b/docs/Help_Spanish/Topics/XS2038.xml
deleted file mode 100644
index fced5f599d..0000000000
--- a/docs/Help_Spanish/Topics/XS2038.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS2038
-
- XS2038
-
-
-
- Warning XS2038
-
- The language name '{0}' is invalid.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2039.xml b/docs/Help_Spanish/Topics/XS2039.xml
deleted file mode 100644
index 829e357992..0000000000
--- a/docs/Help_Spanish/Topics/XS2039.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2039
-
-XS2039
-
-
-
- Error XS2039
-
- Command-line syntax error: Invalid Guid format '{0}' for option '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2040.xml b/docs/Help_Spanish/Topics/XS2040.xml
deleted file mode 100644
index 28c71f0a10..0000000000
--- a/docs/Help_Spanish/Topics/XS2040.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2040
-
-XS2040
-
-
-
- Error XS2040
-
- Command-line syntax error: Missing Guid for option '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2041.xml b/docs/Help_Spanish/Topics/XS2041.xml
deleted file mode 100644
index 379cee45ca..0000000000
--- a/docs/Help_Spanish/Topics/XS2041.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2041
-
-XS2041
-
-
-
- Error XS2041
-
- Invalid output name: {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2042.xml b/docs/Help_Spanish/Topics/XS2042.xml
deleted file mode 100644
index cee2808840..0000000000
--- a/docs/Help_Spanish/Topics/XS2042.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2042
-
-XS2042
-
-
-
- Error XS2042
-
- Invalid debug information format: {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2043.xml b/docs/Help_Spanish/Topics/XS2043.xml
deleted file mode 100644
index 9a0746d792..0000000000
--- a/docs/Help_Spanish/Topics/XS2043.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2043
-
-XS2043
-
-
-
- Error XS2043
-
- 'id#' syntax is no longer supported. Use '$id' instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2044.xml b/docs/Help_Spanish/Topics/XS2044.xml
deleted file mode 100644
index a09d1f6e6e..0000000000
--- a/docs/Help_Spanish/Topics/XS2044.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2044
-
-XS2044
-
-
-
- Error XS2044
-
- /sourcelink switch is only supported when emitting Portable PDB (/debug:portable or /debug:embedded must be specified).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2045.xml b/docs/Help_Spanish/Topics/XS2045.xml
deleted file mode 100644
index 321765a106..0000000000
--- a/docs/Help_Spanish/Topics/XS2045.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS2045
-
-XS2045
-
-
-
- Error XS2045
-
- /embed switch is only supported when emitting Portable PDB (/debug:portable or /debug:embedded).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS2046.XML b/docs/Help_Spanish/Topics/XS2046.XML
deleted file mode 100644
index c7514bc8eb..0000000000
--- a/docs/Help_Spanish/Topics/XS2046.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS2046
-
-XS2046
-
-
-
- Error XS2046
-
- Command-line syntax error: '{0}' is not a valid value for the '{1}' option. The value must be of the form '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3000.xml b/docs/Help_Spanish/Topics/XS3000.xml
deleted file mode 100644
index 3a111c1b3d..0000000000
--- a/docs/Help_Spanish/Topics/XS3000.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3000
-
- XS3000
-
-
-
- Warning XS3000
-
- Methods with variable arguments are not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3001.xml b/docs/Help_Spanish/Topics/XS3001.xml
deleted file mode 100644
index cf5423bc35..0000000000
--- a/docs/Help_Spanish/Topics/XS3001.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3001
-
- XS3001
-
-
-
- Warning XS3001
-
- Argument type '{0}' is not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3002.xml b/docs/Help_Spanish/Topics/XS3002.xml
deleted file mode 100644
index fff3f715e1..0000000000
--- a/docs/Help_Spanish/Topics/XS3002.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3002
-
- XS3002
-
-
-
- Warning XS3002
-
- Return type of '{0}' is not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3003.xml b/docs/Help_Spanish/Topics/XS3003.xml
deleted file mode 100644
index 27e606cac0..0000000000
--- a/docs/Help_Spanish/Topics/XS3003.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS3003
-
- XS3003
-
-
-
- Warning XS3003
-
- Type of 'variable' is not CLS-compliant
-
- A public, protected, or protected internal variable must be of a type that is compliant with the Common Language Specification (CLS). For more information on CLS Compliance, see Language Independence and Language-Independent Components.
- Example
-
- The following example generates XS3003:
-
-
- // XS3003.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3005.xml b/docs/Help_Spanish/Topics/XS3005.xml
deleted file mode 100644
index ad4357a0d6..0000000000
--- a/docs/Help_Spanish/Topics/XS3005.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3005
-
- XS3005
-
-
-
- Warning XS3005
-
- Identifier '{0}' differing only in case is not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3006.xml b/docs/Help_Spanish/Topics/XS3006.xml
deleted file mode 100644
index c38853f522..0000000000
--- a/docs/Help_Spanish/Topics/XS3006.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3006
-
- XS3006
-
-
-
- Warning XS3006
-
- Overloaded method '{0}' differing only in ref or out, or in array rank, is not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3007.xml b/docs/Help_Spanish/Topics/XS3007.xml
deleted file mode 100644
index 638a766160..0000000000
--- a/docs/Help_Spanish/Topics/XS3007.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS3007
-
- XS3007
-
-
-
- Warning XS3007
-
- Overloaded method 'method' differing only by unnamed array types is not CLS-compliant
-
- This error occurs if you have an overloaded method that takes a jagged array and the only difference between the method signatures is the element type of the array. To avoid this error, consider using a rectangular array rather than a jagged array; use an additional parameter to disambiguate the function call; rename one or more of the overloaded methods; or, if CLS Compliance is not needed, remove the CLSCompliantAttribute attribute. For more information on CLS Compliance, see Language Independence and Language-Independent Components.
- Example
-
- The following example generates XS3007:
-
-
- // XS3007.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3008.xml b/docs/Help_Spanish/Topics/XS3008.xml
deleted file mode 100644
index 675c66befa..0000000000
--- a/docs/Help_Spanish/Topics/XS3008.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3008
-
- XS3008
-
-
-
- Warning XS3008
-
- Identifier '{0}' is not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3009.xml b/docs/Help_Spanish/Topics/XS3009.xml
deleted file mode 100644
index 5d27268bcd..0000000000
--- a/docs/Help_Spanish/Topics/XS3009.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS3009
-
- XS3009
-
-
-
- Warning XS3009
-
- 'type': base type 'type' is not CLS-compliant
-
- A base type was marked as not having to be compliant with the Common Language Specification (CLS) in an assembly that was marked as being CLS compliant. Either remove the attribute that specifies the assembly is CLS compliant or remove the attribute that indicates the type is not CLS compliant. For more information on CLS Compliance, see Writing CLS-Compliant Code and Language Independence and Language-Independent Components.
- Example
-
- The following example generates XS3009:
-
-
- // XS3009.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3010.xml b/docs/Help_Spanish/Topics/XS3010.xml
deleted file mode 100644
index 92a14bb211..0000000000
--- a/docs/Help_Spanish/Topics/XS3010.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3010
-
- XS3010
-
-
-
- Warning XS3010
-
- '{0}': CLS-compliant interfaces must have only CLS-compliant members
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3011.xml b/docs/Help_Spanish/Topics/XS3011.xml
deleted file mode 100644
index 18eee377f1..0000000000
--- a/docs/Help_Spanish/Topics/XS3011.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3011
-
- XS3011
-
-
-
- Warning XS3011
-
- '{0}': only CLS-compliant members can be abstract
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3012.xml b/docs/Help_Spanish/Topics/XS3012.xml
deleted file mode 100644
index f9dd2b4fe3..0000000000
--- a/docs/Help_Spanish/Topics/XS3012.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3012
-
- XS3012
-
-
-
- Warning XS3012
-
- You must specify the CLSCompliant attribute on the assembly, not the module, to enable CLS compliance checking
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3013.xml b/docs/Help_Spanish/Topics/XS3013.xml
deleted file mode 100644
index 7c78b2270d..0000000000
--- a/docs/Help_Spanish/Topics/XS3013.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3013
-
- XS3013
-
-
-
- Warning XS3013
-
- Added modules must be marked with the CLSCompliant attribute to match the assembly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3014.xml b/docs/Help_Spanish/Topics/XS3014.xml
deleted file mode 100644
index 53f1ab0cf2..0000000000
--- a/docs/Help_Spanish/Topics/XS3014.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3014
-
- XS3014
-
-
-
- Warning XS3014
-
- '{0}' cannot be marked as CLS-compliant because the assembly does not have a CLSCompliant attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3015.xml b/docs/Help_Spanish/Topics/XS3015.xml
deleted file mode 100644
index 7eeaddb00b..0000000000
--- a/docs/Help_Spanish/Topics/XS3015.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3015
-
- XS3015
-
-
-
- Warning XS3015
-
- '{0}' has no accessible constructors which use only CLS-compliant types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3016.xml b/docs/Help_Spanish/Topics/XS3016.xml
deleted file mode 100644
index cf6ef3d4f4..0000000000
--- a/docs/Help_Spanish/Topics/XS3016.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3016
-
- XS3016
-
-
-
- Warning XS3016
-
- Arrays as attribute arguments is not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3017.xml b/docs/Help_Spanish/Topics/XS3017.xml
deleted file mode 100644
index c327ce2270..0000000000
--- a/docs/Help_Spanish/Topics/XS3017.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3017
-
- XS3017
-
-
-
- Warning XS3017
-
- You cannot specify the CLSCompliant attribute on a module that differs from the CLSCompliant attribute on the assembly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3018.xml b/docs/Help_Spanish/Topics/XS3018.xml
deleted file mode 100644
index 60a3c8f2f3..0000000000
--- a/docs/Help_Spanish/Topics/XS3018.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3018
-
- XS3018
-
-
-
- Warning XS3018
-
- '{0}' cannot be marked as CLS-compliant because it is a member of non-CLS-compliant type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3019.xml b/docs/Help_Spanish/Topics/XS3019.xml
deleted file mode 100644
index ab3edb8f20..0000000000
--- a/docs/Help_Spanish/Topics/XS3019.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3019
-
- XS3019
-
-
-
- Warning XS3019
-
- CLS compliance checking will not be performed on '{0}' because it is not visible from outside this assembly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3021.xml b/docs/Help_Spanish/Topics/XS3021.xml
deleted file mode 100644
index 7dd9aeb08a..0000000000
--- a/docs/Help_Spanish/Topics/XS3021.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3021
-
- XS3021
-
-
-
- Warning XS3021
-
- '{0}' does not need a CLSCompliant attribute because the assembly does not have a CLSCompliant attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3022.xml b/docs/Help_Spanish/Topics/XS3022.xml
deleted file mode 100644
index 31be6c120d..0000000000
--- a/docs/Help_Spanish/Topics/XS3022.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3022
-
- XS3022
-
-
-
- Warning XS3022
-
- CLSCompliant attribute has no meaning when applied to parameters. Try putting it on the method instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3023.xml b/docs/Help_Spanish/Topics/XS3023.xml
deleted file mode 100644
index d59bac6bb7..0000000000
--- a/docs/Help_Spanish/Topics/XS3023.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3023
-
- XS3023
-
-
-
- Warning XS3023
-
- CLSCompliant attribute has no meaning when applied to return types. Try putting it on the method instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3024.xml b/docs/Help_Spanish/Topics/XS3024.xml
deleted file mode 100644
index 54b86803a4..0000000000
--- a/docs/Help_Spanish/Topics/XS3024.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3024
-
- XS3024
-
-
-
- Warning XS3024
-
- Constraint type '{0}' is not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3026.xml b/docs/Help_Spanish/Topics/XS3026.xml
deleted file mode 100644
index c14f045bbd..0000000000
--- a/docs/Help_Spanish/Topics/XS3026.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3026
-
- XS3026
-
-
-
- Warning XS3026
-
- CLS-compliant field '{0}' cannot be volatile
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3027.xml b/docs/Help_Spanish/Topics/XS3027.xml
deleted file mode 100644
index ee144ea758..0000000000
--- a/docs/Help_Spanish/Topics/XS3027.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS3027
-
- XS3027
-
-
-
- Warning XS3027
-
- '{0}' is not CLS-compliant because base interface '{1}' is not CLS-compliant
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS3028.xml b/docs/Help_Spanish/Topics/XS3028.xml
deleted file mode 100644
index 2ef51dd2d2..0000000000
--- a/docs/Help_Spanish/Topics/XS3028.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS3028
-
-XS3028
-
-
-
- Error XS3028
-
- Algorithm '{0}' is not supported
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4001.xml b/docs/Help_Spanish/Topics/XS4001.xml
deleted file mode 100644
index bb998a6a07..0000000000
--- a/docs/Help_Spanish/Topics/XS4001.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4001
-
-XS4001
-
-
-
- Error XS4001
-
- Cannot await '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4003.xml b/docs/Help_Spanish/Topics/XS4003.xml
deleted file mode 100644
index 9be3c1354c..0000000000
--- a/docs/Help_Spanish/Topics/XS4003.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4003
-
-XS4003
-
-
-
- Error XS4003
-
- 'await' cannot be used as an identifier within an async method or lambda expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4004.xml b/docs/Help_Spanish/Topics/XS4004.xml
deleted file mode 100644
index 1407bfdd38..0000000000
--- a/docs/Help_Spanish/Topics/XS4004.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4004
-
-XS4004
-
-
-
- Error XS4004
-
- Cannot await in an unsafe context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4005.xml b/docs/Help_Spanish/Topics/XS4005.xml
deleted file mode 100644
index 552e1db9cd..0000000000
--- a/docs/Help_Spanish/Topics/XS4005.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4005
-
-XS4005
-
-
-
- Error XS4005
-
- Async methods cannot have unsafe parameters or return types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4006.xml b/docs/Help_Spanish/Topics/XS4006.xml
deleted file mode 100644
index a4b7221ba9..0000000000
--- a/docs/Help_Spanish/Topics/XS4006.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4006
-
-XS4006
-
-
-
- Error XS4006
-
- __arglist is not allowed in the parameter list of async methods
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4007.xml b/docs/Help_Spanish/Topics/XS4007.xml
deleted file mode 100644
index b871daa381..0000000000
--- a/docs/Help_Spanish/Topics/XS4007.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4007
-
-XS4007
-
-
-
- Error XS4007
-
- 'await' cannot be used in an expression containing the type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4008.xml b/docs/Help_Spanish/Topics/XS4008.xml
deleted file mode 100644
index 79a498d745..0000000000
--- a/docs/Help_Spanish/Topics/XS4008.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4008
-
-XS4008
-
-
-
- Error XS4008
-
- Cannot await 'void'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4009.xml b/docs/Help_Spanish/Topics/XS4009.xml
deleted file mode 100644
index 578e7af96f..0000000000
--- a/docs/Help_Spanish/Topics/XS4009.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4009
-
-XS4009
-
-
-
- Error XS4009
-
- '{0}': an entry point cannot be marked with the 'async' modifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4010.xml b/docs/Help_Spanish/Topics/XS4010.xml
deleted file mode 100644
index c150ad4d2b..0000000000
--- a/docs/Help_Spanish/Topics/XS4010.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4010
-
-XS4010
-
-
-
- Error XS4010
-
- Cannot convert async {0} to delegate type '{1}'. An async {0} may return void, Task or Task, none of which are convertible to '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4011.xml b/docs/Help_Spanish/Topics/XS4011.xml
deleted file mode 100644
index d9f3e11a80..0000000000
--- a/docs/Help_Spanish/Topics/XS4011.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4011
-
-XS4011
-
-
-
- Error XS4011
-
- 'await' requires that the return type '{0}' of '{1}.GetAwaiter()' have suitable IsCompleted, OnCompleted, and GetResult members, and implement INotifyCompletion or ICriticalNotifyCompletion
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4012.xml b/docs/Help_Spanish/Topics/XS4012.xml
deleted file mode 100644
index 54759738ee..0000000000
--- a/docs/Help_Spanish/Topics/XS4012.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4012
-
-XS4012
-
-
-
- Error XS4012
-
- Parameters or locals of type '{0}' cannot be declared in async methods or lambda expressions.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4013.xml b/docs/Help_Spanish/Topics/XS4013.xml
deleted file mode 100644
index b755fa3923..0000000000
--- a/docs/Help_Spanish/Topics/XS4013.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4013
-
-XS4013
-
-
-
- Error XS4013
-
- Instance of type '{0}' cannot be used inside an anonymous function, query expression, iterator block or async method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4014.xml b/docs/Help_Spanish/Topics/XS4014.xml
deleted file mode 100644
index ca5b8bb24b..0000000000
--- a/docs/Help_Spanish/Topics/XS4014.xml
+++ /dev/null
@@ -1,67 +0,0 @@
-
-
-
- XS4014
-
- XS4014
-
-
-
- Warning XS4014
-
- Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
-
- The current method calls an async method that returns a Task or a Task<TResult> and doesn’t apply the await operator to the result. The call to the async method starts an asynchronous task. However, because no await operator is applied, the program continues without waiting for the task to complete. In most cases, that behavior isn't what you expect. Usually other aspects of the calling method depend on the results of the call or, minimally, the called method is expected to complete before you return from the method that contains the call.
-
- An equally important issue is what happens to exceptions that are raised in the called async method. An exception that's raised in a method that returns a Task or Task<TResult> is stored in the returned task. If you don't await the task or explicitly check for exceptions, the exception is lost. If you await the task, its exception is rethrown.
-
- As a best practice, you should always await the call.
-
- You should consider suppressing the warning only if you're sure that you don't want to wait for the asynchronous call to complete and that the called method won't raise any exceptions. In that case, you can suppress the warning by assigning the task result of the call to a variable.
-
- The following example shows how to cause the warning, how to suppress it, and how to await the call.
-
-
-
-
-
- In the example, if you choose Call #1 or Call #2, the unawaited async method (CalledMethodAsync) finishes after both its caller (CallingMethodAsync) and the caller's caller (startButton_Click) are complete. The last line in the following output shows you when the called method finishes. Entry to and exit from the event handler that calls CallingMethodAsync in the full example are marked in the output.
-
-
-
-
-
- You
- can also suppress compiler warnings by using #pragma warning directives.
- Example
-
- The following Windows Presentation Foundation (WPF) application contains the methods from the previous example. The following steps set up the application.
-
-
-
Create a WPF application, and name it AsyncWarning.
-
In the Visual Studio Code Editor, choose the MainWindow.xaml tab.
-
- If the tab isn't visible, open the shortcut menu for MainWindow.xaml in Solution Explorer, and then choose View Code.
-
-
Replace the code in the XAML view of MainWindow.xaml with the following code.
-
-
-
-
-
-
- A simple window that contains a button and a text box appears in the Design view of MainWindow.xaml.
-
- For more information about the XAML Designer, see Creating a UI by using XAML Designer. For information about how to build your own simple UI, see the "To create a WPF application" and "To design a simple WPF MainWindow" sections of Walkthrough: Accessing the Web by Using Async and Await.
-
- 4. Replace the code in MainWindow.xaml.prg with the following code.
-
-
-
-
-
- 5. Choose the F5 key to run the program, and then choose the Start button.
-
- The expected output appears at the end of the code.
-
-
diff --git a/docs/Help_Spanish/Topics/XS4015.xml b/docs/Help_Spanish/Topics/XS4015.xml
deleted file mode 100644
index 993996549f..0000000000
--- a/docs/Help_Spanish/Topics/XS4015.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4015
-
-XS4015
-
-
-
- Error XS4015
-
- 'MethodImplOptions.Synchronized' cannot be applied to an async method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4016.xml b/docs/Help_Spanish/Topics/XS4016.xml
deleted file mode 100644
index b9575cf71c..0000000000
--- a/docs/Help_Spanish/Topics/XS4016.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4016
-
-XS4016
-
-
-
- Error XS4016
-
- Since this is an async method, the return expression must be of type '{0}' rather than 'Task<{0}>'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4017.xml b/docs/Help_Spanish/Topics/XS4017.xml
deleted file mode 100644
index f61465a240..0000000000
--- a/docs/Help_Spanish/Topics/XS4017.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4017
-
-XS4017
-
-
-
- Error XS4017
-
- CallerLineNumberAttribute cannot be applied because there are no standard conversions from type '{0}' to type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4018.xml b/docs/Help_Spanish/Topics/XS4018.xml
deleted file mode 100644
index ad2267f8a3..0000000000
--- a/docs/Help_Spanish/Topics/XS4018.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4018
-
-XS4018
-
-
-
- Error XS4018
-
- CallerFilePathAttribute cannot be applied because there are no standard conversions from type '{0}' to type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4019.xml b/docs/Help_Spanish/Topics/XS4019.xml
deleted file mode 100644
index e936c3fa12..0000000000
--- a/docs/Help_Spanish/Topics/XS4019.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4019
-
-XS4019
-
-
-
- Error XS4019
-
- CallerMemberNameAttribute cannot be applied because there are no standard conversions from type '{0}' to type '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4020.xml b/docs/Help_Spanish/Topics/XS4020.xml
deleted file mode 100644
index 504c9af339..0000000000
--- a/docs/Help_Spanish/Topics/XS4020.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4020
-
-XS4020
-
-
-
- Error XS4020
-
- The CallerLineNumberAttribute may only be applied to parameters with default values
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4021.xml b/docs/Help_Spanish/Topics/XS4021.xml
deleted file mode 100644
index d678f8e52b..0000000000
--- a/docs/Help_Spanish/Topics/XS4021.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4021
-
-XS4021
-
-
-
- Error XS4021
-
- The CallerFilePathAttribute may only be applied to parameters with default values
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4022.xml b/docs/Help_Spanish/Topics/XS4022.xml
deleted file mode 100644
index 97cea444d1..0000000000
--- a/docs/Help_Spanish/Topics/XS4022.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4022
-
-XS4022
-
-
-
- Error XS4022
-
- The CallerMemberNameAttribute may only be applied to parameters with default values
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4023.xml b/docs/Help_Spanish/Topics/XS4023.xml
deleted file mode 100644
index 610e105fdd..0000000000
--- a/docs/Help_Spanish/Topics/XS4023.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4023
-
-XS4023
-
-
-
- Error XS4023
-
- /platform:anycpu32bitpreferred can only be used with /t:exe, /t:winexe and /t:appcontainerexe
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4024.xml b/docs/Help_Spanish/Topics/XS4024.xml
deleted file mode 100644
index 80b857130d..0000000000
--- a/docs/Help_Spanish/Topics/XS4024.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS4024
-
- XS4024
-
-
-
- Warning XS4024
-
- The CallerLineNumberAttribute applied to parameter '{0}' will have no effect because it applies to a member that is used in contexts that do not allow optional arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4025.xml b/docs/Help_Spanish/Topics/XS4025.xml
deleted file mode 100644
index 8c9d533c92..0000000000
--- a/docs/Help_Spanish/Topics/XS4025.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS4025
-
- XS4025
-
-
-
- Warning XS4025
-
- The CallerFilePathAttribute applied to parameter '{0}' will have no effect because it applies to a member that is used in contexts that do not allow optional arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4026.xml b/docs/Help_Spanish/Topics/XS4026.xml
deleted file mode 100644
index 29e9f0c559..0000000000
--- a/docs/Help_Spanish/Topics/XS4026.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS4026
-
- XS4026
-
-
-
- Warning XS4026
-
- The CallerMemberNameAttribute applied to parameter '{0}' will have no effect because it applies to a member that is used in contexts that do not allow optional arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4027.xml b/docs/Help_Spanish/Topics/XS4027.xml
deleted file mode 100644
index 896740c2c8..0000000000
--- a/docs/Help_Spanish/Topics/XS4027.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4027
-
-XS4027
-
-
-
- Error XS4027
-
- '{0}' does not implement '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4028.xml b/docs/Help_Spanish/Topics/XS4028.xml
deleted file mode 100644
index a9ce7e7180..0000000000
--- a/docs/Help_Spanish/Topics/XS4028.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4028
-
-XS4028
-
-
-
- Error XS4028
-
- 'await' requires that the type '{0}' have a suitable GetAwaiter method. Are you missing a using directive for 'System'?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4029.xml b/docs/Help_Spanish/Topics/XS4029.xml
deleted file mode 100644
index c876ae55a8..0000000000
--- a/docs/Help_Spanish/Topics/XS4029.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4029
-
-XS4029
-
-
-
- Error XS4029
-
- Cannot return an expression of type 'void'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4030.xml b/docs/Help_Spanish/Topics/XS4030.xml
deleted file mode 100644
index f233a58e94..0000000000
--- a/docs/Help_Spanish/Topics/XS4030.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4030
-
-XS4030
-
-
-
- Error XS4030
-
- Security attribute '{0}' cannot be applied to an Async method.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4031.xml b/docs/Help_Spanish/Topics/XS4031.xml
deleted file mode 100644
index 4e271cdc46..0000000000
--- a/docs/Help_Spanish/Topics/XS4031.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4031
-
-XS4031
-
-
-
- Error XS4031
-
- Async methods are not allowed in an Interface, Class, or Structure which has the 'SecurityCritical' or 'SecuritySafeCritical' attribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4032.xml b/docs/Help_Spanish/Topics/XS4032.xml
deleted file mode 100644
index 9c36094a88..0000000000
--- a/docs/Help_Spanish/Topics/XS4032.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4032
-
-XS4032
-
-
-
- Error XS4032
-
- The 'await' operator can only be used within an async method. Consider marking this method with the 'async' modifier and changing its return type to 'Task<{0}>'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4033.xml b/docs/Help_Spanish/Topics/XS4033.xml
deleted file mode 100644
index e545b40757..0000000000
--- a/docs/Help_Spanish/Topics/XS4033.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4033
-
-XS4033
-
-
-
- Error XS4033
-
- The 'await' operator can only be used within an async method. Consider marking this method with the 'async' modifier and changing its return type to 'Task'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4034.xml b/docs/Help_Spanish/Topics/XS4034.xml
deleted file mode 100644
index 004f746a9b..0000000000
--- a/docs/Help_Spanish/Topics/XS4034.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4034
-
-XS4034
-
-
-
- Error XS4034
-
- The 'await' operator can only be used within an async {0}. Consider marking this {0} with the 'async' modifier.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS4036.xml b/docs/Help_Spanish/Topics/XS4036.xml
deleted file mode 100644
index db7bb5e9c5..0000000000
--- a/docs/Help_Spanish/Topics/XS4036.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS4036
-
-XS4036
-
-
-
- Error XS4036
-
- '{0}' does not contain a definition for '{1}' and no extension method '{1}' accepting a first argument of type '{0}' could be found (are you missing a using directive for '{2}'?)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS5001.xml b/docs/Help_Spanish/Topics/XS5001.xml
deleted file mode 100644
index bb15d8ec29..0000000000
--- a/docs/Help_Spanish/Topics/XS5001.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS5001
-
-XS5001
-
-
-
- Error XS5001
-
- Program does not contain a static 'Start' method suitable for an entry point
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7000.xml b/docs/Help_Spanish/Topics/XS7000.xml
deleted file mode 100644
index c7b35f6c0a..0000000000
--- a/docs/Help_Spanish/Topics/XS7000.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7000
-
-XS7000
-
-
-
- Error XS7000
-
- Unexpected use of an aliased name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7002.xml b/docs/Help_Spanish/Topics/XS7002.xml
deleted file mode 100644
index 0611cfa414..0000000000
--- a/docs/Help_Spanish/Topics/XS7002.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7002
-
-XS7002
-
-
-
- Error XS7002
-
- Unexpected use of a generic name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7003.xml b/docs/Help_Spanish/Topics/XS7003.xml
deleted file mode 100644
index f96c59f404..0000000000
--- a/docs/Help_Spanish/Topics/XS7003.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7003
-
-XS7003
-
-
-
- Error XS7003
-
- Unexpected use of an unbound generic name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7006.xml b/docs/Help_Spanish/Topics/XS7006.xml
deleted file mode 100644
index de2b735312..0000000000
--- a/docs/Help_Spanish/Topics/XS7006.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7006
-
-XS7006
-
-
-
- Error XS7006
-
- Expressions and statements can only occur in a method body
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7007.xml b/docs/Help_Spanish/Topics/XS7007.xml
deleted file mode 100644
index 90308ec820..0000000000
--- a/docs/Help_Spanish/Topics/XS7007.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7007
-
-XS7007
-
-
-
- Error XS7007
-
- A 'using static' directive can only be applied to types; '{0}' is a namespace not a type. Consider a 'using namespace' directive instead
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7008.xml b/docs/Help_Spanish/Topics/XS7008.xml
deleted file mode 100644
index 05a642c0e6..0000000000
--- a/docs/Help_Spanish/Topics/XS7008.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7008
-
-XS7008
-
-
-
- Error XS7008
-
- The assembly name '{0}' is reserved and cannot be used as a reference in an interactive session
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7009.xml b/docs/Help_Spanish/Topics/XS7009.xml
deleted file mode 100644
index e6f61694f8..0000000000
--- a/docs/Help_Spanish/Topics/XS7009.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7009
-
-XS7009
-
-
-
- Error XS7009
-
- Cannot use #r after first token in file
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7010.xml b/docs/Help_Spanish/Topics/XS7010.xml
deleted file mode 100644
index 22e033341d..0000000000
--- a/docs/Help_Spanish/Topics/XS7010.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7010
-
-XS7010
-
-
-
- Error XS7010
-
- Quoted file name expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7011.xml b/docs/Help_Spanish/Topics/XS7011.xml
deleted file mode 100644
index d9cdf18865..0000000000
--- a/docs/Help_Spanish/Topics/XS7011.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7011
-
-XS7011
-
-
-
- Error XS7011
-
- #r is only allowed in scripts
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7012.xml b/docs/Help_Spanish/Topics/XS7012.xml
deleted file mode 100644
index 067e3b86dd..0000000000
--- a/docs/Help_Spanish/Topics/XS7012.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7012
-
-XS7012
-
-
-
- Error XS7012
-
- The name '{0}' does not exist in the current context (are you missing a reference to assembly '{1}'?)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7013.xml b/docs/Help_Spanish/Topics/XS7013.xml
deleted file mode 100644
index e98448555f..0000000000
--- a/docs/Help_Spanish/Topics/XS7013.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7013
-
-XS7013
-
-
-
- Error XS7013
-
- Name '{0}' exceeds the maximum length allowed in metadata.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7014.xml b/docs/Help_Spanish/Topics/XS7014.xml
deleted file mode 100644
index f9b3b3207d..0000000000
--- a/docs/Help_Spanish/Topics/XS7014.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7014
-
-XS7014
-
-
-
- Error XS7014
-
- Attributes are not valid in this context.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7015.xml b/docs/Help_Spanish/Topics/XS7015.xml
deleted file mode 100644
index 6704b74010..0000000000
--- a/docs/Help_Spanish/Topics/XS7015.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7015
-
-XS7015
-
-
-
- Error XS7015
-
- 'extern alias' is not valid in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7016.xml b/docs/Help_Spanish/Topics/XS7016.xml
deleted file mode 100644
index 87f9edb1ea..0000000000
--- a/docs/Help_Spanish/Topics/XS7016.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7016
-
-XS7016
-
-
-
- Error XS7016
-
- Alias '{0}' conflicts with {1} definition
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7017.xml b/docs/Help_Spanish/Topics/XS7017.xml
deleted file mode 100644
index c6ba76e2ec..0000000000
--- a/docs/Help_Spanish/Topics/XS7017.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7017
-
-XS7017
-
-
-
- Error XS7017
-
- Member definition, statement, or end-of-file expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7018.xml b/docs/Help_Spanish/Topics/XS7018.xml
deleted file mode 100644
index f2e3c19cfe..0000000000
--- a/docs/Help_Spanish/Topics/XS7018.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7018
-
-XS7018
-
-
-
- Error XS7018
-
- Expected a script (.csx file) but none specified
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7019.xml b/docs/Help_Spanish/Topics/XS7019.xml
deleted file mode 100644
index 9613245a49..0000000000
--- a/docs/Help_Spanish/Topics/XS7019.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7019
-
-XS7019
-
-
-
- Error XS7019
-
- Type of '{0}' cannot be inferred since its initializer directly or indirectly refers to the definition.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7020.xml b/docs/Help_Spanish/Topics/XS7020.xml
deleted file mode 100644
index f041aed104..0000000000
--- a/docs/Help_Spanish/Topics/XS7020.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7020
-
-XS7020
-
-
-
- Error XS7020
-
- Cannot use 'yield' in top-level script code
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7021.xml b/docs/Help_Spanish/Topics/XS7021.xml
deleted file mode 100644
index 32a663581c..0000000000
--- a/docs/Help_Spanish/Topics/XS7021.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7021
-
-XS7021
-
-
-
- Error XS7021
-
- Cannot declare namespace in script code
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7022.xml b/docs/Help_Spanish/Topics/XS7022.xml
deleted file mode 100644
index d2c0047eff..0000000000
--- a/docs/Help_Spanish/Topics/XS7022.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS7022
-
- XS7022
-
-
-
- Warning XS7022
-
- The entry point of the program is global script code; ignoring '{0}' entry point.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7023.xml b/docs/Help_Spanish/Topics/XS7023.xml
deleted file mode 100644
index 853fc5cf1c..0000000000
--- a/docs/Help_Spanish/Topics/XS7023.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7023
-
-XS7023
-
-
-
- Error XS7023
-
- The second operand of an 'is' or 'as' operator may not be static type '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7024.xml b/docs/Help_Spanish/Topics/XS7024.xml
deleted file mode 100644
index 93a5e214ff..0000000000
--- a/docs/Help_Spanish/Topics/XS7024.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7024
-
-XS7024
-
-
-
- Error XS7024
-
- Delegate '{0}' has no invoke method or an invoke method with a return type or parameter types that are not supported.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7025.xml b/docs/Help_Spanish/Topics/XS7025.xml
deleted file mode 100644
index 7cd2aca8f7..0000000000
--- a/docs/Help_Spanish/Topics/XS7025.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7025
-
-XS7025
-
-
-
- Error XS7025
-
- Inconsistent accessibility: event type '{1}' is less accessible than event '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7026.xml b/docs/Help_Spanish/Topics/XS7026.xml
deleted file mode 100644
index 48a29a2d68..0000000000
--- a/docs/Help_Spanish/Topics/XS7026.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7026
-
-XS7026
-
-
-
- Error XS7026
-
- Assembly and module attributes are not allowed in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7027.xml b/docs/Help_Spanish/Topics/XS7027.xml
deleted file mode 100644
index 3a535305f2..0000000000
--- a/docs/Help_Spanish/Topics/XS7027.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7027
-
-XS7027
-
-
-
- Error XS7027
-
- Error signing output with public key from file '{0}' -- {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7028.xml b/docs/Help_Spanish/Topics/XS7028.xml
deleted file mode 100644
index 80c401f65e..0000000000
--- a/docs/Help_Spanish/Topics/XS7028.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7028
-
-XS7028
-
-
-
- Error XS7028
-
- Error signing output with public key from container '{0}' -- {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7029.xml b/docs/Help_Spanish/Topics/XS7029.xml
deleted file mode 100644
index b764d29563..0000000000
--- a/docs/Help_Spanish/Topics/XS7029.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7029
-
-XS7029
-
-
-
- Error XS7029
-
- Friend access was granted by '{0}', but the strong name signing state of the output assembly does not match that of the granting assembly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7030.xml b/docs/Help_Spanish/Topics/XS7030.xml
deleted file mode 100644
index 9176f14784..0000000000
--- a/docs/Help_Spanish/Topics/XS7030.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7030
-
-XS7030
-
-
-
- Error XS7030
-
- Cannot pass null for friend assembly name
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7032.xml b/docs/Help_Spanish/Topics/XS7032.xml
deleted file mode 100644
index a78e2212b1..0000000000
--- a/docs/Help_Spanish/Topics/XS7032.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7032
-
-XS7032
-
-
-
- Error XS7032
-
- Key file '{0}' is missing the private key needed for signing
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7033.xml b/docs/Help_Spanish/Topics/XS7033.xml
deleted file mode 100644
index d742f0465c..0000000000
--- a/docs/Help_Spanish/Topics/XS7033.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS7033
-
- XS7033
-
-
-
- Warning XS7033
-
- Delay signing was specified and requires a public key, but no public key was specified
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7034.xml b/docs/Help_Spanish/Topics/XS7034.xml
deleted file mode 100644
index 8e428d86ff..0000000000
--- a/docs/Help_Spanish/Topics/XS7034.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7034
-
-XS7034
-
-
-
- Error XS7034
-
- The specified version string does not conform to the required format - major[.minor[.build[.revision]]]
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7035.xml b/docs/Help_Spanish/Topics/XS7035.xml
deleted file mode 100644
index 4873795e2a..0000000000
--- a/docs/Help_Spanish/Topics/XS7035.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS7035
-
- XS7035
-
-
-
- Warning XS7035
-
- The specified version string does not conform to the recommended format - major.minor.build.revision
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7036.xml b/docs/Help_Spanish/Topics/XS7036.xml
deleted file mode 100644
index ee68c801e7..0000000000
--- a/docs/Help_Spanish/Topics/XS7036.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7036
-
-XS7036
-
-
-
- Error XS7036
-
- There is no argument given that corresponds to the required formal parameter '{0}' of '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7038.xml b/docs/Help_Spanish/Topics/XS7038.xml
deleted file mode 100644
index 8407e5eea6..0000000000
--- a/docs/Help_Spanish/Topics/XS7038.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7038
-
-XS7038
-
-
-
- Error XS7038
-
- Failed to emit module '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7041.xml b/docs/Help_Spanish/Topics/XS7041.xml
deleted file mode 100644
index 6a356c0e3b..0000000000
--- a/docs/Help_Spanish/Topics/XS7041.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7041
-
-XS7041
-
-
-
- Error XS7041
-
- Each linked resource and module must have a unique filename. Filename '{0}' is specified more than once in this assembly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7042.xml b/docs/Help_Spanish/Topics/XS7042.xml
deleted file mode 100644
index ba58c2ca04..0000000000
--- a/docs/Help_Spanish/Topics/XS7042.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7042
-
-XS7042
-
-
-
- Error XS7042
-
- The DllImport attribute cannot be applied to a method that is generic or contained in a generic type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7043.xml b/docs/Help_Spanish/Topics/XS7043.xml
deleted file mode 100644
index 04e6098978..0000000000
--- a/docs/Help_Spanish/Topics/XS7043.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7043
-
-XS7043
-
-
-
- Error XS7043
-
- Cannot update '{0}'; attribute '{1}' is missing.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7045.xml b/docs/Help_Spanish/Topics/XS7045.xml
deleted file mode 100644
index 08801720f7..0000000000
--- a/docs/Help_Spanish/Topics/XS7045.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7045
-
-XS7045
-
-
-
- Error XS7045
-
- Parameter not valid for the specified unmanaged type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7046.xml b/docs/Help_Spanish/Topics/XS7046.xml
deleted file mode 100644
index 6fec648401..0000000000
--- a/docs/Help_Spanish/Topics/XS7046.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7046
-
-XS7046
-
-
-
- Error XS7046
-
- Attribute parameter '{0}' must be specified.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7047.xml b/docs/Help_Spanish/Topics/XS7047.xml
deleted file mode 100644
index d1f167b9e0..0000000000
--- a/docs/Help_Spanish/Topics/XS7047.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7047
-
-XS7047
-
-
-
- Error XS7047
-
- Attribute parameter '{0}' or '{1}' must be specified.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7048.xml b/docs/Help_Spanish/Topics/XS7048.xml
deleted file mode 100644
index 9d6411dea3..0000000000
--- a/docs/Help_Spanish/Topics/XS7048.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7048
-
-XS7048
-
-
-
- Error XS7048
-
- First argument to a security attribute must be a valid SecurityAction
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7049.xml b/docs/Help_Spanish/Topics/XS7049.xml
deleted file mode 100644
index 75e569d2f1..0000000000
--- a/docs/Help_Spanish/Topics/XS7049.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7049
-
-XS7049
-
-
-
- Error XS7049
-
- Security attribute '{0}' has an invalid SecurityAction value '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7050.xml b/docs/Help_Spanish/Topics/XS7050.xml
deleted file mode 100644
index fcd3ebd571..0000000000
--- a/docs/Help_Spanish/Topics/XS7050.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7050
-
-XS7050
-
-
-
- Error XS7050
-
- SecurityAction value '{0}' is invalid for security attributes applied to an assembly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7051.xml b/docs/Help_Spanish/Topics/XS7051.xml
deleted file mode 100644
index 3116891562..0000000000
--- a/docs/Help_Spanish/Topics/XS7051.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7051
-
-XS7051
-
-
-
- Error XS7051
-
- SecurityAction value '{0}' is invalid for security attributes applied to a type or a method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7052.xml b/docs/Help_Spanish/Topics/XS7052.xml
deleted file mode 100644
index eb3f9aa66b..0000000000
--- a/docs/Help_Spanish/Topics/XS7052.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7052
-
-XS7052
-
-
-
- Error XS7052
-
- SecurityAction value '{0}' is invalid for PrincipalPermission attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7053.xml b/docs/Help_Spanish/Topics/XS7053.xml
deleted file mode 100644
index 9bc1c1b1ef..0000000000
--- a/docs/Help_Spanish/Topics/XS7053.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7053
-
-XS7053
-
-
-
- Error XS7053
-
- An expression tree may not contain '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7054.xml b/docs/Help_Spanish/Topics/XS7054.xml
deleted file mode 100644
index 43d19025bc..0000000000
--- a/docs/Help_Spanish/Topics/XS7054.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7054
-
-XS7054
-
-
-
- Error XS7054
-
- Unmanaged type '{0}' not valid for fields.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7055.xml b/docs/Help_Spanish/Topics/XS7055.xml
deleted file mode 100644
index 5bf6dde1c6..0000000000
--- a/docs/Help_Spanish/Topics/XS7055.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7055
-
-XS7055
-
-
-
- Error XS7055
-
- Unmanaged type '{0}' is only valid for fields.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7056.xml b/docs/Help_Spanish/Topics/XS7056.xml
deleted file mode 100644
index 9764f4e1a9..0000000000
--- a/docs/Help_Spanish/Topics/XS7056.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7056
-
-XS7056
-
-
-
- Error XS7056
-
- Unable to resolve file path '{0}' specified for the named argument '{1}' for PermissionSet attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7057.xml b/docs/Help_Spanish/Topics/XS7057.xml
deleted file mode 100644
index 876ebd4ed9..0000000000
--- a/docs/Help_Spanish/Topics/XS7057.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7057
-
-XS7057
-
-
-
- Error XS7057
-
- Error reading file '{0}' specified for the named argument '{1}' for PermissionSet attribute: '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7058.xml b/docs/Help_Spanish/Topics/XS7058.xml
deleted file mode 100644
index 11c2a974d2..0000000000
--- a/docs/Help_Spanish/Topics/XS7058.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7058
-
-XS7058
-
-
-
- Error XS7058
-
- The specified version string does not conform to the required format - major.minor.build.revision
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7059.xml b/docs/Help_Spanish/Topics/XS7059.xml
deleted file mode 100644
index 026300ed5f..0000000000
--- a/docs/Help_Spanish/Topics/XS7059.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7059
-
-XS7059
-
-
-
- Error XS7059
-
- Executables cannot be satellite assemblies; culture should always be empty
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7061.xml b/docs/Help_Spanish/Topics/XS7061.xml
deleted file mode 100644
index 423413ac92..0000000000
--- a/docs/Help_Spanish/Topics/XS7061.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7061
-
-XS7061
-
-
-
- Error XS7061
-
- Duplicate '{0}' attribute in '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7064.xml b/docs/Help_Spanish/Topics/XS7064.xml
deleted file mode 100644
index 23caa1e40b..0000000000
--- a/docs/Help_Spanish/Topics/XS7064.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7064
-
-XS7064
-
-
-
- Error XS7064
-
- Error opening icon file {0} -- {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7065.xml b/docs/Help_Spanish/Topics/XS7065.xml
deleted file mode 100644
index 591bec75a6..0000000000
--- a/docs/Help_Spanish/Topics/XS7065.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7065
-
-XS7065
-
-
-
- Error XS7065
-
- Error building Win32 resources -- {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7066.xml b/docs/Help_Spanish/Topics/XS7066.xml
deleted file mode 100644
index b7da3a2336..0000000000
--- a/docs/Help_Spanish/Topics/XS7066.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7066
-
-XS7066
-
-
-
- Error XS7066
-
- Yield statements may not appear at the top level in interactive code.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7067.xml b/docs/Help_Spanish/Topics/XS7067.xml
deleted file mode 100644
index 57b33dbfd0..0000000000
--- a/docs/Help_Spanish/Topics/XS7067.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7067
-
-XS7067
-
-
-
- Error XS7067
-
- Attribute constructor parameter '{0}' is optional, but no default parameter value was specified.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7068.xml b/docs/Help_Spanish/Topics/XS7068.xml
deleted file mode 100644
index 3da224810e..0000000000
--- a/docs/Help_Spanish/Topics/XS7068.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7068
-
-XS7068
-
-
-
- Error XS7068
-
- Reference to type '{0}' claims it is defined in this assembly, but it is not defined in source or any added modules
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7069.xml b/docs/Help_Spanish/Topics/XS7069.xml
deleted file mode 100644
index 89ebab9d9b..0000000000
--- a/docs/Help_Spanish/Topics/XS7069.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7069
-
-XS7069
-
-
-
- Error XS7069
-
- Reference to type '{0}' claims it is defined in '{1}', but it could not be found
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7070.xml b/docs/Help_Spanish/Topics/XS7070.xml
deleted file mode 100644
index 9cbc8ea513..0000000000
--- a/docs/Help_Spanish/Topics/XS7070.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7070
-
-XS7070
-
-
-
- Error XS7070
-
- Security attribute '{0}' is not valid on this declaration type. Security attributes are only valid on assembly, type and method declarations.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7071.xml b/docs/Help_Spanish/Topics/XS7071.xml
deleted file mode 100644
index 7dafeeed98..0000000000
--- a/docs/Help_Spanish/Topics/XS7071.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7071
-
-XS7071
-
-
-
- Error XS7071
-
- Assembly reference '{0}' is invalid and cannot be resolved
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7079.xml b/docs/Help_Spanish/Topics/XS7079.xml
deleted file mode 100644
index 1cf78bbcce..0000000000
--- a/docs/Help_Spanish/Topics/XS7079.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7079
-
-XS7079
-
-
-
- Error XS7079
-
- The type '{0}' is defined in a module that has not been added. You must add the module '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7080.xml b/docs/Help_Spanish/Topics/XS7080.xml
deleted file mode 100644
index bfcf1d1c19..0000000000
--- a/docs/Help_Spanish/Topics/XS7080.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS7080
-
- XS7080
-
-
-
- Warning XS7080
-
- The CallerMemberNameAttribute applied to parameter '{0}' will have no effect. It is overridden by the CallerFilePathAttribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7081.xml b/docs/Help_Spanish/Topics/XS7081.xml
deleted file mode 100644
index cfd518b156..0000000000
--- a/docs/Help_Spanish/Topics/XS7081.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS7081
-
- XS7081
-
-
-
- Warning XS7081
-
- The CallerMemberNameAttribute applied to parameter '{0}' will have no effect. It is overridden by the CallerLineNumberAttribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7082.xml b/docs/Help_Spanish/Topics/XS7082.xml
deleted file mode 100644
index 19d4affac7..0000000000
--- a/docs/Help_Spanish/Topics/XS7082.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS7082
-
- XS7082
-
-
-
- Warning XS7082
-
- The CallerFilePathAttribute applied to parameter '{0}' will have no effect. It is overridden by the CallerLineNumberAttribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7083.xml b/docs/Help_Spanish/Topics/XS7083.xml
deleted file mode 100644
index 21f1bbce34..0000000000
--- a/docs/Help_Spanish/Topics/XS7083.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7083
-
-XS7083
-
-
-
- Error XS7083
-
- Expression must be implicitly convertible to Boolean or its type '{0}' must define operator '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7084.xml b/docs/Help_Spanish/Topics/XS7084.xml
deleted file mode 100644
index d38b020b7d..0000000000
--- a/docs/Help_Spanish/Topics/XS7084.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7084
-
-XS7084
-
-
-
- Error XS7084
-
- A Windows Runtime event may not be passed as an out or ref parameter.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7085.xml b/docs/Help_Spanish/Topics/XS7085.xml
deleted file mode 100644
index 2eebef0e51..0000000000
--- a/docs/Help_Spanish/Topics/XS7085.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7085
-
-XS7085
-
-
-
- Error XS7085
-
- By-reference return type 'ref {0}' is not supported.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7086.xml b/docs/Help_Spanish/Topics/XS7086.xml
deleted file mode 100644
index a8bf2f771f..0000000000
--- a/docs/Help_Spanish/Topics/XS7086.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7086
-
-XS7086
-
-
-
- Error XS7086
-
- Module name '{0}' stored in '{1}' must match its filename.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7087.xml b/docs/Help_Spanish/Topics/XS7087.xml
deleted file mode 100644
index 398902a623..0000000000
--- a/docs/Help_Spanish/Topics/XS7087.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7087
-
-XS7087
-
-
-
- Error XS7087
-
- {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7088.xml b/docs/Help_Spanish/Topics/XS7088.xml
deleted file mode 100644
index 6aad12b875..0000000000
--- a/docs/Help_Spanish/Topics/XS7088.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7088
-
-XS7088
-
-
-
- Error XS7088
-
- Invalid '{0}' value: '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7089.xml b/docs/Help_Spanish/Topics/XS7089.xml
deleted file mode 100644
index 56644346ca..0000000000
--- a/docs/Help_Spanish/Topics/XS7089.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7089
-
-XS7089
-
-
-
- Error XS7089
-
- AppConfigPath must be absolute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7090.xml b/docs/Help_Spanish/Topics/XS7090.xml
deleted file mode 100644
index de8d457211..0000000000
--- a/docs/Help_Spanish/Topics/XS7090.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS7090
-
- XS7090
-
-
-
- Warning XS7090
-
- Attribute '{0}' from module '{1}' will be ignored in favor of the instance appearing in source
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7091.xml b/docs/Help_Spanish/Topics/XS7091.xml
deleted file mode 100644
index 2c9a1145c6..0000000000
--- a/docs/Help_Spanish/Topics/XS7091.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7091
-
-XS7091
-
-
-
- Error XS7091
-
- Attribute '{0}' given in a source file conflicts with option '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7092.xml b/docs/Help_Spanish/Topics/XS7092.xml
deleted file mode 100644
index 9512b29ec4..0000000000
--- a/docs/Help_Spanish/Topics/XS7092.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7092
-
-XS7092
-
-
-
- Error XS7092
-
- A fixed buffer may only have one dimension.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7093.xml b/docs/Help_Spanish/Topics/XS7093.xml
deleted file mode 100644
index b7c8eb5e04..0000000000
--- a/docs/Help_Spanish/Topics/XS7093.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7093
-
-XS7093
-
-
-
- Error XS7093
-
- Cannot read config file '{0}' -- '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7094.xml b/docs/Help_Spanish/Topics/XS7094.xml
deleted file mode 100644
index e80ceb4c79..0000000000
--- a/docs/Help_Spanish/Topics/XS7094.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7094
-
-XS7094
-
-
-
- Error XS7094
-
- Cannot await in the filter expression of a catch clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7095.xml b/docs/Help_Spanish/Topics/XS7095.xml
deleted file mode 100644
index 1486cb614a..0000000000
--- a/docs/Help_Spanish/Topics/XS7095.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS7095
-
- XS7095
-
-
-
- Warning XS7095
-
- Filter expression is a constant, consider removing the filter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7096.xml b/docs/Help_Spanish/Topics/XS7096.xml
deleted file mode 100644
index 390a30c0b2..0000000000
--- a/docs/Help_Spanish/Topics/XS7096.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7096
-
-XS7096
-
-
-
- Error XS7096
-
- Cannot continue since the edit includes a reference to an embedded type: '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7098.xml b/docs/Help_Spanish/Topics/XS7098.xml
deleted file mode 100644
index 5555248c51..0000000000
--- a/docs/Help_Spanish/Topics/XS7098.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7098
-
-XS7098
-
-
-
- Error XS7098
-
- Linked netmodule metadata must provide a full PE image: '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7099.xml b/docs/Help_Spanish/Topics/XS7099.xml
deleted file mode 100644
index 258ceda4e6..0000000000
--- a/docs/Help_Spanish/Topics/XS7099.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7099
-
-XS7099
-
-
-
- Error XS7099
-
- Metadata references are not supported.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7100.xml b/docs/Help_Spanish/Topics/XS7100.xml
deleted file mode 100644
index 949556e29c..0000000000
--- a/docs/Help_Spanish/Topics/XS7100.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7100
-
-XS7100
-
-
-
- Error XS7100
-
- Assembly culture strings may not contain embedded NUL characters.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7101.xml b/docs/Help_Spanish/Topics/XS7101.xml
deleted file mode 100644
index 1a5c38fa3d..0000000000
--- a/docs/Help_Spanish/Topics/XS7101.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7101
-
-XS7101
-
-
-
- Error XS7101
-
- Member '{0}' added during the current debug session can only be accessed from within its declaring assembly '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7102.xml b/docs/Help_Spanish/Topics/XS7102.xml
deleted file mode 100644
index 365bc88381..0000000000
--- a/docs/Help_Spanish/Topics/XS7102.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS7102
-
-XS7102
-
-
-
- Error XS7102
-
- Compilation options '{0}' and '{1}' can't both be specified at the same time.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS7103.XML b/docs/Help_Spanish/Topics/XS7103.XML
deleted file mode 100644
index 9c432a0360..0000000000
--- a/docs/Help_Spanish/Topics/XS7103.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS7103
-
-XS7103
-
-
-
- Error XS7103
-
- Unable to read debug information of method '{0}' (token 0x{1:X8}) from assembly '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8001.xml b/docs/Help_Spanish/Topics/XS8001.xml
deleted file mode 100644
index 33373b58dc..0000000000
--- a/docs/Help_Spanish/Topics/XS8001.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8001
-
- XS8001
-
-
-
- Warning XS8001
-
- The command line switch '{0}' is not yet implemented and was ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8002.xml b/docs/Help_Spanish/Topics/XS8002.xml
deleted file mode 100644
index c1f97c99f7..0000000000
--- a/docs/Help_Spanish/Topics/XS8002.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8002
-
- XS8002
-
-
-
- Warning XS8002
-
- Referenced assembly '{0}' does not have a strong name.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8003.xml b/docs/Help_Spanish/Topics/XS8003.xml
deleted file mode 100644
index 26ea3aaf9d..0000000000
--- a/docs/Help_Spanish/Topics/XS8003.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8003
-
-XS8003
-
-
-
- Error XS8003
-
- Invalid signature public key specified in AssemblySignatureKeyAttribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8004.xml b/docs/Help_Spanish/Topics/XS8004.xml
deleted file mode 100644
index a66be9a3af..0000000000
--- a/docs/Help_Spanish/Topics/XS8004.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8004
-
-XS8004
-
-
-
- Error XS8004
-
- Type '{0}' exported from module '{1}' conflicts with type declared in primary module of this assembly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8005.xml b/docs/Help_Spanish/Topics/XS8005.xml
deleted file mode 100644
index 0b6bdeaff4..0000000000
--- a/docs/Help_Spanish/Topics/XS8005.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8005
-
-XS8005
-
-
-
- Error XS8005
-
- Type '{0}' exported from module '{1}' conflicts with type '{2}' exported from module '{3}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8006.xml b/docs/Help_Spanish/Topics/XS8006.xml
deleted file mode 100644
index 0dae86d3f7..0000000000
--- a/docs/Help_Spanish/Topics/XS8006.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8006
-
-XS8006
-
-
-
- Error XS8006
-
- Forwarded type '{0}' conflicts with type declared in primary module of this assembly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8007.xml b/docs/Help_Spanish/Topics/XS8007.xml
deleted file mode 100644
index e1be48e1a3..0000000000
--- a/docs/Help_Spanish/Topics/XS8007.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8007
-
-XS8007
-
-
-
- Error XS8007
-
- Type '{0}' forwarded to assembly '{1}' conflicts with type '{2}' forwarded to assembly '{3}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8008.xml b/docs/Help_Spanish/Topics/XS8008.xml
deleted file mode 100644
index 5612c657af..0000000000
--- a/docs/Help_Spanish/Topics/XS8008.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8008
-
-XS8008
-
-
-
- Error XS8008
-
- Type '{0}' forwarded to assembly '{1}' conflicts with type '{2}' exported from module '{3}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8009.xml b/docs/Help_Spanish/Topics/XS8009.xml
deleted file mode 100644
index 67e66d6d8e..0000000000
--- a/docs/Help_Spanish/Topics/XS8009.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8009
-
- XS8009
-
-
-
- Warning XS8009
-
- Referenced assembly '{0}' has different culture setting of '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8010.xml b/docs/Help_Spanish/Topics/XS8010.xml
deleted file mode 100644
index d483aa881d..0000000000
--- a/docs/Help_Spanish/Topics/XS8010.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8010
-
-XS8010
-
-
-
- Error XS8010
-
- Agnostic assembly cannot have a processor specific module '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8011.xml b/docs/Help_Spanish/Topics/XS8011.xml
deleted file mode 100644
index c176d91cc9..0000000000
--- a/docs/Help_Spanish/Topics/XS8011.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8011
-
-XS8011
-
-
-
- Error XS8011
-
- Assembly and module '{0}' cannot target different processors.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8012.xml b/docs/Help_Spanish/Topics/XS8012.xml
deleted file mode 100644
index 53ad885ec8..0000000000
--- a/docs/Help_Spanish/Topics/XS8012.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8012
-
- XS8012
-
-
-
- Warning XS8012
-
- Referenced assembly '{0}' targets a different processor.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8013.xml b/docs/Help_Spanish/Topics/XS8013.xml
deleted file mode 100644
index c278d014b1..0000000000
--- a/docs/Help_Spanish/Topics/XS8013.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8013
-
-XS8013
-
-
-
- Error XS8013
-
- Cryptographic failure while creating hashes.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8014.xml b/docs/Help_Spanish/Topics/XS8014.xml
deleted file mode 100644
index b5d6405c90..0000000000
--- a/docs/Help_Spanish/Topics/XS8014.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8014
-
-XS8014
-
-
-
- Error XS8014
-
- Reference to '{0}' netmodule missing.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8015.xml b/docs/Help_Spanish/Topics/XS8015.xml
deleted file mode 100644
index e8f4252428..0000000000
--- a/docs/Help_Spanish/Topics/XS8015.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8015
-
-XS8015
-
-
-
- Error XS8015
-
- Module '{0}' is already defined in this assembly. Each module must have a unique filename.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8016.xml b/docs/Help_Spanish/Topics/XS8016.xml
deleted file mode 100644
index 32b2245fcf..0000000000
--- a/docs/Help_Spanish/Topics/XS8016.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8016
-
-XS8016
-
-
-
- Error XS8016
-
- Transparent identifier member access failed for field '{0}' of '{1}'. Does the data being queried implement the query pattern?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8017.xml b/docs/Help_Spanish/Topics/XS8017.xml
deleted file mode 100644
index b3d4e89e87..0000000000
--- a/docs/Help_Spanish/Topics/XS8017.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8017
-
-XS8017
-
-
-
- Error XS8017
-
- The parameter has multiple distinct default values.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8018.xml b/docs/Help_Spanish/Topics/XS8018.xml
deleted file mode 100644
index 273d16f70c..0000000000
--- a/docs/Help_Spanish/Topics/XS8018.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8018
-
- XS8018
-
-
-
- Warning XS8018
-
- Within cref attributes, nested types of generic types should be qualified.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8019.xml b/docs/Help_Spanish/Topics/XS8019.xml
deleted file mode 100644
index f6061bbb30..0000000000
--- a/docs/Help_Spanish/Topics/XS8019.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8019
-
-XS8019
-
-
-
- Error XS8019
-
- Unnecessary using directive.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8020.xml b/docs/Help_Spanish/Topics/XS8020.xml
deleted file mode 100644
index d6272701d2..0000000000
--- a/docs/Help_Spanish/Topics/XS8020.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8020
-
-XS8020
-
-
-
- Error XS8020
-
- Unused extern alias.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8021.xml b/docs/Help_Spanish/Topics/XS8021.xml
deleted file mode 100644
index 864e2b90ef..0000000000
--- a/docs/Help_Spanish/Topics/XS8021.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8021
-
- XS8021
-
-
-
- Warning XS8021
-
- No value for RuntimeMetadataVersion found. No assembly containing System.Object was found nor was a value for RuntimeMetadataVersion specified through options.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8022.xml b/docs/Help_Spanish/Topics/XS8022.xml
deleted file mode 100644
index e03e0ce45b..0000000000
--- a/docs/Help_Spanish/Topics/XS8022.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8022
-
-XS8022
-
-
-
- Error XS8022
-
- Feature '{0}' is not available in X# 1.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8023.xml b/docs/Help_Spanish/Topics/XS8023.xml
deleted file mode 100644
index ffd68cad67..0000000000
--- a/docs/Help_Spanish/Topics/XS8023.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8023
-
-XS8023
-
-
-
- Error XS8023
-
- Feature '{0}' is not available in X# 2.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8024.xml b/docs/Help_Spanish/Topics/XS8024.xml
deleted file mode 100644
index 4982f28c99..0000000000
--- a/docs/Help_Spanish/Topics/XS8024.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8024
-
-XS8024
-
-
-
- Error XS8024
-
- Feature '{0}' is not available in X# 3.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8025.xml b/docs/Help_Spanish/Topics/XS8025.xml
deleted file mode 100644
index a1404128b5..0000000000
--- a/docs/Help_Spanish/Topics/XS8025.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8025
-
-XS8025
-
-
-
- Error XS8025
-
- Feature '{0}' is not available in X# 4.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8026.xml b/docs/Help_Spanish/Topics/XS8026.xml
deleted file mode 100644
index 81645c441f..0000000000
--- a/docs/Help_Spanish/Topics/XS8026.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8026
-
-XS8026
-
-
-
- Error XS8026
-
- Feature '{0}' is not available in X# 5.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8027.xml b/docs/Help_Spanish/Topics/XS8027.xml
deleted file mode 100644
index 2a1349a5fe..0000000000
--- a/docs/Help_Spanish/Topics/XS8027.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8027
-
-XS8027
-
-
-
- Error XS8027
-
- The field has multiple distinct constant values.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8028.xml b/docs/Help_Spanish/Topics/XS8028.xml
deleted file mode 100644
index 9682a5c247..0000000000
--- a/docs/Help_Spanish/Topics/XS8028.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8028
-
-XS8028
-
-
-
- Error XS8028
-
- '{0}': a class with the ComImport attribute cannot specify field initializers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8029.xml b/docs/Help_Spanish/Topics/XS8029.xml
deleted file mode 100644
index 20f826df78..0000000000
--- a/docs/Help_Spanish/Topics/XS8029.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8029
-
- XS8029
-
-
-
- Warning XS8029
-
- Local name '{0}' is too long for PDB. Consider shortening or compiling without /debug.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8030.xml b/docs/Help_Spanish/Topics/XS8030.xml
deleted file mode 100644
index 4c3888d57a..0000000000
--- a/docs/Help_Spanish/Topics/XS8030.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8030
-
-XS8030
-
-
-
- Error XS8030
-
- Anonymous function converted to a void returning delegate cannot return a value
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8031.xml b/docs/Help_Spanish/Topics/XS8031.xml
deleted file mode 100644
index a3f9d0341d..0000000000
--- a/docs/Help_Spanish/Topics/XS8031.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8031
-
-XS8031
-
-
-
- Error XS8031
-
- Async lambda expression converted to a 'Task' returning delegate cannot return a value. Did you intend to return 'Task'?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8032.xml b/docs/Help_Spanish/Topics/XS8032.xml
deleted file mode 100644
index 4c05ced3da..0000000000
--- a/docs/Help_Spanish/Topics/XS8032.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8032
-
- XS8032
-
-
-
- Warning XS8032
-
- An instance of analyzer {0} cannot be created from {1} : {2}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8033.xml b/docs/Help_Spanish/Topics/XS8033.xml
deleted file mode 100644
index 33e9b14486..0000000000
--- a/docs/Help_Spanish/Topics/XS8033.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8033
-
- XS8033
-
-
-
- Warning XS8033
-
- The assembly {0} does not contain any analyzers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8034.xml b/docs/Help_Spanish/Topics/XS8034.xml
deleted file mode 100644
index 00b945735d..0000000000
--- a/docs/Help_Spanish/Topics/XS8034.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8034
-
- XS8034
-
-
-
- Warning XS8034
-
- Unable to load Analyzer assembly {0} : {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8035.xml b/docs/Help_Spanish/Topics/XS8035.xml
deleted file mode 100644
index d637451e8b..0000000000
--- a/docs/Help_Spanish/Topics/XS8035.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8035
-
-XS8035
-
-
-
- Error XS8035
-
- Error reading ruleset file {0} - {1}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8036.xml b/docs/Help_Spanish/Topics/XS8036.xml
deleted file mode 100644
index 6d4aa642cb..0000000000
--- a/docs/Help_Spanish/Topics/XS8036.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8036
-
-XS8036
-
-
-
- Error XS8036
-
- Error reading debug information for '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8040.xml b/docs/Help_Spanish/Topics/XS8040.xml
deleted file mode 100644
index 5994caee52..0000000000
--- a/docs/Help_Spanish/Topics/XS8040.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8040
-
-XS8040
-
-
-
- Error XS8040
-
- Skipping some types in analyzer assembly {0} due to a ReflectionTypeLoadException : {1}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8050.xml b/docs/Help_Spanish/Topics/XS8050.xml
deleted file mode 100644
index 2a1277041e..0000000000
--- a/docs/Help_Spanish/Topics/XS8050.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8050
-
-XS8050
-
-
-
- Error XS8050
-
- Only auto-implemented properties can have initializers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8051.xml b/docs/Help_Spanish/Topics/XS8051.xml
deleted file mode 100644
index ec6cf14a18..0000000000
--- a/docs/Help_Spanish/Topics/XS8051.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8051
-
-XS8051
-
-
-
- Error XS8051
-
- Auto-implemented properties must have get accessors.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8052.xml b/docs/Help_Spanish/Topics/XS8052.xml
deleted file mode 100644
index 63400b914d..0000000000
--- a/docs/Help_Spanish/Topics/XS8052.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8052
-
-XS8052
-
-
-
- Error XS8052
-
- Auto-implemented properties inside interfaces cannot have initializers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8053.XML b/docs/Help_Spanish/Topics/XS8053.XML
deleted file mode 100644
index 71f9880c36..0000000000
--- a/docs/Help_Spanish/Topics/XS8053.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8053
-
-XS8053
-
-
-
- Error XS8053
-
- Instance properties in interfaces cannot have initializers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8054.xml b/docs/Help_Spanish/Topics/XS8054.xml
deleted file mode 100644
index 2cd9ffb3d6..0000000000
--- a/docs/Help_Spanish/Topics/XS8054.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8054
-
-XS8054
-
-
-
- Error XS8054
-
- Enums cannot contain explicit parameterless constructors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8055.xml b/docs/Help_Spanish/Topics/XS8055.xml
deleted file mode 100644
index e058af6053..0000000000
--- a/docs/Help_Spanish/Topics/XS8055.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8055
-
-XS8055
-
-
-
- Error XS8055
-
- Cannot emit debug information for a source text without encoding.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8056.xml b/docs/Help_Spanish/Topics/XS8056.xml
deleted file mode 100644
index a1b89ff47a..0000000000
--- a/docs/Help_Spanish/Topics/XS8056.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8056
-
-XS8056
-
-
-
- Error XS8056
-
- Properties cannot combine accessor lists with expression bodies.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8057.xml b/docs/Help_Spanish/Topics/XS8057.xml
deleted file mode 100644
index a4ae293a85..0000000000
--- a/docs/Help_Spanish/Topics/XS8057.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8057
-
-XS8057
-
-
-
- Error XS8057
-
- Methods cannot combine block bodies with expression bodies.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8058.xml b/docs/Help_Spanish/Topics/XS8058.xml
deleted file mode 100644
index 15ed588be9..0000000000
--- a/docs/Help_Spanish/Topics/XS8058.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8058
-
-XS8058
-
-
-
- Error XS8058
-
- Feature '{0}' is only available in 'experimental' language version.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8059.xml b/docs/Help_Spanish/Topics/XS8059.xml
deleted file mode 100644
index 946859f147..0000000000
--- a/docs/Help_Spanish/Topics/XS8059.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8059
-
-XS8059
-
-
-
- Error XS8059
-
- Feature '{0}' is not available in X# 6.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8070.xml b/docs/Help_Spanish/Topics/XS8070.xml
deleted file mode 100644
index ece06672ce..0000000000
--- a/docs/Help_Spanish/Topics/XS8070.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8070
-
-XS8070
-
-
-
- Error XS8070
-
- Control cannot fall out of switch from final case label ('{0}')
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8072.xml b/docs/Help_Spanish/Topics/XS8072.xml
deleted file mode 100644
index acef7f89b9..0000000000
--- a/docs/Help_Spanish/Topics/XS8072.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8072
-
-XS8072
-
-
-
- Error XS8072
-
- An expression tree lambda may not contain a null propagating operator.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8073.xml b/docs/Help_Spanish/Topics/XS8073.xml
deleted file mode 100644
index aacac9e733..0000000000
--- a/docs/Help_Spanish/Topics/XS8073.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8073
-
- XS8073
-
-
-
- Warning XS8073
-
- The result of the expression is always '{0}' since a value of type '{1}' is never equal to 'null' of type '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8074.xml b/docs/Help_Spanish/Topics/XS8074.xml
deleted file mode 100644
index 80912af2ae..0000000000
--- a/docs/Help_Spanish/Topics/XS8074.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8074
-
-XS8074
-
-
-
- Error XS8074
-
- An expression tree lambda may not contain a dictionary initializer.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8075.xml b/docs/Help_Spanish/Topics/XS8075.xml
deleted file mode 100644
index 28d7f6e856..0000000000
--- a/docs/Help_Spanish/Topics/XS8075.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8075
-
-XS8075
-
-
-
- Error XS8075
-
- An extension Add method is not supported for a collection initializer in an expression lambda.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8076.xml b/docs/Help_Spanish/Topics/XS8076.xml
deleted file mode 100644
index a642371e2a..0000000000
--- a/docs/Help_Spanish/Topics/XS8076.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8076
-
-XS8076
-
-
-
- Error XS8076
-
- Missing close delimiter '}' for interpolated expression started with '{'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8077.xml b/docs/Help_Spanish/Topics/XS8077.xml
deleted file mode 100644
index 2c4418dffc..0000000000
--- a/docs/Help_Spanish/Topics/XS8077.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8077
-
-XS8077
-
-
-
- Error XS8077
-
- A single-line comment may not be used in an interpolated string.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8078.xml b/docs/Help_Spanish/Topics/XS8078.xml
deleted file mode 100644
index 773a3348f4..0000000000
--- a/docs/Help_Spanish/Topics/XS8078.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8078
-
-XS8078
-
-
-
- Error XS8078
-
- An expression is too long or complex to compile
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8079.xml b/docs/Help_Spanish/Topics/XS8079.xml
deleted file mode 100644
index 412002daab..0000000000
--- a/docs/Help_Spanish/Topics/XS8079.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8079
-
- XS8079
-
-
-
- Warning XS8079
-
- Use of possibly unassigned auto-implemented property '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8080.xml b/docs/Help_Spanish/Topics/XS8080.xml
deleted file mode 100644
index bda8043750..0000000000
--- a/docs/Help_Spanish/Topics/XS8080.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8080
-
-XS8080
-
-
-
- Error XS8080
-
- Auto-implemented properties must override all accessors of the overridden property.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8081.xml b/docs/Help_Spanish/Topics/XS8081.xml
deleted file mode 100644
index bafacdef3e..0000000000
--- a/docs/Help_Spanish/Topics/XS8081.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8081
-
-XS8081
-
-
-
- Error XS8081
-
- Expression does not have a name.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8082.xml b/docs/Help_Spanish/Topics/XS8082.xml
deleted file mode 100644
index b59e7228e0..0000000000
--- a/docs/Help_Spanish/Topics/XS8082.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8082
-
-XS8082
-
-
-
- Error XS8082
-
- Sub-expression cannot be used in an argument to nameof.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8083.xml b/docs/Help_Spanish/Topics/XS8083.xml
deleted file mode 100644
index a9269b3906..0000000000
--- a/docs/Help_Spanish/Topics/XS8083.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8083
-
-XS8083
-
-
-
- Error XS8083
-
- An alias-qualified name is not an expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8084.xml b/docs/Help_Spanish/Topics/XS8084.xml
deleted file mode 100644
index 48bf8d3755..0000000000
--- a/docs/Help_Spanish/Topics/XS8084.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8084
-
-XS8084
-
-
-
- Error XS8084
-
- Type parameters are not allowed on a method group as an argument to 'nameof'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8085.xml b/docs/Help_Spanish/Topics/XS8085.xml
deleted file mode 100644
index 02fac8d68e..0000000000
--- a/docs/Help_Spanish/Topics/XS8085.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8085
-
-XS8085
-
-
-
- Error XS8085
-
- A 'using static' directive cannot be used to declare an alias
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8086.xml b/docs/Help_Spanish/Topics/XS8086.xml
deleted file mode 100644
index 9fc2da18d2..0000000000
--- a/docs/Help_Spanish/Topics/XS8086.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8086
-
-XS8086
-
-
-
- Error XS8086
-
- A '{0}' character must be escaped (by doubling) in an interpolated string.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8087.xml b/docs/Help_Spanish/Topics/XS8087.xml
deleted file mode 100644
index 91e1e535d0..0000000000
--- a/docs/Help_Spanish/Topics/XS8087.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8087
-
-XS8087
-
-
-
- Error XS8087
-
- A '{0}' character may only be escaped by doubling '{0}{0}' in an interpolated string.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8088.xml b/docs/Help_Spanish/Topics/XS8088.xml
deleted file mode 100644
index 3b902659ba..0000000000
--- a/docs/Help_Spanish/Topics/XS8088.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8088
-
-XS8088
-
-
-
- Error XS8088
-
- A format specifier may not contain trailing whitespace.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8089.xml b/docs/Help_Spanish/Topics/XS8089.xml
deleted file mode 100644
index 1ef491c5ea..0000000000
--- a/docs/Help_Spanish/Topics/XS8089.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8089
-
-XS8089
-
-
-
- Error XS8089
-
- Empty format specifier.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8090.xml b/docs/Help_Spanish/Topics/XS8090.xml
deleted file mode 100644
index eabe03f1cc..0000000000
--- a/docs/Help_Spanish/Topics/XS8090.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8090
-
-XS8090
-
-
-
- Error XS8090
-
- There is an error in a referenced assembly '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8091.xml b/docs/Help_Spanish/Topics/XS8091.xml
deleted file mode 100644
index 966ca24ca4..0000000000
--- a/docs/Help_Spanish/Topics/XS8091.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8091
-
-XS8091
-
-
-
- Error XS8091
-
- '{0}' cannot be extern and have a constructor initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8092.xml b/docs/Help_Spanish/Topics/XS8092.xml
deleted file mode 100644
index 7d0a92ea04..0000000000
--- a/docs/Help_Spanish/Topics/XS8092.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8092
-
-XS8092
-
-
-
- Error XS8092
-
- Expression or declaration statement expected.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8093.xml b/docs/Help_Spanish/Topics/XS8093.xml
deleted file mode 100644
index d68fd62034..0000000000
--- a/docs/Help_Spanish/Topics/XS8093.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8093
-
-XS8093
-
-
-
- Error XS8093
-
- Extension method groups are not allowed as an argument to 'nameof'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8094.xml b/docs/Help_Spanish/Topics/XS8094.xml
deleted file mode 100644
index ef1cd151df..0000000000
--- a/docs/Help_Spanish/Topics/XS8094.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8094
-
- XS8094
-
-
-
- Warning XS8094
-
- Alignment value {0} has a magnitude greater than {1} and may result in a large formatted string.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8095.xml b/docs/Help_Spanish/Topics/XS8095.xml
deleted file mode 100644
index 0d1e7c0f3b..0000000000
--- a/docs/Help_Spanish/Topics/XS8095.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8095
-
-XS8095
-
-
-
- Error XS8095
-
- Length of String constant exceeds current memory limit. Try splitting the string into multiple constants.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8096.xml b/docs/Help_Spanish/Topics/XS8096.xml
deleted file mode 100644
index a45d682678..0000000000
--- a/docs/Help_Spanish/Topics/XS8096.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8096
-
-XS8096
-
-
-
- Error XS8096
-
- Debug entry point must be a definition of a method declared in the current compilation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8097.xml b/docs/Help_Spanish/Topics/XS8097.xml
deleted file mode 100644
index a0224f92ba..0000000000
--- a/docs/Help_Spanish/Topics/XS8097.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8097
-
-XS8097
-
-
-
- Error XS8097
-
- #load is only allowed in scripts
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8098.xml b/docs/Help_Spanish/Topics/XS8098.xml
deleted file mode 100644
index 33f712419c..0000000000
--- a/docs/Help_Spanish/Topics/XS8098.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8098
-
-XS8098
-
-
-
- Error XS8098
-
- Cannot use #load after first token in file
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8099.xml b/docs/Help_Spanish/Topics/XS8099.xml
deleted file mode 100644
index 9464633a41..0000000000
--- a/docs/Help_Spanish/Topics/XS8099.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8099
-
-XS8099
-
-
-
- Error XS8099
-
- Source file references are not supported.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8100.xml b/docs/Help_Spanish/Topics/XS8100.xml
deleted file mode 100644
index 6b1db61518..0000000000
--- a/docs/Help_Spanish/Topics/XS8100.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8100
-
-XS8100
-
-
-
- Error XS8100
-
- The 'await' operator cannot be used in a static script variable initializer.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8101.xml b/docs/Help_Spanish/Topics/XS8101.xml
deleted file mode 100644
index e9ee006a4a..0000000000
--- a/docs/Help_Spanish/Topics/XS8101.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8101
-
-XS8101
-
-
-
- Error XS8101
-
- The pathmap option was incorrectly formatted.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8102.xml b/docs/Help_Spanish/Topics/XS8102.xml
deleted file mode 100644
index 26810fa673..0000000000
--- a/docs/Help_Spanish/Topics/XS8102.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8102
-
-XS8102
-
-
-
- Error XS8102
-
- Public signing was specified and requires a public key, but no public key was specified.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8103.xml b/docs/Help_Spanish/Topics/XS8103.xml
deleted file mode 100644
index 284c1a54f1..0000000000
--- a/docs/Help_Spanish/Topics/XS8103.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8103
-
-XS8103
-
-
-
- Error XS8103
-
- Combined length of user strings used by the program exceeds allowed limit. Try to decrease use of string literals.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8104.xml b/docs/Help_Spanish/Topics/XS8104.xml
deleted file mode 100644
index 85cb48bfe4..0000000000
--- a/docs/Help_Spanish/Topics/XS8104.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8104
-
-XS8104
-
-
-
- Error XS8104
-
- An error occurred while writing the output file: {0}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8105.xml b/docs/Help_Spanish/Topics/XS8105.xml
deleted file mode 100644
index d40b84af3f..0000000000
--- a/docs/Help_Spanish/Topics/XS8105.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8105
-
- XS8105
-
-
-
- Warning XS8105
-
- Attribute '{0}' is ignored when public signing is specified.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8106.xml b/docs/Help_Spanish/Topics/XS8106.xml
deleted file mode 100644
index 4ed0a3a941..0000000000
--- a/docs/Help_Spanish/Topics/XS8106.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8106
-
-XS8106
-
-
-
- Error XS8106
-
- Option '{0}' must be an absolute path.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8107.xml b/docs/Help_Spanish/Topics/XS8107.xml
deleted file mode 100644
index b4a82eac20..0000000000
--- a/docs/Help_Spanish/Topics/XS8107.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8107
-
-XS8107
-
-
-
- Error XS8107
-
- Feature '{0}' is not available in X# 7. Please use language version {1} or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8108.xml b/docs/Help_Spanish/Topics/XS8108.xml
deleted file mode 100644
index 10a49fd313..0000000000
--- a/docs/Help_Spanish/Topics/XS8108.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8108
-
-XS8108
-
-
-
- Error XS8108
-
- Cannot pass argument with dynamic type to params parameter '{0}' of local function '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8110.xml b/docs/Help_Spanish/Topics/XS8110.xml
deleted file mode 100644
index eaf3b78cb7..0000000000
--- a/docs/Help_Spanish/Topics/XS8110.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8110
-
-XS8110
-
-
-
- Error XS8110
-
- An expression tree may not contain a reference to a local function
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8111.xml b/docs/Help_Spanish/Topics/XS8111.xml
deleted file mode 100644
index 017e119e52..0000000000
--- a/docs/Help_Spanish/Topics/XS8111.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8111
-
-XS8111
-
-
-
- Error XS8111
-
- Invalid instrumentation kind: {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8112.XML b/docs/Help_Spanish/Topics/XS8112.XML
deleted file mode 100644
index aaf4be87d9..0000000000
--- a/docs/Help_Spanish/Topics/XS8112.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8112
-
-XS8112
-
-
-
- Error XS8112
-
- '{0}' is a local function and must therefore always have a body.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8113.XML b/docs/Help_Spanish/Topics/XS8113.XML
deleted file mode 100644
index da69d19a25..0000000000
--- a/docs/Help_Spanish/Topics/XS8113.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8113
-
-XS8113
-
-
-
- Error XS8113
-
- Invalid hash algorithm name: '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8115.xml b/docs/Help_Spanish/Topics/XS8115.xml
deleted file mode 100644
index 1a243b0e8e..0000000000
--- a/docs/Help_Spanish/Topics/XS8115.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8115
-
-XS8115
-
-
-
- Error XS8115
-
- A throw expression is not allowed in this context.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8116.xml b/docs/Help_Spanish/Topics/XS8116.xml
deleted file mode 100644
index a00ff29eac..0000000000
--- a/docs/Help_Spanish/Topics/XS8116.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8116
-
-XS8116
-
-
-
- Error XS8116
-
- It is not legal to use nullable type '{0}' in a pattern; use the underlying type '{1}' instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8117.xml b/docs/Help_Spanish/Topics/XS8117.xml
deleted file mode 100644
index 38f1c275c6..0000000000
--- a/docs/Help_Spanish/Topics/XS8117.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8117
-
-XS8117
-
-
-
- Error XS8117
-
- Invalid operand for pattern match; value required, but found '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8119.xml b/docs/Help_Spanish/Topics/XS8119.xml
deleted file mode 100644
index 923da24bb2..0000000000
--- a/docs/Help_Spanish/Topics/XS8119.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8119
-
-XS8119
-
-
-
- Error XS8119
-
- The switch expression must be a value; found {0}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8120.xml b/docs/Help_Spanish/Topics/XS8120.xml
deleted file mode 100644
index f594078620..0000000000
--- a/docs/Help_Spanish/Topics/XS8120.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8120
-
-XS8120
-
-
-
- Error XS8120
-
- The switch case has already been handled by a previous case.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8121.xml b/docs/Help_Spanish/Topics/XS8121.xml
deleted file mode 100644
index b0fbaec025..0000000000
--- a/docs/Help_Spanish/Topics/XS8121.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8121
-
-XS8121
-
-
-
- Error XS8121
-
- An expression of type {0} cannot be handled by a pattern of type {1}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8122.xml b/docs/Help_Spanish/Topics/XS8122.xml
deleted file mode 100644
index f286beb086..0000000000
--- a/docs/Help_Spanish/Topics/XS8122.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8122
-
-XS8122
-
-
-
- Error XS8122
-
- An expression tree may not contain an 'is' pattern-matching operator.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8123.xml b/docs/Help_Spanish/Topics/XS8123.xml
deleted file mode 100644
index 8ad060f0fc..0000000000
--- a/docs/Help_Spanish/Topics/XS8123.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS8123
-
- XS8123
-
-
-
- Warning XS8123
-
- The tuple element name '{0}' is ignored because a different name is specified by the target type '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8124.xml b/docs/Help_Spanish/Topics/XS8124.xml
deleted file mode 100644
index 2d1e1b6598..0000000000
--- a/docs/Help_Spanish/Topics/XS8124.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8124
-
-XS8124
-
-
-
- Error XS8124
-
- Tuple must contain at least two elements.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8125.xml b/docs/Help_Spanish/Topics/XS8125.xml
deleted file mode 100644
index a86f1f0bb5..0000000000
--- a/docs/Help_Spanish/Topics/XS8125.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8125
-
-XS8125
-
-
-
- Error XS8125
-
- Tuple element name '{0}' is only allowed at position {1}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8126.xml b/docs/Help_Spanish/Topics/XS8126.xml
deleted file mode 100644
index e25f789d0b..0000000000
--- a/docs/Help_Spanish/Topics/XS8126.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8126
-
-XS8126
-
-
-
- Error XS8126
-
- Tuple element name '{0}' is disallowed at any position.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8127.xml b/docs/Help_Spanish/Topics/XS8127.xml
deleted file mode 100644
index 341d9b3fe6..0000000000
--- a/docs/Help_Spanish/Topics/XS8127.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8127
-
-XS8127
-
-
-
- Error XS8127
-
- Tuple element names must be unique.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8128.xml b/docs/Help_Spanish/Topics/XS8128.xml
deleted file mode 100644
index 19d5cc691d..0000000000
--- a/docs/Help_Spanish/Topics/XS8128.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8128
-
-XS8128
-
-
-
- Error XS8128
-
- Member '{0}' was not found on type '{1}' from assembly '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8129.xml b/docs/Help_Spanish/Topics/XS8129.xml
deleted file mode 100644
index 8de5e79c18..0000000000
--- a/docs/Help_Spanish/Topics/XS8129.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8129
-
-XS8129
-
-
-
- Error XS8129
-
- No Deconstruct instance or extension method was found for type '{0}', with {1} out parameters and a void return type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8130.xml b/docs/Help_Spanish/Topics/XS8130.xml
deleted file mode 100644
index 0ff9806401..0000000000
--- a/docs/Help_Spanish/Topics/XS8130.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8130
-
-XS8130
-
-
-
- Error XS8130
-
- Cannot infer the type of implicitly-typed deconstruction variable '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8131.xml b/docs/Help_Spanish/Topics/XS8131.xml
deleted file mode 100644
index 4a9da452db..0000000000
--- a/docs/Help_Spanish/Topics/XS8131.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8131
-
-XS8131
-
-
-
- Error XS8131
-
- Deconstruct assignment requires an expression with a type on the right-hand-side.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8132.xml b/docs/Help_Spanish/Topics/XS8132.xml
deleted file mode 100644
index 2b3fb433f0..0000000000
--- a/docs/Help_Spanish/Topics/XS8132.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8132
-
-XS8132
-
-
-
- Error XS8132
-
- Cannot deconstruct a tuple of '{0}' elements into '{1}' variables.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8133.xml b/docs/Help_Spanish/Topics/XS8133.xml
deleted file mode 100644
index 72f919ccc1..0000000000
--- a/docs/Help_Spanish/Topics/XS8133.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8133
-
-XS8133
-
-
-
- Error XS8133
-
- Cannot deconstruct dynamic objects.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8134.xml b/docs/Help_Spanish/Topics/XS8134.xml
deleted file mode 100644
index d38385723a..0000000000
--- a/docs/Help_Spanish/Topics/XS8134.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8134
-
-XS8134
-
-
-
- Error XS8134
-
- Deconstruction must contain at least two variables.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8135.xml b/docs/Help_Spanish/Topics/XS8135.xml
deleted file mode 100644
index 418b9a6c61..0000000000
--- a/docs/Help_Spanish/Topics/XS8135.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8135
-
-XS8135
-
-
-
- Error XS8135
-
- Tuple with {0} elements cannot be converted to type '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8136.xml b/docs/Help_Spanish/Topics/XS8136.xml
deleted file mode 100644
index ca2032da56..0000000000
--- a/docs/Help_Spanish/Topics/XS8136.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8136
-
-XS8136
-
-
-
- Error XS8136
-
- Deconstruction 'var (...)' form disallows a specific type for 'var'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8137.xml b/docs/Help_Spanish/Topics/XS8137.xml
deleted file mode 100644
index d8307c6b9c..0000000000
--- a/docs/Help_Spanish/Topics/XS8137.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8137
-
-XS8137
-
-
-
- Error XS8137
-
- Cannot define a class or member that utilizes tuples because the compiler required type '{0}' cannot be found. Are you missing a reference?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8138.xml b/docs/Help_Spanish/Topics/XS8138.xml
deleted file mode 100644
index e9645a4936..0000000000
--- a/docs/Help_Spanish/Topics/XS8138.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8138
-
-XS8138
-
-
-
- Error XS8138
-
- Cannot reference 'System.Runtime.CompilerServices.TupleElementNamesAttribute' explicitly. Use the tuple syntax to define tuple names.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8139.xml b/docs/Help_Spanish/Topics/XS8139.xml
deleted file mode 100644
index 87cb0742d5..0000000000
--- a/docs/Help_Spanish/Topics/XS8139.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8139
-
-XS8139
-
-
-
- Error XS8139
-
- '{0}': cannot change tuple element names when overriding inherited member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8140.xml b/docs/Help_Spanish/Topics/XS8140.xml
deleted file mode 100644
index 24f1ce584f..0000000000
--- a/docs/Help_Spanish/Topics/XS8140.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8140
-
-XS8140
-
-
-
- Error XS8140
-
- '{0}' is already listed in the interface list on type '{2}' with different tuple element names, as '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8141.xml b/docs/Help_Spanish/Topics/XS8141.xml
deleted file mode 100644
index 90da988f41..0000000000
--- a/docs/Help_Spanish/Topics/XS8141.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8141
-
-XS8141
-
-
-
- Error XS8141
-
- The tuple element names in the signature of method '{0}' must match the tuple element names of interface method '{1}' (including on the return type).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8142.xml b/docs/Help_Spanish/Topics/XS8142.xml
deleted file mode 100644
index d647b91538..0000000000
--- a/docs/Help_Spanish/Topics/XS8142.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8142
-
-XS8142
-
-
-
- Error XS8142
-
- Both partial method declarations, '{0}' and '{1}', must use the same tuple element names.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8143.xml b/docs/Help_Spanish/Topics/XS8143.xml
deleted file mode 100644
index 9444a78c09..0000000000
--- a/docs/Help_Spanish/Topics/XS8143.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8143
-
-XS8143
-
-
-
- Error XS8143
-
- An expression tree may not contain a tuple literal.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8144.xml b/docs/Help_Spanish/Topics/XS8144.xml
deleted file mode 100644
index c096ac0aad..0000000000
--- a/docs/Help_Spanish/Topics/XS8144.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8144
-
-XS8144
-
-
-
- Error XS8144
-
- An expression tree may not contain a tuple conversion.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8145.xml b/docs/Help_Spanish/Topics/XS8145.xml
deleted file mode 100644
index 77ba4e912d..0000000000
--- a/docs/Help_Spanish/Topics/XS8145.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8145
-
-XS8145
-
-
-
- Error XS8145
-
- Auto-implemented properties cannot return by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8146.xml b/docs/Help_Spanish/Topics/XS8146.xml
deleted file mode 100644
index c1bedc3ec0..0000000000
--- a/docs/Help_Spanish/Topics/XS8146.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8146
-
-XS8146
-
-
-
- Error XS8146
-
- Properties which return by reference must have a get accessor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8147.xml b/docs/Help_Spanish/Topics/XS8147.xml
deleted file mode 100644
index 2a344e7434..0000000000
--- a/docs/Help_Spanish/Topics/XS8147.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8147
-
-XS8147
-
-
-
- Error XS8147
-
- Properties which return by reference cannot have set accessors
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8148.xml b/docs/Help_Spanish/Topics/XS8148.xml
deleted file mode 100644
index e36b77688a..0000000000
--- a/docs/Help_Spanish/Topics/XS8148.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8148
-
-XS8148
-
-
-
- Error XS8148
-
- '{0}' must {2}return by reference to match overridden member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8149.xml b/docs/Help_Spanish/Topics/XS8149.xml
deleted file mode 100644
index 5cbabf0e4c..0000000000
--- a/docs/Help_Spanish/Topics/XS8149.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8149
-
-XS8149
-
-
-
- Error XS8149
-
- By-reference returns may only be used in methods that return by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8150.xml b/docs/Help_Spanish/Topics/XS8150.xml
deleted file mode 100644
index 7331adbf97..0000000000
--- a/docs/Help_Spanish/Topics/XS8150.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8150
-
-XS8150
-
-
-
- Error XS8150
-
- By-value returns may only be used in methods that return by value
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8151.xml b/docs/Help_Spanish/Topics/XS8151.xml
deleted file mode 100644
index db66c85762..0000000000
--- a/docs/Help_Spanish/Topics/XS8151.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8151
-
-XS8151
-
-
-
- Error XS8151
-
- The return expression must be of type '{0}' because this method returns by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8152.xml b/docs/Help_Spanish/Topics/XS8152.xml
deleted file mode 100644
index 13b57b052f..0000000000
--- a/docs/Help_Spanish/Topics/XS8152.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8152
-
-XS8152
-
-
-
- Error XS8152
-
- '{0}' does not implement interface member '{1}'. '{2}' cannot implement '{1}' because it does not return by {3}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8153.xml b/docs/Help_Spanish/Topics/XS8153.xml
deleted file mode 100644
index d812978935..0000000000
--- a/docs/Help_Spanish/Topics/XS8153.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8153
-
-XS8153
-
-
-
- Error XS8153
-
- An expression tree lambda may not contain a call to a method, property, or indexer that returns by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8154.xml b/docs/Help_Spanish/Topics/XS8154.xml
deleted file mode 100644
index c59acd47c8..0000000000
--- a/docs/Help_Spanish/Topics/XS8154.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8154
-
-XS8154
-
-
-
- Error XS8154
-
- The body of '{0}' cannot be an iterator block because '{0}' returns by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8155.xml b/docs/Help_Spanish/Topics/XS8155.xml
deleted file mode 100644
index 081a70e1e5..0000000000
--- a/docs/Help_Spanish/Topics/XS8155.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8155
-
-XS8155
-
-
-
- Error XS8155
-
- Lambda expressions that return by reference cannot be converted to expression trees
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8156.xml b/docs/Help_Spanish/Topics/XS8156.xml
deleted file mode 100644
index e9d85d3cee..0000000000
--- a/docs/Help_Spanish/Topics/XS8156.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8156
-
-XS8156
-
-
-
- Error XS8156
-
- An expression cannot be used in this context because it may not be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8157.xml b/docs/Help_Spanish/Topics/XS8157.xml
deleted file mode 100644
index 483b8f9309..0000000000
--- a/docs/Help_Spanish/Topics/XS8157.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8157
-
-XS8157
-
-
-
- Error XS8157
-
- Cannot return '{0}' by reference because it was initialized to a value that cannot be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8158.xml b/docs/Help_Spanish/Topics/XS8158.xml
deleted file mode 100644
index b719ae89f9..0000000000
--- a/docs/Help_Spanish/Topics/XS8158.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8158
-
-XS8158
-
-
-
- Error XS8158
-
- Cannot return by reference a member of '{0}' because it was initialized to a value that cannot be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8159.xml b/docs/Help_Spanish/Topics/XS8159.xml
deleted file mode 100644
index 47e861f498..0000000000
--- a/docs/Help_Spanish/Topics/XS8159.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8159
-
-XS8159
-
-
-
- Error XS8159
-
- Cannot return the range variable '{0}' by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8160.xml b/docs/Help_Spanish/Topics/XS8160.xml
deleted file mode 100644
index 8aab9ddf00..0000000000
--- a/docs/Help_Spanish/Topics/XS8160.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8160
-
-XS8160
-
-
-
- Error XS8160
-
- A readonly field cannot be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8161.xml b/docs/Help_Spanish/Topics/XS8161.xml
deleted file mode 100644
index e21ad60868..0000000000
--- a/docs/Help_Spanish/Topics/XS8161.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8161
-
-XS8161
-
-
-
- Error XS8161
-
- A static readonly field cannot be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8162.xml b/docs/Help_Spanish/Topics/XS8162.xml
deleted file mode 100644
index d17987c719..0000000000
--- a/docs/Help_Spanish/Topics/XS8162.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8162
-
-XS8162
-
-
-
- Error XS8162
-
- Members of readonly field '{0}' cannot be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8163.xml b/docs/Help_Spanish/Topics/XS8163.xml
deleted file mode 100644
index 8a8b032bf1..0000000000
--- a/docs/Help_Spanish/Topics/XS8163.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8163
-
-XS8163
-
-
-
- Error XS8163
-
- Fields of static readonly field '{0}' cannot be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8164.xml b/docs/Help_Spanish/Topics/XS8164.xml
deleted file mode 100644
index f7477133a7..0000000000
--- a/docs/Help_Spanish/Topics/XS8164.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8164
-
-XS8164
-
-
-
- Error XS8164
-
- Cannot return by reference a result of '{0}' because the argument passed to parameter '{1}' cannot be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8165.xml b/docs/Help_Spanish/Topics/XS8165.xml
deleted file mode 100644
index 336edfa2e5..0000000000
--- a/docs/Help_Spanish/Topics/XS8165.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8165
-
-XS8165
-
-
-
- Error XS8165
-
- Cannot return by reference a member of result of '{0}' because the argument passed to parameter '{1}' cannot be returned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8166.xml b/docs/Help_Spanish/Topics/XS8166.xml
deleted file mode 100644
index 707480c23e..0000000000
--- a/docs/Help_Spanish/Topics/XS8166.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8166
-
-XS8166
-
-
-
- Error XS8166
-
- Cannot return a parameter by reference '{0}' because it is not a ref or out parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8167.xml b/docs/Help_Spanish/Topics/XS8167.xml
deleted file mode 100644
index e9c6d22dbd..0000000000
--- a/docs/Help_Spanish/Topics/XS8167.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8167
-
-XS8167
-
-
-
- Error XS8167
-
- Cannot return or a member of parameter '{0}' by reference because it is not a ref or out parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8168.xml b/docs/Help_Spanish/Topics/XS8168.xml
deleted file mode 100644
index 3e760f1419..0000000000
--- a/docs/Help_Spanish/Topics/XS8168.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8168
-
-XS8168
-
-
-
- Error XS8168
-
- Cannot return local '{0}' by reference because it is not a ref local
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8169.xml b/docs/Help_Spanish/Topics/XS8169.xml
deleted file mode 100644
index 03915aec9b..0000000000
--- a/docs/Help_Spanish/Topics/XS8169.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8169
-
-XS8169
-
-
-
- Error XS8169
-
- Cannot return a member of local '{0}' by reference because it is not a ref local
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8170.xml b/docs/Help_Spanish/Topics/XS8170.xml
deleted file mode 100644
index c1bf80c943..0000000000
--- a/docs/Help_Spanish/Topics/XS8170.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8170
-
-XS8170
-
-
-
- Error XS8170
-
- Struct members cannot return 'this' or other instance members by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8171.xml b/docs/Help_Spanish/Topics/XS8171.xml
deleted file mode 100644
index 83381d8a3f..0000000000
--- a/docs/Help_Spanish/Topics/XS8171.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8171
-
-XS8171
-
-
-
- Error XS8171
-
- Cannot initialize a by-value variable with a reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8172.xml b/docs/Help_Spanish/Topics/XS8172.xml
deleted file mode 100644
index 9be98a9d8f..0000000000
--- a/docs/Help_Spanish/Topics/XS8172.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8172
-
-XS8172
-
-
-
- Error XS8172
-
- Cannot initialize a by-reference variable with a value
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8173.xml b/docs/Help_Spanish/Topics/XS8173.xml
deleted file mode 100644
index 2857babf3e..0000000000
--- a/docs/Help_Spanish/Topics/XS8173.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8173
-
-XS8173
-
-
-
- Error XS8173
-
- The expression must be of type '{0}' because it is being assigned by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8174.xml b/docs/Help_Spanish/Topics/XS8174.xml
deleted file mode 100644
index a6ba5cc05b..0000000000
--- a/docs/Help_Spanish/Topics/XS8174.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8174
-
-XS8174
-
-
-
- Error XS8174
-
- A declaration of a by-reference variable must have an initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8175.xml b/docs/Help_Spanish/Topics/XS8175.xml
deleted file mode 100644
index 1a3a4e3cd4..0000000000
--- a/docs/Help_Spanish/Topics/XS8175.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8175
-
-XS8175
-
-
-
- Error XS8175
-
- Cannot use ref local '{0}' inside an anonymous method, lambda expression, or query expression
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8176.xml b/docs/Help_Spanish/Topics/XS8176.xml
deleted file mode 100644
index ed59337c02..0000000000
--- a/docs/Help_Spanish/Topics/XS8176.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8176
-
-XS8176
-
-
-
- Error XS8176
-
- Iterators cannot have by reference locals
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8177.xml b/docs/Help_Spanish/Topics/XS8177.xml
deleted file mode 100644
index 5ad9b12976..0000000000
--- a/docs/Help_Spanish/Topics/XS8177.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8177
-
-XS8177
-
-
-
- Error XS8177
-
- Async methods cannot have by reference locals
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8178.xml b/docs/Help_Spanish/Topics/XS8178.xml
deleted file mode 100644
index a891afe660..0000000000
--- a/docs/Help_Spanish/Topics/XS8178.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8178
-
-XS8178
-
-
-
- Error XS8178
-
- 'await' cannot be used in an expression containing a call to '{0}' because it returns by reference
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8179.xml b/docs/Help_Spanish/Topics/XS8179.xml
deleted file mode 100644
index 8b060c8366..0000000000
--- a/docs/Help_Spanish/Topics/XS8179.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8179
-
-XS8179
-
-
-
- Error XS8179
-
- Predefined type '{0}' is not defined or imported
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8180.xml b/docs/Help_Spanish/Topics/XS8180.xml
deleted file mode 100644
index 7978e0b655..0000000000
--- a/docs/Help_Spanish/Topics/XS8180.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8180
-
-XS8180
-
-
-
- Error XS8180
-
- { or ; or => expected
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8181.xml b/docs/Help_Spanish/Topics/XS8181.xml
deleted file mode 100644
index bdaf886dfe..0000000000
--- a/docs/Help_Spanish/Topics/XS8181.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8181
-
-XS8181
-
-
-
- Error XS8181
-
- 'new' cannot be used with tuple type. Use a tuple literal expression instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8182.xml b/docs/Help_Spanish/Topics/XS8182.xml
deleted file mode 100644
index 6d0606af0f..0000000000
--- a/docs/Help_Spanish/Topics/XS8182.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8182
-
-XS8182
-
-
-
- Error XS8182
-
- Predefined type '{0}' must be a struct.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8183.xml b/docs/Help_Spanish/Topics/XS8183.xml
deleted file mode 100644
index 7433ac8c51..0000000000
--- a/docs/Help_Spanish/Topics/XS8183.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8183
-
-XS8183
-
-
-
- Error XS8183
-
- Cannot infer the type of implicitly-typed discard.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8184.xml b/docs/Help_Spanish/Topics/XS8184.xml
deleted file mode 100644
index 30f0d369d9..0000000000
--- a/docs/Help_Spanish/Topics/XS8184.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8184
-
-XS8184
-
-
-
- Error XS8184
-
- A deconstruction cannot mix declarations and expressions on the left-hand-side.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8185.xml b/docs/Help_Spanish/Topics/XS8185.xml
deleted file mode 100644
index 02589b78ef..0000000000
--- a/docs/Help_Spanish/Topics/XS8185.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8185
-
-XS8185
-
-
-
- Error XS8185
-
- A declaration is not allowed in this context.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8186.xml b/docs/Help_Spanish/Topics/XS8186.xml
deleted file mode 100644
index 700f072668..0000000000
--- a/docs/Help_Spanish/Topics/XS8186.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8186
-
-XS8186
-
-
-
- Error XS8186
-
- A foreach loop must declare its iteration variables.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8187.xml b/docs/Help_Spanish/Topics/XS8187.xml
deleted file mode 100644
index 2376cc4760..0000000000
--- a/docs/Help_Spanish/Topics/XS8187.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8187
-
-XS8187
-
-
-
- Error XS8187
-
- Tuple element names are not permitted on the left of a deconstruction.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8188.xml b/docs/Help_Spanish/Topics/XS8188.xml
deleted file mode 100644
index 2f2e7de164..0000000000
--- a/docs/Help_Spanish/Topics/XS8188.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8188
-
-XS8188
-
-
-
- Error XS8188
-
- An expression tree may not contain a throw-expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8189.xml b/docs/Help_Spanish/Topics/XS8189.xml
deleted file mode 100644
index fa430f6de6..0000000000
--- a/docs/Help_Spanish/Topics/XS8189.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8189
-
-XS8189
-
-
-
- Error XS8189
-
- Ref mismatch between '{0}' and delegate '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8190.XML b/docs/Help_Spanish/Topics/XS8190.XML
deleted file mode 100644
index b6b3d09502..0000000000
--- a/docs/Help_Spanish/Topics/XS8190.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8190
-
-XS8190
-
-
-
- Error XS8190
-
- Provided source code kind is unsupported or invalid: '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8191.XML b/docs/Help_Spanish/Topics/XS8191.XML
deleted file mode 100644
index ffe0f86dcd..0000000000
--- a/docs/Help_Spanish/Topics/XS8191.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8191
-
-XS8191
-
-
-
- Error XS8191
-
- Provided documentation mode is unsupported or invalid: '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8192.XML b/docs/Help_Spanish/Topics/XS8192.XML
deleted file mode 100644
index 9bb055557b..0000000000
--- a/docs/Help_Spanish/Topics/XS8192.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8192
-
-XS8192
-
-
-
- Error XS8192
-
- Provided language version is unsupported or invalid: '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8196.xml b/docs/Help_Spanish/Topics/XS8196.xml
deleted file mode 100644
index 10734bb730..0000000000
--- a/docs/Help_Spanish/Topics/XS8196.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8196
-
-XS8196
-
-
-
- Error XS8196
-
- Reference to an implicitly-typed out variable '{0}' is not permitted in the same argument list.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8197.xml b/docs/Help_Spanish/Topics/XS8197.xml
deleted file mode 100644
index 7fce9d00aa..0000000000
--- a/docs/Help_Spanish/Topics/XS8197.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8197
-
-XS8197
-
-
-
- Error XS8197
-
- Cannot infer the type of implicitly-typed out variable '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8198.xml b/docs/Help_Spanish/Topics/XS8198.xml
deleted file mode 100644
index d441f12a9a..0000000000
--- a/docs/Help_Spanish/Topics/XS8198.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8198
-
-XS8198
-
-
-
- Error XS8198
-
- An expression tree may not contain an out argument variable declaration.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8199.xml b/docs/Help_Spanish/Topics/XS8199.xml
deleted file mode 100644
index 0fc57a456a..0000000000
--- a/docs/Help_Spanish/Topics/XS8199.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8199
-
-XS8199
-
-
-
- Error XS8199
-
- The syntax 'var (...)' as an lvalue is reserved.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8200.xml b/docs/Help_Spanish/Topics/XS8200.xml
deleted file mode 100644
index 2f2112bc35..0000000000
--- a/docs/Help_Spanish/Topics/XS8200.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8200
-
-XS8200
-
-
-
- Error XS8200
-
- Out variable and pattern variable declarations are not allowed within constructor initializers, field initializers, or property initializers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8201.xml b/docs/Help_Spanish/Topics/XS8201.xml
deleted file mode 100644
index 1a86c7fbef..0000000000
--- a/docs/Help_Spanish/Topics/XS8201.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8201
-
-XS8201
-
-
-
- Error XS8201
-
- Out variable and pattern variable declarations are not allowed within a query clause.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8202.xml b/docs/Help_Spanish/Topics/XS8202.xml
deleted file mode 100644
index ab996ca2d2..0000000000
--- a/docs/Help_Spanish/Topics/XS8202.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8202
-
-XS8202
-
-
-
- Error XS8202
-
- Public signing is not supported for netmodules.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8203.xml b/docs/Help_Spanish/Topics/XS8203.xml
deleted file mode 100644
index 5e4733c438..0000000000
--- a/docs/Help_Spanish/Topics/XS8203.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8203
-
-XS8203
-
-
-
- Error XS8203
-
- Invalid assembly name: {0}
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8204.xml b/docs/Help_Spanish/Topics/XS8204.xml
deleted file mode 100644
index 69af2c8e9a..0000000000
--- a/docs/Help_Spanish/Topics/XS8204.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS8204
-
-XS8204
-
-
-
- Error XS8204
-
- Attributes are not allowed on local function parameters or type parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8205.XML b/docs/Help_Spanish/Topics/XS8205.XML
deleted file mode 100644
index 91ac98f301..0000000000
--- a/docs/Help_Spanish/Topics/XS8205.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8205
-
-XS8205
-
-
-
- Error XS8205
-
- Attributes are not allowed on local function parameters or type parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8206.XML b/docs/Help_Spanish/Topics/XS8206.XML
deleted file mode 100644
index ceb02695b6..0000000000
--- a/docs/Help_Spanish/Topics/XS8206.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8206
-
-XS8206
-
-
-
- Error XS8206
-
- Module '{0}' in assembly '{1}' is forwarding the type '{2}' to multiple assemblies: '{3}' and '{4}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8207.XML b/docs/Help_Spanish/Topics/XS8207.XML
deleted file mode 100644
index f31ef9199c..0000000000
--- a/docs/Help_Spanish/Topics/XS8207.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8207
-
-XS8207
-
-
-
- Error XS8207
-
- An expression tree may not contain a discard.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8208.XML b/docs/Help_Spanish/Topics/XS8208.XML
deleted file mode 100644
index 0e9703bbfb..0000000000
--- a/docs/Help_Spanish/Topics/XS8208.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8208
-
-XS8208
-
-
-
- Error XS8208
-
- It is not legal to use the type 'dynamic' in a pattern.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8209.XML b/docs/Help_Spanish/Topics/XS8209.XML
deleted file mode 100644
index 0613d189f2..0000000000
--- a/docs/Help_Spanish/Topics/XS8209.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8209
-
-XS8209
-
-
-
- Error XS8209
-
- A value of type 'void' may not be assigned.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8210.XML b/docs/Help_Spanish/Topics/XS8210.XML
deleted file mode 100644
index 2ac693aa18..0000000000
--- a/docs/Help_Spanish/Topics/XS8210.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8210
-
-XS8210
-
-
-
- Error XS8210
-
- A tuple may not contain a value of type 'void'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8300.XML b/docs/Help_Spanish/Topics/XS8300.XML
deleted file mode 100644
index e1b4e751d4..0000000000
--- a/docs/Help_Spanish/Topics/XS8300.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8300
-
-XS8300
-
-
-
- Error XS8300
-
- Merge conflict marker encountered
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8301.XML b/docs/Help_Spanish/Topics/XS8301.XML
deleted file mode 100644
index e584fa515c..0000000000
--- a/docs/Help_Spanish/Topics/XS8301.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8301
-
-XS8301
-
-
-
- Error XS8301
-
- Invalid name for a preprocessing symbol; '{0}' is not a valid identifier
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8302.XML b/docs/Help_Spanish/Topics/XS8302.XML
deleted file mode 100644
index 51db41b5b6..0000000000
--- a/docs/Help_Spanish/Topics/XS8302.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8302
-
-XS8302
-
-
-
- Error XS8302
-
- Feature '{0}' is not available in X# 7.1. Please use language version {1} or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8303.XML b/docs/Help_Spanish/Topics/XS8303.XML
deleted file mode 100644
index 4dad39a485..0000000000
--- a/docs/Help_Spanish/Topics/XS8303.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8303
-
-XS8303
-
-
-
- Error XS8303
-
- Specified language version '{0}' cannot have leading zeroes
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8304.XML b/docs/Help_Spanish/Topics/XS8304.XML
deleted file mode 100644
index 6c9ad43537..0000000000
--- a/docs/Help_Spanish/Topics/XS8304.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8304
-
-XS8304
-
-
-
- Error XS8304
-
- Compiler version: '{0}'. Language version: {1}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8305.XML b/docs/Help_Spanish/Topics/XS8305.XML
deleted file mode 100644
index 33d2840950..0000000000
--- a/docs/Help_Spanish/Topics/XS8305.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8305
-
-XS8305
-
-
-
- Warning XS8305
-
- '{0}' is for evaluation purposes only and is subject to change or removal in future updates.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8306.XML b/docs/Help_Spanish/Topics/XS8306.XML
deleted file mode 100644
index 210a91dee6..0000000000
--- a/docs/Help_Spanish/Topics/XS8306.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8306
-
-XS8306
-
-
-
- Error XS8306
-
- Tuple element name '{0}' is inferred. Please use language version {1} or greater to access an element by its inferred name.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8307.XML b/docs/Help_Spanish/Topics/XS8307.XML
deleted file mode 100644
index e6402bc12c..0000000000
--- a/docs/Help_Spanish/Topics/XS8307.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8307
-
-XS8307
-
-
-
- Error XS8307
-
- The first operand of an 'as' operator may not be a tuple literal without a natural type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8308.XML b/docs/Help_Spanish/Topics/XS8308.XML
deleted file mode 100644
index b6fbd216df..0000000000
--- a/docs/Help_Spanish/Topics/XS8308.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8308
-
-XS8308
-
-
-
- Error XS8308
-
- Do not use refout when using refonly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8309.XML b/docs/Help_Spanish/Topics/XS8309.XML
deleted file mode 100644
index 97aa6502f4..0000000000
--- a/docs/Help_Spanish/Topics/XS8309.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8309
-
-XS8309
-
-
-
- Error XS8309
-
- Cannot compile net modules when using /refout or /refonly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8310.XML b/docs/Help_Spanish/Topics/XS8310.XML
deleted file mode 100644
index 38d208c914..0000000000
--- a/docs/Help_Spanish/Topics/XS8310.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8310
-
-XS8310
-
-
-
- Error XS8310
-
- Operator '{0}' cannot be applied to operand '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8311.XML b/docs/Help_Spanish/Topics/XS8311.XML
deleted file mode 100644
index ba08c8c1dd..0000000000
--- a/docs/Help_Spanish/Topics/XS8311.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8311
-
-XS8311
-
-
-
- Error XS8311
-
- Cannot use a default literal as an argument to a dynamically dispatched operation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8312.XML b/docs/Help_Spanish/Topics/XS8312.XML
deleted file mode 100644
index 15b6035ce3..0000000000
--- a/docs/Help_Spanish/Topics/XS8312.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8312
-
-XS8312
-
-
-
- Error XS8312
-
- Use of default literal is not valid in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8313.XML b/docs/Help_Spanish/Topics/XS8313.XML
deleted file mode 100644
index 47a0c3a088..0000000000
--- a/docs/Help_Spanish/Topics/XS8313.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8313
-
-XS8313
-
-
-
- Error XS8313
-
- A default literal 'default' is not valid as a case constant. Use another literal (e.g. '0' or 'null') as appropriate. If you intended to write the default label, use 'default:' without 'case'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8314.XML b/docs/Help_Spanish/Topics/XS8314.XML
deleted file mode 100644
index c67d8bf486..0000000000
--- a/docs/Help_Spanish/Topics/XS8314.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8314
-
-XS8314
-
-
-
- Error XS8314
-
- An expression of type '{0}' cannot be handled by a pattern of type '{1}' in X# {2}. Please use language version {3} or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8315.XML b/docs/Help_Spanish/Topics/XS8315.XML
deleted file mode 100644
index b37a4d30b8..0000000000
--- a/docs/Help_Spanish/Topics/XS8315.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8315
-
-XS8315
-
-
-
- Error XS8315
-
- Operator '{0}' is ambiguous on operands 'default' and 'default'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8320.XML b/docs/Help_Spanish/Topics/XS8320.XML
deleted file mode 100644
index f424a8b0a8..0000000000
--- a/docs/Help_Spanish/Topics/XS8320.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8320
-
-XS8320
-
-
-
- Error XS8320
-
- Feature '{0}' is not available in X# 7.2. Please use language version {1} or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8321.XML b/docs/Help_Spanish/Topics/XS8321.XML
deleted file mode 100644
index 13f97ec7f2..0000000000
--- a/docs/Help_Spanish/Topics/XS8321.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8321
-
-XS8321
-
-
-
- Warning XS8321
-
- The local function '{0}' is declared but never used
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8322.XML b/docs/Help_Spanish/Topics/XS8322.XML
deleted file mode 100644
index 2218c73f13..0000000000
--- a/docs/Help_Spanish/Topics/XS8322.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8322
-
-XS8322
-
-
-
- Error XS8322
-
- Cannot pass argument with dynamic type to generic local function '{0}' with inferred type arguments.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8323.XML b/docs/Help_Spanish/Topics/XS8323.XML
deleted file mode 100644
index de2d8393ce..0000000000
--- a/docs/Help_Spanish/Topics/XS8323.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8323
-
-XS8323
-
-
-
- Error XS8323
-
- Named argument '{0}' is used out-of-position but is followed by an unnamed argument
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8324.XML b/docs/Help_Spanish/Topics/XS8324.XML
deleted file mode 100644
index a9493a3ef7..0000000000
--- a/docs/Help_Spanish/Topics/XS8324.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8324
-
-XS8324
-
-
-
- Error XS8324
-
- Named argument specifications must appear after all fixed arguments have been specified in a dynamic invocation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8325.XML b/docs/Help_Spanish/Topics/XS8325.XML
deleted file mode 100644
index fad69cb5e3..0000000000
--- a/docs/Help_Spanish/Topics/XS8325.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8325
-
-XS8325
-
-
-
- Error XS8325
-
- 'await' cannot be used in an expression containing a ref conditional operator
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8326.XML b/docs/Help_Spanish/Topics/XS8326.XML
deleted file mode 100644
index b6eee3ab1e..0000000000
--- a/docs/Help_Spanish/Topics/XS8326.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8326
-
-XS8326
-
-
-
- Error XS8326
-
- Both conditional operator values must be ref values or neither may be a ref value
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8327.XML b/docs/Help_Spanish/Topics/XS8327.XML
deleted file mode 100644
index d3088a5ddf..0000000000
--- a/docs/Help_Spanish/Topics/XS8327.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8327
-
-XS8327
-
-
-
- Error XS8327
-
- The expression must be of type '{0}' to match the alternative ref value
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8328.XML b/docs/Help_Spanish/Topics/XS8328.XML
deleted file mode 100644
index 71c4985535..0000000000
--- a/docs/Help_Spanish/Topics/XS8328.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8328
-
-XS8328
-
-
-
- Error XS8328
-
- The parameter modifier '{0}' cannot be used with '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8329.XML b/docs/Help_Spanish/Topics/XS8329.XML
deleted file mode 100644
index e51d9f0b23..0000000000
--- a/docs/Help_Spanish/Topics/XS8329.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8329
-
-XS8329
-
-
-
- Error XS8329
-
- Cannot use {0} '{1}' as a ref or out value because it is a readonly variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8330.XML b/docs/Help_Spanish/Topics/XS8330.XML
deleted file mode 100644
index 3526981a07..0000000000
--- a/docs/Help_Spanish/Topics/XS8330.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8330
-
-XS8330
-
-
-
- Error XS8330
-
- Members of {0} '{1}' cannot be used as a ref or out value because it is a readonly variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8331.XML b/docs/Help_Spanish/Topics/XS8331.XML
deleted file mode 100644
index 41b53c9595..0000000000
--- a/docs/Help_Spanish/Topics/XS8331.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8331
-
-XS8331
-
-
-
- Error XS8331
-
- Cannot assign to {0} '{1}' because it is a readonly variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8332.XML b/docs/Help_Spanish/Topics/XS8332.XML
deleted file mode 100644
index 59e09a6849..0000000000
--- a/docs/Help_Spanish/Topics/XS8332.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8332
-
-XS8332
-
-
-
- Error XS8332
-
- Cannot assign to a member of {0} '{1}' because it is a readonly variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8333.XML b/docs/Help_Spanish/Topics/XS8333.XML
deleted file mode 100644
index edf97865cd..0000000000
--- a/docs/Help_Spanish/Topics/XS8333.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8333
-
-XS8333
-
-
-
- Error XS8333
-
- Cannot return {0} '{1}' by writable reference because it is a readonly variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8334.XML b/docs/Help_Spanish/Topics/XS8334.XML
deleted file mode 100644
index 16cb9263ff..0000000000
--- a/docs/Help_Spanish/Topics/XS8334.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8334
-
-XS8334
-
-
-
- Error XS8334
-
- Members of {0} '{1}' cannot be returned by writable reference because it is a readonly variable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8335.XML b/docs/Help_Spanish/Topics/XS8335.XML
deleted file mode 100644
index 88c46bd04f..0000000000
--- a/docs/Help_Spanish/Topics/XS8335.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8335
-
-XS8335
-
-
-
- Error XS8335
-
- Do not use '{0}'. This is reserved for compiler usage.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8336.XML b/docs/Help_Spanish/Topics/XS8336.XML
deleted file mode 100644
index 26bfdf2222..0000000000
--- a/docs/Help_Spanish/Topics/XS8336.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8336
-
-XS8336
-
-
-
- Error XS8336
-
- The type name '{0}' is reserved to be used by the compiler.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8337.XML b/docs/Help_Spanish/Topics/XS8337.XML
deleted file mode 100644
index 7438bdbe48..0000000000
--- a/docs/Help_Spanish/Topics/XS8337.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8337
-
-XS8337
-
-
-
- Error XS8337
-
- The first parameter of a 'ref' extension method '{0}' must be a value type or a generic type constrained to struct.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8338.XML b/docs/Help_Spanish/Topics/XS8338.XML
deleted file mode 100644
index 67ced41844..0000000000
--- a/docs/Help_Spanish/Topics/XS8338.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8338
-
-XS8338
-
-
-
- Error XS8338
-
- The first parameter of an 'in' extension method '{0}' must be a value type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8340.XML b/docs/Help_Spanish/Topics/XS8340.XML
deleted file mode 100644
index eb93fbe1ef..0000000000
--- a/docs/Help_Spanish/Topics/XS8340.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8340
-
-XS8340
-
-
-
- Error XS8340
-
- Instance fields of readonly structs must be readonly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8341.XML b/docs/Help_Spanish/Topics/XS8341.XML
deleted file mode 100644
index 418173a886..0000000000
--- a/docs/Help_Spanish/Topics/XS8341.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8341
-
-XS8341
-
-
-
- Error XS8341
-
- Auto-implemented instance properties in readonly structs must be readonly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8342.XML b/docs/Help_Spanish/Topics/XS8342.XML
deleted file mode 100644
index 146d15e9e2..0000000000
--- a/docs/Help_Spanish/Topics/XS8342.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8342
-
-XS8342
-
-
-
- Error XS8342
-
- Field-like events are not allowed in readonly structs.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8343.XML b/docs/Help_Spanish/Topics/XS8343.XML
deleted file mode 100644
index 049c6be32d..0000000000
--- a/docs/Help_Spanish/Topics/XS8343.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8343
-
-XS8343
-
-
-
- Error XS8343
-
- '{0}': ref structs cannot implement interfaces
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8344.XML b/docs/Help_Spanish/Topics/XS8344.XML
deleted file mode 100644
index f422458a4a..0000000000
--- a/docs/Help_Spanish/Topics/XS8344.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8344
-
-XS8344
-
-
-
- Error XS8344
-
- foreach statement cannot operate on enumerators of type '{0}' in async or iterator methods because '{0}' is a ref struct.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8345.XML b/docs/Help_Spanish/Topics/XS8345.XML
deleted file mode 100644
index 374c9aa24d..0000000000
--- a/docs/Help_Spanish/Topics/XS8345.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8345
-
-XS8345
-
-
-
- Error XS8345
-
- Field or auto-implemented property cannot be of type '{0}' unless it is an instance member of a ref struct.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8346.XML b/docs/Help_Spanish/Topics/XS8346.XML
deleted file mode 100644
index ca7038842b..0000000000
--- a/docs/Help_Spanish/Topics/XS8346.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8346
-
-XS8346
-
-
-
- Error XS8346
-
- Conversion of a stackalloc expression of type '{0}' to type '{1}' is not possible.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8347.XML b/docs/Help_Spanish/Topics/XS8347.XML
deleted file mode 100644
index 33e138c5d4..0000000000
--- a/docs/Help_Spanish/Topics/XS8347.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8347
-
-XS8347
-
-
-
- Error XS8347
-
- Cannot use a result of '{0}' in this context because it may expose variables referenced by parameter '{1}' outside of their declaration scope
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8348.XML b/docs/Help_Spanish/Topics/XS8348.XML
deleted file mode 100644
index 90ffacec76..0000000000
--- a/docs/Help_Spanish/Topics/XS8348.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8348
-
-XS8348
-
-
-
- Error XS8348
-
- Cannot use a member of result of '{0}' in this context because it may expose variables referenced by parameter '{1}' outside of their declaration scope
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8349.XML b/docs/Help_Spanish/Topics/XS8349.XML
deleted file mode 100644
index 37bdf6a0f0..0000000000
--- a/docs/Help_Spanish/Topics/XS8349.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8349
-
-XS8349
-
-
-
- Error XS8349
-
- Expression cannot be used in this context because it may indirectly expose variables outside of their declaration scope
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8350.XML b/docs/Help_Spanish/Topics/XS8350.XML
deleted file mode 100644
index 883869821a..0000000000
--- a/docs/Help_Spanish/Topics/XS8350.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8350
-
-XS8350
-
-
-
- Error XS8350
-
- This combination of arguments to '{0}' is disallowed because it may expose variables referenced by parameter '{1}' outside of their declaration scope
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8351.XML b/docs/Help_Spanish/Topics/XS8351.XML
deleted file mode 100644
index 127fd771e6..0000000000
--- a/docs/Help_Spanish/Topics/XS8351.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8351
-
-XS8351
-
-
-
- Error XS8351
-
- Branches of a ref ternary operator cannot refer to variables with incompatible declaration scopes
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8352.XML b/docs/Help_Spanish/Topics/XS8352.XML
deleted file mode 100644
index e72e3ebbc0..0000000000
--- a/docs/Help_Spanish/Topics/XS8352.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8352
-
-XS8352
-
-
-
- Error XS8352
-
- Cannot use local '{0}' in this context because it may expose referenced variables outside of their declaration scope
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8353.XML b/docs/Help_Spanish/Topics/XS8353.XML
deleted file mode 100644
index 365dbcd27d..0000000000
--- a/docs/Help_Spanish/Topics/XS8353.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8353
-
-XS8353
-
-
-
- Error XS8353
-
- A result of a stackalloc expression of type '{0}' cannot be used in this context because it may be exposed outside of the containing method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8354.XML b/docs/Help_Spanish/Topics/XS8354.XML
deleted file mode 100644
index 592d2199f9..0000000000
--- a/docs/Help_Spanish/Topics/XS8354.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8354
-
-XS8354
-
-
-
- Error XS8354
-
- Cannot return 'SELF' by reference.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8355.XML b/docs/Help_Spanish/Topics/XS8355.XML
deleted file mode 100644
index 56e961c966..0000000000
--- a/docs/Help_Spanish/Topics/XS8355.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8355
-
-XS8355
-
-
-
- Error XS8355
-
- An in parameter cannot have the Out attribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8356.XML b/docs/Help_Spanish/Topics/XS8356.XML
deleted file mode 100644
index 419efd3ee4..0000000000
--- a/docs/Help_Spanish/Topics/XS8356.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8356
-
-XS8356
-
-
-
- Error XS8356
-
- Predefined type '{0}' is declared in multiple referenced assemblies: '{1}' and '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8357.XML b/docs/Help_Spanish/Topics/XS8357.XML
deleted file mode 100644
index 804275d771..0000000000
--- a/docs/Help_Spanish/Topics/XS8357.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8357
-
-XS8357
-
-
-
- Error XS8357
-
- The specified version string contains wildcards, which are not compatible with determinism. Either remove wildcards from the version string, or disable determinism for this compilation
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8358.XML b/docs/Help_Spanish/Topics/XS8358.XML
deleted file mode 100644
index 402e5a2691..0000000000
--- a/docs/Help_Spanish/Topics/XS8358.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8358
-
-XS8358
-
-
-
- Error XS8358
-
- Cannot use attribute constructor '{0}' because it is has 'in' parameters.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8359.XML b/docs/Help_Spanish/Topics/XS8359.XML
deleted file mode 100644
index 585feb99f8..0000000000
--- a/docs/Help_Spanish/Topics/XS8359.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8359
-
-XS8359
-
-
-
- Warning XS8359
-
- Filter expression is a constant 'false', consider removing the catch clause
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8360.XML b/docs/Help_Spanish/Topics/XS8360.XML
deleted file mode 100644
index 306f16e3b9..0000000000
--- a/docs/Help_Spanish/Topics/XS8360.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8360
-
-XS8360
-
-
-
- Warning XS8360
-
- Filter expression is a constant 'false', consider removing the try-catch block
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8361.XML b/docs/Help_Spanish/Topics/XS8361.XML
deleted file mode 100644
index c350903233..0000000000
--- a/docs/Help_Spanish/Topics/XS8361.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8361
-
-XS8361
-
-
-
- Error XS8361
-
- A conditional expression cannot be used directly in a string interpolation because the ':' ends the interpolation. Parenthesize the conditional expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8362.XML b/docs/Help_Spanish/Topics/XS8362.XML
deleted file mode 100644
index ac1d5cee06..0000000000
--- a/docs/Help_Spanish/Topics/XS8362.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8362
-
-XS8362
-
-
-
- Error XS8362
-
- __arglist cannot have an argument of void type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8363.XML b/docs/Help_Spanish/Topics/XS8363.XML
deleted file mode 100644
index 3ebb8820ec..0000000000
--- a/docs/Help_Spanish/Topics/XS8363.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8363
-
-XS8363
-
-
-
- Error XS8363
-
- A default literal 'default' is not valid as a pattern. Use another literal (e.g. '0' or 'null') as appropriate. To match everything, use a discard pattern 'var _'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8364.XML b/docs/Help_Spanish/Topics/XS8364.XML
deleted file mode 100644
index 9926e04a54..0000000000
--- a/docs/Help_Spanish/Topics/XS8364.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8364
-
-XS8364
-
-
-
- Error XS8364
-
- Arguments with 'in' modifier cannot be used in dynamically dispatched expessions.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8370.XML b/docs/Help_Spanish/Topics/XS8370.XML
deleted file mode 100644
index 5c88d5d97a..0000000000
--- a/docs/Help_Spanish/Topics/XS8370.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8370
-
-XS8370
-
-
-
- Error XS8370
-
- Feature '{0}' is not available in X# 7.3. Please use language version {1} or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8371.XML b/docs/Help_Spanish/Topics/XS8371.XML
deleted file mode 100644
index e501f817f0..0000000000
--- a/docs/Help_Spanish/Topics/XS8371.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8371
-
-XS8371
-
-
-
- Warning XS8371
-
- Field-targeted attributes on auto-properties are not supported in language version {0}. Please use language version {1} or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8372.XML b/docs/Help_Spanish/Topics/XS8372.XML
deleted file mode 100644
index aaf09a3ce0..0000000000
--- a/docs/Help_Spanish/Topics/XS8372.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8372
-
-XS8372
-
-
-
- Error XS8372
-
- Do not use 'System.Runtime.CompilerServices.FixedBuffer' attribute on a property
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8373.XML b/docs/Help_Spanish/Topics/XS8373.XML
deleted file mode 100644
index f24e45c80c..0000000000
--- a/docs/Help_Spanish/Topics/XS8373.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8373
-
-XS8373
-
-
-
- Error XS8373
-
- The left-hand side of a ref assignment must be a ref local or parameter.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8374.XML b/docs/Help_Spanish/Topics/XS8374.XML
deleted file mode 100644
index 86a91f784e..0000000000
--- a/docs/Help_Spanish/Topics/XS8374.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8374
-
-XS8374
-
-
-
- Error XS8374
-
- Cannot ref-assign '{1}' to '{0}' because '{1}' has a narrower escape scope than '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8375.XML b/docs/Help_Spanish/Topics/XS8375.XML
deleted file mode 100644
index eac8068a2b..0000000000
--- a/docs/Help_Spanish/Topics/XS8375.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8375
-
-XS8375
-
-
-
- Error XS8375
-
- The 'new()' constraint cannot be used with the 'unmanaged' constraint
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8376.XML b/docs/Help_Spanish/Topics/XS8376.XML
deleted file mode 100644
index e9f24b87bd..0000000000
--- a/docs/Help_Spanish/Topics/XS8376.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8376
-
-XS8376
-
-
-
- Error XS8376
-
- The 'unmanaged' constraint must come before any other constraints
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8377.XML b/docs/Help_Spanish/Topics/XS8377.XML
deleted file mode 100644
index 36944d4d1f..0000000000
--- a/docs/Help_Spanish/Topics/XS8377.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8377
-
-XS8377
-
-
-
- Error XS8377
-
- The type '{2}' must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter '{1}' in the generic type or method '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8378.XML b/docs/Help_Spanish/Topics/XS8378.XML
deleted file mode 100644
index 7365527335..0000000000
--- a/docs/Help_Spanish/Topics/XS8378.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8378
-
-XS8378
-
-
-
- Error XS8378
-
- __arglist cannot have an argument passed by 'in' or 'out'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8379.XML b/docs/Help_Spanish/Topics/XS8379.XML
deleted file mode 100644
index 9da53cf9a3..0000000000
--- a/docs/Help_Spanish/Topics/XS8379.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8379
-
-XS8379
-
-
-
- Error XS8379
-
- Type parameter '{1}' has the 'unmanaged' constraint so '{1}' cannot be used as a constraint for '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8380.XML b/docs/Help_Spanish/Topics/XS8380.XML
deleted file mode 100644
index 2b8ac71d10..0000000000
--- a/docs/Help_Spanish/Topics/XS8380.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8380
-
-XS8380
-
-
-
- Error XS8380
-
- '{0}': cannot specify both a constraint class and the 'unmanaged' constraint
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8381.XML b/docs/Help_Spanish/Topics/XS8381.XML
deleted file mode 100644
index e389c84f8c..0000000000
--- a/docs/Help_Spanish/Topics/XS8381.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8381
-
-XS8381
-
-
-
- Error XS8381
-
- "Invalid rank specifier: expected ']'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8382.XML b/docs/Help_Spanish/Topics/XS8382.XML
deleted file mode 100644
index 4a1bfa9269..0000000000
--- a/docs/Help_Spanish/Topics/XS8382.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8382
-
-XS8382
-
-
-
- Error XS8382
-
- An expression tree may not contain a tuple == or != operator
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8383.XML b/docs/Help_Spanish/Topics/XS8383.XML
deleted file mode 100644
index 896408a4e9..0000000000
--- a/docs/Help_Spanish/Topics/XS8383.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8383
-
-XS8383
-
-
-
- Warning XS8383
-
- The tuple element name '{0}' is ignored because a different name or no name is specified on the other side of the tuple == or != operator.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8384.XML b/docs/Help_Spanish/Topics/XS8384.XML
deleted file mode 100644
index 804b30dcff..0000000000
--- a/docs/Help_Spanish/Topics/XS8384.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8384
-
-XS8384
-
-
-
- Error XS8384
-
- Tuple types used as operands of an == or != operator must have matching cardinalities. But this operator has tuple types of cardinality {0} on the left and {1} on the right.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8385.XML b/docs/Help_Spanish/Topics/XS8385.XML
deleted file mode 100644
index 21c2c43b8d..0000000000
--- a/docs/Help_Spanish/Topics/XS8385.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8385
-
-XS8385
-
-
-
- Error XS8385
-
- The given expression cannot be used in a fixed statement
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8386.XML b/docs/Help_Spanish/Topics/XS8386.XML
deleted file mode 100644
index 0cb3a7f96c..0000000000
--- a/docs/Help_Spanish/Topics/XS8386.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8386
-
-XS8386
-
-
-
- Error XS8386
-
- Invalid object creation
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8387.XML b/docs/Help_Spanish/Topics/XS8387.XML
deleted file mode 100644
index f28781affd..0000000000
--- a/docs/Help_Spanish/Topics/XS8387.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8387
-
-XS8387
-
-
-
- Warning XS8387
-
- Type parameter '{0}' has the same name as the type parameter from outer method '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8388.XML b/docs/Help_Spanish/Topics/XS8388.XML
deleted file mode 100644
index 8cac311448..0000000000
--- a/docs/Help_Spanish/Topics/XS8388.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8388
-
-XS8388
-
-
-
- Error XS8388
-
- An out variable cannot be declared as a ref local
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8389.XML b/docs/Help_Spanish/Topics/XS8389.XML
deleted file mode 100644
index 4bb273e9ce..0000000000
--- a/docs/Help_Spanish/Topics/XS8389.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8389
-
-XS8389
-
-
-
- Error XS8389
-
- Omitting the type argument is not allowed in the current context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8400.XML b/docs/Help_Spanish/Topics/XS8400.XML
deleted file mode 100644
index c5eb3bd256..0000000000
--- a/docs/Help_Spanish/Topics/XS8400.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8400
-
-XS8400
-
-
-
- Error XS8400
-
- Feature '{0}' is not available in X# 8.0. Please use language version {1} or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8401.XML b/docs/Help_Spanish/Topics/XS8401.XML
deleted file mode 100644
index e308d19aad..0000000000
--- a/docs/Help_Spanish/Topics/XS8401.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8401
-
-XS8401
-
-
-
- Error XS8401
-
- To use '@$' instead of '$@' for an interpolated verbatim string, please use language version '{0}' or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8403.XML b/docs/Help_Spanish/Topics/XS8403.XML
deleted file mode 100644
index bbba298554..0000000000
--- a/docs/Help_Spanish/Topics/XS8403.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8403
-
-XS8403
-
-
-
- Error XS8403
-
- Method '{0}' with an iterator block must be 'async' to return '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8410.XML b/docs/Help_Spanish/Topics/XS8410.XML
deleted file mode 100644
index 9b07a22727..0000000000
--- a/docs/Help_Spanish/Topics/XS8410.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8410
-
-XS8410
-
-
-
- Error XS8410
-
- '{0}': type used in an asynchronous using statement must be implicitly convertible to 'System.IAsyncDisposable' or implement a suitable 'DisposeAsync' method.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8411.XML b/docs/Help_Spanish/Topics/XS8411.XML
deleted file mode 100644
index 23fdc325af..0000000000
--- a/docs/Help_Spanish/Topics/XS8411.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8411
-
-XS8411
-
-
-
- Error XS8411
-
- Asynchronous foreach statement cannot operate on variables of type '{0}' because '{0}' does not contain a suitable public instance or extension definition for '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8412.XML b/docs/Help_Spanish/Topics/XS8412.XML
deleted file mode 100644
index df09772691..0000000000
--- a/docs/Help_Spanish/Topics/XS8412.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8412
-
-XS8412
-
-
-
- Error XS8412
-
- Asynchronous foreach requires that the return type '{0}' of '{1}' must have a suitable public 'MoveNextAsync' method and public 'Current' property
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8413.XML b/docs/Help_Spanish/Topics/XS8413.XML
deleted file mode 100644
index ac1dd2df39..0000000000
--- a/docs/Help_Spanish/Topics/XS8413.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8413
-
-XS8413
-
-
-
- Error XS8413
-
- Asynchronous foreach statement cannot operate on variables of type '{0}' because it implements multiple instantiations of '{1}'; try casting to a specific interface instantiation
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8414.XML b/docs/Help_Spanish/Topics/XS8414.XML
deleted file mode 100644
index d31a1e2054..0000000000
--- a/docs/Help_Spanish/Topics/XS8414.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8414
-
-XS8414
-
-
-
- Error XS8414
-
- foreach statement cannot operate on variables of type '{0}' because '{0}' does not contain a public instance or extension definition for '{1}'. Did you mean 'await foreach' rather than 'foreach'?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8415.XML b/docs/Help_Spanish/Topics/XS8415.XML
deleted file mode 100644
index 14293559bb..0000000000
--- a/docs/Help_Spanish/Topics/XS8415.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8415
-
-XS8415
-
-
-
- Error XS8415
-
- Asynchronous foreach statement cannot operate on variables of type '{0}' because '{0}' does not contain a public instance or extension definition for '{1}'. Did you mean 'foreach' rather than 'await foreach'?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8416.XML b/docs/Help_Spanish/Topics/XS8416.XML
deleted file mode 100644
index 37117a70b9..0000000000
--- a/docs/Help_Spanish/Topics/XS8416.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8416
-
-XS8416
-
-
-
- Error XS8416
-
- Cannot use a collection of dynamic type in an asynchronous foreach
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8417.XML b/docs/Help_Spanish/Topics/XS8417.XML
deleted file mode 100644
index 496710aeb5..0000000000
--- a/docs/Help_Spanish/Topics/XS8417.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8417
-
-XS8417
-
-
-
- Error XS8417
-
- '{0}': type used in an asynchronous using statement must be implicitly convertible to 'System.IAsyncDisposable' or implement a suitable 'DisposeAsync' method. Did you mean 'using' rather than 'await using'?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8418.XML b/docs/Help_Spanish/Topics/XS8418.XML
deleted file mode 100644
index 247897896f..0000000000
--- a/docs/Help_Spanish/Topics/XS8418.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8418
-
-XS8418
-
-
-
- Error XS8418
-
- '{0}': type used in a using statement must be implicitly convertible to 'System.IDisposable'. Did you mean 'await using' rather than 'using'?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8419.XML b/docs/Help_Spanish/Topics/XS8419.XML
deleted file mode 100644
index bdf7e00c19..0000000000
--- a/docs/Help_Spanish/Topics/XS8419.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8419
-
-XS8419
-
-
-
- Error XS8419
-
- The body of an async-iterator method must contain a 'yield' statement.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8420.XML b/docs/Help_Spanish/Topics/XS8420.XML
deleted file mode 100644
index 523bc355f3..0000000000
--- a/docs/Help_Spanish/Topics/XS8420.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8420
-
-XS8420
-
-
-
- Error XS8420
-
- The body of an async-iterator method must contain a 'yield' statement. Consider removing 'async' from the method declaration or adding a 'yield' statement.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8421.XML b/docs/Help_Spanish/Topics/XS8421.XML
deleted file mode 100644
index 12686f4be6..0000000000
--- a/docs/Help_Spanish/Topics/XS8421.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8421
-
-XS8421
-
-
-
- Error XS8421
-
- A static local function cannot contain a reference to '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8422.XML b/docs/Help_Spanish/Topics/XS8422.XML
deleted file mode 100644
index 7f756b033f..0000000000
--- a/docs/Help_Spanish/Topics/XS8422.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8422
-
-XS8422
-
-
-
- Error XS8422
-
- A static local function cannot contain a reference to 'SELF' or 'SUPER'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8423.XML b/docs/Help_Spanish/Topics/XS8423.XML
deleted file mode 100644
index 24ee872b9c..0000000000
--- a/docs/Help_Spanish/Topics/XS8423.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8423
-
-XS8423
-
-
-
- Error XS8423
-
- Attribute '{0}' is not valid on event accessors. It is only valid on '{1}' declarations.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8424.XML b/docs/Help_Spanish/Topics/XS8424.XML
deleted file mode 100644
index e77eda1ed4..0000000000
--- a/docs/Help_Spanish/Topics/XS8424.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8424
-
-XS8424
-
-
-
- Warning XS8424
-
- The EnumeratorCancellationAttribute applied to parameter '{0}' will have no effect. The attribute is only effective on a parameter of type CancellationToken in an async-iterator method returning IAsyncEnumerable
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8425.XML b/docs/Help_Spanish/Topics/XS8425.XML
deleted file mode 100644
index 6d9e5efd49..0000000000
--- a/docs/Help_Spanish/Topics/XS8425.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8425
-
-XS8425
-
-
-
- Warning XS8425
-
- Async-iterator '{0}' has one or more parameters of type 'CancellationToken' but none of them is decorated with the 'EnumeratorCancellation' attribute, so the cancellation token parameter from the generated 'IAsyncEnumerable<>.GetAsyncEnumerator' will be unconsumed
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8426.XML b/docs/Help_Spanish/Topics/XS8426.XML
deleted file mode 100644
index f46f61108c..0000000000
--- a/docs/Help_Spanish/Topics/XS8426.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8426
-
-XS8426
-
-
-
- Error XS8426
-
- The attribute [EnumeratorCancellation] cannot be used on multiple parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8427.XML b/docs/Help_Spanish/Topics/XS8427.XML
deleted file mode 100644
index e7a0de3ce1..0000000000
--- a/docs/Help_Spanish/Topics/XS8427.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8427
-
-XS8427
-
-
-
- Error XS8427
-
- Enums, classes, and structures cannot be declared in an interface that has an 'in' or 'out' type parameter.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8428.XML b/docs/Help_Spanish/Topics/XS8428.XML
deleted file mode 100644
index 10eb11811c..0000000000
--- a/docs/Help_Spanish/Topics/XS8428.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8428
-
-XS8428
-
-
-
- Error XS8428
-
- Invocation of implicit Index Indexer cannot name the argument.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8429.XML b/docs/Help_Spanish/Topics/XS8429.XML
deleted file mode 100644
index 5fa7e43a9c..0000000000
--- a/docs/Help_Spanish/Topics/XS8429.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8429
-
-XS8429
-
-
-
- Error XS8429
-
- Invocation of implicit Range Indexer cannot name the argument.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8502.XML b/docs/Help_Spanish/Topics/XS8502.XML
deleted file mode 100644
index 5257662ee7..0000000000
--- a/docs/Help_Spanish/Topics/XS8502.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8502
-
-XS8502
-
-
-
- Error XS8502
-
- Matching the tuple type '{0}' requires '{1}' subpatterns, but '{2}' subpatterns are present.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8503.XML b/docs/Help_Spanish/Topics/XS8503.XML
deleted file mode 100644
index a5a163997f..0000000000
--- a/docs/Help_Spanish/Topics/XS8503.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8503
-
-XS8503
-
-
-
- Error XS8503
-
- A property subpattern requires a reference to the property or field to be matched, e.g. '{{ Name: {0} }}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8504.XML b/docs/Help_Spanish/Topics/XS8504.XML
deleted file mode 100644
index fd6e7feb13..0000000000
--- a/docs/Help_Spanish/Topics/XS8504.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8504
-
-XS8504
-
-
-
- Error XS8504
-
- Pattern missing
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8505.XML b/docs/Help_Spanish/Topics/XS8505.XML
deleted file mode 100644
index 63ba6da862..0000000000
--- a/docs/Help_Spanish/Topics/XS8505.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8505
-
-XS8505
-
-
-
- Error XS8505
-
- A default literal 'default' is not valid as a pattern. Use another literal (e.g. '0' or 'null') as appropriate. To match everything, use a discard pattern '_'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8506.XML b/docs/Help_Spanish/Topics/XS8506.XML
deleted file mode 100644
index 332e9fc26d..0000000000
--- a/docs/Help_Spanish/Topics/XS8506.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8506
-
-XS8506
-
-
-
- Error XS8506
-
- No best type was found for the switch expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8508.XML b/docs/Help_Spanish/Topics/XS8508.XML
deleted file mode 100644
index 88dd9ab319..0000000000
--- a/docs/Help_Spanish/Topics/XS8508.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8508
-
-XS8508
-
-
-
- Error XS8508
-
- The syntax 'var' for a pattern is not permitted to refer to a type, but '{0}' is in scope here.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8509.XML b/docs/Help_Spanish/Topics/XS8509.XML
deleted file mode 100644
index 5e070c5fc3..0000000000
--- a/docs/Help_Spanish/Topics/XS8509.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8509
-
-XS8509
-
-
-
- Warning XS8509
-
- The switch expression does not handle all possible values of its input type (it is not exhaustive). For example, the pattern '{0}' is not covered.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8510.XML b/docs/Help_Spanish/Topics/XS8510.XML
deleted file mode 100644
index c2765f9a87..0000000000
--- a/docs/Help_Spanish/Topics/XS8510.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8510
-
-XS8510
-
-
-
- Error XS8510
-
- The pattern is unreachable. It has already been handled by a previous arm of the switch expression or it is impossible to match.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8511.XML b/docs/Help_Spanish/Topics/XS8511.XML
deleted file mode 100644
index 6de94b938e..0000000000
--- a/docs/Help_Spanish/Topics/XS8511.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8511
-
-XS8511
-
-
-
- Error XS8511
-
- An expression of type '{0}' cannot be handled by a pattern of type '{1}'. Please use language version '{2}' or greater to match an open type with a constant pattern.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8512.XML b/docs/Help_Spanish/Topics/XS8512.XML
deleted file mode 100644
index 30c6c075ae..0000000000
--- a/docs/Help_Spanish/Topics/XS8512.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8512
-
-XS8512
-
-
-
- Warning XS8512
-
- The name '_' refers to the constant, not the discard pattern. Use 'var _' to discard the value, or '@_' to refer to a constant by that name.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8513.XML b/docs/Help_Spanish/Topics/XS8513.XML
deleted file mode 100644
index 26c55c1950..0000000000
--- a/docs/Help_Spanish/Topics/XS8513.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8513
-
-XS8513
-
-
-
- Warning XS8513
-
- The name '_' refers to the type '{0}', not the discard pattern. Use '@_' for the type, or 'var _' to discard.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8514.XML b/docs/Help_Spanish/Topics/XS8514.XML
deleted file mode 100644
index b5408c71b1..0000000000
--- a/docs/Help_Spanish/Topics/XS8514.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8514
-
-XS8514
-
-
-
- Error XS8514
-
- An expression tree may not contain a switch expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8515.XML b/docs/Help_Spanish/Topics/XS8515.XML
deleted file mode 100644
index 199ccabdf1..0000000000
--- a/docs/Help_Spanish/Topics/XS8515.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8515
-
-XS8515
-
-
-
- Error XS8515
-
- Parentheses are required around the switch governing expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8516.XML b/docs/Help_Spanish/Topics/XS8516.XML
deleted file mode 100644
index b3592cf92b..0000000000
--- a/docs/Help_Spanish/Topics/XS8516.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8516
-
-XS8516
-
-
-
- Error XS8516
-
- The name '{0}' does not identify tuple element '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8517.XML b/docs/Help_Spanish/Topics/XS8517.XML
deleted file mode 100644
index 4a4695c24c..0000000000
--- a/docs/Help_Spanish/Topics/XS8517.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8517
-
-XS8517
-
-
-
- Error XS8517
-
- The name '{0}' does not match the corresponding 'Deconstruct' parameter '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8518.XML b/docs/Help_Spanish/Topics/XS8518.XML
deleted file mode 100644
index dc4dbd0e5a..0000000000
--- a/docs/Help_Spanish/Topics/XS8518.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8518
-
-XS8518
-
-
-
- Error XS8518
-
- An expression of type '{0}' can never match the provided pattern.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8519.XML b/docs/Help_Spanish/Topics/XS8519.XML
deleted file mode 100644
index 93ee9d2165..0000000000
--- a/docs/Help_Spanish/Topics/XS8519.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8519
-
-XS8519
-
-
-
- Warning XS8519
-
- The given expression never matches the provided pattern.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8520.XML b/docs/Help_Spanish/Topics/XS8520.XML
deleted file mode 100644
index 6f2d5fe2cc..0000000000
--- a/docs/Help_Spanish/Topics/XS8520.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8520
-
-XS8520
-
-
-
- Warning XS8520
-
- The given expression always matches the provided constant.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8521.XML b/docs/Help_Spanish/Topics/XS8521.XML
deleted file mode 100644
index f94f706b76..0000000000
--- a/docs/Help_Spanish/Topics/XS8521.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8521
-
-XS8521
-
-
-
- Error XS8521
-
- Pattern-matching is not permitted for pointer types.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8522.XML b/docs/Help_Spanish/Topics/XS8522.XML
deleted file mode 100644
index 8813557802..0000000000
--- a/docs/Help_Spanish/Topics/XS8522.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8522
-
-XS8522
-
-
-
- Error XS8522
-
- Element names are not permitted when pattern-matching via 'System.Runtime.CompilerServices.ITuple'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8523.XML b/docs/Help_Spanish/Topics/XS8523.XML
deleted file mode 100644
index 80f486609b..0000000000
--- a/docs/Help_Spanish/Topics/XS8523.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8523
-
-XS8523
-
-
-
- Error XS8523
-
- The discard pattern is not permitted as a case label in a switch statement. Use 'case var _:' for a discard pattern, or 'case @_:' for a constant named '_'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8524.XML b/docs/Help_Spanish/Topics/XS8524.XML
deleted file mode 100644
index 3d86049418..0000000000
--- a/docs/Help_Spanish/Topics/XS8524.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8524
-
-XS8524
-
-
-
- Warning XS8524
-
- The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '{0}' is not covered.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8597.XML b/docs/Help_Spanish/Topics/XS8597.XML
deleted file mode 100644
index 30bcb26fb7..0000000000
--- a/docs/Help_Spanish/Topics/XS8597.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8597
-
-XS8597
-
-
-
- Warning XS8597
-
- Thrown value may be null.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8598.XML b/docs/Help_Spanish/Topics/XS8598.XML
deleted file mode 100644
index 7dfe3334f5..0000000000
--- a/docs/Help_Spanish/Topics/XS8598.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8598
-
-XS8598
-
-
-
- Error XS8598
-
- The suppression operator is not allowed in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8600.XML b/docs/Help_Spanish/Topics/XS8600.XML
deleted file mode 100644
index d4a73390d4..0000000000
--- a/docs/Help_Spanish/Topics/XS8600.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8600
-
-XS8600
-
-
-
- Warning XS8600
-
- Converting null literal or possible null value to non-nullable type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8601.XML b/docs/Help_Spanish/Topics/XS8601.XML
deleted file mode 100644
index 94b60deccc..0000000000
--- a/docs/Help_Spanish/Topics/XS8601.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8601
-
-XS8601
-
-
-
- Warning XS8601
-
- Possible null reference assignment.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8602.XML b/docs/Help_Spanish/Topics/XS8602.XML
deleted file mode 100644
index 2d3de41bdd..0000000000
--- a/docs/Help_Spanish/Topics/XS8602.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8602
-
-XS8602
-
-
-
- Warning XS8602
-
- Dereference of a possibly null reference.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8603.XML b/docs/Help_Spanish/Topics/XS8603.XML
deleted file mode 100644
index a0aa6427ce..0000000000
--- a/docs/Help_Spanish/Topics/XS8603.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8603
-
-XS8603
-
-
-
- Warning XS8603
-
- Possible null reference return.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8604.XML b/docs/Help_Spanish/Topics/XS8604.XML
deleted file mode 100644
index 20053b36bd..0000000000
--- a/docs/Help_Spanish/Topics/XS8604.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8604
-
-XS8604
-
-
-
- Warning XS8604
-
- Possible null reference argument for parameter '{0}' in '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8605.XML b/docs/Help_Spanish/Topics/XS8605.XML
deleted file mode 100644
index 123c771fa6..0000000000
--- a/docs/Help_Spanish/Topics/XS8605.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8605
-
-XS8605
-
-
-
- Warning XS8605
-
- Unboxing a possibly null value.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8607.XML b/docs/Help_Spanish/Topics/XS8607.XML
deleted file mode 100644
index 262e835c92..0000000000
--- a/docs/Help_Spanish/Topics/XS8607.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8607
-
-XS8607
-
-
-
- Warning XS8607
-
- A possible null value may not be used for a type marked with [NotNull] or [DisallowNull]
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8608.XML b/docs/Help_Spanish/Topics/XS8608.XML
deleted file mode 100644
index 94a3e6eec0..0000000000
--- a/docs/Help_Spanish/Topics/XS8608.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8608
-
-XS8608
-
-
-
- Warning XS8608
-
- Nullability of reference types in type doesn't match overridden member.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8609.XML b/docs/Help_Spanish/Topics/XS8609.XML
deleted file mode 100644
index a2307afe1e..0000000000
--- a/docs/Help_Spanish/Topics/XS8609.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8609
-
-XS8609
-
-
-
- Warning XS8609
-
- Nullability of reference types in return type doesn't match overridden member.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8610.XML b/docs/Help_Spanish/Topics/XS8610.XML
deleted file mode 100644
index 84123e83d1..0000000000
--- a/docs/Help_Spanish/Topics/XS8610.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8610
-
-XS8610
-
-
-
- Warning XS8610
-
- Nullability of reference types in type of parameter '{0}' doesn't match overridden member.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8611.XML b/docs/Help_Spanish/Topics/XS8611.XML
deleted file mode 100644
index c6c8a49267..0000000000
--- a/docs/Help_Spanish/Topics/XS8611.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8611
-
-XS8611
-
-
-
- Warning XS8611
-
- Nullability of reference types in type of parameter '{0}' doesn't match partial method declaration.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8612.XML b/docs/Help_Spanish/Topics/XS8612.XML
deleted file mode 100644
index f86f05c389..0000000000
--- a/docs/Help_Spanish/Topics/XS8612.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8612
-
-XS8612
-
-
-
- Warning XS8612
-
- Nullability of reference types in type of '{0}' doesn't match implicitly implemented member '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8613.XML b/docs/Help_Spanish/Topics/XS8613.XML
deleted file mode 100644
index 4cbc4bc91b..0000000000
--- a/docs/Help_Spanish/Topics/XS8613.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8613
-
-XS8613
-
-
-
- Warning XS8613
-
- Nullability of reference types in return type of '{0}' doesn't match implicitly implemented member '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8614.XML b/docs/Help_Spanish/Topics/XS8614.XML
deleted file mode 100644
index 9a213acd58..0000000000
--- a/docs/Help_Spanish/Topics/XS8614.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8614
-
-XS8614
-
-
-
- Warning XS8614
-
- Nullability of reference types in type of parameter '{0}' of '{1}' doesn't match implicitly implemented member '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8615.XML b/docs/Help_Spanish/Topics/XS8615.XML
deleted file mode 100644
index 78c3d8597c..0000000000
--- a/docs/Help_Spanish/Topics/XS8615.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8615
-
-XS8615
-
-
-
- Warning XS8615
-
- Nullability of reference types in type doesn't match implemented member '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8616.XML b/docs/Help_Spanish/Topics/XS8616.XML
deleted file mode 100644
index 5e2b6b0b49..0000000000
--- a/docs/Help_Spanish/Topics/XS8616.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8616
-
-XS8616
-
-
-
- Warning XS8616
-
- Nullability of reference types in return type doesn't match implemented member '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8617.XML b/docs/Help_Spanish/Topics/XS8617.XML
deleted file mode 100644
index 6267d5a334..0000000000
--- a/docs/Help_Spanish/Topics/XS8617.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8617
-
-XS8617
-
-
-
- Warning XS8617
-
- Nullability of reference types in type of parameter '{0}' doesn't match implemented member '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8618.XML b/docs/Help_Spanish/Topics/XS8618.XML
deleted file mode 100644
index d903527139..0000000000
--- a/docs/Help_Spanish/Topics/XS8618.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8618
-
-XS8618
-
-
-
- Warning XS8618
-
- Non-nullable {0} '{1}' must contain a non-null value when exiting constructor. Consider declaring the {0} as nullable.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8619.XML b/docs/Help_Spanish/Topics/XS8619.XML
deleted file mode 100644
index 723360333c..0000000000
--- a/docs/Help_Spanish/Topics/XS8619.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8619
-
-XS8619
-
-
-
- Warning XS8619
-
- Nullability of reference types in value of type '{0}' doesn't match target type '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8620.XML b/docs/Help_Spanish/Topics/XS8620.XML
deleted file mode 100644
index 8fa61c41c3..0000000000
--- a/docs/Help_Spanish/Topics/XS8620.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8620
-
-XS8620
-
-
-
- Warning XS8620
-
- Argument of type '{0}' cannot be used for parameter '{2}' of type '{1}' in '{3}' due to differences in the nullability of reference types.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8621.XML b/docs/Help_Spanish/Topics/XS8621.XML
deleted file mode 100644
index 17e35174d2..0000000000
--- a/docs/Help_Spanish/Topics/XS8621.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8621
-
-XS8621
-
-
-
- Warning XS8621
-
- Nullability of reference types in return type of '{0}' doesn't match the target delegate '{1}' (possibly because of nullability attributes).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8622.XML b/docs/Help_Spanish/Topics/XS8622.XML
deleted file mode 100644
index 149587fc0b..0000000000
--- a/docs/Help_Spanish/Topics/XS8622.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8622
-
-XS8622
-
-
-
- Warning XS8622
-
- Nullability of reference types in type of parameter '{0}' of '{1}' doesn't match the target delegate '{2}' (possibly because of nullability attributes).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8623.XML b/docs/Help_Spanish/Topics/XS8623.XML
deleted file mode 100644
index 4f343aca0a..0000000000
--- a/docs/Help_Spanish/Topics/XS8623.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8623
-
-XS8623
-
-
-
- Error XS8623
-
- Explicit application of 'System.Runtime.CompilerServices.NullableAttribute' is not allowed.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8624.XML b/docs/Help_Spanish/Topics/XS8624.XML
deleted file mode 100644
index f4c3222b50..0000000000
--- a/docs/Help_Spanish/Topics/XS8624.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8624
-
-XS8624
-
-
-
- Warning XS8624
-
- Argument of type '{0}' cannot be used as an output of type '{1}' for parameter '{2}' in '{3}' due to differences in the nullability of reference types.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8625.XML b/docs/Help_Spanish/Topics/XS8625.XML
deleted file mode 100644
index a30f984ad2..0000000000
--- a/docs/Help_Spanish/Topics/XS8625.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8625
-
-XS8625
-
-
-
- Warning XS8625
-
- Cannot convert null literal to non-nullable reference type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8627.XML b/docs/Help_Spanish/Topics/XS8627.XML
deleted file mode 100644
index 5f9d58657f..0000000000
--- a/docs/Help_Spanish/Topics/XS8627.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8627
-
-XS8627
-
-
-
- Error XS8627
-
- A nullable type parameter must be known to be a value type or non-nullable reference type unless language version '{0}' or greater is used. Consider changing the language version or adding a 'class', 'struct', or type constraint.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8628.XML b/docs/Help_Spanish/Topics/XS8628.XML
deleted file mode 100644
index 533e3bc7ba..0000000000
--- a/docs/Help_Spanish/Topics/XS8628.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8628
-
-XS8628
-
-
-
- Error XS8628
-
- Cannot use a nullable reference type in object creation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8629.XML b/docs/Help_Spanish/Topics/XS8629.XML
deleted file mode 100644
index b8ce0b87ef..0000000000
--- a/docs/Help_Spanish/Topics/XS8629.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8629
-
-XS8629
-
-
-
- Warning XS8629
-
- Nullable value type may be null.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8630.XML b/docs/Help_Spanish/Topics/XS8630.XML
deleted file mode 100644
index 0298b0cf46..0000000000
--- a/docs/Help_Spanish/Topics/XS8630.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8630
-
-XS8630
-
-
-
- Error XS8630
-
- Invalid '{0}' value: '{1}' for X# {2}. Please use language version '{3}' or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8631.XML b/docs/Help_Spanish/Topics/XS8631.XML
deleted file mode 100644
index ecd51ab681..0000000000
--- a/docs/Help_Spanish/Topics/XS8631.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8631
-
-XS8631
-
-
-
- Warning XS8631
-
- The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. Nullability of type argument '{3}' doesn't match constraint type '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8632.XML b/docs/Help_Spanish/Topics/XS8632.XML
deleted file mode 100644
index c9a7928794..0000000000
--- a/docs/Help_Spanish/Topics/XS8632.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8632
-
-XS8632
-
-
-
- Warning XS8632
-
- The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8633.XML b/docs/Help_Spanish/Topics/XS8633.XML
deleted file mode 100644
index 68866f2619..0000000000
--- a/docs/Help_Spanish/Topics/XS8633.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8633
-
-XS8633
-
-
-
- Warning XS8633
-
- Nullability in constraints for type parameter '{0}' of method '{1}' doesn't match the constraints for type parameter '{2}' of interface method '{3}'. Consider using an explicit interface implementation instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8634.XML b/docs/Help_Spanish/Topics/XS8634.XML
deleted file mode 100644
index 8b379b0891..0000000000
--- a/docs/Help_Spanish/Topics/XS8634.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8634
-
-XS8634
-
-
-
- Warning XS8634
-
- The type '{2}' cannot be used as type parameter '{1}' in the generic type or method '{0}'. Nullability of type argument '{2}' doesn't match 'class' constraint.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8635.XML b/docs/Help_Spanish/Topics/XS8635.XML
deleted file mode 100644
index 95df84b739..0000000000
--- a/docs/Help_Spanish/Topics/XS8635.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8635
-
-XS8635
-
-
-
- Error XS8635
-
- Unexpected character sequence '...'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8636.XML b/docs/Help_Spanish/Topics/XS8636.XML
deleted file mode 100644
index ea3262a916..0000000000
--- a/docs/Help_Spanish/Topics/XS8636.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8636
-
-XS8636
-
-
-
- Error XS8636
-
- Invalid option '{0}' for /nullable; must be 'disable', 'enable', 'warnings' or 'annotations'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8637.XML b/docs/Help_Spanish/Topics/XS8637.XML
deleted file mode 100644
index 6f3601b1e8..0000000000
--- a/docs/Help_Spanish/Topics/XS8637.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8637
-
-XS8637
-
-
-
- Error XS8637
-
- Expected 'enable', 'disable', or 'restore'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8639.XML b/docs/Help_Spanish/Topics/XS8639.XML
deleted file mode 100644
index d54d9a8cfe..0000000000
--- a/docs/Help_Spanish/Topics/XS8639.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8639
-
-XS8639
-
-
-
- Error XS8639
-
- The typeof operator cannot be used on a nullable reference type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8640.XML b/docs/Help_Spanish/Topics/XS8640.XML
deleted file mode 100644
index 3f6b2446d6..0000000000
--- a/docs/Help_Spanish/Topics/XS8640.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8640
-
-XS8640
-
-
-
- Error XS8640
-
- Expression tree cannot contain value of ref struct or restricted type '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8641.XML b/docs/Help_Spanish/Topics/XS8641.XML
deleted file mode 100644
index c5c0a36a83..0000000000
--- a/docs/Help_Spanish/Topics/XS8641.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8641
-
-XS8641
-
-
-
- Error XS8641
-
- 'else' cannot start a statement.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8642.XML b/docs/Help_Spanish/Topics/XS8642.XML
deleted file mode 100644
index e646b7b138..0000000000
--- a/docs/Help_Spanish/Topics/XS8642.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8642
-
-XS8642
-
-
-
- Error XS8642
-
- An expression tree may not contain a null coalescing assignment
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8643.XML b/docs/Help_Spanish/Topics/XS8643.XML
deleted file mode 100644
index 0494de3e1c..0000000000
--- a/docs/Help_Spanish/Topics/XS8643.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8643
-
-XS8643
-
-
-
- Warning XS8643
-
- Nullability of reference types in explicit interface specifier doesn't match interface implemented by the type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8644.XML b/docs/Help_Spanish/Topics/XS8644.XML
deleted file mode 100644
index 5565bd2e50..0000000000
--- a/docs/Help_Spanish/Topics/XS8644.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8644
-
-XS8644
-
-
-
- Warning XS8644
-
- '{0}' does not implement interface member '{1}'. Nullability of reference types in interface implemented by the base type doesn't match.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8645.XML b/docs/Help_Spanish/Topics/XS8645.XML
deleted file mode 100644
index 1ecc5a36b3..0000000000
--- a/docs/Help_Spanish/Topics/XS8645.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8645
-
-XS8645
-
-
-
- Warning XS8645
-
- '{0}' is already listed in the interface list on type '{1}' with different nullability of reference types.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8646.XML b/docs/Help_Spanish/Topics/XS8646.XML
deleted file mode 100644
index 9fbd15e77a..0000000000
--- a/docs/Help_Spanish/Topics/XS8646.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8646
-
-XS8646
-
-
-
- Error XS8646
-
- '{0}' is explicitly implemented more than once.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8647.XML b/docs/Help_Spanish/Topics/XS8647.XML
deleted file mode 100644
index ff4d7d0e3f..0000000000
--- a/docs/Help_Spanish/Topics/XS8647.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8647
-
-XS8647
-
-
-
- Error XS8647
-
- A using variable cannot be used directly within a switch section (consider using braces).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8648.XML b/docs/Help_Spanish/Topics/XS8648.XML
deleted file mode 100644
index 942687aba8..0000000000
--- a/docs/Help_Spanish/Topics/XS8648.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8648
-
-XS8648
-
-
-
- Error XS8648
-
- A goto cannot jump to a location after a using declaration.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8649.XML b/docs/Help_Spanish/Topics/XS8649.XML
deleted file mode 100644
index 0e9ba950cc..0000000000
--- a/docs/Help_Spanish/Topics/XS8649.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8649
-
-XS8649
-
-
-
- Error XS8649
-
- A goto cannot jump to a location before a using declaration within the same block.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8650.XML b/docs/Help_Spanish/Topics/XS8650.XML
deleted file mode 100644
index fba9bf8808..0000000000
--- a/docs/Help_Spanish/Topics/XS8650.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8650
-
-XS8650
-
-
-
- Error XS8650
-
- It is not legal to use nullable reference type '{0}?' in an is-type expression; use the underlying type '{0}' instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8651.XML b/docs/Help_Spanish/Topics/XS8651.XML
deleted file mode 100644
index ba2aefa442..0000000000
--- a/docs/Help_Spanish/Topics/XS8651.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8651
-
-XS8651
-
-
-
- Error XS8651
-
- It is not legal to use nullable reference type '{0}?' in an as expression; use the underlying type '{0}' instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8652.XML b/docs/Help_Spanish/Topics/XS8652.XML
deleted file mode 100644
index 684893c29d..0000000000
--- a/docs/Help_Spanish/Topics/XS8652.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8652
-
-XS8652
-
-
-
- Error XS8652
-
- The feature '{0}' is currently in Preview and *unsupported*. To use Preview features, use the 'preview' language version.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8655.XML b/docs/Help_Spanish/Topics/XS8655.XML
deleted file mode 100644
index 0cab8ed8fb..0000000000
--- a/docs/Help_Spanish/Topics/XS8655.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8655
-
-XS8655
-
-
-
- Warning XS8655
-
- The switch expression does not handle some null inputs (it is not exhaustive). For example, the pattern '{0}' is not covered.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8656.XML b/docs/Help_Spanish/Topics/XS8656.XML
deleted file mode 100644
index c9e7ee8412..0000000000
--- a/docs/Help_Spanish/Topics/XS8656.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8656
-
-XS8656
-
-
-
- Warning XS8656
-
- Call to non-readonly member '{0}' from a 'readonly' member results in an implicit copy of '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8657.XML b/docs/Help_Spanish/Topics/XS8657.XML
deleted file mode 100644
index b5f5cccac9..0000000000
--- a/docs/Help_Spanish/Topics/XS8657.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8657
-
-XS8657
-
-
-
- Error XS8657
-
- Static member '{0}' cannot be marked 'readonly'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8658.XML b/docs/Help_Spanish/Topics/XS8658.XML
deleted file mode 100644
index 7cf0dbbdbd..0000000000
--- a/docs/Help_Spanish/Topics/XS8658.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8658
-
-XS8658
-
-
-
- Error XS8658
-
- Auto-implemented 'set' accessor '{0}' cannot be marked 'readonly'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8659.XML b/docs/Help_Spanish/Topics/XS8659.XML
deleted file mode 100644
index 2d22988bd5..0000000000
--- a/docs/Help_Spanish/Topics/XS8659.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8659
-
-XS8659
-
-
-
- Error XS8659
-
- Auto-implemented property '{0}' cannot be marked 'readonly' because it has a 'set' accessor.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8660.XML b/docs/Help_Spanish/Topics/XS8660.XML
deleted file mode 100644
index a95c06c5df..0000000000
--- a/docs/Help_Spanish/Topics/XS8660.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8660
-
-XS8660
-
-
-
- Error XS8660
-
- Cannot specify 'readonly' modifiers on both property or indexer '{0}' and its accessor. Remove one of them.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8661.XML b/docs/Help_Spanish/Topics/XS8661.XML
deleted file mode 100644
index 4f67bf32f6..0000000000
--- a/docs/Help_Spanish/Topics/XS8661.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8661
-
-XS8661
-
-
-
- Error XS8661
-
- Cannot specify 'readonly' modifiers on both accessors of property or indexer '{0}'. Instead, put a 'readonly' modifier on the property itself.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8662.XML b/docs/Help_Spanish/Topics/XS8662.XML
deleted file mode 100644
index 2e23d47888..0000000000
--- a/docs/Help_Spanish/Topics/XS8662.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8662
-
-XS8662
-
-
-
- Error XS8662
-
- Field-like event '{0}' cannot be 'readonly'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8663.XML b/docs/Help_Spanish/Topics/XS8663.XML
deleted file mode 100644
index 06e48583b9..0000000000
--- a/docs/Help_Spanish/Topics/XS8663.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8663
-
-XS8663
-
-
-
- Error XS8663
-
- Both partial method declarations must be readonly or neither may be readonly
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8664.XML b/docs/Help_Spanish/Topics/XS8664.XML
deleted file mode 100644
index cedcc032f1..0000000000
--- a/docs/Help_Spanish/Topics/XS8664.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8664
-
-XS8664
-
-
-
- Error XS8664
-
- '{0}': 'readonly' can only be used on accessors if the property or indexer has both a get and a set accessor
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8665.XML b/docs/Help_Spanish/Topics/XS8665.XML
deleted file mode 100644
index 3e21345b32..0000000000
--- a/docs/Help_Spanish/Topics/XS8665.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8665
-
-XS8665
-
-
-
- Error XS8665
-
- Method '{0}' specifies a 'class' constraint for type parameter '{1}', but corresponding type parameter '{2}' of overridden or explicitly implemented method '{3}' is not a reference type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8666.XML b/docs/Help_Spanish/Topics/XS8666.XML
deleted file mode 100644
index 19bd356c8e..0000000000
--- a/docs/Help_Spanish/Topics/XS8666.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8666
-
-XS8666
-
-
-
- Error XS8666
-
- Method '{0}' specifies a 'struct' constraint for type parameter '{1}', but corresponding type parameter '{2}' of overridden or explicitly implemented method '{3}' is not a non-nullable value type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8667.XML b/docs/Help_Spanish/Topics/XS8667.XML
deleted file mode 100644
index b766c8eb14..0000000000
--- a/docs/Help_Spanish/Topics/XS8667.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8667
-
-XS8667
-
-
-
- Warning XS8667
-
- Partial method declarations of '{0}' have inconsistent nullability in constraints for type parameter '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8668.XML b/docs/Help_Spanish/Topics/XS8668.XML
deleted file mode 100644
index cf038b4781..0000000000
--- a/docs/Help_Spanish/Topics/XS8668.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8668
-
-XS8668
-
-
-
- Error XS8668
-
- Expected 'warnings', 'annotations', or end of directive
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8669.XML b/docs/Help_Spanish/Topics/XS8669.XML
deleted file mode 100644
index 96c370bf29..0000000000
--- a/docs/Help_Spanish/Topics/XS8669.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8669
-
-XS8669
-
-
-
- Warning XS8669
-
- The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8670.XML b/docs/Help_Spanish/Topics/XS8670.XML
deleted file mode 100644
index 2ab7a84ff1..0000000000
--- a/docs/Help_Spanish/Topics/XS8670.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8670
-
-XS8670
-
-
-
- Warning XS8670
-
- Object or collection initializer implicitly dereferences possibly null member '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8700.XML b/docs/Help_Spanish/Topics/XS8700.XML
deleted file mode 100644
index 26f4bd51e0..0000000000
--- a/docs/Help_Spanish/Topics/XS8700.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8700
-
-XS8700
-
-
-
- Error XS8700
-
- Multiple analyzer config files cannot be in the same directory ('{0}').
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8701.XML b/docs/Help_Spanish/Topics/XS8701.XML
deleted file mode 100644
index 4172c372d4..0000000000
--- a/docs/Help_Spanish/Topics/XS8701.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8701
-
-XS8701
-
-
-
- Error XS8701
-
- Target runtime doesn't support default interface implementation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8702.XML b/docs/Help_Spanish/Topics/XS8702.XML
deleted file mode 100644
index 4bd779c43d..0000000000
--- a/docs/Help_Spanish/Topics/XS8702.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8702
-
-XS8702
-
-
-
- Error XS8702
-
- '{0}' cannot implement interface member '{1}' in type '{2}' because the target runtime doesn't support default interface implementation.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8703.XML b/docs/Help_Spanish/Topics/XS8703.XML
deleted file mode 100644
index 0a43c78109..0000000000
--- a/docs/Help_Spanish/Topics/XS8703.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8703
-
-XS8703
-
-
-
- Error XS8703
-
- The modifier '{0}' is not valid for this item in X# {1}. Please use language version '{2}' or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8704.XML b/docs/Help_Spanish/Topics/XS8704.XML
deleted file mode 100644
index a9f9d9a91e..0000000000
--- a/docs/Help_Spanish/Topics/XS8704.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8704
-
-XS8704
-
-
-
- Error XS8704
-
- '{0}' does not implement interface member '{1}'. '{2}' cannot implicitly implement a non-public member.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8705.XML b/docs/Help_Spanish/Topics/XS8705.XML
deleted file mode 100644
index 6ddeabbf24..0000000000
--- a/docs/Help_Spanish/Topics/XS8705.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8705
-
-XS8705
-
-
-
- Error XS8705
-
- Interface member '{0}' does not have a most specific implementation. Neither '{1}', nor '{2}' are most specific.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8706.XML b/docs/Help_Spanish/Topics/XS8706.XML
deleted file mode 100644
index c609165f23..0000000000
--- a/docs/Help_Spanish/Topics/XS8706.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8706
-
-XS8706
-
-
-
- Error XS8706
-
- '{0}' cannot implement interface member '{1}' in type '{2}' because feature '{3}' is not available in X# {4}. Please use language version '{5}' or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8707.XML b/docs/Help_Spanish/Topics/XS8707.XML
deleted file mode 100644
index 8f1ee0dce0..0000000000
--- a/docs/Help_Spanish/Topics/XS8707.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8707
-
-XS8707
-
-
-
- Error XS8707
-
- Target runtime doesn't support 'protected', 'protected internal', or 'private protected' accessibility for a member of an interface.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8711.XML b/docs/Help_Spanish/Topics/XS8711.XML
deleted file mode 100644
index 20fd626597..0000000000
--- a/docs/Help_Spanish/Topics/XS8711.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8711
-
-XS8711
-
-
-
- Error XS8711
-
- Type '{0}' cannot be embedded because it has a non-abstract member. Consider setting the 'Embed Interop Types' property to false.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8712.XML b/docs/Help_Spanish/Topics/XS8712.XML
deleted file mode 100644
index c819747ad1..0000000000
--- a/docs/Help_Spanish/Topics/XS8712.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8712
-
-XS8712
-
-
-
- Error XS8712
-
- '{0}': abstract event cannot use event accessor syntax
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8714.XML b/docs/Help_Spanish/Topics/XS8714.XML
deleted file mode 100644
index 049e34de06..0000000000
--- a/docs/Help_Spanish/Topics/XS8714.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8714
-
-XS8714
-
-
-
- Warning XS8714
-
- The type '{2}' cannot be used as type parameter '{1}' in the generic type or method '{0}'. Nullability of type argument '{2}' doesn't match 'notnull' constraint.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8715.XML b/docs/Help_Spanish/Topics/XS8715.XML
deleted file mode 100644
index 4e68b70509..0000000000
--- a/docs/Help_Spanish/Topics/XS8715.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8715
-
-XS8715
-
-
-
- Error XS8715
-
- Duplicate null suppression operator ('!')
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8716.XML b/docs/Help_Spanish/Topics/XS8716.XML
deleted file mode 100644
index 7c474bab2c..0000000000
--- a/docs/Help_Spanish/Topics/XS8716.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8716
-
-XS8716
-
-
-
- Error XS8716
-
- There is no target type for the default literal.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8750.XML b/docs/Help_Spanish/Topics/XS8750.XML
deleted file mode 100644
index 7c924ace0c..0000000000
--- a/docs/Help_Spanish/Topics/XS8750.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8750
-
-XS8750
-
-
-
- Error XS8750
-
- Type '{0}' cannot be embedded because it has a re-abstraction of a member from base interface. Consider setting the 'Embed Interop Types' property to false.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8751.XML b/docs/Help_Spanish/Topics/XS8751.XML
deleted file mode 100644
index cfe3b9c8e0..0000000000
--- a/docs/Help_Spanish/Topics/XS8751.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8751
-
-XS8751
-
-
-
- Error XS8751
-
- Internal error in the X# compiler.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8752.XML b/docs/Help_Spanish/Topics/XS8752.XML
deleted file mode 100644
index c4a7a9e222..0000000000
--- a/docs/Help_Spanish/Topics/XS8752.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8752
-
-XS8752
-
-
-
- Error XS8752
-
- The type '{0}' may not be used as the target type of new()
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8753.XML b/docs/Help_Spanish/Topics/XS8753.XML
deleted file mode 100644
index c2ebd08d1a..0000000000
--- a/docs/Help_Spanish/Topics/XS8753.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8753
-
-XS8753
-
-
-
- Error XS8753
-
- Use of new() is not valid in this context
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8754.XML b/docs/Help_Spanish/Topics/XS8754.XML
deleted file mode 100644
index d401b49d83..0000000000
--- a/docs/Help_Spanish/Topics/XS8754.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8754
-
-XS8754
-
-
-
- Error XS8754
-
- There is no target type for '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8755.XML b/docs/Help_Spanish/Topics/XS8755.XML
deleted file mode 100644
index d66887ef74..0000000000
--- a/docs/Help_Spanish/Topics/XS8755.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8755
-
-XS8755
-
-
-
- Error XS8755
-
- '{0}' cannot be used as a modifier on a function pointer parameter.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8756.XML b/docs/Help_Spanish/Topics/XS8756.XML
deleted file mode 100644
index d4e24c6478..0000000000
--- a/docs/Help_Spanish/Topics/XS8756.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8756
-
-XS8756
-
-
-
- Error XS8756
-
- Function pointer '{0}' does not take {1} arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8757.XML b/docs/Help_Spanish/Topics/XS8757.XML
deleted file mode 100644
index 895eba4bbd..0000000000
--- a/docs/Help_Spanish/Topics/XS8757.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8757
-
-XS8757
-
-
-
- Error XS8757
-
- No overload for '{0}' matches function pointer '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8758.XML b/docs/Help_Spanish/Topics/XS8758.XML
deleted file mode 100644
index db51501518..0000000000
--- a/docs/Help_Spanish/Topics/XS8758.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8758
-
-XS8758
-
-
-
- Error XS8758
-
- Ref mismatch between '{0}' and function pointer '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8759.XML b/docs/Help_Spanish/Topics/XS8759.XML
deleted file mode 100644
index 3017443db9..0000000000
--- a/docs/Help_Spanish/Topics/XS8759.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8759
-
-XS8759
-
-
-
- Error XS8759
-
- Cannot create a function pointer for '{0}' because it is not a static method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8760.XML b/docs/Help_Spanish/Topics/XS8760.XML
deleted file mode 100644
index 5752936a47..0000000000
--- a/docs/Help_Spanish/Topics/XS8760.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8760
-
-XS8760
-
-
-
- Error XS8760
-
- '{0}': extern event cannot have initializer
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8761.XML b/docs/Help_Spanish/Topics/XS8761.XML
deleted file mode 100644
index d1a856483d..0000000000
--- a/docs/Help_Spanish/Topics/XS8761.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8761
-
-XS8761
-
-
-
- Error XS8761
-
- Operator '{0}' cannot be applied to 'default' and operand of type '{1}' because it is a type parameter that is not known to be a reference type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8762.XML b/docs/Help_Spanish/Topics/XS8762.XML
deleted file mode 100644
index d63e554007..0000000000
--- a/docs/Help_Spanish/Topics/XS8762.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8762
-
-XS8762
-
-
-
- Warning XS8762
-
- Parameter '{0}' must have a non-null value when exiting with '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8763.XML b/docs/Help_Spanish/Topics/XS8763.XML
deleted file mode 100644
index 6a512e9049..0000000000
--- a/docs/Help_Spanish/Topics/XS8763.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8763
-
-XS8763
-
-
-
- Warning XS8763
-
- A method marked [DoesNotReturn] should not return.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8764.XML b/docs/Help_Spanish/Topics/XS8764.XML
deleted file mode 100644
index 9c4040a9e2..0000000000
--- a/docs/Help_Spanish/Topics/XS8764.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8764
-
-XS8764
-
-
-
- Warning XS8764
-
- Nullability of return type doesn't match overridden member (possibly because of nullability attributes).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8765.XML b/docs/Help_Spanish/Topics/XS8765.XML
deleted file mode 100644
index b66ac66794..0000000000
--- a/docs/Help_Spanish/Topics/XS8765.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8765
-
-XS8765
-
-
-
- Warning XS8765
-
- Nullability of type of parameter '{0}' doesn't match overridden member (possibly because of nullability attributes).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8766.XML b/docs/Help_Spanish/Topics/XS8766.XML
deleted file mode 100644
index 0f69e00287..0000000000
--- a/docs/Help_Spanish/Topics/XS8766.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8766
-
-XS8766
-
-
-
- Warning XS8766
-
- Nullability of reference types in return type of '{0}' doesn't match implicitly implemented member '{1}' (possibly because of nullability attributes).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8767.XML b/docs/Help_Spanish/Topics/XS8767.XML
deleted file mode 100644
index d6216e3935..0000000000
--- a/docs/Help_Spanish/Topics/XS8767.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8767
-
-XS8767
-
-
-
- Warning XS8767
-
- Nullability of reference types in type of parameter '{0}' of '{1}' doesn't match implicitly implemented member '{2}' (possibly because of nullability attributes).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8768.XML b/docs/Help_Spanish/Topics/XS8768.XML
deleted file mode 100644
index 7576bb6055..0000000000
--- a/docs/Help_Spanish/Topics/XS8768.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8768
-
-XS8768
-
-
-
- Warning XS8768
-
- Nullability of reference types in return type doesn't match implemented member '{0}' (possibly because of nullability attributes).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8769.XML b/docs/Help_Spanish/Topics/XS8769.XML
deleted file mode 100644
index cf34fbabd5..0000000000
--- a/docs/Help_Spanish/Topics/XS8769.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8769
-
-XS8769
-
-
-
- Warning XS8769
-
- Nullability of reference types in type of parameter '{0}' doesn't match implemented member '{1}' (possibly because of nullability attributes).
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8770.XML b/docs/Help_Spanish/Topics/XS8770.XML
deleted file mode 100644
index 2e7b56f692..0000000000
--- a/docs/Help_Spanish/Topics/XS8770.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8770
-
-XS8770
-
-
-
- Warning XS8770
-
- Method '{0}' lacks `[DoesNotReturn]` annotation to match implemented or overridden member.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8771.XML b/docs/Help_Spanish/Topics/XS8771.XML
deleted file mode 100644
index 84496d5dce..0000000000
--- a/docs/Help_Spanish/Topics/XS8771.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8771
-
-XS8771
-
-
-
- Error XS8771
-
- Output directory could not be determined
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8772.XML b/docs/Help_Spanish/Topics/XS8772.XML
deleted file mode 100644
index 0dedee0514..0000000000
--- a/docs/Help_Spanish/Topics/XS8772.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8772
-
-XS8772
-
-
-
- Error XS8772
-
- stdin argument '-' is specified, but input has not been redirected from the standard input stream.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8773.XML b/docs/Help_Spanish/Topics/XS8773.XML
deleted file mode 100644
index 7105e5355e..0000000000
--- a/docs/Help_Spanish/Topics/XS8773.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8773
-
-XS8773
-
-
-
- Error XS8773
-
- Feature '{0}' is not available in X# 9.0. Please use language version {1} or greater.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8774.XML b/docs/Help_Spanish/Topics/XS8774.XML
deleted file mode 100644
index ce3a684a8f..0000000000
--- a/docs/Help_Spanish/Topics/XS8774.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8774
-
-XS8774
-
-
-
- Warning XS8774
-
- Member '{0}' must have a non-null value when exiting.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8775.XML b/docs/Help_Spanish/Topics/XS8775.XML
deleted file mode 100644
index ff4c36c0c0..0000000000
--- a/docs/Help_Spanish/Topics/XS8775.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8775
-
-XS8775
-
-
-
- Warning XS8775
-
- Member '{0}' must have a non-null value when exiting with '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8776.XML b/docs/Help_Spanish/Topics/XS8776.XML
deleted file mode 100644
index fccb7a5fd4..0000000000
--- a/docs/Help_Spanish/Topics/XS8776.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8776
-
-XS8776
-
-
-
- Warning XS8776
-
- Member '{0}' cannot be used in this attribute.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8777.XML b/docs/Help_Spanish/Topics/XS8777.XML
deleted file mode 100644
index ba8db89846..0000000000
--- a/docs/Help_Spanish/Topics/XS8777.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8777
-
-XS8777
-
-
-
- Warning XS8777
-
- Parameter '{0}' must have a non-null value when exiting.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8778.XML b/docs/Help_Spanish/Topics/XS8778.XML
deleted file mode 100644
index 6ae7cbf323..0000000000
--- a/docs/Help_Spanish/Topics/XS8778.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8778
-
-XS8778
-
-
-
- Warning XS8778
-
- Constant value '{0}' may overflow '{1}' at runtime (use 'unchecked' syntax to override)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8779.XML b/docs/Help_Spanish/Topics/XS8779.XML
deleted file mode 100644
index eedaa7cba5..0000000000
--- a/docs/Help_Spanish/Topics/XS8779.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8779
-
-XS8779
-
-
-
- Error XS8779
-
- '{0}' is already listed in the interface list on type '{2}' as '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8780.XML b/docs/Help_Spanish/Topics/XS8780.XML
deleted file mode 100644
index 6a946e2807..0000000000
--- a/docs/Help_Spanish/Topics/XS8780.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8780
-
-XS8780
-
-
-
- Error XS8780
-
- A variable may not be declared within a 'not' or 'or' pattern.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8781.XML b/docs/Help_Spanish/Topics/XS8781.XML
deleted file mode 100644
index a3d019006c..0000000000
--- a/docs/Help_Spanish/Topics/XS8781.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8781
-
-XS8781
-
-
-
- Error XS8781
-
- Relational patterns may not be used for a value of type '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8782.XML b/docs/Help_Spanish/Topics/XS8782.XML
deleted file mode 100644
index fc70a2c9b3..0000000000
--- a/docs/Help_Spanish/Topics/XS8782.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8782
-
-XS8782
-
-
-
- Error XS8782
-
- Relational patterns may not be used for a floating-point NaN.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8783.XML b/docs/Help_Spanish/Topics/XS8783.XML
deleted file mode 100644
index 0ce6dd54f0..0000000000
--- a/docs/Help_Spanish/Topics/XS8783.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8783
-
-XS8783
-
-
-
- Error XS8783
-
- Local function '{0}' must be 'static' in order to use the Conditional attribute
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8784.XML b/docs/Help_Spanish/Topics/XS8784.XML
deleted file mode 100644
index 2cf5eef91c..0000000000
--- a/docs/Help_Spanish/Topics/XS8784.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8784
-
-XS8784
-
-
-
- Warning XS8784
-
- Generator '{0}' failed to initialize. It will not contribute to the output and compilation errors may occur as a result. Exception was of type '{1}' with message '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8785.XML b/docs/Help_Spanish/Topics/XS8785.XML
deleted file mode 100644
index fdb6e8a0b3..0000000000
--- a/docs/Help_Spanish/Topics/XS8785.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8785
-
-XS8785
-
-
-
- Warning XS8785
-
- Generator '{0}' failed to generate source. It will not contribute to the output and compilation errors may occur as a result. Exception was of type '{1}' with message '{2}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8786.XML b/docs/Help_Spanish/Topics/XS8786.XML
deleted file mode 100644
index 87bef7310f..0000000000
--- a/docs/Help_Spanish/Topics/XS8786.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8786
-
-XS8786
-
-
-
- Error XS8786
-
- Calling convention of '{0}' is not compatible with '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8787.XML b/docs/Help_Spanish/Topics/XS8787.XML
deleted file mode 100644
index b381a15191..0000000000
--- a/docs/Help_Spanish/Topics/XS8787.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8787
-
-XS8787
-
-
-
- Error XS8787
-
- Cannot convert method to function pointer (Are you missing a '@'?)
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8788.XML b/docs/Help_Spanish/Topics/XS8788.XML
deleted file mode 100644
index af4865ad6e..0000000000
--- a/docs/Help_Spanish/Topics/XS8788.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8788
-
-XS8788
-
-
-
- Error XS8788
-
- Cannot use an extension method with a receiver as the target of a '@' operator.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8789.XML b/docs/Help_Spanish/Topics/XS8789.XML
deleted file mode 100644
index 7b20377c7d..0000000000
--- a/docs/Help_Spanish/Topics/XS8789.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8789
-
-XS8789
-
-
-
- Error XS8789
-
- The type of a local declared in a fixed statement cannot be a function pointer type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8790.XML b/docs/Help_Spanish/Topics/XS8790.XML
deleted file mode 100644
index 86474b6f14..0000000000
--- a/docs/Help_Spanish/Topics/XS8790.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8790
-
-XS8790
-
-
-
- Error XS8790
-
- An expression tree may not contain a pattern System.Index or System.Range indexer access
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8791.XML b/docs/Help_Spanish/Topics/XS8791.XML
deleted file mode 100644
index fc6ebbbab6..0000000000
--- a/docs/Help_Spanish/Topics/XS8791.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8791
-
-XS8791
-
-
-
- Error XS8791
-
- An expression tree may not contain a from-end index ('^') expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8792.XML b/docs/Help_Spanish/Topics/XS8792.XML
deleted file mode 100644
index 7970102de2..0000000000
--- a/docs/Help_Spanish/Topics/XS8792.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8792
-
-XS8792
-
-
-
- Error XS8792
-
- An expression tree may not contain a range ('..') expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8793.XML b/docs/Help_Spanish/Topics/XS8793.XML
deleted file mode 100644
index 30a9144652..0000000000
--- a/docs/Help_Spanish/Topics/XS8793.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8793
-
-XS8793
-
-
-
- Warning XS8793
-
- The given expression always matches the provided pattern.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8794.XML b/docs/Help_Spanish/Topics/XS8794.XML
deleted file mode 100644
index b9e4af2ae6..0000000000
--- a/docs/Help_Spanish/Topics/XS8794.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8794
-
-XS8794
-
-
-
- Warning XS8794
-
- An expression of type '{0}' always matches the provided pattern.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8795.XML b/docs/Help_Spanish/Topics/XS8795.XML
deleted file mode 100644
index 8cbc7494d8..0000000000
--- a/docs/Help_Spanish/Topics/XS8795.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8795
-
-XS8795
-
-
-
- Error XS8795
-
- Partial method '{0}' must have an implementation part because it has accessibility modifiers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8796.XML b/docs/Help_Spanish/Topics/XS8796.XML
deleted file mode 100644
index e993a3b377..0000000000
--- a/docs/Help_Spanish/Topics/XS8796.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8796
-
-XS8796
-
-
-
- Error XS8796
-
- Partial method '{0}' must have accessibility modifiers because it has a non-void return type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8797.XML b/docs/Help_Spanish/Topics/XS8797.XML
deleted file mode 100644
index e237e03bc8..0000000000
--- a/docs/Help_Spanish/Topics/XS8797.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8797
-
-XS8797
-
-
-
- Error XS8797
-
- Partial method '{0}' must have accessibility modifiers because it has 'out' parameters.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8798.XML b/docs/Help_Spanish/Topics/XS8798.XML
deleted file mode 100644
index 0b184472b4..0000000000
--- a/docs/Help_Spanish/Topics/XS8798.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8798
-
-XS8798
-
-
-
- Error XS8798
-
- Partial method '{0}' must have accessibility modifiers because it has a 'virtual', 'override', 'sealed', 'new', or 'extern' modifier.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8799.XML b/docs/Help_Spanish/Topics/XS8799.XML
deleted file mode 100644
index b63c7ccc25..0000000000
--- a/docs/Help_Spanish/Topics/XS8799.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8799
-
-XS8799
-
-
-
- Error XS8799
-
- Both partial method declarations must have identical accessibility modifiers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8800.XML b/docs/Help_Spanish/Topics/XS8800.XML
deleted file mode 100644
index 9b89edd1f4..0000000000
--- a/docs/Help_Spanish/Topics/XS8800.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8800
-
-XS8800
-
-
-
- Error XS8800
-
- Both partial method declarations must have identical combinations of 'virtual', 'override', 'sealed', and 'new' modifiers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8801.XML b/docs/Help_Spanish/Topics/XS8801.XML
deleted file mode 100644
index fc073505c1..0000000000
--- a/docs/Help_Spanish/Topics/XS8801.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8801
-
-XS8801
-
-
-
- Error XS8801
-
- Cannot use local variable or local function '{0}' declared in a top-level statement in this context.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8802.XML b/docs/Help_Spanish/Topics/XS8802.XML
deleted file mode 100644
index f402e1c9c3..0000000000
--- a/docs/Help_Spanish/Topics/XS8802.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8802
-
-XS8802
-
-
-
- Error XS8802
-
- Only one compilation unit can have top-level statements.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8803.XML b/docs/Help_Spanish/Topics/XS8803.XML
deleted file mode 100644
index fb45559231..0000000000
--- a/docs/Help_Spanish/Topics/XS8803.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8803
-
-XS8803
-
-
-
- Error XS8803
-
- Top-level statements must precede namespace and type declarations.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8804.XML b/docs/Help_Spanish/Topics/XS8804.XML
deleted file mode 100644
index e71f243e0f..0000000000
--- a/docs/Help_Spanish/Topics/XS8804.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8804
-
-XS8804
-
-
-
- Error XS8804
-
- Cannot specify /main if there is a compilation unit with top-level statements.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8805.XML b/docs/Help_Spanish/Topics/XS8805.XML
deleted file mode 100644
index 2980d46ee0..0000000000
--- a/docs/Help_Spanish/Topics/XS8805.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8805
-
-XS8805
-
-
-
- Error XS8805
-
- Program using top-level statements must be an executable.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8806.XML b/docs/Help_Spanish/Topics/XS8806.XML
deleted file mode 100644
index 958cbc146d..0000000000
--- a/docs/Help_Spanish/Topics/XS8806.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8806
-
-XS8806
-
-
-
- Error XS8806
-
- The calling convention of '{0}' is not supported by the language.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8807.XML b/docs/Help_Spanish/Topics/XS8807.XML
deleted file mode 100644
index a4684ee262..0000000000
--- a/docs/Help_Spanish/Topics/XS8807.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8807
-
-XS8807
-
-
-
- Error XS8807
-
- '{0}' is not a valid calling convention specifier for a function pointer.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8808.XML b/docs/Help_Spanish/Topics/XS8808.XML
deleted file mode 100644
index 97e319ca98..0000000000
--- a/docs/Help_Spanish/Topics/XS8808.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8808
-
-XS8808
-
-
-
- Error XS8808
-
- '{0}' is not a valid function pointer return type modifier. Valid modifiers are 'ref' and 'ref readonly'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8809.XML b/docs/Help_Spanish/Topics/XS8809.XML
deleted file mode 100644
index 03f17f5654..0000000000
--- a/docs/Help_Spanish/Topics/XS8809.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8809
-
-XS8809
-
-
-
- Error XS8809
-
- A return type can only have one '{0}' modifier.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8810.XML b/docs/Help_Spanish/Topics/XS8810.XML
deleted file mode 100644
index e2e0e7e599..0000000000
--- a/docs/Help_Spanish/Topics/XS8810.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8810
-
-XS8810
-
-
-
- Error XS8810
-
- '@' on methods cannot be used in expression trees
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8811.XML b/docs/Help_Spanish/Topics/XS8811.XML
deleted file mode 100644
index 16a84063f2..0000000000
--- a/docs/Help_Spanish/Topics/XS8811.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8811
-
-XS8811
-
-
-
- Error XS8811
-
- Cannot convert @method '{0}' to delegate type '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8812.XML b/docs/Help_Spanish/Topics/XS8812.XML
deleted file mode 100644
index b5d5909b2a..0000000000
--- a/docs/Help_Spanish/Topics/XS8812.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8812
-
-XS8812
-
-
-
- Error XS8812
-
- Cannot convert @method '{0}' to non-function pointer type '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8813.XML b/docs/Help_Spanish/Topics/XS8813.XML
deleted file mode 100644
index 6777640865..0000000000
--- a/docs/Help_Spanish/Topics/XS8813.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8813
-
-XS8813
-
-
-
- Error XS8813
-
- A module initializer must be an ordinary member method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8814.XML b/docs/Help_Spanish/Topics/XS8814.XML
deleted file mode 100644
index e5ef56ccc2..0000000000
--- a/docs/Help_Spanish/Topics/XS8814.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8814
-
-XS8814
-
-
-
- Error XS8814
-
- Module initializer method '{0}' must be accessible at the module level
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8815.XML b/docs/Help_Spanish/Topics/XS8815.XML
deleted file mode 100644
index e74ac6fa2d..0000000000
--- a/docs/Help_Spanish/Topics/XS8815.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8815
-
-XS8815
-
-
-
- Error XS8815
-
- Module initializer method '{0}' must be static, must have no parameters, and must return 'void'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8816.XML b/docs/Help_Spanish/Topics/XS8816.XML
deleted file mode 100644
index b61870fce2..0000000000
--- a/docs/Help_Spanish/Topics/XS8816.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8816
-
-XS8816
-
-
-
- Error XS8816
-
- Module initializer method '{0}' must not be generic and must not be contained in a generic type
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8817.XML b/docs/Help_Spanish/Topics/XS8817.XML
deleted file mode 100644
index fa19925236..0000000000
--- a/docs/Help_Spanish/Topics/XS8817.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8817
-
-XS8817
-
-
-
- Error XS8817
-
- Both partial method declarations must have the same return type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8818.XML b/docs/Help_Spanish/Topics/XS8818.XML
deleted file mode 100644
index 17a76b5bc6..0000000000
--- a/docs/Help_Spanish/Topics/XS8818.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8818
-
-XS8818
-
-
-
- Error XS8818
-
- Partial method declarations must have matching ref return values.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8819.XML b/docs/Help_Spanish/Topics/XS8819.XML
deleted file mode 100644
index 4efb195a9c..0000000000
--- a/docs/Help_Spanish/Topics/XS8819.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8819
-
-XS8819
-
-
-
- Warning XS8819
-
- Nullability of reference types in return type doesn't match partial method declaration.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8820.XML b/docs/Help_Spanish/Topics/XS8820.XML
deleted file mode 100644
index fed19f4af7..0000000000
--- a/docs/Help_Spanish/Topics/XS8820.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8820
-
-XS8820
-
-
-
- Error XS8820
-
- A static anonymous function cannot contain a reference to '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8821.XML b/docs/Help_Spanish/Topics/XS8821.XML
deleted file mode 100644
index 452e04c4ee..0000000000
--- a/docs/Help_Spanish/Topics/XS8821.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8821
-
-XS8821
-
-
-
- Error XS8821
-
- A static anonymous function cannot contain a reference to 'SELF' or 'SUPER'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8822.XML b/docs/Help_Spanish/Topics/XS8822.XML
deleted file mode 100644
index 444070b0dd..0000000000
--- a/docs/Help_Spanish/Topics/XS8822.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8822
-
-XS8822
-
-
-
- Error XS8822
-
- Method '{0}' specifies a 'default' constraint for type parameter '{1}', but corresponding type parameter '{2}' of overridden or explicitly implemented method '{3}' is constrained to a reference type or a value type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8823.XML b/docs/Help_Spanish/Topics/XS8823.XML
deleted file mode 100644
index 7249bb7073..0000000000
--- a/docs/Help_Spanish/Topics/XS8823.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8823
-
-XS8823
-
-
-
- Error XS8823
-
- The 'default' constraint is valid on override and explicit interface implementation methods only.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8824.XML b/docs/Help_Spanish/Topics/XS8824.XML
deleted file mode 100644
index c33b896398..0000000000
--- a/docs/Help_Spanish/Topics/XS8824.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8824
-
-XS8824
-
-
-
- Warning XS8824
-
- Parameter '{0}' must have a non-null value when exiting because parameter '{1}' is non-null.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8825.XML b/docs/Help_Spanish/Topics/XS8825.XML
deleted file mode 100644
index f9e6f916e5..0000000000
--- a/docs/Help_Spanish/Topics/XS8825.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8825
-
-XS8825
-
-
-
- Warning XS8825
-
- Return value must be non-null because parameter '{0}' is non-null.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8830.XML b/docs/Help_Spanish/Topics/XS8830.XML
deleted file mode 100644
index 43ae97be58..0000000000
--- a/docs/Help_Spanish/Topics/XS8830.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8830
-
-XS8830
-
-
-
- Error XS8830
-
- '{0}': Target runtime doesn't support covariant return types in overrides. Return type must be '{2}' to match overridden member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8831.XML b/docs/Help_Spanish/Topics/XS8831.XML
deleted file mode 100644
index fa73f2cb27..0000000000
--- a/docs/Help_Spanish/Topics/XS8831.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8831
-
-XS8831
-
-
-
- Error XS8831
-
- '{0}': Target runtime doesn't support covariant types in overrides. Type must be '{2}' to match overridden member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8846.XML b/docs/Help_Spanish/Topics/XS8846.XML
deleted file mode 100644
index f759da6041..0000000000
--- a/docs/Help_Spanish/Topics/XS8846.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8846
-
-XS8846
-
-
-
- Warning XS8846
-
- The switch expression does not handle all possible values of its input type (it is not exhaustive). For example, the pattern '{0}' is not covered. However, a pattern with a 'when' clause might successfully match this value.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8847.XML b/docs/Help_Spanish/Topics/XS8847.XML
deleted file mode 100644
index 20ac2715b3..0000000000
--- a/docs/Help_Spanish/Topics/XS8847.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8847
-
-XS8847
-
-
-
- Warning XS8847
-
- The switch expression does not handle some null inputs (it is not exhaustive). For example, the pattern '{0}' is not covered. However, a pattern with a 'when' clause might successfully match this value.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8848.XML b/docs/Help_Spanish/Topics/XS8848.XML
deleted file mode 100644
index 4b67424505..0000000000
--- a/docs/Help_Spanish/Topics/XS8848.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8848
-
-XS8848
-
-
-
- Warning XS8848
-
- Operator '{0}' cannot be used here due to precedence. Use parentheses to disambiguate.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8849.XML b/docs/Help_Spanish/Topics/XS8849.XML
deleted file mode 100644
index 2f09c91ce5..0000000000
--- a/docs/Help_Spanish/Topics/XS8849.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8849
-
-XS8849
-
-
-
- Error XS8849
-
- An expression tree may not contain a with-expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8850.XML b/docs/Help_Spanish/Topics/XS8850.XML
deleted file mode 100644
index 95d14c6938..0000000000
--- a/docs/Help_Spanish/Topics/XS8850.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8850
-
-XS8850
-
-
-
- Warning XS8850
-
- The assembly '{0}' containing type '{1}' references .NET Framework, which is not supported.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8851.XML b/docs/Help_Spanish/Topics/XS8851.XML
deleted file mode 100644
index 6391408949..0000000000
--- a/docs/Help_Spanish/Topics/XS8851.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8851
-
-XS8851
-
-
-
- Warning XS8851
-
- '{0}' defines 'Equals' but not 'GetHashCode'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8852.XML b/docs/Help_Spanish/Topics/XS8852.XML
deleted file mode 100644
index 8bf4384be8..0000000000
--- a/docs/Help_Spanish/Topics/XS8852.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8852
-
-XS8852
-
-
-
- Error XS8852
-
- Init-only property or indexer '{0}' can only be assigned in an object initializer, or on 'SELF' or 'SUPER' in an instance constructor or an 'init' accessor.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8853.XML b/docs/Help_Spanish/Topics/XS8853.XML
deleted file mode 100644
index 95493280e9..0000000000
--- a/docs/Help_Spanish/Topics/XS8853.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8853
-
-XS8853
-
-
-
- Error XS8853
-
- '{0}' must match by init-only of overridden member '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8854.XML b/docs/Help_Spanish/Topics/XS8854.XML
deleted file mode 100644
index 3ba71eb66a..0000000000
--- a/docs/Help_Spanish/Topics/XS8854.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8854
-
-XS8854
-
-
-
- Error XS8854
-
- '{0}' does not implement interface member '{1}'. '{2}' cannot implement '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8855.XML b/docs/Help_Spanish/Topics/XS8855.XML
deleted file mode 100644
index c14174687c..0000000000
--- a/docs/Help_Spanish/Topics/XS8855.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8855
-
-XS8855
-
-
-
- Error XS8855
-
- Accessors '{0}' and '{1}' should both be init-only or neither
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8856.XML b/docs/Help_Spanish/Topics/XS8856.XML
deleted file mode 100644
index 921101cfe1..0000000000
--- a/docs/Help_Spanish/Topics/XS8856.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8856
-
-XS8856
-
-
-
- Error XS8856
-
- The 'init' accessor is not valid on static members
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8857.XML b/docs/Help_Spanish/Topics/XS8857.XML
deleted file mode 100644
index e552cf7b23..0000000000
--- a/docs/Help_Spanish/Topics/XS8857.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8857
-
-XS8857
-
-
-
- Error XS8857
-
- The receiver of a `with` expression must have a non-void type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8858.XML b/docs/Help_Spanish/Topics/XS8858.XML
deleted file mode 100644
index 5dcba21438..0000000000
--- a/docs/Help_Spanish/Topics/XS8858.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8858
-
-XS8858
-
-
-
- Error XS8858
-
- The receiver type '{0}' is not a valid record type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8859.XML b/docs/Help_Spanish/Topics/XS8859.XML
deleted file mode 100644
index fa8b4f9c31..0000000000
--- a/docs/Help_Spanish/Topics/XS8859.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8859
-
-XS8859
-
-
-
- Error XS8859
-
- Members named 'Clone' are disallowed in records.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8860.XML b/docs/Help_Spanish/Topics/XS8860.XML
deleted file mode 100644
index ad1a1b88a1..0000000000
--- a/docs/Help_Spanish/Topics/XS8860.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8860
-
-XS8860
-
-
-
- Warning XS8860
-
- Types and aliases should not be named 'record'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8861.XML b/docs/Help_Spanish/Topics/XS8861.XML
deleted file mode 100644
index 3a97991ea4..0000000000
--- a/docs/Help_Spanish/Topics/XS8861.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8861
-
-XS8861
-
-
-
- Error XS8861
-
- Unexpected argument list.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8862.XML b/docs/Help_Spanish/Topics/XS8862.XML
deleted file mode 100644
index 0b614b89ad..0000000000
--- a/docs/Help_Spanish/Topics/XS8862.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8862
-
-XS8862
-
-
-
- Error XS8862
-
- A constructor declared in a record with parameter list must have 'SELF' constructor initializer.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8863.XML b/docs/Help_Spanish/Topics/XS8863.XML
deleted file mode 100644
index a5635dc021..0000000000
--- a/docs/Help_Spanish/Topics/XS8863.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8863
-
-XS8863
-
-
-
- Error XS8863
-
- Only a single record partial declaration may have a parameter list
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8864.XML b/docs/Help_Spanish/Topics/XS8864.XML
deleted file mode 100644
index ae9356dc2c..0000000000
--- a/docs/Help_Spanish/Topics/XS8864.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8864
-
-XS8864
-
-
-
- Error XS8864
-
- Records may only inherit from object or another record
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8865.XML b/docs/Help_Spanish/Topics/XS8865.XML
deleted file mode 100644
index 02699c93cd..0000000000
--- a/docs/Help_Spanish/Topics/XS8865.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8865
-
-XS8865
-
-
-
- Error XS8865
-
- Only records may inherit from records.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8866.XML b/docs/Help_Spanish/Topics/XS8866.XML
deleted file mode 100644
index 3841a20fb6..0000000000
--- a/docs/Help_Spanish/Topics/XS8866.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8866
-
-XS8866
-
-
-
- Error XS8866
-
- Record member '{0}' must be a readable instance property of type '{1}' to match positional parameter '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8867.XML b/docs/Help_Spanish/Topics/XS8867.XML
deleted file mode 100644
index 56cb8e5f90..0000000000
--- a/docs/Help_Spanish/Topics/XS8867.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8867
-
-XS8867
-
-
-
- Error XS8867
-
- No accessible copy constructor found in base type '{0}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8868.XML b/docs/Help_Spanish/Topics/XS8868.XML
deleted file mode 100644
index 6d174ed393..0000000000
--- a/docs/Help_Spanish/Topics/XS8868.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8868
-
-XS8868
-
-
-
- Error XS8868
-
- A copy constructor in a record must call a copy constructor of the base, or a parameterless object constructor if the record inherits from object.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8869.XML b/docs/Help_Spanish/Topics/XS8869.XML
deleted file mode 100644
index 2c5351d77f..0000000000
--- a/docs/Help_Spanish/Topics/XS8869.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8869
-
-XS8869
-
-
-
- Error XS8869
-
- '{0}' does not override expected method from 'object'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8870.XML b/docs/Help_Spanish/Topics/XS8870.XML
deleted file mode 100644
index dc9142da7f..0000000000
--- a/docs/Help_Spanish/Topics/XS8870.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8870
-
-XS8870
-
-
-
- Error XS8870
-
- '{0}' cannot be sealed because containing record is not sealed.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8871.XML b/docs/Help_Spanish/Topics/XS8871.XML
deleted file mode 100644
index 3ba612d5de..0000000000
--- a/docs/Help_Spanish/Topics/XS8871.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8871
-
-XS8871
-
-
-
- Error XS8871
-
- '{0}' does not override expected method from '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8872.XML b/docs/Help_Spanish/Topics/XS8872.XML
deleted file mode 100644
index 81ad10fe28..0000000000
--- a/docs/Help_Spanish/Topics/XS8872.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8872
-
-XS8872
-
-
-
- Error XS8872
-
- '{0}' must allow overriding because the containing record is not sealed.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8873.XML b/docs/Help_Spanish/Topics/XS8873.XML
deleted file mode 100644
index 89c8df7e62..0000000000
--- a/docs/Help_Spanish/Topics/XS8873.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8873
-
-XS8873
-
-
-
- Error XS8873
-
- Record member '{0}' must be public.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8874.XML b/docs/Help_Spanish/Topics/XS8874.XML
deleted file mode 100644
index 33f31d4bf4..0000000000
--- a/docs/Help_Spanish/Topics/XS8874.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8874
-
-XS8874
-
-
-
- Error XS8874
-
- Record member '{0}' must return '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8875.XML b/docs/Help_Spanish/Topics/XS8875.XML
deleted file mode 100644
index 1285b6b08c..0000000000
--- a/docs/Help_Spanish/Topics/XS8875.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8875
-
-XS8875
-
-
-
- Error XS8875
-
- Record member '{0}' must be protected.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8876.XML b/docs/Help_Spanish/Topics/XS8876.XML
deleted file mode 100644
index 818662848c..0000000000
--- a/docs/Help_Spanish/Topics/XS8876.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8876
-
-XS8876
-
-
-
- Error XS8876
-
- '{0}' does not override expected property from '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8877.XML b/docs/Help_Spanish/Topics/XS8877.XML
deleted file mode 100644
index 5d679cc3b8..0000000000
--- a/docs/Help_Spanish/Topics/XS8877.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8877
-
-XS8877
-
-
-
- Error XS8877
-
- Record member '{0}' may not be static.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8878.XML b/docs/Help_Spanish/Topics/XS8878.XML
deleted file mode 100644
index ed3e6cf79b..0000000000
--- a/docs/Help_Spanish/Topics/XS8878.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8878
-
-XS8878
-
-
-
- Error XS8878
-
- A copy constructor '{0}' must be public or protected because the record is not sealed.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8879.XML b/docs/Help_Spanish/Topics/XS8879.XML
deleted file mode 100644
index d83f5be636..0000000000
--- a/docs/Help_Spanish/Topics/XS8879.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8879
-
-XS8879
-
-
-
- Error XS8879
-
- Record member '{0}' must be private.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8880.XML b/docs/Help_Spanish/Topics/XS8880.XML
deleted file mode 100644
index aa095ede79..0000000000
--- a/docs/Help_Spanish/Topics/XS8880.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8880
-
-XS8880
-
-
-
- Warning XS8880
-
- Auto-implemented property '{0}' must be fully assigned before control is returned to the caller.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8881.XML b/docs/Help_Spanish/Topics/XS8881.XML
deleted file mode 100644
index ea25e7a50e..0000000000
--- a/docs/Help_Spanish/Topics/XS8881.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8881
-
-XS8881
-
-
-
- Warning XS8881
-
- Field '{0}' must be fully assigned before control is returned to the caller
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8882.XML b/docs/Help_Spanish/Topics/XS8882.XML
deleted file mode 100644
index 21fc17db75..0000000000
--- a/docs/Help_Spanish/Topics/XS8882.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8882
-
-XS8882
-
-
-
- Warning XS8882
-
- The out parameter '{0}' must be assigned to before control leaves the current method
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8883.XML b/docs/Help_Spanish/Topics/XS8883.XML
deleted file mode 100644
index 5ced4737b5..0000000000
--- a/docs/Help_Spanish/Topics/XS8883.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8883
-
-XS8883
-
-
-
- Warning XS8883
-
- Use of possibly unassigned auto-implemented property '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8884.XML b/docs/Help_Spanish/Topics/XS8884.XML
deleted file mode 100644
index 8c41cf2908..0000000000
--- a/docs/Help_Spanish/Topics/XS8884.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8884
-
-XS8884
-
-
-
- Warning XS8884
-
- Use of possibly unassigned field '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8885.XML b/docs/Help_Spanish/Topics/XS8885.XML
deleted file mode 100644
index b23daa6637..0000000000
--- a/docs/Help_Spanish/Topics/XS8885.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8885
-
-XS8885
-
-
-
- Warning XS8885
-
- The 'SELF' object cannot be used before all of its fields have been assigned
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8886.XML b/docs/Help_Spanish/Topics/XS8886.XML
deleted file mode 100644
index d138fd1448..0000000000
--- a/docs/Help_Spanish/Topics/XS8886.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8886
-
-XS8886
-
-
-
- Warning XS8886
-
- Use of unassigned out parameter '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8887.XML b/docs/Help_Spanish/Topics/XS8887.XML
deleted file mode 100644
index bfcbe839c9..0000000000
--- a/docs/Help_Spanish/Topics/XS8887.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8887
-
-XS8887
-
-
-
- Warning XS8887
-
- Use of unassigned local variable '{0}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8888.XML b/docs/Help_Spanish/Topics/XS8888.XML
deleted file mode 100644
index 8fa0e7ef94..0000000000
--- a/docs/Help_Spanish/Topics/XS8888.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8888
-
-XS8888
-
-
-
- Error XS8888
-
- 'managed' calling convention cannot be combined with unmanaged calling convention specifiers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8889.XML b/docs/Help_Spanish/Topics/XS8889.XML
deleted file mode 100644
index 22dd58f18c..0000000000
--- a/docs/Help_Spanish/Topics/XS8889.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8889
-
-XS8889
-
-
-
- Error XS8889
-
- The target runtime doesn't support extensible or runtime-environment default calling conventions.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8890.XML b/docs/Help_Spanish/Topics/XS8890.XML
deleted file mode 100644
index d0f1fc3ae1..0000000000
--- a/docs/Help_Spanish/Topics/XS8890.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8890
-
-XS8890
-
-
-
- Error XS8890
-
- Type '{0}' is not defined.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8891.XML b/docs/Help_Spanish/Topics/XS8891.XML
deleted file mode 100644
index c5a6c5de5c..0000000000
--- a/docs/Help_Spanish/Topics/XS8891.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8891
-
-XS8891
-
-
-
- Error XS8891
-
- Type '{0}' must be public to be used as a calling convention.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8892.XML b/docs/Help_Spanish/Topics/XS8892.XML
deleted file mode 100644
index f527fb2ad0..0000000000
--- a/docs/Help_Spanish/Topics/XS8892.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8892
-
-XS8892
-
-
-
- Warning XS8892
-
- Method '{0}' will not be used as an entry point because a synchronous entry point '{1}' was found.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8893.XML b/docs/Help_Spanish/Topics/XS8893.XML
deleted file mode 100644
index 44292c47a1..0000000000
--- a/docs/Help_Spanish/Topics/XS8893.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8893
-
-XS8893
-
-
-
- Error XS8893
-
- '{0}' is not a valid calling convention type for 'UnmanagedCallersOnly'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8894.XML b/docs/Help_Spanish/Topics/XS8894.XML
deleted file mode 100644
index 19b9381644..0000000000
--- a/docs/Help_Spanish/Topics/XS8894.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8894
-
-XS8894
-
-
-
- Error XS8894
-
- Cannot use '{0}' as a {1} type on a method attributed with 'UnmanagedCallersOnly'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8895.XML b/docs/Help_Spanish/Topics/XS8895.XML
deleted file mode 100644
index a34b3573ce..0000000000
--- a/docs/Help_Spanish/Topics/XS8895.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8895
-
-XS8895
-
-
-
- Error XS8895
-
- Methods attributed with 'UnmanagedCallersOnly' cannot have generic type parameters and cannot be declared in a generic type.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8896.XML b/docs/Help_Spanish/Topics/XS8896.XML
deleted file mode 100644
index fc3f5d323f..0000000000
--- a/docs/Help_Spanish/Topics/XS8896.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8896
-
-XS8896
-
-
-
- Error XS8896
-
- 'UnmanagedCallersOnly' can only be applied to ordinary static methods or static local functions.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8897.XML b/docs/Help_Spanish/Topics/XS8897.XML
deleted file mode 100644
index a1fffe97ca..0000000000
--- a/docs/Help_Spanish/Topics/XS8897.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8897
-
-XS8897
-
-
-
- Warning XS8897
-
- '{0}': static types cannot be used as parameters
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8898.XML b/docs/Help_Spanish/Topics/XS8898.XML
deleted file mode 100644
index 7a99ca3072..0000000000
--- a/docs/Help_Spanish/Topics/XS8898.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8898
-
-XS8898
-
-
-
- Warning XS8898
-
- '{0}': static types cannot be used as return types
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8899.XML b/docs/Help_Spanish/Topics/XS8899.XML
deleted file mode 100644
index a844471370..0000000000
--- a/docs/Help_Spanish/Topics/XS8899.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8899
-
-XS8899
-
-
-
- Error XS8899
-
- Application entry points cannot be attributed with 'UnmanagedCallersOnly'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8900.XML b/docs/Help_Spanish/Topics/XS8900.XML
deleted file mode 100644
index 37e92579bc..0000000000
--- a/docs/Help_Spanish/Topics/XS8900.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8900
-
-XS8900
-
-
-
- Error XS8900
-
- Module initializer cannot be attributed with 'UnmanagedCallersOnly'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8901.XML b/docs/Help_Spanish/Topics/XS8901.XML
deleted file mode 100644
index e355189919..0000000000
--- a/docs/Help_Spanish/Topics/XS8901.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8901
-
-XS8901
-
-
-
- Error XS8901
-
- '{0}' is attributed with 'UnmanagedCallersOnly' and cannot be called directly. Obtain a function pointer to this method.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8902.XML b/docs/Help_Spanish/Topics/XS8902.XML
deleted file mode 100644
index 91cbfed159..0000000000
--- a/docs/Help_Spanish/Topics/XS8902.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8902
-
-XS8902
-
-
-
- Error XS8902
-
- '{0}' is attributed with 'UnmanagedCallersOnly' and cannot be converted to a delegate type. Obtain a function pointer to this method.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8903.XML b/docs/Help_Spanish/Topics/XS8903.XML
deleted file mode 100644
index d3f60e1111..0000000000
--- a/docs/Help_Spanish/Topics/XS8903.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8903
-
-XS8903
-
-
-
- Error XS8903
-
- 'init' accessors cannot be marked 'readonly'. Mark '{0}' readonly instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8904.XML b/docs/Help_Spanish/Topics/XS8904.XML
deleted file mode 100644
index aaddeee7ed..0000000000
--- a/docs/Help_Spanish/Topics/XS8904.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8904
-
-XS8904
-
-
-
- Error XS8904
-
- Invalid variance: The type parameter '{1}' must be {3} valid on '{0}' unless language version '{4}' or greater is used. '{1}' is {2}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8905.XML b/docs/Help_Spanish/Topics/XS8905.XML
deleted file mode 100644
index b831971a10..0000000000
--- a/docs/Help_Spanish/Topics/XS8905.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8905
-
-XS8905
-
-
-
- Error XS8905
-
- A function pointer cannot be called with named arguments.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8906.XML b/docs/Help_Spanish/Topics/XS8906.XML
deleted file mode 100644
index a6ddf46d8a..0000000000
--- a/docs/Help_Spanish/Topics/XS8906.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8906
-
-XS8906
-
-
-
- Error XS8906
-
- Record equality contract property '{0}' must have a get accessor.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8907.XML b/docs/Help_Spanish/Topics/XS8907.XML
deleted file mode 100644
index 081c4b6826..0000000000
--- a/docs/Help_Spanish/Topics/XS8907.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8907
-
-XS8907
-
-
-
- Warning XS8907
-
- Parameter '{0}' is unread. Did you forget to use it to initialize the property with that name?
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8908.XML b/docs/Help_Spanish/Topics/XS8908.XML
deleted file mode 100644
index 17d3229024..0000000000
--- a/docs/Help_Spanish/Topics/XS8908.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8908
-
-XS8908
-
-
-
- Error XS8908
-
- The type '{0}' may not be used for a field of a record.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8909.XML b/docs/Help_Spanish/Topics/XS8909.XML
deleted file mode 100644
index 1402202cf6..0000000000
--- a/docs/Help_Spanish/Topics/XS8909.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS8909
-
-XS8909
-
-
-
- Warning XS8909
-
- Comparison of function pointers might yield an unexpected result, since pointers to the same function may be distinct.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS8910.XML b/docs/Help_Spanish/Topics/XS8910.XML
deleted file mode 100644
index 31f68ec32a..0000000000
--- a/docs/Help_Spanish/Topics/XS8910.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS8910
-
-XS8910
-
-
-
- Error XS8910
-
- The primary constructor conflicts with the synthesized copy constructor.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9001.xml b/docs/Help_Spanish/Topics/XS9001.xml
deleted file mode 100644
index 67ddb3ec31..0000000000
--- a/docs/Help_Spanish/Topics/XS9001.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9001
-
- XS9001
-
-
-
- Warning XS9001
-
- Use of pointers and fixed-size buffers should be marked as unsafe
-
-
diff --git a/docs/Help_Spanish/Topics/XS9002.xml b/docs/Help_Spanish/Topics/XS9002.xml
deleted file mode 100644
index f63f3f85d8..0000000000
--- a/docs/Help_Spanish/Topics/XS9002.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9002
-
- XS9002
-
-
-
- Error XS9002
-
- Parser: {0}
-
-
diff --git a/docs/Help_Spanish/Topics/XS9003.xml b/docs/Help_Spanish/Topics/XS9003.xml
deleted file mode 100644
index 0783db7471..0000000000
--- a/docs/Help_Spanish/Topics/XS9003.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9003
-
- XS9003
-
-
-
- Error XS9003
-
- Pre-processor: {0}
-
-
diff --git a/docs/Help_Spanish/Topics/XS9004.xml b/docs/Help_Spanish/Topics/XS9004.xml
deleted file mode 100644
index 537f2c7f3b..0000000000
--- a/docs/Help_Spanish/Topics/XS9004.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9004
-
- XS9004
-
-
-
- Warning XS9004
-
- Pre-processor: {0}
-
-
diff --git a/docs/Help_Spanish/Topics/XS9005.xml b/docs/Help_Spanish/Topics/XS9005.xml
deleted file mode 100644
index b64ac56d9a..0000000000
--- a/docs/Help_Spanish/Topics/XS9005.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9005
-
- XS9005
-
-
-
- Error XS9005
-
- Recursive preprocessor rule '#{0}' detected
-
-
diff --git a/docs/Help_Spanish/Topics/XS9006.xml b/docs/Help_Spanish/Topics/XS9006.xml
deleted file mode 100644
index d6bdfc2867..0000000000
--- a/docs/Help_Spanish/Topics/XS9006.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- XS9006
-
- XS9006
-
-
-
- Error XS9006Illegal combination of commandline options:
-
- This error is produced for illegal combinations of commandline options. For example the fox2 command line option MUST be used in the FoxPro dialect and in combination with the memvar commandline option. When one of these two options is not specified you will see the error message:
-
- error XS9006: Illegal combination of commandline options: /fox2 must be combined with the FoxPro dialect and /memvars.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9007.xml b/docs/Help_Spanish/Topics/XS9007.xml
deleted file mode 100644
index 23e84c5d70..0000000000
--- a/docs/Help_Spanish/Topics/XS9007.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS9007
-
- XS9007
-
-
-
- Error XS9007
-
- Feature '{0}' is not available in the selected dialect {1}
-
- This error is generated with you compile in a dialect that does not support a particular feature
- Assume the following code is compiled in the Core dialect
-
- // Compile in Core dialect
- FUNCTION Test(a,b,c)// error XS9007: Feature 'USUAL' is not available in the selected dialect Core
- RETURN a,b,c
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9008.xml b/docs/Help_Spanish/Topics/XS9008.xml
deleted file mode 100644
index 4064cdd352..0000000000
--- a/docs/Help_Spanish/Topics/XS9008.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- XS9008
-
- XS9008
-
-
-
- Error XS9008
-
- Untyped arrays are not available in the selected dialect '{0}'
-
- This error happens when you use an untyped (VO) array in a dialect that does not support that.
-
- // Compile in Core dialect
- FUNCTION Test(a AS LONG,b AS LONG) AS OBJECT[]
- RETURN {a,b} // error XS9008: Untyped arrays are not available in the selected dialect 'Core'
-
-
- The following code will work and will return a types array of objects:
- // Compile in Core dialect
- FUNCTION Test(a AS LONG,b AS LONG) AS OBJECT[]
- RETURN <OBJECT>{a,b}
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9009.xml b/docs/Help_Spanish/Topics/XS9009.xml
deleted file mode 100644
index 5210a1a549..0000000000
--- a/docs/Help_Spanish/Topics/XS9009.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9009
-
- XS9009
-
-
-
- Error XS9009
-
- Typed Parameters are not supported in combination with CLIPPER calling convention
-
-
diff --git a/docs/Help_Spanish/Topics/XS9010.xml b/docs/Help_Spanish/Topics/XS9010.xml
deleted file mode 100644
index 0de87d95b4..0000000000
--- a/docs/Help_Spanish/Topics/XS9010.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9010
-
- XS9010
-
-
-
- Error XS9010
-
- The function '{0}' is only supported in functions or methods with CLIPPER calling convention
-
-
diff --git a/docs/Help_Spanish/Topics/XS9011.xml b/docs/Help_Spanish/Topics/XS9011.xml
deleted file mode 100644
index d82dc246a9..0000000000
--- a/docs/Help_Spanish/Topics/XS9011.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9011
-
- XS9011
-
-
-
- Error XS9011
-
- Ambiguous case between '{0}' and '{1}'
-
-
diff --git a/docs/Help_Spanish/Topics/XS9012.xml b/docs/Help_Spanish/Topics/XS9012.xml
deleted file mode 100644
index d5d50b56bc..0000000000
--- a/docs/Help_Spanish/Topics/XS9012.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS9012
-
- XS9012
-
-
-
- Warning XS9012
-
- Duplicate define with different value detected '{0}', {1} <=> {2}
-
-
- This warning is generated when a second define was found with a different value.
- Please note that the preprocessor does not "evaluate" the contents of the define. It does a strict text comparison.
- So "1" is not the same as "1L" or "1U'
-
- #define MYDEFINE 1
- #define MYDEFINE 1U// Warning XS9012
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9013.xml b/docs/Help_Spanish/Topics/XS9013.xml
deleted file mode 100644
index b66f726b1c..0000000000
--- a/docs/Help_Spanish/Topics/XS9013.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- XS9013
-
- XS9013
-
-
-
- Warning XS9013
-
- Duplicate define detected '{0}'
-
- This warning is generated when a second define was found that defines the same value:
-
-
- #define MYDEFINE 1
- #define MYDEFINE 1// Warning XS9013
-
-
diff --git a/docs/Help_Spanish/Topics/XS9014.xml b/docs/Help_Spanish/Topics/XS9014.xml
deleted file mode 100644
index 6332860a37..0000000000
--- a/docs/Help_Spanish/Topics/XS9014.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9014
-
- XS9014
-
-
-
- Error XS9014
-
- The dialect '{0}' requires a reference to the runtime DLLs {1}.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9015.xml b/docs/Help_Spanish/Topics/XS9015.xml
deleted file mode 100644
index eba2ca6d44..0000000000
--- a/docs/Help_Spanish/Topics/XS9015.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9015
-
- XS9015
-
-
-
- Warning XS9015
-
- No explicit constructor chaining; generating implicit call to super constructor.
- This error happens if you do not have a call to SUPER() in the body of your CONSTRUCTOR
-
-
diff --git a/docs/Help_Spanish/Topics/XS9016.xml b/docs/Help_Spanish/Topics/XS9016.xml
deleted file mode 100644
index 171047cb72..0000000000
--- a/docs/Help_Spanish/Topics/XS9016.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9016
-
- XS9016
-
-
-
- Error XS9016
-
- Class name {0} for method differs from parent class name {1}
-
-
diff --git a/docs/Help_Spanish/Topics/XS9017.xml b/docs/Help_Spanish/Topics/XS9017.xml
deleted file mode 100644
index 9f953d036a..0000000000
--- a/docs/Help_Spanish/Topics/XS9017.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9017
-
- XS9017
-
-
-
- Error XS9017
-
- Invalid dialect {0}. Must be 'Core', 'Vo', 'Vulcan', 'dBase', 'FoxPro', 'Harbour' or 'XBasepp'
-
-
diff --git a/docs/Help_Spanish/Topics/XS9018.xml b/docs/Help_Spanish/Topics/XS9018.xml
deleted file mode 100644
index c6e20449bd..0000000000
--- a/docs/Help_Spanish/Topics/XS9018.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9018
-
- XS9018
-
-
-
- Error XS9018
-
- Using a numeric DLL entrypoint '{0}' is not supported in .NET
-
-
diff --git a/docs/Help_Spanish/Topics/XS9019.xml b/docs/Help_Spanish/Topics/XS9019.xml
deleted file mode 100644
index 8ad657b4b4..0000000000
--- a/docs/Help_Spanish/Topics/XS9019.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9019
-
- XS9019
-
-
-
- Error XS9019
-
- Compiler option '{0}' ({1}) is not supported for dialect {2}
-
-
diff --git a/docs/Help_Spanish/Topics/XS9020.xml b/docs/Help_Spanish/Topics/XS9020.xml
deleted file mode 100644
index a7268d9131..0000000000
--- a/docs/Help_Spanish/Topics/XS9020.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- XS9020
-
- XS9020
-
-
-
- Warning XS9020
-
- Narrowing conversion from 'type 1' to 'type 2' may lead to loss of data or overflow errors
-
- Example
- This warning may occur in code where you assigning a value from a larger type into a smaller type
- The warning will only be shown when you compile with the compiler option /vo11 (Compatible Numeric Conversions).
- Without this compiler option the error XS0266 (Cannot implicitly convert type 'type 1' to 'type 2'. An explicit conversion exists (are you missing a cast?)) will be shown.
-
- FUNCTION Test() ASVOID LOCAL dw asDWORD LOCAL b asBYTE dw := SomeFunctionThatReturnsADword() b := dw // warning XS9020 Narrowing conversion from 'DWORD' to 'BYTE' may lead to loss of data or overflow errors
-
-
diff --git a/docs/Help_Spanish/Topics/XS9021.xml b/docs/Help_Spanish/Topics/XS9021.xml
deleted file mode 100644
index 5eb3449a91..0000000000
--- a/docs/Help_Spanish/Topics/XS9021.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9021
-
- XS9021
-
-
-
- Warning XS9021
-
- Signed/unsigned conversions from '{0}' to '{1}' may lead to loss of data or overflow errors
-
-
diff --git a/docs/Help_Spanish/Topics/XS9022.xml b/docs/Help_Spanish/Topics/XS9022.xml
deleted file mode 100644
index cafdff16cd..0000000000
--- a/docs/Help_Spanish/Topics/XS9022.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9022
-
- XS9022
-
-
-
- Error XS9022
-
- Conflicting commandline options '/ovf' and '/fovf' are not allowed (both are internally mapped to /checked)
-
-
diff --git a/docs/Help_Spanish/Topics/XS9023.xml b/docs/Help_Spanish/Topics/XS9023.xml
deleted file mode 100644
index b76119789e..0000000000
--- a/docs/Help_Spanish/Topics/XS9023.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9023
-
- XS9023
-
-
-
- Warning XS9023
-
- You are taking the address of an unfixed expression
-
-
diff --git a/docs/Help_Spanish/Topics/XS9024.xml b/docs/Help_Spanish/Topics/XS9024.xml
deleted file mode 100644
index 339d449e1e..0000000000
--- a/docs/Help_Spanish/Topics/XS9024.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9024
-
- XS9024
-
-
-
- Error XS9024
-
- The EXIT statement is not allowed inside a SWITCH statement
-
-
diff --git a/docs/Help_Spanish/Topics/XS9025.xml b/docs/Help_Spanish/Topics/XS9025.xml
deleted file mode 100644
index 4f15723769..0000000000
--- a/docs/Help_Spanish/Topics/XS9025.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9025
-
- XS9025
-
-
-
- Warning XS9025
-
- Missing RETURN statement. A statement with a default 'empty' return value is returned.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9026.xml b/docs/Help_Spanish/Topics/XS9026.xml
deleted file mode 100644
index 42a7267a65..0000000000
--- a/docs/Help_Spanish/Topics/XS9026.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9026
-
- XS9026
-
-
-
- Warning XS9026
-
- Missing RETURN value. A default 'empty' return value is returned
-
-
diff --git a/docs/Help_Spanish/Topics/XS9027.xml b/docs/Help_Spanish/Topics/XS9027.xml
deleted file mode 100644
index 2a1e860fcc..0000000000
--- a/docs/Help_Spanish/Topics/XS9027.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9027
-
- XS9027
-
-
-
- Error XS9027
-
- VoStruct member type must be one of the following: bool, byte, short, int, long, char, sbyte, ushort, uint, ulong, float, double, ptr, psz or vostruct
-
-
diff --git a/docs/Help_Spanish/Topics/XS9028.xml b/docs/Help_Spanish/Topics/XS9028.xml
deleted file mode 100644
index c2e4d6d731..0000000000
--- a/docs/Help_Spanish/Topics/XS9028.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- XS9028
-
- XS9028
-
-
-
- Error XS9028
-
- Unknown Literal Typename {0} found in VOTypeNameExpression
-
- In the VO and Vulcan language you can use type names a literal values, for example in an expression like:
- IFUsualType(uExpr) == LONG .. ENDIF
-
- If you see error 9028 then you have a literal typename in an expression that is not properly handled by the compiler. If you see this error, then please submit a code example to bugreports@xsharp.eu
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9029.xml b/docs/Help_Spanish/Topics/XS9029.xml
deleted file mode 100644
index 0191f1ae75..0000000000
--- a/docs/Help_Spanish/Topics/XS9029.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9029
-
- XS9029
-
-
-
- Warning XS9029
-
- Compiler Option {0} ({1}) is recognized by the compiler but not yet implemented
-
-
diff --git a/docs/Help_Spanish/Topics/XS9030.xml b/docs/Help_Spanish/Topics/XS9030.xml
deleted file mode 100644
index 6f441ce6e4..0000000000
--- a/docs/Help_Spanish/Topics/XS9030.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- XS9030
-
- XS9030
-
-
-
- Error XS9030
-
- Keyword {0} missing
-
- You may see this error in code that is incomplete, such as IF statements where the ENDIF is missing, or FOR statements where the NEXT keyword is missing.
- In most case the error will be clear enough to indicate what the missing keyword is.
- Example:
- FUNCTIONStartASVOID LOCALiASLONG FORi := 1TO10 ? i RETURN
-
- In this example the error message will point to the line that starts with the FOR keyword, since that is the keyword that has a missing end token.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9031.xml b/docs/Help_Spanish/Topics/XS9031.xml
deleted file mode 100644
index 91b23bbf0b..0000000000
--- a/docs/Help_Spanish/Topics/XS9031.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9031
-
- XS9031
-
-
-
- Error XS9031
-
- Array initializers cannot be combined with initial dimensions.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9032.xml b/docs/Help_Spanish/Topics/XS9032.xml
deleted file mode 100644
index 1fefac9819..0000000000
--- a/docs/Help_Spanish/Topics/XS9032.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- XS9032
-
- XS9032
-
-
-
- Warning XS9032
-
- This entity type cannot return a value. Return value ignored.
-
- VO unfortunately permits to return a value from an assign. Since this is not permitted in .NET, the X# compiler will return an error of
- Warning XS9032 This entity type cannot return a value. Return value ignored.
- The following code, perfectly valid in VO, will throw this warning in X#:
- class MyClass protect _cMyVar as string
- access MyVar
- return _cMyVar
- assign MyVar( cMyVar _cMyVar := cMyVar
return _cMyVar
-
- end class
-
- to solve the problem simply remove the return value from the return statement inside the Assign:
- class MyClass protect _cMyVar as string
access MyVar
- return _cMyVar
- assign MyVar( cMyVar ) _cMyVar := cMyVar return
-
- end class
-
-
- and if you are changing the code anyway it is also a good idea to add typing to your access/assign:
-
- class MyClass protect _cMyVar as string
- access MyVar as string
- return _cMyVar assign MyVar( cMyVar as string ) _cMyVar := cMyVar return
-
- end class
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9033.xml b/docs/Help_Spanish/Topics/XS9033.xml
deleted file mode 100644
index 5f5fafba3b..0000000000
--- a/docs/Help_Spanish/Topics/XS9033.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- XS9033
-
- XS9033
-
-
-
- Error XS9033
-
- Init and Exit procedures cannot define parameters.
-
- Init procedures and exit procedures are called by the runtime system and will not receive any parameters.
- PROCEDURERunAtStartup(a,b,c) _INIT1 RETURN
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9034.xml b/docs/Help_Spanish/Topics/XS9034.xml
deleted file mode 100644
index 1522ec411c..0000000000
--- a/docs/Help_Spanish/Topics/XS9034.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9034
-
- XS9034
-
-
-
- Warning XS9034
-
- Direct calls to Axit methods (Finalizers) are not supported with the /vo1 compiler option.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9035.xml b/docs/Help_Spanish/Topics/XS9035.xml
deleted file mode 100644
index b0fb93e483..0000000000
--- a/docs/Help_Spanish/Topics/XS9035.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9035
-
- XS9035
-
-
-
- Error XS9035
-
- The first argument to {0} must be a '{1}'.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9036.xml b/docs/Help_Spanish/Topics/XS9036.xml
deleted file mode 100644
index b080f6a4a1..0000000000
--- a/docs/Help_Spanish/Topics/XS9036.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9036
-
- XS9036
-
-
-
- Error XS9036
-
- The '{0} pseudo function requires one generic type argument to describe its return type.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9037.xml b/docs/Help_Spanish/Topics/XS9037.xml
deleted file mode 100644
index 6d0f1b0fcc..0000000000
--- a/docs/Help_Spanish/Topics/XS9037.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9037
-
- XS9037
-
-
-
- Error XS9037
-
- The '{0}' pseudo function uses a typed pointer to the function '{1}' which cannot be found.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9038.xml b/docs/Help_Spanish/Topics/XS9038.xml
deleted file mode 100644
index f670f1e70a..0000000000
--- a/docs/Help_Spanish/Topics/XS9038.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9038
-
- XS9038
-
-
-
- Error XS9038
-
- Error locating the generated Delegate '{1}' for the pseudo function '{0}'.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9039.xml b/docs/Help_Spanish/Topics/XS9039.xml
deleted file mode 100644
index 21b9b7443b..0000000000
--- a/docs/Help_Spanish/Topics/XS9039.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9039
-
- XS9039
-
-
-
- Error XS9039
-
- The parameters for the Access and Assign declarations must match by name and type. The first ASSIGN parameter is the value, the other parameters are the indexers and must be the same as the ACCESS parameters.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9040.xml b/docs/Help_Spanish/Topics/XS9040.xml
deleted file mode 100644
index e2813de00c..0000000000
--- a/docs/Help_Spanish/Topics/XS9040.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9040
-
- XS9040
-
-
-
- Error XS9040
-
- The type of the first ASSIGN parameter must match the returntype of the ACCESS
-
-
diff --git a/docs/Help_Spanish/Topics/XS9041.xml b/docs/Help_Spanish/Topics/XS9041.xml
deleted file mode 100644
index 5b007af9c2..0000000000
--- a/docs/Help_Spanish/Topics/XS9041.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9041
-
- XS9041
-
-
-
- Error XS9041
-
- Override of virtual method '{0}' has STRICT calling convention but overridden method in parent class is CLIPPER
-
-
diff --git a/docs/Help_Spanish/Topics/XS9042.xml b/docs/Help_Spanish/Topics/XS9042.xml
deleted file mode 100644
index a51fefd239..0000000000
--- a/docs/Help_Spanish/Topics/XS9042.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9042
-
- XS9042
-
-
-
- Error XS9042
-
- Override of virtual method '{0}' has CLIPPER calling convention but overridden method in parent class is STRICT.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9043.xml b/docs/Help_Spanish/Topics/XS9043.xml
deleted file mode 100644
index 5766ecee5f..0000000000
--- a/docs/Help_Spanish/Topics/XS9043.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9043
-
- XS9043
-
-
-
- Warning XS9043
-
- Function or type '{0}' is ambiguous. Could be '{1}' or '{2}'. Using the first one.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9044.xml b/docs/Help_Spanish/Topics/XS9044.xml
deleted file mode 100644
index dfcc2a6d4b..0000000000
--- a/docs/Help_Spanish/Topics/XS9044.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS9044
-
-XS9044
-
-
-
- Error XS9044
-
- Implicitly-typed variables cannot be STATIC.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9045.xml b/docs/Help_Spanish/Topics/XS9045.xml
deleted file mode 100644
index 005963b13b..0000000000
--- a/docs/Help_Spanish/Topics/XS9045.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9045
-
- XS9045
-
-
-
- Error XS9045
-
- Cannot use static local '{0}' in a codeblock.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9046.xml b/docs/Help_Spanish/Topics/XS9046.xml
deleted file mode 100644
index 78800ea498..0000000000
--- a/docs/Help_Spanish/Topics/XS9046.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS9046
-
-XS9046
-
-
-
- Error XS9046
-
- Cannot assign to '{0}' because it is a '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9047.xml b/docs/Help_Spanish/Topics/XS9047.xml
deleted file mode 100644
index 2d8ee24b1a..0000000000
--- a/docs/Help_Spanish/Topics/XS9047.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9047
-
- XS9047
-
-
-
- Warning XS9047
-
- A get or set accessor must have a body, an auto property will be generated
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9048.xml b/docs/Help_Spanish/Topics/XS9048.xml
deleted file mode 100644
index 3fa67231ba..0000000000
--- a/docs/Help_Spanish/Topics/XS9048.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-XS9048
-
-XS9048
-
-
-
- Error XS9048
-
- ASSIGN methods must have at least one parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9049.xml b/docs/Help_Spanish/Topics/XS9049.xml
deleted file mode 100644
index b8b487f9a5..0000000000
--- a/docs/Help_Spanish/Topics/XS9049.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9049
-
- XS9049
-
-
-
- Error XS9049
-
- ACCESS and ASSIGN methods cannot have Clipper Calling Convention
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9050.xml b/docs/Help_Spanish/Topics/XS9050.xml
deleted file mode 100644
index 4479868fcc..0000000000
--- a/docs/Help_Spanish/Topics/XS9050.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9050
-
- XS9050
-
-
-
- Error XS9050
-
- Expecting 'end of statement', found '{0}'
-
-
diff --git a/docs/Help_Spanish/Topics/XS9051.XML b/docs/Help_Spanish/Topics/XS9051.XML
deleted file mode 100644
index 6f7de2006a..0000000000
--- a/docs/Help_Spanish/Topics/XS9051.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9051
-
- XS9051
-
-
-
- Warning XS9051
-
- A get accessor is automatically generated for a set accessor without body.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9052.xml b/docs/Help_Spanish/Topics/XS9052.xml
deleted file mode 100644
index 883795939a..0000000000
--- a/docs/Help_Spanish/Topics/XS9052.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9052
-
- XS9052
-
-
-
- Error XS9052
-
- In .Net you cannot take the address of a method or a function. For callback functions you need to use a delegate instead.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9053.xml b/docs/Help_Spanish/Topics/XS9053.xml
deleted file mode 100644
index 2f457ba772..0000000000
--- a/docs/Help_Spanish/Topics/XS9053.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9053
-
- XS9053
-
-
-
- Error XS9053
-
- No overload for method '{0}' found with {1} arguments and default values for one or more arguments
-
-
diff --git a/docs/Help_Spanish/Topics/XS9054.xml b/docs/Help_Spanish/Topics/XS9054.xml
deleted file mode 100644
index cdedbfa41e..0000000000
--- a/docs/Help_Spanish/Topics/XS9054.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9054
-
- XS9054
-
-
-
- Warning XS9054
-
- Possible conflict between assignment to local variable {0} and named argument syntax. The compiler will assume the named argument syntax. Surround the expression with parentheses to resolve the problem.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9055.xml b/docs/Help_Spanish/Topics/XS9055.xml
deleted file mode 100644
index 38d16f738b..0000000000
--- a/docs/Help_Spanish/Topics/XS9055.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9055
-
- XS9055
-
-
-
- Error XS9055
-
- Codeblocks cannot be declared with the Lambda Expression Syntax.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9056.xml b/docs/Help_Spanish/Topics/XS9056.xml
deleted file mode 100644
index 37c36a3e58..0000000000
--- a/docs/Help_Spanish/Topics/XS9056.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9056
-
- XS9056
-
-
-
- Error XS9056
-
- You cannot assign an untyped codeblock to a delegate of type {0}. Use the Lambda Expression syntax (=>) in stead.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9057.xml b/docs/Help_Spanish/Topics/XS9057.xml
deleted file mode 100644
index 03fa3f15d3..0000000000
--- a/docs/Help_Spanish/Topics/XS9057.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9057
-
- XS9057
-
-
-
- Error XS9057
-
- Typed parameters in codeblocks are not supported by the runtime.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9058.xml b/docs/Help_Spanish/Topics/XS9058.xml
deleted file mode 100644
index 0ceaee3704..0000000000
--- a/docs/Help_Spanish/Topics/XS9058.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9058
-
- XS9058
-
-
-
- Warning XS9058
-
- Lamda Expression should not contain pipe ('|') characters around the parameters.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9059.xml b/docs/Help_Spanish/Topics/XS9059.xml
deleted file mode 100644
index 406908878a..0000000000
--- a/docs/Help_Spanish/Topics/XS9059.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9059
-
- XS9059
-
-
-
- Error XS9059
-
- Cannot convert Array Index from '{0}' to '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9060.xml b/docs/Help_Spanish/Topics/XS9060.xml
deleted file mode 100644
index 87d12be056..0000000000
--- a/docs/Help_Spanish/Topics/XS9060.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9060
-
- XS9060
-
-
-
- Error XS9060
-
- Cannot cast type '{0}' to '{1}'
-
-
diff --git a/docs/Help_Spanish/Topics/XS9061.xml b/docs/Help_Spanish/Topics/XS9061.xml
deleted file mode 100644
index 034477345b..0000000000
--- a/docs/Help_Spanish/Topics/XS9061.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9061
-
- XS9061
-
-
-
- Error XS9061
-
- The "PTR(..) operation" is not allowed for method or function calls. If the method or function returns a pointer then consider using the (<Type> PTR) syntax instead.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9062.xml b/docs/Help_Spanish/Topics/XS9062.xml
deleted file mode 100644
index 6875ee2a12..0000000000
--- a/docs/Help_Spanish/Topics/XS9062.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- XS9062
-
- XS9062
-
-
-
- Error XS9062
-
- The {0} name '{1}' conflicts with the compiler generated globals name '{2}'. You should either rename the type or the output assembly.
-
- This error may occur when you have a class or other type that has the same name as the assembly that it is located in.
- The compiler will generate a special class for global members, such as defines, globals, functions and procedures.
- The name of that class is derived from the assembly name and has a name conflict with the class that you have declared yourself.
- You need to either rename the class or the output assembly
-
-
diff --git a/docs/Help_Spanish/Topics/XS9063.xml b/docs/Help_Spanish/Topics/XS9063.xml
deleted file mode 100644
index 6d7230228b..0000000000
--- a/docs/Help_Spanish/Topics/XS9063.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- XS9063
-
- NULL
- REF
- XS9063
-
-
-
- Warning XS9063
-
- Passing a NULL pointer to a REF variable is allowed (with /vo7) but strongly discouraged. You MUST make sure that the function being called does a check for NULL pointers for the REF parameter.
- The following code shows how you should add a test to the function being called
- FUNCTION Start() ASVOID LOCAL n ASINT n := 1 ? TempRef(10 , n) // 11 ? TempRef(10 , NULL) // 1976
RETURN
FUNCTION TempRef(a ASINT, r REF INT) ASINT IF @r == NULL// Check for NULL pointer! RETURN 1976 ENDIF RETURN a + r
-
-
diff --git a/docs/Help_Spanish/Topics/XS9064.xml b/docs/Help_Spanish/Topics/XS9064.xml
deleted file mode 100644
index 3b486031f3..0000000000
--- a/docs/Help_Spanish/Topics/XS9064.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- XS9064
-
- XS9064
-
-
-
- Warning XS9064
-
- Cannot assign to '{0}' because it is a '{1}'
-
- This warning occurs when you are assigning a value directly to a foreach loop variable
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9065.xml b/docs/Help_Spanish/Topics/XS9065.xml
deleted file mode 100644
index fa87b6e36d..0000000000
--- a/docs/Help_Spanish/Topics/XS9065.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- XS9065
-
- Assignment operator
- VAR
- XS9065
-
-
-
- Warning XS9065
-
- Assignment operator ':=' expected.
- This warning is generated for VAR statements that use a single equals operator in stead of the assignment operator.
-
-
- FUNCTION Start asVOID VAR x = SomeFunction() ? x RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/XS9066.xml b/docs/Help_Spanish/Topics/XS9066.xml
deleted file mode 100644
index dbef0b4f91..0000000000
--- a/docs/Help_Spanish/Topics/XS9066.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- XS9066
-
- XS9066
-
-
-
- Warning XS9066
-
- This warning has been introduced in version 2.0.0.4 to help you find name conflicts between (built-in) functions and methods.
-
- The following code demonstrates this new warning:
-
- FUNCTION Left(c ASSTRING , dwLen ASINT) ASSTRING RETURNNULL
CLASS TestClass METHOD Test(cPath ASSTRING) ASSTRING Left(cPath , 1) STATICMETHOD Left(c ASSTRING,n AS Int32) ASSTRING // do something RETURNNULL ENDCLASS
-
- A warning will be generated for the call to Left inside TestClass:Test():
- Method 'Left' is ambiguous. Could be 'Functions.Left(string, int)' or 'TestClass.Left(string, int)'. Using the function because in X# functions take precedence over static methods. To call the method use the fully qualified name.
- This behavior has been changed to be compatible with Visual Objects. In Visual Objects the concept of static methods does not exist and you would always call the Left() function in this code. If you want to call the method from the class instead of the function you need to change the code to
- TestClass.Left(cPath , 1)
-
- If you change the code in the class and make Left() an instance method, then you need to prefix the call to Left with SELF: if you want to call the method in the class like in the example below:
- FUNCTION Left(c ASSTRING , dwLen ASINT) ASSTRING RETURNNULL
CLASS TestClass METHOD Test(cPath ASSTRING) ASSTRING SELF:Left(cPath , 1) METHOD Left(c ASSTRING,n AS Int32) ASSTRING // Do something RETURNNULL ENDCLASS
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9067.xml b/docs/Help_Spanish/Topics/XS9067.xml
deleted file mode 100644
index 07d5e787a7..0000000000
--- a/docs/Help_Spanish/Topics/XS9067.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XS9067
-
- XS9067
-
-
-
- Error XS9067
-
- This error will be thrown if an interface method has CLIPPER calling convention and the implementation does not have that convention, or vice versa.
- This usually occurs when the interface is declared in an assembly where compiler option /vo5 (Implicit clipper calling convention) has a different setting then the app where the interface is implemented.
- Assume the following code in one assembly
-
- // compiled with /vo5- INTERFACE IProvider METHOD DoSomething() ASVOID ENDINTERFACE
-
-
- And this implementation in another assembly
-
- // compiled with /vo5+ CLASS MyProvider IMPLEMENTS IProvider METHOD DoSomething() ASVOID ? "Done" ENDINTERFACE
-
-
- At first site the implementation looks OK but because the implementation is compiled with /VO5 then the method will actually be compiled as follows:
-
- CLASS MyProvider IMPLEMENTS IProvider METHOD DoSomething(aArgs PARAMSUSUAL[]) ASVOID ? "Done" ENDINTERFACE
-
-
- By writing it like this it is immediately clear that the implementation is quite different from the definition in the interface
-
-
diff --git a/docs/Help_Spanish/Topics/XS9068.xml b/docs/Help_Spanish/Topics/XS9068.xml
deleted file mode 100644
index 754da9721a..0000000000
--- a/docs/Help_Spanish/Topics/XS9068.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS9068
-
- PSZ
- String2Psz()
- StringAlloc()
- XS9068
-
-
-
- Warning XS9068
-
- The compiler generated an automatic conversion to PSZ. This will create a memory leak in your application. Please use String2Psz() to let the compiler manage the lifetime of the PSZ or use StringAlloc() and memory the lifetime of the PSZ yourself.
-
- This may happen in code like this:
- FUNCTION Start() ASVOID LOCAL uValue ASUSUAL uValue := "SomeString" ? Test(uValue) ? Test(PSZ(_CAST, "AnotherString")) RETURN
FUNCTION Test(p ASPSZ) ASSTRING RETURN Psz2String(p)
- The compiler detects that the Test() function wants to receive a Psz() and creates a conversion from USUAL to PSZ on the fly. When the contents of the usual is a Pointer then no memory will be allocated. When the contents of the usual is a string then memory will be allocated that will hold the PSZ after the conversion from Unicode to Ansi. The compiler does not know what the Test() function will do with the PSZ and can't therefor control the lifetime of the variable. We recommend that you change the code to either use String2Psz() or StringAlloc(). Of course these functions will only work if the usual contains a string like in the example above.
- FUNCTION Start() ASVOID LOCAL uValue ASUSUAL uValue := "SomeString" ? Test(String2Psz(uValue)) ? Test(String2Psz("AnotherString")) RETURN
FUNCTION Test(p ASPSZ) ASSTRING RETURN Psz2String(p)
- or
- FUNCTION Start() ASVOID LOCAL uValue ASUSUAL LOCAL p asPSZ uValue := "SomeString" p := StringAlloc(uValue) ? Test(p) MemFree(p) p := StringAlloc("AnotherString") ? Test(p) MemFree(p) RETURN
FUNCTION Test(p ASPSZ) ASSTRING RETURN Psz2String(p)
-
-
diff --git a/docs/Help_Spanish/Topics/XS9069.xml b/docs/Help_Spanish/Topics/XS9069.xml
deleted file mode 100644
index 2d0015c7bf..0000000000
--- a/docs/Help_Spanish/Topics/XS9069.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9069
-
-XS9069
-
-
-
- Warning XS9069
-
- Argument {0} is passed with REF keyword but should be passed with the '{1}' keyword
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9070.xml b/docs/Help_Spanish/Topics/XS9070.xml
deleted file mode 100644
index 8e7bfc596f..0000000000
--- a/docs/Help_Spanish/Topics/XS9070.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- Warning XS9070
-
- XS9070
-
-
-
- Warning XS9070
-
- The compiler generated an implicit cast to a smaller type from type '{0}' to '{1}'
-
-
diff --git a/docs/Help_Spanish/Topics/XS9071.xml b/docs/Help_Spanish/Topics/XS9071.xml
deleted file mode 100644
index 686985349d..0000000000
--- a/docs/Help_Spanish/Topics/XS9071.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Warning XS9071
-
- Modifier
- Parameter
- XS9071
-
-
-
- Warning XS9071
-
- Parameter {0} needs a(n) '{1}' modifier. This modifier was automatically added.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9072.xml b/docs/Help_Spanish/Topics/XS9072.xml
deleted file mode 100644
index 3e234d3632..0000000000
--- a/docs/Help_Spanish/Topics/XS9072.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- XS9072
-
- Clipper calling convention
- Default value
- Parameter
- XS9072
-
-
-
- Error XS9072
-
- Parameters with CLIPPER calling convention cannot have default values.
- This error occurs in code like the following.
-
- FUNCTION Test(a, b := 10, c := 20) RETURN a+b+c
- This will become a function with CLIPPER calling convention since the parameters are not typed. The following will work:
- FUNCTION Test(a AS USUAL, b := 10 AS USUAL, c := 20 AS USUAL) RETURN a+b+c
- or
- FUNCTION Test(a,b,c) Default(@b, 10) // or better: Default( REF b, 10) Default(@c, 20) // or better: Default( REF c, 20) RETURN a+b+c
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9073.xml b/docs/Help_Spanish/Topics/XS9073.xml
deleted file mode 100644
index 0ff2b8465e..0000000000
--- a/docs/Help_Spanish/Topics/XS9073.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- XS9073
-
- Undeclared variable
- XS9073
-
-
-
- Warning XS9073
-
- Variable '{0}' has not been declared. Assuming this is a FIELD or a MEMVAR.
- This error message may occur if you are compiling with the -undeclared commandline option.
- For example in the following code
-
-
- // Compile in VO dialect with -memvar and -undeclared and use the X# runtime FUNCTION Start asVOID PUBLIC Name Name := "Bill" Test() RETURN
FUNCTION Test() ? Name // <-- Warning XS9073 here RETURN TRUE
-
-
diff --git a/docs/Help_Spanish/Topics/XS9074.xml b/docs/Help_Spanish/Topics/XS9074.xml
deleted file mode 100644
index 1d64c6a109..0000000000
--- a/docs/Help_Spanish/Topics/XS9074.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- XS9074
-
- Declared parameters
- PARAMETERS statement
- XS9074
-
-
-
- Error XS9074
-
- You cannot have both a PARAMETERS statement and declared parameters in the same entity.
- This error message may occur in code like the following (and will only be shown if you have enabled the -memvar commandline option)
- You either remove the declared parameters par1 and par2 or the PARAMETERS statement with par3 and par4.
- The declared parameters are preferred over the PARAMETERS statement because this declares local variables which are faster than dynamic variables.
-
- FUNCTION DoSomething(par1, par2) PARAMETERS par3, par4 return par3 + par4
-
-
diff --git a/docs/Help_Spanish/Topics/XS9075.xml b/docs/Help_Spanish/Topics/XS9075.xml
deleted file mode 100644
index 78871545e5..0000000000
--- a/docs/Help_Spanish/Topics/XS9075.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XS9075
-
- already defined
- Field already defined
- Memvar already defined
- XS9075
-
-
-
- Error XS9075
-
- A MEMVAR or FIELD with the name '{0}' has already been defined.
- This happens in code where a local statement, memvar statement or field statement redefines a name that has been defined before in the same entity, such as in the code below
-
-
- FUNCTION DoSomething() MEMVAR name LOCAL name ASSTRING// <-- Error 9075 here
- or
- FUNCTION DoSomething() MEMVAR name FIELD name IN CUSTOMER // <-- Error 9075 here
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9076.xml b/docs/Help_Spanish/Topics/XS9076.xml
deleted file mode 100644
index bdfebaec95..0000000000
--- a/docs/Help_Spanish/Topics/XS9076.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- XS9076
-
- Empty Case
- XS9076
-
-
-
- Warning XS9076
-
- Empty CASE statement.
- This warning will be shown when you have a CASE statement with only an OTHERWISE block, such as in the code below
-
- FUNCTION Start ASVOID LOCAL i ASINT i := 10 DOCASE// <-- Warning 9076 here OTHERWISE ? i ENDCASE WAIT RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/XS9077.xml b/docs/Help_Spanish/Topics/XS9077.xml
deleted file mode 100644
index ce9f25edcc..0000000000
--- a/docs/Help_Spanish/Topics/XS9077.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9077
-
- XS9077
-
-
-
- Error XS9077
-
- Type parameters or constraints are not allowed on ACCESS and ASSIGN methods.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9078.xml b/docs/Help_Spanish/Topics/XS9078.xml
deleted file mode 100644
index 83a52fa5e8..0000000000
--- a/docs/Help_Spanish/Topics/XS9078.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- XS9078
-
- XS9078
-
-
-
- Error XS9078
-
- All elements of a string concatenation must be of type 'string'. Element {0} is of type '{1}'
- Previous version of the X# compiler (just like C#) allowed you to do a string concatenation of non string values. This has been disabled now.
-
- FUNCTION Start asVOID LOCAL sName asSTRING LOCAL iAge asLONG sName := "John Doe" iAge := 42 ? sName + iAge // error XS9078: All elements of a string concatenation must be of type 'string'. Element 2 is of type 'int' Console.ReadLine() RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/XS9079.xml b/docs/Help_Spanish/Topics/XS9079.xml
deleted file mode 100644
index c26cda77c6..0000000000
--- a/docs/Help_Spanish/Topics/XS9079.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- XS9079
-
- Aliased Expression
- XS9079
-
-
-
- Error XS9079
-
- Cannot take the address of an aliased expression.
- This error occurs in code like the following
-
- FUNCTION Start asVOID USE Customer DoSomething(@Customer->LastName) USE WAIT RETURN
FUNCTION Dosomething (uValue REFUSUAL) AS LOGIC uValue := uValue + uValue RETURN TRUE
-
- To work around this, assign the value of the aliased expression to a temporary variable and then after the function call assign the changed value of the variable back to the aliased expression:
-
- FUNCTION Start asVOID LOCAL uTemp asUSUAL USE Customer uTemp := Customer->LastName DoSomething(@uTemp) Customer->LastName := uTemp USE WAIT RETURN
FUNCTION Dosomething (uValue REFUSUAL) AS LOGIC uValue := uValue + uValue RETURN TRUE
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9080.xml b/docs/Help_Spanish/Topics/XS9080.xml
deleted file mode 100644
index 1a3ca93840..0000000000
--- a/docs/Help_Spanish/Topics/XS9080.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- XS9080
-
- XS9080
-
-
-
- Error XS9080
-
- Invalid literal expression.
-
- This error gets generated when a Date or DateTime literal has been included that contains invalid values
- FUNCTION Start asVOID ? 2019.06.31 // Error XS9080 here, June 31 does not exist ? {^2019-06-31} // Error XS9080 here, June 31 does not exist ? {^2019-06-30 01:60:00} // Error XS9080 here, 60 is an invalid number for minutes. RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/XS9081.xml b/docs/Help_Spanish/Topics/XS9081.xml
deleted file mode 100644
index a4b0bb8c5a..0000000000
--- a/docs/Help_Spanish/Topics/XS9081.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- XS9081
-
- Include file
- XS9081
-
-
-
- Warning XS9081
-
- Include file '{0}' will be skipped because its values are included in assembly '{1}'.
-
- Vulcan.Net and some of the other dialects use Include files to define various constants. These constants are now included as DEFINE in the X# runtime libraries.
- When the compiler detects that your code is still including these include files it will warn you and will NOT read the contents of the include files. This is in particular important for some header files, such as SET.CH from Xbase++ where some of the numeric values of the defines have been changed because they were incompatible with the same named values in other dialects.
-
- // Assume you compile with the X# runtime and VO SDK libraries included #include "VOWin32APILibrary.vh" // warning XS9081 here FUNCTION Start asVOID ? WM_CREATE // this will still work because WM_CREATE is included as constant in VOWin32APILibrary.dll RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/XS9082.xml b/docs/Help_Spanish/Topics/XS9082.xml
deleted file mode 100644
index 08b6738f5b..0000000000
--- a/docs/Help_Spanish/Topics/XS9082.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- XS9082
-
- WITH statement
- XS9082
-
-
-
- Error XS9082
-
- Can't locate WITH statement for DOT/COLON expression without left hand side.
- This error will be generated when the compiler finds a DOT/COLON expression outside of a WITH statement.
- In the FoxPro dialect this error may be replaced with a warning XS9108
- FUNCTION Start asVOID LOCAL oError as Error TRY oError := Error{} WITH oError :Description := "Some Test" // This works, inside the WITH block :GenCode := EG_ARG ENDWITH :SubCode := 12345 // Error XS9082 here because this is outside of the WITH block THROW oError CATCH e as Error ? e:ToString() ENDTRY RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/XS9083.xml b/docs/Help_Spanish/Topics/XS9083.xml
deleted file mode 100644
index 14147dbaec..0000000000
--- a/docs/Help_Spanish/Topics/XS9083.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- XS9083
-
-
- Error XS9083
-
- Cannot implicitly convert between '{0}' and 'PTR' in platform '{1}' because the size of 'PTR' cannot be determined at compile time.
-
- This error occurs when compiling for platforms other then X86 and X64 because the compiler does not know the size of the PTR type at compile time.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9084.xml b/docs/Help_Spanish/Topics/XS9084.xml
deleted file mode 100644
index 3c5218c0c9..0000000000
--- a/docs/Help_Spanish/Topics/XS9084.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- XS9084
-
- implicitly convert
- X64
- X86
- XS9084
-
-
-
- Error XS9084
-
- Cannot implicitly convert between '{0}' and 'PTR' in platform '{1}' because the size of '{0}' does not match the size of 'PTR' for the target platform.
-
- This error occurs when casting a variable to a PTR in the X86 or X64 platform
-
- The only allowed conversions are:
-
-
-
-
- Platform
-
-
- Allowed
-
-
-
-
- X86
-
-
- LONG -> PTR DWORD -> PTR
-
-
-
-
- X64
-
-
- INT64 -> PTR
- UINT64->PTR
-
-
-
-
- All other conversions will produce this error.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9085.xml b/docs/Help_Spanish/Topics/XS9085.xml
deleted file mode 100644
index 8022aa49b1..0000000000
--- a/docs/Help_Spanish/Topics/XS9085.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- XS9085
-
- Delimiters
- TEXT .. ENDTEXT
- TEXTMERGE
- XS9085
-
-
-
- Warning XS9085
-
- FoxPro dialect: Unbalanced textmerge operators '<<' and '>>'.
-
- This warning message is produced when the number of << and >> textmerge delimiters in a TEXT .. ENDTEXT block or a Text statement (\ or \\) does not match.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9086.xml b/docs/Help_Spanish/Topics/XS9086.xml
deleted file mode 100644
index 8545336e5e..0000000000
--- a/docs/Help_Spanish/Topics/XS9086.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9086
-
- TEXT .. ENDTEXT
- XS9086
-
-
-
- Error XS9086
-
- FoxPro dialect: TEXT statement found without matching ENDTEXT.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9087.XML b/docs/Help_Spanish/Topics/XS9087.XML
deleted file mode 100644
index 73645c85d6..0000000000
--- a/docs/Help_Spanish/Topics/XS9087.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9087
-
-XS9087
-
-
-
- Warning XS9087
-
- 'ARRAY' does not have a method '{0}'. This code is converted to an 'ASend()' function call.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9088.XML b/docs/Help_Spanish/Topics/XS9088.XML
deleted file mode 100644
index 532822e6a8..0000000000
--- a/docs/Help_Spanish/Topics/XS9088.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9088
-
-XS9088
-
-
-
- Error XS9088
-
- Unexpected Command or Statement.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9089.XML b/docs/Help_Spanish/Topics/XS9089.XML
deleted file mode 100644
index 8458c76beb..0000000000
--- a/docs/Help_Spanish/Topics/XS9089.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9089
-
-XS9089
-
-
-
- Error XS9089
-
- Functions cannot have an INIT or EXIT clause.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9090.XML b/docs/Help_Spanish/Topics/XS9090.XML
deleted file mode 100644
index 6f02228133..0000000000
--- a/docs/Help_Spanish/Topics/XS9090.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9090
-
-XS9090
-
-
-
- Error XS9090
-
- The _DLL syntax for Methods, Accesses and Assigns is not supported and not needed in .Net. You should add a reference to the assembly.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9091.XML b/docs/Help_Spanish/Topics/XS9091.XML
deleted file mode 100644
index 2873bf8f4f..0000000000
--- a/docs/Help_Spanish/Topics/XS9091.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9091
-
-XS9091
-
-
-
- Error XS9091
-
- To use Dynamic variables (PUBLIC, PRIVATE, MEMVAR) you will have to pass the /memvar commandline option.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9092.xml b/docs/Help_Spanish/Topics/XS9092.xml
deleted file mode 100644
index 190ea42bd0..0000000000
--- a/docs/Help_Spanish/Topics/XS9092.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9092
-
-
- Warning XS9092
-
- '{0}' has not been declared. Assuming this is a VARIABLE or a CURSOR.
- This warning will be shown when compiling in the FoxPro dialect for code in the following style
- ? Customer.LastName // XS9092 'Customer' has not been declared. Assuming this is a VARIABLE or a CURSOR.
- when the /undeclared compiler option is enabled. The compiler has no idea at compile time if Customer is the name of a memory variable or a cursor. This will be resolved at runtime or lead to a runtime error.
- If you declare a local variable in the code with the name 'Customer' then the compiler will assume that Customer is an object with a LastName property.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9093.xml b/docs/Help_Spanish/Topics/XS9093.xml
deleted file mode 100644
index 93b3bc49bd..0000000000
--- a/docs/Help_Spanish/Topics/XS9093.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9093
-
-
- Warning XS9093
-
- '{0}' has not been declared. Assuming this is a CURSOR.
-
- This warning will be shown when compiling in the FoxPro dialect for code in the following style
- ? Customer.LastName // XS9093 'Customer' has not been declared. Assuming this is a CURSOR.
- when the /undeclared compiler option is NOT enabled
-
-
diff --git a/docs/Help_Spanish/Topics/XS9094.xml b/docs/Help_Spanish/Topics/XS9094.xml
deleted file mode 100644
index c77a03e30e..0000000000
--- a/docs/Help_Spanish/Topics/XS9094.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- XS9094
-
- XS9094
-
-
-
- Warning XS9094
-
- Type '{0}' does not have a member '{1}'. This gets resolved to a late bound call to its method '{2}'.
-
- This warning indicates that you are calling a property or method on a type object but that type does not have the property.
- The compiler has detected however that the type has a NoIvarGet(), NoIVarPut() or NoMethod() method and will call this method in stead.
- LOCAL oServer as DbServer oServer := DbServer{"C:\Test\Customer.dbf"} ? oServer:LastName // warning XS9094 Type 'DbServer' does not have a member 'LastName'. This gets resolved to a late bound call to its method 'NoIVarGet'. oServer:FirstName // warning XS9094 Type 'DbServer' does not have a member 'FirstName'. This gets resolved to a late bound call to its method 'NoIVarPut'. oServer:Close()
-
-
diff --git a/docs/Help_Spanish/Topics/XS9095.xml b/docs/Help_Spanish/Topics/XS9095.xml
deleted file mode 100644
index b33a293796..0000000000
--- a/docs/Help_Spanish/Topics/XS9095.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- XS9095
-
-
- Error XS9095
-
- The CURRENCY Type requires a reference to the X# runtime and is not supported by the Vulcan runtime.
-
- This error will be shown if you compile code that uses the new CURRENCY type against the Vulcan runtime.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9096.xml b/docs/Help_Spanish/Topics/XS9096.xml
deleted file mode 100644
index b66a784763..0000000000
--- a/docs/Help_Spanish/Topics/XS9096.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9096
-
-
- WARNING XS9096
-
- Unrecognized or unsupported #pragma option value '{0}'
- This warning will be shown if you have a pragma with an unrecognized or unsupported option.
-
- Example
- #pragma options ("ab", on) // warning XS9096
-
-
diff --git a/docs/Help_Spanish/Topics/XS9097.xml b/docs/Help_Spanish/Topics/XS9097.xml
deleted file mode 100644
index 7283bb7f78..0000000000
--- a/docs/Help_Spanish/Topics/XS9097.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9097
-
-
- Error XS9097
-
- The base class '{0}' declares a {1} '{2}' that differs from this {1} '{3}' only in case.
-
- This error will be shown if you declare a method in a subclass that only differs in case from a method in the base class when the /cs (case sensitive compilation) flag is enabled.
- Without this compiler option the compiler will "adjust" the case of the method in the subclass.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9098.xml b/docs/Help_Spanish/Topics/XS9098.xml
deleted file mode 100644
index 493c9a9186..0000000000
--- a/docs/Help_Spanish/Topics/XS9098.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- XS9098
-
-
- Warning XS9098
-
- Type '{0}' does not have a {2} '{1}'. This gets resolved to a late bound {2} {3}.
- This warning will only appear when compiling in the FoxPro dialect when the /lb compiler option is not enabled.
-
- For example
- FUNCTION Start asVOID local o asUSUAL o := Foo{}
o:Bar := "Test" // warning XS9098: Type 'USUAL' does not have a property 'Bar'. This gets resolved to a late bound propertyassign. ? o:Bar // warning XS9098: Type 'USUAL' does not have a property 'Bar'. This gets resolved to a late bound propertyaccess. ? o:Hello() // warning XS9098: Type 'USUAL' does not have a method 'Hello'. This gets resolved to a late bound method call.
WAIT RETURN
CLASS Foo PROPERTY Bar asSTRINGAUTO METHOD Hello asSTRING RETURN "Hello "+Bar ENDCLASS
- This code will generate 3 warnings when compiled in the FoxPro dialect if the /lb compiler option is not enabled
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9099.XML b/docs/Help_Spanish/Topics/XS9099.XML
deleted file mode 100644
index c719d88854..0000000000
--- a/docs/Help_Spanish/Topics/XS9099.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9099
-
-XS9099
-
-
-
- Error XS9099
-
- Public declarations cannot have both an array specification and an initialization value.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9100.XML b/docs/Help_Spanish/Topics/XS9100.XML
deleted file mode 100644
index 73b462d687..0000000000
--- a/docs/Help_Spanish/Topics/XS9100.XML
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-Error XS9100
-
-XS9100
-
-
-
- Error XS9100
-
-
- Using the _Chr() or Chr() functions in a DEFINE is only allowed for literal values between 0 and 127.
- The character values between 128 and 255 are code page dependent and cannot be determined at compile time.
- You may want to use a GLOBAL variable as a work around.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9101.xml b/docs/Help_Spanish/Topics/XS9101.xml
deleted file mode 100644
index 097c29129f..0000000000
--- a/docs/Help_Spanish/Topics/XS9101.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- XS9101
-
-
- XS9101
-
- Try statement found without CATCH clause and without FINALLY clause. The compiler will generate a default CATCH clause that catches and ignores all exceptions.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9102.XML b/docs/Help_Spanish/Topics/XS9102.XML
deleted file mode 100644
index 10a69b56bc..0000000000
--- a/docs/Help_Spanish/Topics/XS9102.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9102
-
-XS9102
-
-
-
- Warning XS9102
-
- {0} is unsupported and will be ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9103.XML b/docs/Help_Spanish/Topics/XS9103.XML
deleted file mode 100644
index 04dd54e3cb..0000000000
--- a/docs/Help_Spanish/Topics/XS9103.XML
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Error XS9103
-
- Unexpected token
- XS9103
-
-
-
- Error XS9103
-
- Unexpected token '{0}', expected '{1}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9104.XML b/docs/Help_Spanish/Topics/XS9104.XML
deleted file mode 100644
index 8f8b3eea1d..0000000000
--- a/docs/Help_Spanish/Topics/XS9104.XML
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- Error XS9104
-
- clipper
- clipper calling convention
- Expression Body
- XS9104
-
-
-
- Error XS9104
-
- An Expression Body is not supported for methods / functions with clipper calling convention
-
- Example
- This is not allowed
-
- FUNCTION Start ASVOID ? Test(1,2) RETURN
FUNCTION Test(a,b) => a + b // error here
-
- This is allowed however
-
FUNCTION Start ASVOID ? Test(1,2) RETURN
FUNCTION Test(a asusual,b asusual) => a + b // this is Ok
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9105.XML b/docs/Help_Spanish/Topics/XS9105.XML
deleted file mode 100644
index 1b1147a29c..0000000000
--- a/docs/Help_Spanish/Topics/XS9105.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9105
-
-XS9105
-
-
-
- Warning XS9105
-
- '{0}': Type was changed to '{2}' in the parenttype '{1}'. The compiler will automatically propagate the new type '{2}' to the subclass.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9106.XML b/docs/Help_Spanish/Topics/XS9106.XML
deleted file mode 100644
index 380db3a068..0000000000
--- a/docs/Help_Spanish/Topics/XS9106.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9106
-
-XS9106
-
-
-
- Error XS9106
-
- '{0}': The method signature was changed in the method '{1}'. You will have to update the parameter types and/or return type in the method of the subclass too.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9107.XML b/docs/Help_Spanish/Topics/XS9107.XML
deleted file mode 100644
index db602df88c..0000000000
--- a/docs/Help_Spanish/Topics/XS9107.XML
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Error XS9107
-
- NIL
- XS9107
-
-
-
- Error XS9107
-
- The NIL value cannot be passed as an argument to a function or method declared with a REF or OUT parameter
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9108.xml b/docs/Help_Spanish/Topics/XS9108.xml
deleted file mode 100644
index 65af31e776..0000000000
--- a/docs/Help_Spanish/Topics/XS9108.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- Warning XS9108
-
- WITH
- WITH block
- XS9108
-
-
-
- Warning XS9108
-
- Cannot locate WITH block for member access expression without left hand side. This will be resolved into a late bound call at runtime and may cause an exception when no active WITH block is found.
-
- You will only see this warning when compiling in the FoxPro dialect and when the "Late Binding" option is enabled.
- For all other dialects the missing left hand side of the expression will generate a compilation error XS9082
-
- Example
-
- FUNCTION Foo() LOCAL oError as Error oError = Error{} WITH oError .Description = "SomeDescription" Bar() ENDWITH
PROCEDURE Bar() IF .Description == "SomeDescription" // Warning XS9108 .Description = "SomeOtherDescription" // Warning XS9108 ENDIF RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/XS9109.xml b/docs/Help_Spanish/Topics/XS9109.xml
deleted file mode 100644
index f4529957c9..0000000000
--- a/docs/Help_Spanish/Topics/XS9109.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- XS9109
-
- @
- OUT
- REF
- XS9109
-
-
-
- XS9109
-
- Argument 'arg' may not be passed with the '@' prefix
-
- You may not pass an argument with a @ prefix to a method or function that does not expect a REF or OUT parameter.
-
- This may happen in code like this
-
- FUNCTION Start() ASVOID LOCAL n ASINT n := 123 test(@n) ? n
PROCEDURE test(u ASUSUAL) ? u u := 345
- If you really want to pass the address of the USUAL to the TEST function then you have to assign the address to a local variable first:
-
- FUNCTION Start() ASVOID LOCAL n ASINT LOCAL p asPTR n := 123 p := @n // assign address to local of type ptr test(p) // pass the pointer ? n
PROCEDURE test(u ASUSUAL) ? u u := 345
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9110.xml b/docs/Help_Spanish/Topics/XS9110.xml
deleted file mode 100644
index a304e2bb40..0000000000
--- a/docs/Help_Spanish/Topics/XS9110.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- XS9110
-
- Cast2Psz
- String2Psz
- StringAlloc
- XS9110
-
-
-
- Warning XS9110
-
- String2Psz() and Cast2Psz() are only allowed in a local context:
-
- the result of String2Psz() or Cast2Psz() cannot be persisted in a memory location that does not have a local scope. T
- he PSZ value is destroyed when the scope in which it is allocated ends.
- You have to use StringAlloc() instead and managed the lifetime of the PSZ in code.
-
- Example
- In the code below the p2 field is inline initialized with String2Psz(). this is not allowed.
- Also in the constructor we try to assign the value of p1 with String2Psz(). This is also not allowed.
- CLASS TestClass EXPORT p1 ASPSZ EXPORT p2 := String2Psz("psz2") ASPSZ // Error here
CONSTRUCTOR() p1 := String2Psz("psz1") // Error here RETURN ENDCLASS
-
-
- The solution is something like this
-
- CLASS TestClass EXPORT p1 ASPSZ EXPORT p2 ASPSZ
RETURN ENDCLASS
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9111.XML b/docs/Help_Spanish/Topics/XS9111.XML
deleted file mode 100644
index 05b7761f2f..0000000000
--- a/docs/Help_Spanish/Topics/XS9111.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9111
-
-XS9111
-
-
-
- Error XS9111
-
- The error is most likely related to the token '{0}' that was used at this location.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9112.XML b/docs/Help_Spanish/Topics/XS9112.XML
deleted file mode 100644
index ab09152d5a..0000000000
--- a/docs/Help_Spanish/Topics/XS9112.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9112
-
-XS9112
-
-
-
- Error XS9112
-
- Can't access the instance member '{0}' with the {1} operator '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9113.XML b/docs/Help_Spanish/Topics/XS9113.XML
deleted file mode 100644
index b2ca8d9402..0000000000
--- a/docs/Help_Spanish/Topics/XS9113.XML
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Error XS9113
-
- STACKALLOC
- XS9113
-
-
-
- Error XS9113
-
- The STACKALLOC keyword needs to be followed by a literal array or an array creation expression.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9114.XML b/docs/Help_Spanish/Topics/XS9114.XML
deleted file mode 100644
index ce3c2f963e..0000000000
--- a/docs/Help_Spanish/Topics/XS9114.XML
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Error XS9114
-
- static member
- XS9114
-
-
-
- Error XS9114
-
- Can't access the static member '{0}' with the {1} operator '{2}'.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9115.XML b/docs/Help_Spanish/Topics/XS9115.XML
deleted file mode 100644
index 68afbd0f41..0000000000
--- a/docs/Help_Spanish/Topics/XS9115.XML
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Error XS9115
-
- COLON
- XS9115
-
-
-
- Error XS9115
-
- Can't use the COLON operator ':' as delimiter in the {0} '{1}'
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9116.xml b/docs/Help_Spanish/Topics/XS9116.xml
deleted file mode 100644
index 374a37e541..0000000000
--- a/docs/Help_Spanish/Topics/XS9116.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- XS9116
-
- NULL
- NULL_PSZ
- XS9116
-
-
-
- Warning XS9116
-
- Passing a NULL_PSZ for an argument declared as 'string' may have unexpected results when the code checks for a string with the value NULL.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9117.xml b/docs/Help_Spanish/Topics/XS9117.xml
deleted file mode 100644
index e622ec22aa..0000000000
--- a/docs/Help_Spanish/Topics/XS9117.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- XS9117
-
- NIL
- XS9117
-
-
-
- Warning XS9117
-
- A conversion from NIL to '{0}' is not supported and may have unwanted results.
-
-
diff --git a/docs/Help_Spanish/Topics/XS9118.xml b/docs/Help_Spanish/Topics/XS9118.xml
deleted file mode 100644
index 340ff1904c..0000000000
--- a/docs/Help_Spanish/Topics/XS9118.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- XS9118
-
- Clipper calling convention
- PARAMS
- XS9118
-
-
-
- Warning XS9118
-
- Untyped parameter '{0}' and '{1}' calling convention, assuming 'USUAL' type.
-
- This error will be generated by code such as the following:
- FUNCTION Test1(c asstring, i ) asstring// warning XS9118: Untyped parameter 'i' and 'STRICT' calling convention, assuming 'USUAL' type. return c
- Omitting the type of other parameters is allowed, because in that case this parameter will get the same type as the parameter following it. In the sample below both c and i will be of type int.
- FUNCTION Test2(c, i asint) asstring return c
- If you omit all types such as in the code below
- FUNCTION Test3(c, i ) asstring return c
- then the compiler will generate a function (or method) of CLIPPER calling convention. All parameters will be of type USUAL then and all parameters are optional. You can call this function with as many parameters as you like. Of course you need to write code inside the function to check if the parameters and their types are corrected.
- When processing the CLIPPER calling convention, the X# compiler will generate a new PARAMS parameter of type USUAL[] and will create locals for each of the declared parameters and will assign the right element from the PARAMS array into the local variables.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9119.XML b/docs/Help_Spanish/Topics/XS9119.XML
deleted file mode 100644
index 6803558d84..0000000000
--- a/docs/Help_Spanish/Topics/XS9119.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9119
-
-XS9119
-
-
-
- Warning XS9119
-
- Property parameters should be specified between Square Brackets ('[ ]').
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9120.XML b/docs/Help_Spanish/Topics/XS9120.XML
deleted file mode 100644
index 4021018521..0000000000
--- a/docs/Help_Spanish/Topics/XS9120.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9120
-
-XS9120
-
-
-
- Error XS9120
-
- {0} cannot have an initial value.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9121.XML b/docs/Help_Spanish/Topics/XS9121.XML
deleted file mode 100644
index 6e8819efd7..0000000000
--- a/docs/Help_Spanish/Topics/XS9121.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9121
-
-XS9121
-
-
-
- Error XS9121
-
- Cannot convert from Lambda Expression to {0}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9122.XML b/docs/Help_Spanish/Topics/XS9122.XML
deleted file mode 100644
index 1fb58d05fe..0000000000
--- a/docs/Help_Spanish/Topics/XS9122.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9122
-
-XS9122
-
-
-
- Warning XS9122
-
- File Wide Memory Variable found with the same name '{0}'. You must use the MEMVAR or M prefix to access that variable.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9123.XML b/docs/Help_Spanish/Topics/XS9123.XML
deleted file mode 100644
index 2fbc0d7d0f..0000000000
--- a/docs/Help_Spanish/Topics/XS9123.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9123
-
-XS9123
-
-
-
- Error XS9123
-
- The named argument '{0}' is not supported when creating typed arrays.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9200.xml b/docs/Help_Spanish/Topics/XS9200.xml
deleted file mode 100644
index e3e8f9dd8b..0000000000
--- a/docs/Help_Spanish/Topics/XS9200.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9200
-
-XS9200
-
-
-
- Error XS9200
-
- XPP: Multiple Inheritance is not supported by the .Net Runtime.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9201.xml b/docs/Help_Spanish/Topics/XS9201.xml
deleted file mode 100644
index cdd47f43eb..0000000000
--- a/docs/Help_Spanish/Topics/XS9201.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9201
-
-XS9201
-
-
-
- Warning XS9201
-
- XPP: The FROM clause is interpreted as SHARING because variables in parent classes are always shared in the .Net Runtime.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9202.xml b/docs/Help_Spanish/Topics/XS9202.xml
deleted file mode 100644
index 7aabb21450..0000000000
--- a/docs/Help_Spanish/Topics/XS9202.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9202
-
-XS9202
-
-
-
- Warning XS9202
-
- The XPP: FROZEN method modifier is not supported and ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9203.xml b/docs/Help_Spanish/Topics/XS9203.xml
deleted file mode 100644
index c93c8bf15d..0000000000
--- a/docs/Help_Spanish/Topics/XS9203.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9203
-
-XS9203
-
-
-
- Warning XS9203
-
- The XPP: VAR .. IS .. IN .. clause is not supported. There is no multiple inheritance, so this is no longer needed.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9204.xml b/docs/Help_Spanish/Topics/XS9204.xml
deleted file mode 100644
index 24d7496b1f..0000000000
--- a/docs/Help_Spanish/Topics/XS9204.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9204
-
-XS9204
-
-
-
- Warning XS9204
-
- XPP: Variables are SHARED by default in .Net
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9205.xml b/docs/Help_Spanish/Topics/XS9205.xml
deleted file mode 100644
index a671c3cfea..0000000000
--- a/docs/Help_Spanish/Topics/XS9205.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9205
-
-XS9205
-
-
-
- Warning XS9205
-
- The XPP: ASSIGNMENT clause for instance variables is not supported (yet) and ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9206.xml b/docs/Help_Spanish/Topics/XS9206.xml
deleted file mode 100644
index 8ede6eec30..0000000000
--- a/docs/Help_Spanish/Topics/XS9206.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9206
-
-XS9206
-
-
-
- Warning XS9206
-
- The XPP: READONLY clause for instance variables is not supported (yet) and ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9207.xml b/docs/Help_Spanish/Topics/XS9207.xml
deleted file mode 100644
index 09188c99d4..0000000000
--- a/docs/Help_Spanish/Topics/XS9207.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9207
-
-XS9207
-
-
-
- Warning XS9207
-
- XPP: Method {0} has been declared but has not been implemented.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9208.xml b/docs/Help_Spanish/Topics/XS9208.xml
deleted file mode 100644
index fd5870aec6..0000000000
--- a/docs/Help_Spanish/Topics/XS9208.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9208
-
-XS9208
-
-
-
- Warning XS9208
-
- XPP: Method {0} has NOT been declared.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9209.xml b/docs/Help_Spanish/Topics/XS9209.xml
deleted file mode 100644
index a6f486064d..0000000000
--- a/docs/Help_Spanish/Topics/XS9209.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9209
-
-XS9209
-
-
-
- Error XS9209
-
- XPP: Class {0} has not been declared.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9210.XML b/docs/Help_Spanish/Topics/XS9210.XML
deleted file mode 100644
index 5592460db1..0000000000
--- a/docs/Help_Spanish/Topics/XS9210.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9210
-
-XS9210
-
-
-
- Error XS9210
-
- XPP: Accessor '{0}' should not be declared more than once.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9211.XML b/docs/Help_Spanish/Topics/XS9211.XML
deleted file mode 100644
index 9039be91e8..0000000000
--- a/docs/Help_Spanish/Topics/XS9211.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9211
-
-XS9211
-
-
-
- Error XS9211
-
- XPP: The type for the '{0}' property declaration does not match the returntype of the method that implemens the property.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9212.XML b/docs/Help_Spanish/Topics/XS9212.XML
deleted file mode 100644
index 9619b3b6e6..0000000000
--- a/docs/Help_Spanish/Topics/XS9212.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9212
-
-XS9212
-
-
-
- Error XS9212
-
- .Net Classes cannot have a field and a property with the same name {0}.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9214.XML b/docs/Help_Spanish/Topics/XS9214.XML
deleted file mode 100644
index 419cd60289..0000000000
--- a/docs/Help_Spanish/Topics/XS9214.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9214
-
-XS9214
-
-
-
- Error XS9214
-
- Parenthesized Expression Lists are not supported when using the -modernsyntax compiler option.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9230.XML b/docs/Help_Spanish/Topics/XS9230.XML
deleted file mode 100644
index e203611033..0000000000
--- a/docs/Help_Spanish/Topics/XS9230.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Warning XS9230
-
-XS9230
-
-
-
- Warning XS9230
-
- The '{0}' clause is not supported and ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9231.XML b/docs/Help_Spanish/Topics/XS9231.XML
deleted file mode 100644
index c6f81fb95f..0000000000
--- a/docs/Help_Spanish/Topics/XS9231.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- Error XS9231
-
- XS9231
-
-
-
- Error XS9231
-
- The 'AS BaseType' clause is mandatory in the FoxPro dialect
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9232.XML b/docs/Help_Spanish/Topics/XS9232.XML
deleted file mode 100644
index b585b110c9..0000000000
--- a/docs/Help_Spanish/Topics/XS9232.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- Error XS9232
-
- XS9232
-
-
-
- Error XS9232
-
- CONSTRUCTOR and DESTRUCTOR are not allowed for classes declared with DEFINE CLASS
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9233.XML b/docs/Help_Spanish/Topics/XS9233.XML
deleted file mode 100644
index 8f922d2c72..0000000000
--- a/docs/Help_Spanish/Topics/XS9233.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9233
-
-XS9233
-
-
-
- Error XS9233
-
- DECLARE DLL Statements in .Net cannot have a STRING parameter by reference because .Net strings are immutable. Use a System.Text.StringBuilder argument instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9234.XML b/docs/Help_Spanish/Topics/XS9234.XML
deleted file mode 100644
index 93c7c1f872..0000000000
--- a/docs/Help_Spanish/Topics/XS9234.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9234
-
-XS9234
-
-
-
- Error XS9234
-
- FoxPro DIMENSION statement or LOCAL ARRAY statement supports 1 or 2 dimensions, not more.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9235.XML b/docs/Help_Spanish/Topics/XS9235.XML
deleted file mode 100644
index 6a9f3f7ea7..0000000000
--- a/docs/Help_Spanish/Topics/XS9235.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9235
-
-XS9235
-
-
-
- Error XS9235
-
- FoxPro Array support requires the /memvar compiler option.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9236.XML b/docs/Help_Spanish/Topics/XS9236.XML
deleted file mode 100644
index c3374a5227..0000000000
--- a/docs/Help_Spanish/Topics/XS9236.XML
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-Error XS9236
-
-XS9236
-
-
-
- Error XS9236
-
- Cannot locate WITH block for member access expression without left hand side. Enable 'Late Binding' to allow resolving the WITH expression at runtime.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XS9999.xml b/docs/Help_Spanish/Topics/XS9999.xml
deleted file mode 100644
index c5214fd681..0000000000
--- a/docs/Help_Spanish/Topics/XS9999.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- XS9999
-
- XS9999
-
-
-
- Error XS9999
-
- When an internal error occurs in the X# compiler then you may see error XS9999.
- If you happen to see this error, then please send the error message to support@xsharp.eu.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp-Open-Software-License.xml b/docs/Help_Spanish/Topics/XSharp-Open-Software-License.xml
deleted file mode 100644
index a0cae6357b..0000000000
--- a/docs/Help_Spanish/Topics/XSharp-Open-Software-License.xml
+++ /dev/null
@@ -1,242 +0,0 @@
-
-
-
- XSharp Open Software License
-
-
- Error XSharp Open Software License
-
- The X# Compiler binaries and runtime binaries are licensed under the XSharp Open Software License Agreement. The full text of this license is:
-
- XSHARP OPEN SOFTWARE LICENSE AGREEMENT
-
- Version effective date: Sept 15, 2015
-
- Preamble:
-
- The use of the Software is unsupported and is for personal or
- commercial use. Support is available from XSharp under a separate
- agreement, see Part 3.c.
- For redistribution of the Software, you will require an OEM license,
- see part 4.b. For more information on support options or
- redistribution (e.g. OEM Licensing) please contact XSharp.
- This license establishes the terms under which the Software may be
- used, copied, modified, distributed and/or redistributed. The intent
- of this license is that XSharp maintains control over the
- development and distribution of the Software, while allowing its use
- it in a variety of ways. If the terms of this license do not permit
- your proposed usage or if you require clarification regarding your
- intended use of the Software, please contact info@xsharp.eu
-
- XSharp BV. ("XSharp") is willing to license the software only upon
- the condition that you accept all of the terms contained in this
- software license agreement. Please read the terms carefully. By
- clicking on "yes, accept" or by installing the software, you will
- indicate your agreement with them. If you are entering into this
- agreement on behalf of a company or other legal entity, your
- acceptance represents that you have the authority to bind such
- entity to these terms, in which case "you" or "your" shall refer to
- your entity. If you do not agree with these terms, or if you do not
- have the authority to bind your entity, then XSharp is unwilling to
- license the software, and you should not install the software.
-
- 1. Parties.
-
- The parties to this Agreement are you, the licensee ("You") and
- XSharp. If You are not acting on behalf of yourself as an
- individual, then "You" means your company or organization. A company
- or organization shall in either case mean a single business entity,
- and shall not include its affiliates or wholly owned subsidiaries.
-
- 2. The software.
-
- The accompanying materials including, but not limited to, binary
- executables, documentation, images, and scripts, which are
- distributed by XSharp, and derivatives of that collection and/or
- those files are referred to herein as the "Software".
-
- 3. License Grant for the Software.
-
- a.You are granted worldwide, perpetual, paid up, royalty free,
- non-exclusive rights to install and use the Software subject to the
- terms and conditions contained herein.
-
- b.You may: (i) copy the Software for archival purposes, (ii) copy
- the Software for personal use purposes, (iii) use, copy, and
- distribute the Software solely for your organization's internal use
- and or business operation purposes including copying the Software to
- other workstations inside Your organization. Any copy must contain
- the original Software's proprietary notices in unaltered form.
-
- c.No Other Software and Services. XSharp will not provide you
- with any other software or services (including any support or
- maintenance services) relating to the Software, except to the extent
- that such software and services, if any, are required and provided
- pursuant to an applicable maintenance and support agreement.
-
- 4. Restrictions.
-
- a.XSharp encourages you to promote use of the Software. However,
- this agreement does not grant permission to use the trade names,
- trademarks, service marks, or product names of XSharp, except as
- required for reasonable and customary use in describing the origin
- of the Software. In particular, you cannot use any of these marks in
- any way that might state or imply that XSharp endorses Your work, or
- might state or imply that You created the Software covered by this
- Agreement. Except as expressly provided herein, you may not:
-
- i.modify or translate the Software;
-
- ii.reverse engineer, decompile, or disassemble the Software,
- except to the extent this restriction is expressly prohibited by
- applicable law;
-
- iii.create derivative works based on the Software;
-
- iv.merge the Software with another product;
-
- v.copy the Software; or
-
- vi.remove or obscure any proprietary rights notices or labels on
- the Software.
-
- b. You may not distribute the Software via OEM Distribution (as
- defined below) without entering into a separate OEM Distribution
- Agreement with XSharp. "OEM Distribution" means permitting others
- outside Your organization to use the Software, distribution and/or
- use of the Software as either a bundled add-on to, or embedded
- component of, another application, with such application being made
- available to its users as, but not limited to, an on-premises
- application, a hosted application, a Software-as-a-Service offering
- or a subscription service for which the distributor of the
- application receives a license fee or any form of direct or indirect
- compensation. Except as expressly provided herein, you may not:
-
- i.permit others outside Your organization to use the Software,
-
- ii.redistribute:
- 1. the Software as a whole whether as a wrapped application or
- on a stand-alone basis, or
- 2. parts of the Software to create a language distribution, or
- 3. the XSharp components with Your Wrapped Application.
-
- The exception to this rule are the components of the software that
- are explicitly listed in the documentation as “redistributable
- files”. These files are also copied by the installation process of
- the Software into to a separate folder with the name “Redist” under
- the Software’s installation folder.
-
- c.You are excluded from the foregoing restrictions in paragraph
- 4b if You are using the Software for non-commercial purposes as
- determined by XSharp at its sole discretion, or if You are using the
- Software solely for Your organization’s internal use and or internal
- business operation purposes on non-production servers (e.g.
- development and or testing).
-
- 5. Ownership.
-
- XSharp and its suppliers own the Software and all intellectual
- property rights embodied therein, including copyrights and valuable
- trade secrets embodied in the Software's design and coding
- methodology. The Software is protected by the copyright laws from
- The Netherlands and international treaty provisions. This Agreement
- provides You only a limited use license, and no ownership of any
- intellectual property.
-
- 6. Infringement Indemnification.
-
- You shall defend or settle, at Your expense, any action brought
- against XSharp based upon the claim that any modifications to the
- Software or combination of the Software with products infringes or
- violates any third party right; provided, however, that: (i) XSharp
- shall notify Licensee promptly in writing of any such claim; (ii)
- XSharp shall not enter into any settlement or compromise any such
- claim without Your prior written consent; (iii) You shall have sole
- control of any such action and settlement negotiations; and (iv)
- XSharp shall provide You with commercially reasonable information
- and assistance, at Your request and expense, necessary to settle or
- defend such claim. You agree to pay all damages and costs finally
- awarded against XSharp attributable to such claim.
-
- 7. Limited Warranty.
-
- Neither XSharp nor any of its suppliers or resellers makes any
- warranty of any kind, express or implied, and XSharp and its
- suppliers specifically disclaim the implied warranties of title,
- non-infringement, merchantability, fitness for a particular purpose,
- system integration, and data accuracy. There is no warranty or
- guarantee that the operation of the software will be uninterrupted,
- error-free, or virus-free, or that the software will meet any
- particular criteria of performance, quality, accuracy, purpose, or
- need. You assume the entire risk of selection, installation, and use
- of the software. This disclaimer of warranty constitutes an
- essential part of this agreement. No use of the software is
- authorized hereunder except under this disclaimer.
-
- 8. Local Law.
-
- If implied warranties may not be disclaimed under applicable law,
- then any implied warranties are limited in duration to the period
- required by applicable law. Some jurisdictions do not allow
- limitations on how long an implied warranty may last, so the above
- limitations may not apply to You. This warranty gives you specific
- rights, and You may have other rights which vary from jurisdiction
- to jurisdiction.
-
- 9. Limitation of Liability.
-
- Independent of the forgoing provisions, in no event and under no
- legal theory, including without limitation, tort, contract, or
- strict products liability, shall XSharp or any of its suppliers be
- liable to you or any other person for any indirect, special,
- incidental, or consequential damages of any kind, including without
- limitation, damages for loss of goodwill, work stoppage, computer
- malfunction, or any other kind of commercial damage, even if XSharp
- has been advised of the possibility of such damages. This limitation
- shall not apply to liability for death or personal injury to the
- extent prohibited by applicable law. In no event shall XSharp's
- liability for damages for any cause whatsoever, and regardless of
- the form of action, exceed in the aggregate the amount of the
- purchase price paid for the software license.
-
- 10. Export Controls.
-
- You agree to comply with all export laws and restrictions and
- regulations of The Netherlands, The European Union or foreign
- agencies or authorities, and not to export or re-export the Software
- or any direct product thereof in violation of any such restrictions,
- laws or regulations, or without all necessary approvals. As
- applicable, each party shall obtain and bear all expenses relating
- to any necessary licenses and/or exemptions with respect to its own
- export of the Software from The Netherlands or the European Union.
-
- 11. Severability.
-
- If any provision of this Agreement is declared invalid or
- unenforceable, such provision shall be deemed modified to the extent
- necessary and possible to render it valid and enforceable. In any
- event, the unenforceability or invalidity of any provision shall not
- affect any other provision of this Agreement, and this Agreement
- shall continue in full force and effect, and be construed and
- enforced, as if such provision had not been included, or had been
- modified as above provided, as the case may be.
-
- 12. Jurisdiction and Venue.
-
- This Agreement is governed by the applicable laws of The
- Netherlands.
-
- 13. Assignment.
-
- Except as expressly provided herein neither this Agreement nor any
- rights granted hereunder, nor the use of any of the Software may be
- assigned, or otherwise transferred, in whole or in part, by
- Licensee, without the prior written consent of XSharp. XSharp may
- assign this Agreement in the event of a merger or sale of all or
- substantially all of the stock of assets of XSharp without the
- consent of Licensee. Any attempted assignment will be void and of no
- effect unless permitted by the foregoing. This Agreement shall inure
- to the benefit of the parties permitted successors and assigns.
-
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp.xml b/docs/Help_Spanish/Topics/XSharp.xml
deleted file mode 100644
index c7073983e1..0000000000
--- a/docs/Help_Spanish/Topics/XSharp.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- X# Documentation
-
- Click here for the version history
-
-
-
- X# (XSharp)
-
- Welcome to X# (XSharp) <%TXTVERSION%>
-
-
-
- Click here for the version history
- Click here for the list of known issues
- X# is an open source development language for .NET, based on the xBase language.
-
- It comes in different flavors, such as Core, Visual Objects, Vulcan.NET, xBase++, Harbour, Foxpro and more.
- The current version of X# supports the Core dialect as well as the VO, Vulcan and Harbour dialect
-
-
-
- This documentation is still under development. Some sections in the documentation are incomplete.
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_Core.xml b/docs/Help_Spanish/Topics/XSharp_Core.xml
deleted file mode 100644
index 49553e8c9d..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_Core.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- XSharp.Core
-
- XSharp.Core
-
-
-
- XSharp.Core
-
- This is the base DLL of the X# Runtime. It contains:
-
-
Common interfaces, such as IDate, IFloat, ICodeBlock, IMacroCompiler, used by other X# components;
-
Runtime functions that use standard .Net datatypes such as SLen(), AllTrim(), SLen();
-
-
-
The Runtime State (SetDeleted() , SetExact() etc);
-
The Workarea information;
-
The nation resources and collations;
-
-
-
RDD related functions that do not depend on XBase types as DATE, USUAL and FLOAT;
-
-
-
The low level File/IO.
-
- This assembly can be used in all dialects of X#
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_Data.xml b/docs/Help_Spanish/Topics/XSharp_Data.xml
deleted file mode 100644
index c6aa098333..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_Data.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- XSharp.Data
-
-
- XSharp.Data
-
- This DLL contains support code for .Net SQL based data access and for SQL based cursors (VFP).
- The DLL also has data aware classes and functions that return DataTables or DataSources based on workareas/cursors
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_Macrocompiler.xml b/docs/Help_Spanish/Topics/XSharp_Macrocompiler.xml
deleted file mode 100644
index 8cdd13771e..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_Macrocompiler.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- XSharp.Macrocompiler
-
- XSharp.Macrocompiler
-
-
-
- XSharp.Macrocompiler
-
- This DLL is the X# "fast" macro compiler. The Macro compiler is written in C# and has a hardcoded dependency on XSharp.Core.
- Please note that there is no link between XSharp.RT.DLL and XSharp.Macrocompiler.DLL. When you compile a macro, the runtime will try to locate the macro compiler with the method listed below. You can override this mechanism by calling SetMacroCompiler() with the type of the class that implements the macro compiler. This type should implement the XSharp.IMacroCompiler interface. If you want to use the standard macro compiler, you need to add a reference to XSharp.MacroCompiler.dll and add the following code to the startup code of your application:
-
- SetMacroCompiler(typeof(XSharp.Runtime.MacroCompiler))
-
- If you don't do this, the runtime will try to locate the macro compiler in the following locations:
-
-
The directory where the XSharp.RT.DLL is loaded from.
-
The directories in the path. If you use this, make sure that the assemblies listed below are in the same folder as XSharp.MacroCompiler.DLL.
-
The Global Assembly Cache (GAC). If you use this mechanism, make sure that the assemblies listed below are also in the GAC.
-
-
- This assembly depends on:
-
-
XSharp.Core.DLL
-
- Note
- The XSharp installer adds the Macro compiler and the assemblies it depends on to the GAC so you will be able to run your apps without adding the macro compiler to the references list of your application. Please make sure you include the macro compiler in your installer when deploying your applications.
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_Macrocompiler_Full_DLL.xml b/docs/Help_Spanish/Topics/XSharp_Macrocompiler_Full_DLL.xml
deleted file mode 100644
index 69fdadc6cf..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_Macrocompiler_Full_DLL.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- XSharp.Macrocompiler.Full.DLL
-
- XSharp.Macrocompiler.Full.DLL
-
-
-
- XSharp.Macrocompiler.Full.DLL
-
- This DLL is the X# "full" macro compiler. The Macro compiler is created as a class wrapper on top of the X# scripting engine.
We are working on a smaller and faster macro compiler. More news about that will follow.
Please note that there is no link between XSharp.VO.DLL and XSharp.Macrocompiler.DLL. When you compile a macro, the runtime will try to locate the macro compiler with the method listed below. You can override this mechanism by calling SetMacroCompiler() with the type of the class that implements the macro compiler. This type should implement the XSharp.IMacroCompiler interface. If you want to use the full macro compiler in stead of the standard (fast) macro compiler, you need to add a reference to XSharp.MacroCompiler.Full.dll and add the following code to the startup code of your application:
-
- SetMacroCompiler(typeof(XSharp.MacroCompiler))
-
- If you don't do this then the runtime will try to locate the standard macro compiler in the following locations:
-
-
The directory where the XSharp.R.DLL is loaded from.
-
The directories in the path. If you use this, make sure that the assemblies listed below are in the same folder as XSharp.MacroCompiler.DLL.
-
The Global Assembly Cache (GAC). If you use this mechanism, make sure that the assemblies listed below are also in the GAC.
-
-
- This assembly depends on:
-
-
XSharp.Scripting.DLL
-
-
-
XSharp.CodeAnalysis.DLL
-
System.Collections.Immutable
-
System.Reflection.Metadata
-
-
- Note
- The XSharp installer adds the Macro compiler and the assemblies it depends on to the GAC so you will be able to run your apps without adding the macro compiler to the references list of your application. Please make sure you include the macro compiler in your installer when deploying your applications.
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_RDD.xml b/docs/Help_Spanish/Topics/XSharp_RDD.xml
deleted file mode 100644
index 258cd42af1..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_RDD.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- XSharp.RDD
-
- XSharp.RDD
-
-
-
- XSharp.RDD
-
- This DLL contains the various RDDs that come with X#:
-
-
DBFNTX (including DBT memos);
-
DBFCDX (Including FPT memos);
-
-
-
DBFVFP = DBFCDX with support for additional Visual FoxPro datatypes.
-
-
- You can also uses "limited" RDDs which do not have all the functionality:
-
-
CAVODBF or DBF: Just DBF Files;
-
DBFDBT: DBF files with DBT memos, no index support;
-
DBFFPT: DBF files with FPT memos, no index support.
-
-
- The Advantage RDDs (require external advantage DLLs, such as ACE32, ACE64, adsloc32.dll, adsloc64.dll, etc.):
-
-
ADSADT;
-
AXDBFCDX;
-
AXDBFNTX;
-
AXDBFVFP;
-
-
-
-
Advantage.ADSADT;
-
Advantage.AXSQLCDX;
-
Advantage.AXSQLNTX;
-
Advantage.AXSQLVFP.
-
-
- In one of the coming releases we will add support for:
-
-
DBFMEMO = DBF + NTX + DBV;
-
DBFBLOB = DBF without associated DBF file;
-
DELIM;
-
SDF.
-
and perhaps, if there is enough interest:
-
- DBFNSX = DBF + SMT + NSX.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_RT.xml b/docs/Help_Spanish/Topics/XSharp_RT.xml
deleted file mode 100644
index 817495caa1..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_RT.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- XSharp.RT
-
- XSharp.RT
-
-
-
- XSharp.RT
-
- This DLL adds the following features to the runtime:
-
-
XBase specific types , such as DATE, ARRAY, USUAL, PSZ, SYMBOL, etc.;
-
CodeBlock type (base class for compile time codeblocks);
-
_CodeBlock type (base class for macro compiled codeblocks);
-
Runtime functions that accept parameters of these types;
-
Memory related functions (MemAlloc, MemFree etc);
-
Terminal IO functions (QOut(), Accept, Wait);
-
RDD-related functions that have optional parameters or parameters of XBase Type;
-
Functions to compile and evaluate macros (MComp, MExec);
-
Late binding functions such as Send(), IVarGet(), etc.;
-
VObject type;
-
OLEAutoObject type.
-
- This assembly should be linked in when you compile for anything other than the Core dialect
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_RT_Debugger_DLL.xml b/docs/Help_Spanish/Topics/XSharp_RT_Debugger_DLL.xml
deleted file mode 100644
index 85537d5f52..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_RT_Debugger_DLL.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- XSharp.RT.Debugger.DLL
-
- DbgShowGlobals
- DbgShowMemvars
- DbgShowSettings
- DbgShowWorkareas
- XSharp.RT.Debugger.DLL
-
-
-
- XSharp.RT.Debugger.DLL
-
- This DLL adds the runtime Debugger functions and windows:
-
-
DbgShowGlobals();
-
DbgShowWorkareas();
-
DbgShowMemvars();
-
DbgShowSettings().
-
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_VFP.xml b/docs/Help_Spanish/Topics/XSharp_VFP.xml
deleted file mode 100644
index aacc14b47a..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_VFP.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- XSharp.VFP
-
- XSharp.VFP
-
-
-
- XSharp.VFP
-
- This DLL adds some specific types and functions that are unique to the FoxPro dialect.
-
- These are functions such as:
- CreateObject()
- etc.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_VFP_UI.xml b/docs/Help_Spanish/Topics/XSharp_VFP_UI.xml
deleted file mode 100644
index 373c92b30c..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_VFP_UI.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- XSharp.VFP.UI
-
-
- XSharp.VFP.UI
-
- This DLL contains forms and controls that are used by applications converted from FoxPro to X# using the VFP Exporter.
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_VO.xml b/docs/Help_Spanish/Topics/XSharp_VO.xml
deleted file mode 100644
index c5a542bb5d..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_VO.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- XSharp.VO
-
- XSharp.VO
-
-
-
- XSharp.VO
-
- This DLL adds some specific types and functions that are unique to the VO and Vulcan dialect. These are functions such as : QueryRtRegInt()
- QueryRtRegString()
- MB..()
-
- Also, many obsolete functions from VO are in this DLL.
-
- Furthermore, this DLL contains the classes:
- ErrorDialog
- NameArg
- OleAutoObject
- OleAutoObjectFromFile
- OleDateTime
- VObject
-
-
-
diff --git a/docs/Help_Spanish/Topics/XSharp_XPP.xml b/docs/Help_Spanish/Topics/XSharp_XPP.xml
deleted file mode 100644
index 9cfeaa6b22..0000000000
--- a/docs/Help_Spanish/Topics/XSharp_XPP.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- XSharp.XPP
-
- XSharp.XPP
-
-
-
- XSharp.XPP
-
- This DLL adds some specific types and functions that are unique to the Xbase++ dialect, and also many of the Xbase++ defines.
- These are functions such as:
- ClassCreate
- ClassDestroy()
- ClassObject()
- XMLDocOpenFile()
- XMLDocSetAction()
- etc.
-
- Also, these are some Xbase++ specific types such as:
- Abstract
- ClassObject
-
-
diff --git a/docs/Help_Spanish/Topics/_EditorConfig-files.xml b/docs/Help_Spanish/Topics/_EditorConfig-files.xml
deleted file mode 100644
index e3aa349cbe..0000000000
--- a/docs/Help_Spanish/Topics/_EditorConfig-files.xml
+++ /dev/null
@@ -1,70 +0,0 @@
-
-
-
- .EditorConfig files
-
- .editorconfig
- align_do_case
- align_method
- charset
- end_of_line
- identifier_case
- indent_size
- indent_style
- insert_final_newline
- keyword_case
- tab_width
- trim_trailing_whitespace
-
-
-
- .EditorConfig files
-
- Since X# version 2.8, the use of .editorconfig files is supported. These files can be used in your solution or project to control the source code editor settings for several options, such as:
-
-
use tab or space
-
tab with
-
encoding for the source files
-
-
- This allows you to synchronize the editor settings for a team and ignore individual differences between team members.
-
- We are supporting the default tokens for .editorconfig as listed on https://editorconfig.org/:
-
-
indent_style (tab or space)
-
indent_size (number)
-
tab_width (number)
-
end_of_line (cr, lf or crlf)
-
charset (latin1, utf-8, utf-8-bom, utf-16be or utf-16le)
-
trim_trailing_whitespace (true or false)
-
insert_final_newline (true or false)
-
-
- Additionally, we have added a few X# specific options:
-
-
keyword_case (upper, lower, title or none)
-
udc_case (true or false)
-
identifier_case (true or false)
-
-
-
indent_namespace (true or false)
-
-
-
indent_type_members (true or false)
-
indent_type_fields (true or false)
-
-
-
indent_entity_content (true or false)
-
indent_block_content (true or false)
-
indent_case_label (true or false)
-
indent_case_content (true or false)
-
indent_continued_lines (true or false)
-
indent_preprocessor (true or false)
-
-
-
- The settings inside the .editorconfig overrule the settings on Tools/Options for the X# editor.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/__ByRef.xml b/docs/Help_Spanish/Topics/__ByRef.xml
deleted file mode 100644
index 04dabc6869..0000000000
--- a/docs/Help_Spanish/Topics/__ByRef.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
- __ByRef
-
- NotePlease note that passing variables by reference to untyped functions/methods (the so called CLIPPER calling convention) is not supported in the current release of X#
-
-
diff --git a/docs/Help_Spanish/Topics/__CommandInclude.xml b/docs/Help_Spanish/Topics/__CommandInclude.xml
deleted file mode 100644
index 82ed3af391..0000000000
--- a/docs/Help_Spanish/Topics/__CommandInclude.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
- __CommandInclude
-
- NoteThis command is defined in a header file and will be preprocessed by the X# preprocessor to a function call. If you disable the standard header (-nostddefs) files then this command will not be available. If you tell the compiler to use a different standard header file (-stddef ) then this command may also be not available
-
-
diff --git a/docs/Help_Spanish/Topics/__ConsoleExample.xml b/docs/Help_Spanish/Topics/__ConsoleExample.xml
deleted file mode 100644
index e9d16eac51..0000000000
--- a/docs/Help_Spanish/Topics/__ConsoleExample.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- __ConsoleExample
-
-
- __ConsoleExample
-
- FUNCTION Start USE Customers NEW SETALTERNATETO CustomerList.TXT SETCONSOLE OFF DOWHILE .NOT. Eof() ? Customers->LastName, Customers->FirstName ? Customers->Street ? Customers->City + ",", Customers->State, Customers->Zip ? SKIP ENDDO SETALTERNATETO SETCONSOLEON USE
RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/__ExitLoop.xml b/docs/Help_Spanish/Topics/__ExitLoop.xml
deleted file mode 100644
index e75ffe5d2f..0000000000
--- a/docs/Help_Spanish/Topics/__ExitLoop.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- __ExitLoop
-
-
- __ExitLoop
-
- EXITUnconditionally branches control from within a FOR, FOREACH , REPEAT or DO WHILE statement to the statement immediately following the corresponding ENDDO or NEXT statement.
-
- LOOPBranches control to the most recently executed FOR, FOREACH , REPEAT or DO WHILE statement.
-
-
diff --git a/docs/Help_Spanish/Topics/__FieldList.xml b/docs/Help_Spanish/Topics/__FieldList.xml
deleted file mode 100644
index 66ecdcb069..0000000000
--- a/docs/Help_Spanish/Topics/__FieldList.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __FieldList
-
-
- __FieldList
-
- FIELDS <idFieldList>The list of fields to append from <xcSourceFile>. The default is all fields.
- Only fields with the same names and types in both files are appended. If fields with the same name do not match in data type, a runtime error is raised.
-
-
diff --git a/docs/Help_Spanish/Topics/__For.xml b/docs/Help_Spanish/Topics/__For.xml
deleted file mode 100644
index 5c42b72c42..0000000000
--- a/docs/Help_Spanish/Topics/__For.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __For
-
-
- __For
-
- FOR <lCondition>A condition that each visible record within the scope must meet in order to be processed. If a record does not meet the specified condition, it is ignored and the next visible record is processed. If no <Scope> or WHILE clause is specified, having a for condition changes the default scope to all visible records.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__FoxFieldList.xml b/docs/Help_Spanish/Topics/__FoxFieldList.xml
deleted file mode 100644
index cb1e596fd5..0000000000
--- a/docs/Help_Spanish/Topics/__FoxFieldList.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- __FieldList_2
-
-
- __FoxFieldList
-
- FIELDS <idFieldList>The list of fields to process. The default is all fields with the exception of memo fields, unless the command supports the MEMO clause.
- Only fields with the same names and types in both files are appended. If fields with the same name do not match in data type, a runtime error is raised.
- FIELDS LIKE <Skeleton>You can specify field names with a wild card, such as FIELDS LIKE *name
- FIELDS EXCEPT <Skeleton>You can exclude fields, such as for example the primary keys: FIELDS EXCEPT Id <Skeleton> supports wildcards (* and ?). For example, to replace all fields that begin with the letters A and P, use: FIELDS LIKE A*,P*
-
- Please note that you can combine FIELDS LIKE and FIELDS EXCEPT but you cannot combine a fields list with the LIKE and EXCEPT clauses.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__FoxProOnly.xml b/docs/Help_Spanish/Topics/__FoxProOnly.xml
deleted file mode 100644
index d21202eb42..0000000000
--- a/docs/Help_Spanish/Topics/__FoxProOnly.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
- __FoxProOnly
-
- NoteThis command is only available in the FOXPRO dialect
-
-
diff --git a/docs/Help_Spanish/Topics/__In.xml b/docs/Help_Spanish/Topics/__In.xml
deleted file mode 100644
index 933b3c2bc6..0000000000
--- a/docs/Help_Spanish/Topics/__In.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- __In
-
-
- __In
-
- IN|ALIAS <workarea>Specifies the work area for which the operation must be performed
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeAttributes.xml b/docs/Help_Spanish/Topics/__IncludeAttributes.xml
deleted file mode 100644
index fe9229c615..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeAttributes.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-
-
-
- __IncludeAttributes
-
- AttributesAn optional list of one or more attributes that describe meta information for am entity, such as for example the [TestMethod] attribute on a method/function containing tests in a MsTest class library. Please note that Attributes must be on the same line or suffixed with a semi colon when they are written on the line above that keyword.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeBody.xml b/docs/Help_Spanish/Topics/__IncludeBody.xml
deleted file mode 100644
index a957910407..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeBody.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __IncludeBody
-
-
- __IncludeBody
-
- <Body>Program statements that form the code of this entity. The <Body> can contain one or more RETURN statements to return control to the calling routine and to serve as the function return value. If no return statement is specified, control passes back to the calling routine when the function definition ends, and the function will return a default value depending on the return value data type specified (NIL if the return value is not strongly typed). CANNOT be combined with an Expression Body
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeEndMethod.xml b/docs/Help_Spanish/Topics/__IncludeEndMethod.xml
deleted file mode 100644
index 99cfb7c1b1..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeEndMethod.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- __IncludeEndMethod
-
-
- __IncludeEndMethod
-
- END METHODOptional end clause to indicate the end of the inline METHOD entity
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeExpression.xml b/docs/Help_Spanish/Topics/__IncludeExpression.xml
deleted file mode 100644
index f6a88dcab9..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeExpression.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __IncludeExpression
-
-
- __IncludeExpression
-
- <Expression>Expression that implements the accessor
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeExpressionBody.xml b/docs/Help_Spanish/Topics/__IncludeExpressionBody.xml
deleted file mode 100644
index 80fdd2c077..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeExpressionBody.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __IncludeExpressionBody
-
-
- __IncludeExpressionBody
-
- => <Expression>Single expression that replaces the multiline body for the entity. CANNOT be compiled with a body
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeFuncProcModifiers.xml b/docs/Help_Spanish/Topics/__IncludeFuncProcModifiers.xml
deleted file mode 100644
index d032dae878..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeFuncProcModifiers.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- __IncludeFuncProcModifiers
-
-
- __IncludeFuncProcModifiers
-
- ModifiersAn optional list of modifiers that specify the visibility or scope of the entity, such as PUBLIC, STATIC, INTERNAL, EXPORT and UNSAFE.
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeFunctionParameters.xml b/docs/Help_Spanish/Topics/__IncludeFunctionParameters.xml
deleted file mode 100644
index 9b6ffdb2cd..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeFunctionParameters.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- __IncludeFunctionParameters
-
-
- __IncludeFunctionParameters
-
-
- TypeParametersThis is supported for methods with generic type arguments. This something like <T> for a method with one type parameter named T. Usually one of the parameters in the parameter list is then also of type T.
-
-
-
- TypeParameterConstraintsHere you can specify constraints for the Type parameters, such as WHERE T IS SomeName or WHERE T IS New
-
-
-
- EXPORT LOCALThis clause is allowed by X# but ignored.
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeLibCore.xml b/docs/Help_Spanish/Topics/__IncludeLibCore.xml
deleted file mode 100644
index de1fb87076..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeLibCore.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- __IncludeLibCore
-
- XSharp.Core.DLL
-
-
-
- __IncludeLibCore
-
-
- Assembly
- XSharp.Core.DLL
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeLibRT.xml b/docs/Help_Spanish/Topics/__IncludeLibRT.xml
deleted file mode 100644
index 80235a7757..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeLibRT.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __IncludeLibRT
-
-
- __IncludeLibRT
-
- Assembly
- XSharp.RT.DLL
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeLibVFP.xml b/docs/Help_Spanish/Topics/__IncludeLibVFP.xml
deleted file mode 100644
index 7465ff6082..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeLibVFP.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __IncludeLibRT_2
-
-
- __IncludeLibVFP
-
- Assembly
- XSharp.VFP.DLL
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeLocalFunctionParameters.xml b/docs/Help_Spanish/Topics/__IncludeLocalFunctionParameters.xml
deleted file mode 100644
index 0423e9fcfd..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeLocalFunctionParameters.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- __IncludeLocalFunctionParameters
-
-
- __IncludeLocalFunctionParameters
-
-
- TypeParametersThis is supported for methods with generic type arguments. This something like <T> for a method with one type parameter named T. Usually one of the parameters in the parameter list is then also of type T.
-
-
-
- TypeParameterConstraintsHere you can specify constraints for the Type parameters, such as WHERE T IS SomeName or WHERE T IS New
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeMethodModifiers.xml b/docs/Help_Spanish/Topics/__IncludeMethodModifiers.xml
deleted file mode 100644
index f9e8dc244a..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeMethodModifiers.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-
-
-
- __IncludeMethodModifiers
-
-
- ModifiersAn optional list of modifiers that specify the visibility or scope of the entity, such as PUBLIC, PROTECTED, HIDDEN, INTERNAL, SEALED, ABSTRACT or STATIC.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeMethodParameters.xml b/docs/Help_Spanish/Topics/__IncludeMethodParameters.xml
deleted file mode 100644
index 1aa8c7ed81..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeMethodParameters.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- __IncludeMethodParameters
-
-
-
-
-
-
- CLASS <idClass>The class to which this method belongs. This clause is mandatory for entities declared outside of a CLASS .. END CLASS construct
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeParameters.xml b/docs/Help_Spanish/Topics/__IncludeParameters.xml
deleted file mode 100644
index 6c24087f00..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeParameters.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- __IncludeParameters
-
-
- __IncludeParameters
-
- <idParam>A parameter variable. A variable specified in this manner is automatically declared local. These variables, also called formal parameters, are used to receive arguments that you pass when you call the entity.
-
- AS | REF|OUT|IN <idType>Specifies the data type of the parameter variable (called strong typing). AS indicates that the parameter must be passed by value, and REF indicates that it must be passed by reference with the @ operator. OUT is a special kind of REF parameter that does not have to be assigned before the call and must be assigned inside the body of the entity. IN parameters are passed as READONLY references. The last parameter in the list can also be declared as PARAMS <idType>[] which will tell the compiler that the function/method may receive zero or more optional parameters. Functions or Methods of the CLIPPER calling convention are compiled to a function with a single parameter that this declared as Args PARAMS USUAL[]
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeStrongTyping.xml b/docs/Help_Spanish/Topics/__IncludeStrongTyping.xml
deleted file mode 100644
index fd4a270958..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeStrongTyping.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- __IncludeStrongTyping
-
- Strongly typed Methods
-
- In addition to <%APP%> untyped method implementation, strong typing of method parameters and return values is now supported, providing you with a mechanism through which highly stable code can be obtained. The type information supplied enables the compiler to perform the necessary type checking and, thus, guarantee a much higher stable code quality.
-
- A further benefit obtained by utilizing strongly typed methods is that of performance. The implementation of typed methods presumes that when the programmer employs strongly typed messages, the compiler can effectively perform an early binding for the respective methods invocation. As a result of this implementation, typed methods invocations are somewhat faster than the respective untyped counterparts. These advantages are, however, attained at the price of losing the flexibility which untyped methods offer.
-
- It is, therefore, important to remember that interchangeably using both the typed and the untyped versions of a particular methods in an inheritance chain is neither permissible nor possible.
-
- <%APP%> allows strong typing of METHODs, ACCESSes and ASSIGNs. The programmer accomplishes the specification of the strongly typed methods with <%APP%> in two steps:
-
- 1.A mandatory declaration of the typed method is given in its respective class.
- This declaration is reponsible for declaring the order of the methods in the so-called virtual table which <%APP%> employs for the invocation of typed methods. A re-declaration of a method in a subclass is NOT permissible, since it would cause abiguity for the compiler.
- 2.Define the strongly typed method.
- Unlike strongly typed functions, method typing requires strongly typing of the method arguments, the method return value AND speficying a valid calling convention. The following calling conventions are valid for typed methods: STRICT, PASCAL or CALLBACK.
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeTypeParameterConstraints.xml b/docs/Help_Spanish/Topics/__IncludeTypeParameterConstraints.xml
deleted file mode 100644
index af58e536b6..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeTypeParameterConstraints.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __IncludeTypeParameterConstraints
-
-
- __IncludeTypeParameterConstraints
-
- TypeParameterConstraintsHere you can specify constraints for the Type parameters, such as WHERE T IS SomeName or WHERE T IS New
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeTypeParameters.xml b/docs/Help_Spanish/Topics/__IncludeTypeParameters.xml
deleted file mode 100644
index f29ce61b37..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeTypeParameters.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __IncludeTypeParameters
-
-
- __IncludeTypeParameters
-
- TypeParametersThis is supported for methods with generic type arguments. This something like <T> for a method with one type parameter named T. Usually one of the parameters in the parameter list is then also of type T.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__IncludeXPPMethodNames.xml b/docs/Help_Spanish/Topics/__IncludeXPPMethodNames.xml
deleted file mode 100644
index 8a497f5d6b..0000000000
--- a/docs/Help_Spanish/Topics/__IncludeXPPMethodNames.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- __IncludeXPPMethodNames
-
-
- __IncludeXPPMethodNames
-
- Special method Names
- In Xbase++ there are some reserved method names:
-
- InitThis is the name of the constructor
- InitClassThis is the name of the class constructor.
-
- The implementation of constructors in .Net is somewhat different from Xbase++.
-
-
Therefore the class constructor cannot have any parameters.
-
The parameters of the Init() method become the constructor parameters.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__InterpolatedStrings.xml b/docs/Help_Spanish/Topics/__InterpolatedStrings.xml
deleted file mode 100644
index 0ec6e9d167..0000000000
--- a/docs/Help_Spanish/Topics/__InterpolatedStrings.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- __InterpolatedStrings
-
-
- __InterpolatedStrings
-
- Interpolated strings is a feature that allows you to embed local variables, instance variables or other expressions inside literal strings. X# supports two kinds of interpolated strings:
-
- 1.Normal Interpolated strings: i"...."
-
- This works like a normal X# string but with an embedded expression:
-
- FUNCTION Start ASVOID LOCAL Who ASSTRING Who := "World" Console.Writeline( i"Hello {Who}") Console.Read() RETURN
- 2.Extended Interpolated strings: ie"..." and ei"...."
- This is a combination of an interpolated string and an extended string. In the example below the \t will be replaced with a tab character:
-
- FUNCTION Start ASVOID LOCAL Who ASSTRING Who := "World" Console.Writeline( ie"Hello\t{Who}") Console.Read() RETURN
- Notes
- Expression inside Interpolated strings inside X# have the form of
- {<interpolationExpression>[,<alignment>][::<formatString>]}
- In C# the formatString is prefixed with a single colon. Please note that because in X# the colon (:) operator is the default member access operator for instance fields, properties and methods, it is not always possible to use that operator to separate expressions and format string. We have therefore changed that operator to the double colon (::). I you compile with /allowdot+ then you can also use the single colon for the format separator.
- To represent a literal '{' or '}' character you will have to duplicate them inside the string. The expressions inside the string are in italics in this example.
-
- An example of this could be
- FUNCTION Start() ASVOID local X := 2 asINT local Y := 3 asINT var pointMessage := i"The point {{{X}, {Y}}} is {Math.Sqrt(X * X + Y * Y)::F3} from the origin" Console.WriteLine(pointMessage) // Output is: // The point {2, 3} is 3.606 from the origin
-
- The expression elements inside the string can use formatting notation just like the String.Format() notation. For example:
-
- FUNCTION Start ASVOID LOCAL i AS INT i := 42 Console.Writeline( i"Hello {i:x}") // i is printed in hex notation, so Hello 2a Console.Read() RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/__NotInCoreVulcan.xml b/docs/Help_Spanish/Topics/__NotInCoreVulcan.xml
deleted file mode 100644
index 3c50bbfad8..0000000000
--- a/docs/Help_Spanish/Topics/__NotInCoreVulcan.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
- __NotInCoreVulcan
-
- NoteThis command is not available in the Core and Vulcan dialects
-
-
diff --git a/docs/Help_Spanish/Topics/__Scope.xml b/docs/Help_Spanish/Topics/__Scope.xml
deleted file mode 100644
index bb5e1abe5f..0000000000
--- a/docs/Help_Spanish/Topics/__Scope.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __Scope
-
-
- __Scope
-
- <Scope>The portion of the current database file to process. The default is all visible records. Scope is one or more clauses of: [NEXT <NEXT>]Optionally specifies the number of records to process starting with the first record of the source file. [RECORD <rec>]An optional record ID If specified, the processing begins with this data record in the source file. [<rest:REST>]The option REST specifies whether records are sequentially searched only from the current up to the last record. If a condition is specified, the option ALL is the default value. [ALL]The option ALL specifies that all records from the source file are imported. This is the default setting.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__SeeAlsoExitLoop.xml b/docs/Help_Spanish/Topics/__SeeAlsoExitLoop.xml
deleted file mode 100644
index 920b2e2467..0000000000
--- a/docs/Help_Spanish/Topics/__SeeAlsoExitLoop.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __SeeAlsoExitLoop
-
-
- __SeeAlsoExitLoop
-
- See Also
- EXIT, LOOP
-
-
diff --git a/docs/Help_Spanish/Topics/__TextMerge-Example.xml b/docs/Help_Spanish/Topics/__TextMerge-Example.xml
deleted file mode 100644
index 238611ebd2..0000000000
--- a/docs/Help_Spanish/Topics/__TextMerge-Example.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- __TextMerge Example
-
-
- __TextMerge Example
-
- CLEAR CLOSEDATABASES SETTEXTMERGEON SETTEXTMERGETO ContactList.TXT USE customer TEXT CONTACT NAMES <<DATE( )>> <<TIME( )>> ENDTEXT WAIT "Press a key to generate the first ten names." SCANNEXT 10 TEXT <<contact>> ENDTEXT ENDSCAN CLOSEALL
-
-
diff --git a/docs/Help_Spanish/Topics/__TypeAndCLass.xml b/docs/Help_Spanish/Topics/__TypeAndCLass.xml
deleted file mode 100644
index e78fd51392..0000000000
--- a/docs/Help_Spanish/Topics/__TypeAndCLass.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- __TypeAndCLass
-
-
- __TypeAndCLass
-
- <Type> & <ClassLibrary>The compiler recognizes the AS <Type> and the AS <Type> of <Classlibrary> clauses in the FoxPro dialect.
-
-
diff --git a/docs/Help_Spanish/Topics/__VoVulcanOnly.xml b/docs/Help_Spanish/Topics/__VoVulcanOnly.xml
deleted file mode 100644
index 8082392fc0..0000000000
--- a/docs/Help_Spanish/Topics/__VoVulcanOnly.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
- __VoVulcanOnly
-
- NoteThis command is only available in the VO and Vulcan dialects
-
-
diff --git a/docs/Help_Spanish/Topics/__VsDialect.xml b/docs/Help_Spanish/Topics/__VsDialect.xml
deleted file mode 100644
index 1939bd58e6..0000000000
--- a/docs/Help_Spanish/Topics/__VsDialect.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- __VsDialect
-
-
- __VsDialect
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page
-
Click the Dialect tab.
-
Change the value
-
-
-
diff --git a/docs/Help_Spanish/Topics/__While.xml b/docs/Help_Spanish/Topics/__While.xml
deleted file mode 100644
index 892f9afc61..0000000000
--- a/docs/Help_Spanish/Topics/__While.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __While
-
-
- __While
-
- WHILE <lCondition>A condition that each visible record within the scope must meet, starting with the current record. As soon as the while condition fails, the process terminates. If no <Scope> is specified, having a while condition changes the default scope to the rest of the visible records in the file.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__XppOnly.xml b/docs/Help_Spanish/Topics/__XppOnly.xml
deleted file mode 100644
index d098e7837e..0000000000
--- a/docs/Help_Spanish/Topics/__XppOnly.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-
-
-
- __XppOnly
-
- NoteThis command is only available in the Xbase++ dialect
-
-
diff --git a/docs/Help_Spanish/Topics/__asType.xml b/docs/Help_Spanish/Topics/__asType.xml
deleted file mode 100644
index 727607bcd1..0000000000
--- a/docs/Help_Spanish/Topics/__asType.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __asType
-
-
- __asType
-
- AS <idType>Specifies the data type. If omitted, then depending on the compiler options the type will be either USUAL or determined by the compiler.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__buildExtra.xml b/docs/Help_Spanish/Topics/__buildExtra.xml
deleted file mode 100644
index ab9eb429f9..0000000000
--- a/docs/Help_Spanish/Topics/__buildExtra.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- __buildExtra
-
-
- __buildExtra
-
- To set this compiler option in the Visual Studio development environment
-
-
-
Open the project's Properties page.
-
Click the Build property page.
-
Add the option in the "Extra Command Line options" property
-
-
-
diff --git a/docs/Help_Spanish/Topics/__callingconvention.xml b/docs/Help_Spanish/Topics/__callingconvention.xml
deleted file mode 100644
index 9902259068..0000000000
--- a/docs/Help_Spanish/Topics/__callingconvention.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- __callingconvention
-
-
- __callingconvention
-
- <idConvention>Specifies the calling convention for this entity. <idConvention> must be one of the following:
-
-
-
CLIPPER
-
STRICT
-
PASCAL
-
CALLBACK
-
THISCALL
-
-
- Most calling conventions are for backward compatibility only. There are 2 exceptions: CLIPPER declares that a method has untyped parameters. This is usually only needed for methods without any declared parameters. Otherwise the compiler will assume CLIPPER calling convention when it detects untyped parameters. Methods and Functions in external DLL may have STRICT, PASCAL, CALLBACK
-
-
-
diff --git a/docs/Help_Spanish/Topics/__includeIdClass.xml b/docs/Help_Spanish/Topics/__includeIdClass.xml
deleted file mode 100644
index 7064d422e9..0000000000
--- a/docs/Help_Spanish/Topics/__includeIdClass.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- __includeIdClass
-
-
- __includeIdClass
-
- <idClass>A valid identifier name for the class. A class is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a class and a global variable, for example, with the same name.
-
-
-
diff --git a/docs/Help_Spanish/Topics/__isType.xml b/docs/Help_Spanish/Topics/__isType.xml
deleted file mode 100644
index aa7bacb4dd..0000000000
--- a/docs/Help_Spanish/Topics/__isType.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- __isType
-
-
- __isType
-
- IS <idType>Specifies a VOSTRUCT or UNION data type in which the memory needed to hold the structure is allocated on the stack (<idStructure> is the only <idType> allowed with the IS keyword.) See the VOSTRUCT entry in this guide for more information on data structure memory allocation.
-
-
diff --git a/docs/Help_Spanish/Topics/__localSpec.xml b/docs/Help_Spanish/Topics/__localSpec.xml
deleted file mode 100644
index 86b06252ea..0000000000
--- a/docs/Help_Spanish/Topics/__localSpec.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- __localSpec
-
-
- __localSpec
-
-
- <idVar>A valid identifier name for the local variable to declare.
-
- <uValue>The initial value to assign to the variable.
-
- For LOCAL, this can be any valid expression.
-
- For STATIC LOCAL, this value can be a literal representation of one of the data types listed below or a simple expression involving only operators, literals, and DEFINE constants; however, more complicated expressions (including class instantiation) are not allowed.
-
- Note: Although <uValue> can be a literal array, it must be one-dimensional. Multi-dimensional literal arrays are not allowed. For example, {1, 2, 3} is allowed, but {{1, 2, 3}, {4, 5, 6}, {7, 8, 9}} is not.
-
- Note: Although the Chr() function cannot be used in <uValue>, the _Chr() operator can. _Chr() is otherwise identical in functionality to Chr().
-
- If <uValue> is not specified, the initial value of the variable depends on the data type you declare (e.g., NIL if you do not use strong typing, 0 for AS INT, etc.)
-
- DIM <ArraySpec>The specification for a dimensioned array to declare.
-
- <ArraySpec>The specification for a dynamic array to declare. In both cases, <ArraySpec> is one of the following: <idArray>[<nElements>, <nElements>, <nElements>] <idArray>[<nElements>][<nElements>][<nElements>] All dimensions except the first are optional.
-
- <idArray> is a valid identifier name for the array to declare. For dynamic arrays, array elements are initialized to NIL. For dimensioned arrays, the initial value of the elements depends on the data type as explained above for <uValue>.
-
- <nElements> defines the number of elements in a particular dimension of an array. The number of dimensions is determined by how many <nElements> arguments you specify.
-
- <nElements> can be a literal numeric representation or a simple numeric expression involving only operators, literals, and DEFINE constants; however, more complicated expressions (such as function calls) are not allowed.
-
-
-
-
- IS <idType>Specifies a structure data type in which the memory needed to hold the structure is allocated on the stack (<idStructure> is the only <idType> allowed with the IS keyword.) See the VOSTRUCT entry in this guide for more information on data structure memory allocation.
-
- AS ARRAYFor dynamic array declarations, specifies the data type of the entire array.
-
- <arrayName>Variable name of array . The array will have the dimensions as declared with <nRows> and <nColumns>. The array may be declared with parentheses as delimiters but also with square brackets. We recommend the use of square brackets.
-
-
diff --git a/docs/Help_Spanish/Topics/__typeList.xml b/docs/Help_Spanish/Topics/__typeList.xml
deleted file mode 100644
index a34b1f6bac..0000000000
--- a/docs/Help_Spanish/Topics/__typeList.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- __typeList
-
-
- __typeList
-
- The valid values for <idType> and the initial values associated with each are listed in the table below:
-
- Data TypeDefault/Initial Value
- ARRAYNULL_ARRAY
- CODEBLOCKNULL_CODEBLOCK
- DATENULL_DATE
- LOGICFALSE
- OBJECTNULL_OBJECT
- <idClass>NULL_OBJECT
- STRINGNULL_STRING
- SYMBOLNULL_SYMBOL
- All numerics0
- USUALNIL
- PSZNULL_PSZ
- PTRNULL_PTR
-
-
-
diff --git a/docs/Help_Spanish/Topics/_showdefs.xml b/docs/Help_Spanish/Topics/_showdefs.xml
deleted file mode 100644
index d4dfe4c65a..0000000000
--- a/docs/Help_Spanish/Topics/_showdefs.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- opt-showdefs
-
- -showdefs
-
-
-
- /showdefs
-
- Shows the #define tokens that the preprocessor sees.
- Syntax
- /showdefs[+|-]
- Arguments
- + | - Specifying +, or just /showdefs, causes the compiler to output the names of #defines as they are processed.
- Remarks
- This command line option is useful to debug the defines that are included in the compilation.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_Database.xml b/docs/Help_Spanish/Topics/cmd_cat_Database.xml
deleted file mode 100644
index a8bee65cbe..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_Database.xml
+++ /dev/null
@@ -1,70 +0,0 @@
-
-
-
- Database
-
- /nostddef
- CommandsDatabase
- Database Commands
-
-
-
- Database
-
- Most Database commands are implemented as User Defined command in the standard header files, and call Runtime Functions under the hood.
- Make sure that you include the standard header file during compilation (so do NOT use the option -nostddefs).
- If you use the compiler option -stddefs to use an alternate standard header file, it is your responsibility to make sure that these commands are implemented.
-
- APPEND BLANK
- APPEND FROM
- AVERAGE
- CLEAR ALL
- CLOSE
- COMMIT
- CONTINUE
- COPY STRUCTURE
- COPY STRUCTURE EXTENDED
- COPY TO
- COUNT
- CREATE
- CREATE FROM
- DELETE
- DELETE TAG
- FIELD
- FIND
- GO|GOTO
- INDEX
- JOIN
- LOCATE
- PACK
- RECALL
- REINDEX
- REPLACE
- SEEK
- SELECT
- SET DELETED
- SET DESCENDING
- SET DRIVER
- SET EXCLUSIVE
- SET FILTER
- SET INDEX
- SET MEMOBLOCK
- SET OPTIMIZE
- SET ORDER
- SET RELATION
- SET SCOPE
- SET SCOPEBOTTOM
- SET SCOPETOP
- SET SOFTSEEK
- SET UNIQUE
- SKIP
- SORT
- SUM
- TOTAL
- UNLOCK
- UPDATE
- USE
- ZAP
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_comment.xml b/docs/Help_Spanish/Topics/cmd_cat_comment.xml
deleted file mode 100644
index 9e5739259e..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_comment.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Comment
-
- CommandsComments
- Comments
-
-
-
- Comment
-
-
- NOTE
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_concur.xml b/docs/Help_Spanish/Topics/cmd_cat_concur.xml
deleted file mode 100644
index a3043a6e16..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_concur.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- Concurrency Control
-
- CommandsConcurrency ControlLocking
- Concurrency Control Commands
- Locking Commands
-
-
-
- Concurrency Control
-
-
- COMMIT
- SET EXCLUSIVE
- UNLOCK
- USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_control.xml b/docs/Help_Spanish/Topics/cmd_cat_control.xml
deleted file mode 100644
index 761af9925f..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_control.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- Program Control
-
- CommandsProgram Control
- Program control
-
-
-
- Program Control
-
-
- #ifdef
- #else
- #endif
- #ifndef
- ASYNC .. AWAIT
- BEGIN SEQUENCE
- BREAK
- CANCEL
- DEFAULT
- DO
- DO CASE
- DO WHILE
- EXTERNAL
- FOR
- FOREACH
- IF
- LOOP
- NOP
- QUIT
- REPEAT UNTIL
- RETURN
- RUN
- SWITCH
- TEXT
- THROW
- TRY CATCH
- WITH
- YIELD
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_date.xml b/docs/Help_Spanish/Topics/cmd_cat_date.xml
deleted file mode 100644
index 5e28dd381c..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_date.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Date and Time
-
- CommandsDate
- Date Commands
-
-
-
- Date and Time
-
-
- SET CENTURY
- SET DATE
- SET DATE FORMAT
- SET EPOCH
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_entdecl.xml b/docs/Help_Spanish/Topics/cmd_cat_entdecl.xml
deleted file mode 100644
index 5fad437b0d..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_entdecl.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- Entity Declaration
-
- CommandsEntity Declaration
- Entity Declaration Commands
-
-
-
- Entity Declaration
-
-
- _DLL
- ACCESS
- ASSIGN
- CLASS (Generic)
- CLASS (FoxPro)
- CLASS (Xbase++)
- CONSTRUCTOR
- DECLARE METHOD
- DEFINE
- DELEGATE
- DESTRUCTOR
- ENUM
- EVENT
- FUNCTION
- GLOBAL
- INTERFACE
- METHOD
- OPERATOR
- PROCEDURE
- PROPERTY
- STRUCTURE
- UNION
- VOSTRUCT
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_file.xml b/docs/Help_Spanish/Topics/cmd_cat_file.xml
deleted file mode 100644
index b90fbcf62d..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_file.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- File
-
- CommandsFile
- File Commands
-
-
-
- File
-
-
- COPY FILE
- DELETE FILE
- DIR
- ERASE
- RENAME
- SET DEFAULT
- SET PATH
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_index.xml b/docs/Help_Spanish/Topics/cmd_cat_index.xml
deleted file mode 100644
index e2380246f9..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_index.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- Index/Order
-
- CommandsIndexIndex / OrderOrder
- Index Commands
- Index/Order Commands
- Order Commands
-
-
-
- Index/Order
-
-
- CLOSE
- DELETE TAG
- FIND
- INDEX
- REINDEX
- SEEK
- SET DESCENDING
- SET INDEX
- SET OPTIMIZE
- SET ORDER
- SET SCOPE
- SET SCOPEBOTTOM
- SET SCOPETOP
- SET SOFTSEEK
- SET UNIQUE
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_international.xml b/docs/Help_Spanish/Topics/cmd_cat_international.xml
deleted file mode 100644
index 0628bfc88e..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_international.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- International
-
- CommandsInternational
- International Commands
-
-
-
- International
-
-
- SET COLLATION
- SET INTERNATIONAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_memvar.xml b/docs/Help_Spanish/Topics/cmd_cat_memvar.xml
deleted file mode 100644
index e73bc5248d..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_memvar.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- Memory Variable
-
- CommandsMemory Variable
- Memory Variable Commands
-
-
-
- Memory Variable
-
-
- CLEAR MEMORY
- DECLARE
- MEMVAR
- PARAMETERS
- PRIVATE
- PUBLIC
- RELEASE
- RESTORE
- SAVE
- STORE
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_num.xml b/docs/Help_Spanish/Topics/cmd_cat_num.xml
deleted file mode 100644
index d7c7a3e4b8..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_num.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Numeric
-
- CommandsNumeric
- Numeric Commands
-
-
-
- Numeric
-
-
- SET DECIMALS
- SET DIGITFIXED
- SET DIGITS
- SET FIXED
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_rtdecl.xml b/docs/Help_Spanish/Topics/cmd_cat_rtdecl.xml
deleted file mode 100644
index ba1087ea8d..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_rtdecl.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Runtime Declaration
-
- CommandsRuntime Declaration
- Runtime Declaration Commands
-
-
-
- Runtime Declaration
-
- LOCAL Statement
- DECLARE
- PARAMETERS
- PRIVATE
- PUBLIC
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_set.xml b/docs/Help_Spanish/Topics/cmd_cat_set.xml
deleted file mode 100644
index 6534559e03..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_set.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- Environment
-
- CommandsEnvironment
- Environment Commands
-
-
-
- Environment
-
-
- SET ANSI
- SET CENTURY
- SET DATE
- SET DATE FORMAT
- SET DECIMALS
- SET DEFAULT
- SET DIGITFIXED
- SET DIGITS
- SET DRIVER
- SET EPOCH
- SET EXCLUSIVE
- SET FIXED
- SET PATH
-
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_terminal.xml b/docs/Help_Spanish/Topics/cmd_cat_terminal.xml
deleted file mode 100644
index 5b2a11fed4..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_terminal.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- Terminal Window
-
- CommandsTerminal Window
- Terminal Window Commands
-
-
-
- Terminal Window
-
- ?|??
- ACCEPT
- SET COLOR
- WAIT
-
- Note: <%APP%> does not support the following commands:
-
- @...BOX
- @...CLEAR
- @...SAY
- @...TO
- @..GET
- DISPLAY
- INPUT
- LIST
- READ
- SET CONSOLE
- SET DEVICE
- SET PRINTER
- TEXT ... ENDTEXT
- TYPE
-
-
diff --git a/docs/Help_Spanish/Topics/cmd_cat_vardecl.xml b/docs/Help_Spanish/Topics/cmd_cat_vardecl.xml
deleted file mode 100644
index f357145458..0000000000
--- a/docs/Help_Spanish/Topics/cmd_cat_vardecl.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Variable Declaration
-
- CommandsVariable Declaration
- Variable Declaration Commands
-
-
-
- Variable Declaration
-
-
- FIELD
- LOCAL
- MEMVAR
- STATIC
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_ACCEPT.xml b/docs/Help_Spanish/Topics/command_ACCEPT.xml
deleted file mode 100644
index 6d96c21e5e..0000000000
--- a/docs/Help_Spanish/Topics/command_ACCEPT.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- ACCEPT Command
-
- ACCEPT command
- Commands
- Terminal window
- Wait states
-
-
-
- ACCEPT Command
-
-
- Purpose
- Takes input from the keyboard and assigns it to a memory variable.
- Syntax
- ACCEPT [<uValuePrompt>] TO <idVar>
- Arguments
- <uValuePrompt>An optional prompt displayed before the input area.
- TO <idVar>The variable that will hold input from the keyboard. If there is no variable named <idVar> that is visible to the current routine, a private variable is created.
- Description
- When ACCEPT is executed, it first performs a carriage return/linefeed, displays the prompt in the terminal window, and begins taking characters from the keyboard at the position immediately following the prompt.
-
- Up to 255 characters can be entered. When input reaches the edge of the window, as defined by MaxCol(), the cursor moves to the next line.
-
- ACCEPT supports only two editing keys: Backspace and Enter (Esc is not supported). Backspace deletes the last character typed. Enter confirms entry and is the only key that can terminate an ACCEPT. If Enter is the only key pressed, ACCEPT assigns a NULL_STRING to <idVar>.
- Examples
- This example uses ACCEPT to get keyboard input from the user:
-
- LOCAL cVar ACCEPT "Enter a value: "TO cVar IF cVar = NULL_STRING ?"User pressed Enter" ELSE ?"User input:", cVar ENDIF
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_ACCESS.xml b/docs/Help_Spanish/Topics/command_ACCESS.xml
deleted file mode 100644
index 34ee26eb8c..0000000000
--- a/docs/Help_Spanish/Topics/command_ACCESS.xml
+++ /dev/null
@@ -1,92 +0,0 @@
-
-
-
- ACCESS Statement
-
- ACCESS statement
- Access() Methods
- Compile-time declaration
- Declaration statements
- Entity declaration
- Instance variables
- Instance variables
- Instance variablesaccessingnon-exportedvirtual variables
- Methodsaccessing instance variables
- Statements
- Strong typingdefined
- Virtual variables
-
-
-
- ACCESS Statement
-
- Purpose
- Declare a method to access a non-exported or virtual instance variable.
- Syntax
- [Attributes] [Modifiers] ACCESS <idName>
- [([<idParam> [AS | REF <idType>] [, ...])]
- [AS <idType>] [<idConvention>]
- [CLASS <idClass>]
- [=> <expression>]
- CRLF
- [<Body>]
- [END ACCESS]
- Arguments
-
- <idName>A valid identifier name for the instance variable whose access method you are defining. Like other methods, access methods are entities; however, the system uses a unique naming scheme for them to prevent collisions with other entity names. Access method names must be unique within a class, but can share the same name as other entities in your application.
-
-
- END ACCESSOptional end clause to indicate the end of the ACCESS entity.
- Description
- ACCESS declares a special method, called an access method, that is automatically executed each time you access the named instance variable.
-
- You can define four types of instance variables in a CLASS declaration. All of these, except EXPORT, are called non-exported instance variables, because they are not directly accessible externally (i.e., outside of the class).
-
- For example, if you want to access a non-exported instance variable of an object from a function, you must use a method. Indeed, this is the purpose of not exporting the variable: encapsulation by being able to control all references to it through a method. However, the syntax for referencing a method is obviously different from that of referencing a variable. This violates encapsulation and is just plain cumbersome, since users of the class must be aware of how a property of the class is implemented in order to know whether to use a functional style or a variable style of reference.
-
- For example, note the difference in accessing the instance variables x and y in the function UseClass() when the class uses a regular method for exporting the variable:
-
- CLASS Test EXPORT x :=100 INSTANCE y :=10000
METHOD GetValueY()CLASS Test RETURN y
FUNCTION UseClass() LOCAL oTest AS Test oTest := Test{} ? oTest:x ? oTest:GetValueY()// Access y using method
-
- If you replace the regular method with an access method, the syntax for accessing both variables is the same, even though one of them is insulated by a method:
-
- ACCESS y CLASS Test RETURN y
FUNCTION UseClass() LOCAL oTest AS Test oTest := Test{} ? oTest:x ? oTest:y// Using ACCESS method
-
- Non-exported variables come in three categories, each with its own properties (see the CLASS statement entry in this guide for details):
-
-
INSTANCE
-
PROTECT
-
HIDDEN
-
-
- INSTANCE variables are specifically designed to work with access and assign methods which is the main reason for their late binding. By defining an access method with the same name as an INSTANCE variable, you effectively override the variable by causing all non-assignment references, both external and internal, to invoke the access method.
-
- The exception is that within an access (or assign) method, instance variables of the same name refer to the variable — otherwise, you would never get anywhere.
- For example:
-
- CLASS Person INSTANCE Name, SSN
ACCESS Name CLASS Person RETURN Name // Refers to variable Name
METHOD ShowName() CLASS Person ? Name // Refers to ACCESS method
- You can also use PROTECT and HIDDEN variables in conjunction with access methods. By defining an access method with the same name as a PROTECT or HIDDEN variable, you can access the variable externally, using the same syntax as you would inside the class. Internal references, however, always refer directly to the variable because of early binding.
-
- Of course, you do not have to give the access method and the instance variable the same name, this is only for your convenience. It is the return value of the method that is used when you access <idVar>. Thus, for PROTECT/HIDDEN variables, you can provide an access method with a different name. For example:
-
- CLASS Person PROTECT Name_Protected
ACCESS Name CLASS Person RETURN Name_Protected
- A virtual variable is one that is not defined as part of the class but composed from other instance variables. In other words, it is a variable that is calculated based on the values of other instance variables. As with non-exported instance variables, you could use a regular method to compute virtual variables, but this means using a different syntax for accessing them. Access methods extend the syntax used for accessing instance variables to virtual variables.
- For example:
-
- CLASS Person INSTANCE Name, SSN
ACCESS Name CLASS Person RETURN Name
METHOD Init(cName, cSSN) CLASS Person Name := cName SSN := cSSN
ACCESS FullID CLASS Person RETURN Name + SSN
FUNCTION UseClass() LOCAL oFriend AS Person oFriend := Person{"Bill Brown", "213-88-9546"} ? oFriend:Name // Bill Brown ? oFriend:FullID // Bill Brown213-88-9546
- EXPORT variables are a lot faster and easier to use than non-exported variables and access methods, but using them defies the encapsulation that you should strive for to maintain the integrity of your application. Using access and assign methods, you can use exported variables early in the prototyping stage of an application, and later protect the variables with methods without changing the class interface.
-
- ACCESS is a special case of METHOD and, except for the way you invoke it (i.e., without arguments, like an instance variable), its behavior is the same as any other method. See the METHOD statement in this guide for more details.
-
- Note: Internal references to access methods that do not have a corresponding regular INSTANCE variable (e.g., virtual variables or public access to HIDDEN or PROTECT variables with different names) must use the SELF: prefix. Internal references means references from inside methods of the class or one of its subclasses. If the system does not find an instance variable, it assumes a memory variable (which can produce a compiler error depending on whether Allow Undeclared Variables has been chosen in the compiler settings), and it does not attempt to identify the reference as an access method, unless SELF: is used.
-
-
- Examples
- The following example uses ACCESS to perform a calculation based on the value of other instance variables:
-
- CLASS Rectangle INSTANCE Length, Height ASINT
METHOD Init(nX, nY) CLASS Rectangle Length := nX Height := nY RETURNSELF
ACCESS Area CLASS Rectangle RETURN Length * Height
FUNCTION FindArea() LOCAL oShape AS Rectangle oShape := Rectangle{3, 4} ? oShape:Area // Displays: 12
- See Also
- ASSIGN, CLASS, METHOD, PROPERTY
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_APPEND_BLANK.xml b/docs/Help_Spanish/Topics/command_APPEND_BLANK.xml
deleted file mode 100644
index 9da52fefa5..0000000000
--- a/docs/Help_Spanish/Topics/command_APPEND_BLANK.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
- APPEND BLANK Command
-
- Addingrecords
- APPEND BLANK command
- Commands
- Databases
- Recordsadding
-
-
-
- APPEND BLANK Command
-
-
- Purpose
- Add a new record to the end of the current database file and make it the current record.
- Syntax
- APPEND BLANK [[IN|ALIAS] <workarea>]
-
- Arguments
-
- Description
- The new field values are initialized to the empty values for each data type: character fields are assigned with spaces; numeric fields are assigned 0; logical fields are assigned FALSE; date fields are assigned NULL_DATE; and memo fields are left empty.
-
- For a shared database, APPEND BLANK automatically places a record lock on the new record. If the record cannot be locked, NetErr() is set to TRUE, indicating that the record was not added, and execution continues.
-
- Note: APPEND BLANK will not release any file locks set by the current process.
- If NetErr() returns FALSE, the record was successfully added and locked, you can begin updating it. The newly appended record remains locked until you explicitly release the lock (for example, with UNLOCK), close the database file, or attempt another lock.
- Examples
- This example attempts to add a record to a shared database file and uses NetErr() to test if the operation succeeded:
-
- USE sales SHAREDNEW <Statements>... APPEND BLANK IF !NetErr() <Update EMPTY record>... ELSE ? "Append operation failed" BREAK ENDIF
-
- See Also
- APPEND FROM, DBAppend(), DBRLock(), FLock(), NetErr(), RLock()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_APPEND_FROM.xml b/docs/Help_Spanish/Topics/command_APPEND_FROM.xml
deleted file mode 100644
index 4b5ccfbbbc..0000000000
--- a/docs/Help_Spanish/Topics/command_APPEND_FROM.xml
+++ /dev/null
@@ -1,93 +0,0 @@
-
-
-
- APPEND FROM Command
-
- APPEND FROM command
- Commands
- Databases
- Importingrecords
- Recordsimporting
-
-
-
- APPEND FROM Command (non FoxPro)
-
-
- Purpose
- Import records from a database or text file.
- Syntax
- APPEND FROM <xcSourceFile> [FIELDS <idFieldList>] [<Scope>] [WHILE <lCondition>] [FOR <lCondition>] [SDF] | [DELIMITED [WITH <xcDelimiter> | BLANK]] | [VIA <cDriver>] [INHERIT FROM <acRDDs>]
- Arguments
- FROM <xcSourceFile>The name of the source file to be used for adding records, which may include an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD. For text files, it is .TXT.
- This command attempts to open <xcSourceFile> in shared mode. If the file does not exist, a runtime error is raised. If the file is successfully opened, the operation proceeds. If access is denied because, for example, another process has exclusive use of the file, NetErr() is set to TRUE.
-
-
-
-
-
-
- SDFA System Data Format file with format specifications as shown in the table below. Records and fields are fixed length.
-
-
- File ElementFormat
- Character fieldsPadded with trailing blanks
- Date fieldsyyyymmdd
- Logical fieldsT or F
- Memo fieldsIgnored
- Numeric fieldsPadded with leading blanks or zeros
- Field separatorNone
- Record separatorCarriage return/linefeed
- End of file marker1A hex or Chr(26)
-
- DELIMITED [WITH <xcDelimiter>]
- A text file in which character fields are enclosed in double quote marks (the default delimiter) or the specified <xcDelimiter>. Fields and records vary in length, and the format specifications are shown in the table below:
-
-
- File ElementFormat
- Character fieldsCan be delimited, with trailing blanks truncated
- Date fieldsyyyymmdd
- Logical fieldsT or F
- Memo fieldsIgnored
- Numeric fieldsLeading zeros can be truncated
- Field separatorComma
- Record separatorCarriage return/linefeed
- End of file marker1A hex or Chr(26)
- Note: Delimiters are not required and APPEND FROM correctly handles character fields not enclosed with them.
-
- DELIMITED WITH BLANK
- A text file in which fields are separated by one space and character fields are not enclosed in delimiters. The format specifications are shown in the table below:
-
- File ElementFormat
- Character fieldsNot delimited, trailing blanks can be truncated
- Date fieldsyyyymmdd
- Logical fieldsT or F
- Memo fieldsIgnored
- Numeric fieldsLeading zeros can be truncated
- Field separatorSingle blank space
- Record separatorCarriage return/linefeed
- End of file marker1A hex or Chr(26)
- Warning! If the DELIMITED WITH clause is specified on an APPEND FROM command line, it must be the last clause specified.
-
- VIA <cDriver>The name of the RDD that will service the work area. If not specified, the default RDD as determined by RDDSetDefault() is used.
-
- INHERIT FROM <acRDDs>
- A one-dimensional array with the names of RDDs from which the main RDD inherits special functionality. This allows you to use RDDs with special capabilities, like encryption or decryption, in different work areas with different database drivers. These RDDs overlay special functions of the main RDD (specified with the VIA clause). If multiple RDDs (specified with this INHERIT FROM clause) implement the same function, the function associated with the last RDD in the list takes precedence.
- Notes
- Deleted records: If SetDeleted() is FALSE, deleted records in <xcSourceFile> are appended to the current database file and retain their deleted status. If SetDeleted() is TRUE, however, deleted records are not visible and are, therefore, not processed.
-
- Unmatched field widths: If a field in the current database file is character type and has a field length greater than the incoming <xcSourceFile> data, APPEND FROM pads the source data with blanks. If the current field is character data type and its field length is less than the incoming source data, the source data is truncated to fit. If the current field is numeric type and the incoming source data has more digits than the current field length, a runtime error is raised.
- Examples
- This example demonstrates an APPEND FROM command using a fields list and a condition:
-
- USE sales NEW APPENDFROM branchfile FIELDS Branch, Salesman, Amount FOR Branch = 100
-
- The next example demonstrates how a <Scope> can be specified to import a particular record from another database file:
-
- APPEND RECORD 5 FROM temp
-
- See Also
- COPY TO, DbApp(), DbAppDelim(), DbAppSDF(), RDDSetDefault(), SetDefault(), SetPath(), SetDeleted()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_APPEND_FROM_FoxPro.xml b/docs/Help_Spanish/Topics/command_APPEND_FROM_FoxPro.xml
deleted file mode 100644
index a440b9f98f..0000000000
--- a/docs/Help_Spanish/Topics/command_APPEND_FROM_FoxPro.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-
-
-
- APPEND FROM Command (FoxPro)
-
- APPEND FROM command
- Commands
- Databases
- Importingrecords
- Recordsimporting
-
-
-
- APPEND FROM Command (FoxPro)
-
-
- Purpose
- Import records from a database or text file.
- Syntax
- APPEND FROM <xcSourceFile> [FIELDS <idFieldList> | FIELDS LIKE <Skeleton> | FIELDS EXCEPT <Skeleton>] [<Scope>] [WHILE <lCondition>] [FOR <lCondition>] [[TYPE] [DELIMITED [WITH <Delim> | WITH BLANK | WITH TAB | WITH CHARACTER <cDelim>] | DIF | FW2 | MOD | PDOX | RPD | SDF | SYLK | WK1 | WK3 | WKS | WR1 | WRK | CSV | XLS | XL5 [SHEET <cSheetName>] | XL8 [SHEET <cSheetName>]]] [AS <nCodePage>]
- Arguments
- FROM <xcSourceFile>The name of the source file from which to add records, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD. For text files, it is .TXT.
- This command attempts to open <xcSourceFile> in shared mode. If the file does not exist, a runtime error is raised. If the file is successfully opened, the operation proceeds If access is denied because, for example, another process has exclusive use of the file, NetErr() is set to TRUE.
-
-
-
-
-
-
-
- DELIMITED WITH <Delim>Indicates that character fields are separated by a character other than the quotation mark.
- DELIMITED WITH BLANK Specifies files that contain fields separated by spaces instead of commas.
- DELIMITED WITH TAB Specifies files that contain fields separated by tabs rather than commas.
- WITH CHARACTER <cDelim>Specifies files that contain fields all enclosed by the character specified with Delimiter. If Delimiter is a semicolon (the character used in Visual FoxPro to indicate command line continuation), enclose the semicolon in quotation marks. You can also specify the BLANK and TAB keywords for Delimiter. The WITH Delimiter clause can be combined with the WITH CHARACTER clause.
-
- TYPEFrom the various types that FoxPro allows only the following ones are supported in X# at this moment:
- SDFAn SDF file is an ASCII text file in which records have a fixed length and end with a carriage return and line feed. Fields are not delimited. The file name extension is assumed to be .txt for SDF files.
- CSVA comma separated value file. A CSV file has field names as the first line in the file; the field names are ignored when the file is imported. The file name extension is assumed to be .csv for CSV files. OTHERNOT SUPPORTED AT THIS MOMENT
-
- AS <nCodePage>Specifies the codepage to use for the source file. NOT SUPPORTED AT THIS MOMENT
-
- Notes
- Deleted records: If SetDeleted() is FALSE, deleted records in <xcSourceFile> are appended to the current database file and retain their deleted status. If SetDeleted() is TRUE, however, deleted records are not visible and are, therefore, not processed.
-
- Unmatched field widths:If a field in the current database file is character type and has a field length greater than the incoming <xcSourceFile> data, APPEND FROM pads the source data with blanks. If the current field is character data type and its field length is less than the incoming source data, the source data is truncated to fit. If the current field is numeric type and the incoming source data has more digits than the current field length, a runtime error is raised.
- Examples
- This example demonstrates an APPEND FROM command using a fields list and a condition:
-
- USE sales NEW APPENDFROM branchfile FIELDS Branch, Salesman, Amount FOR Branch = 100
-
- The next example demonstrates how a <Scope> can be specified to import a particular record from another database file:
-
- APPEND RECORD 5 FROM temp
-
- See Also
- COPY TO, DbApp(), DbAppDelim(), DbAppSDF(), RDDSetDefault(), SetDefault(), SetPath(), SetDeleted()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_ASSIGN.xml b/docs/Help_Spanish/Topics/command_ASSIGN.xml
deleted file mode 100644
index 96c93b4166..0000000000
--- a/docs/Help_Spanish/Topics/command_ASSIGN.xml
+++ /dev/null
@@ -1,83 +0,0 @@
-
-
-
- ASSIGN Statement
-
- ASSIGN statement
- Assign() Methods
- Compile-time declaration
- Declaration statements
- Entity declaration
- Instance variablesassigning values
- Methodsassigning values to instance variables
- Statements
- Strong typingdefined
-
-
-
- ASSIGN Statement
-
- Purpose
- Declare a method to assign a value to a particular instance variable.
- Syntax
- [Attributes] [Modifiers] ASSIGN <idVar>
- [([<idParam> [AS | REF <idType>] [, ...])]
- [AS <idType>] [<idConvention>]
- [CLASS <idClass>]
- [=> <expression>]
- CRLF
- [<Body>]
- [END ACCESS]
- Arguments
-
- <idVar>A valid identifier name for the instance variable whose assign method you are defining. Like other methods, assign methods are entities; however, the system uses a unique naming scheme for them to prevent collisions with other entity names. Assign method names must be unique within a class, but can share the same name as other entities in your application.
-
-
-
- END ASSIGNOptional end clause to indicate the end of the ASSIGN entity
- Description
- ASSIGN declares a special method, called an assign method, that is automatically executed each time you assign a value to the named instance variable (e.g., <idVar> := <uValue>). The value on the right-hand side of the assignment operator is passed to the ASSIGN method as an argument.
-
- You can define four types of instance variables in a CLASS declaration. All of these, except EXPORT, are called non-exported instance variables, because they are not directly accessible externally (i.e., outside of the class).
- For example, if you want to assign a value to a non-exported variable in a function, you must use a method. This means that the interface for assigning to instance variables is dependent on the implementation of the class. Assign methods give you a common syntax for assigning values to all instance variables. Used in conjunction with access methods (see the ACCESS statement in this guide), assign methods let you enforce encapsulation principles in your application while maintaining a stable class interface.
-
- The following example illustrates using a traditional method for assigning a value to a non-exported instance variable. Note the difference in assigning values to the instance variables x and y in UseClass():
-
- CLASS Test EXPORT x INSTANCE y
METHOD PutValueY(nPut)CLASS Test y := nPut RETURN y
FUNCTION UseClass() LOCAL oTest AS Test oTest := Test{} ? oTest:x :=100 ? oTest:PutValueY(100)// Using regular method
-
- If you replace the method with an assign method, as follows, the syntax for assignment to both variables is the same:
-
- ASSIGN y(nPut)CLASS Test y := nPut RETURN y
- FUNCTION UseClass() LOCAL oTest AS Test oTest := Test{} ? oTest:x :=100 ? oTest:y :=100// Using ASSIGN method
-
- Note: ASSIGN methods should generally return the actual assigned value to ensure that the hypothetical variable it represents actually behaves like a variable — technically, that assignment is associative. This will allow chained assignments the same way as for regular variables (e.g., Var2 := oTest1:y := oTest1:x := Var1 := 10000).
-
- Non-exported variables come in three categories, each with its own properties (see the CLASS statement entry in this guide for details):
-
-
INSTANCE
-
PROTECT
-
HIDDEN
-
-
- INSTANCE variables are specifically designed to work with assign and access methods, which is the main reason for their late binding. By defining an assign method with the same name as an INSTANCE variable, you effectively override the variable by causing all assignment references, both external and internal, to invoke the assign method. The exception is that within an assign (or access) method, instance variables of the same name refer to the variable — otherwise, you would never get anywhere.
-
- You can also use PROTECT and HIDDEN variables in conjunction with assign methods. By defining an assign method with the same name as a PROTECT or HIDDEN variable, you can make assignments to the variable externally, using the same syntax as you would inside the class. Internal references, however, always refer directly to the variable because of early binding.
-
- Of course, you do not have to give the assign method and the instance variable the same name. This is only for your convenience. It is the method itself that determines which instance variable name to use when you access <idVar> via an assignment. Thus, for PROTECT/HIDDEN variables, you can provide an assign method with a different name. For example:
-
- CLASS Person PROTECT Name_Protected
ASSIGN Name(cPutName)CLASS Person Name_Protected := cPutName RETURN Name_Protected
-
- EXPORT variables are a lot faster and easier to use than non-exported variables and assign methods, but using them defies the encapsulation that you should strive for to maintain the integrity of your application. Using assign and access methods, you can use exported variables early in the prototyping stage of an application, and later protect the variables with methods without changing the class interface.
-
- ASSIGN is a special case of METHOD and, except for the way you invoke it (i.e., without arguments, like an instance variable), its behavior is the same as any other method. See the METHOD statement in this guide for more details.
-
- Note: Internal references to access methods that do not have a corresponding regular INSTANCE variable (e.g., virtual variables or public access to HIDDEN or PROTECT variables with different names) must use the SELF: prefix. Internal references means references from inside methods of the class or one of its subclasses. If the system does not find an instance variable, it assumes a memory variable (which can produce a compiler error depending on whether Allow Undeclared Variables has been chosen in the compiler settings), and it does not attempt to identify the reference as an access method, unless SELF: is used.
-
- Examples
- The following example uses ASSIGN to establish a public protocol for making assignments to INSTANCE variables:
-
- CLASS Rectangle INSTANCE Length, Height ASINT
ASSIGN Height(nY)CLASS Rectangle Height := nY RETURN Height
FUNCTION UseClass() LOCAL oShape AS Rectangle oShape := Rectangle{} oShape:Length :=3 oShape:Height :=4a
- See Also
- ACCESS, CLASS, METHOD, PROPERTY
-
-
diff --git a/docs/Help_Spanish/Topics/command_ASYNC_AWAIT.xml b/docs/Help_Spanish/Topics/command_ASYNC_AWAIT.xml
deleted file mode 100644
index 4426ece43a..0000000000
--- a/docs/Help_Spanish/Topics/command_ASYNC_AWAIT.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- command_ASYNC .. AWAIT
-
- ASYNC
- AWAIT
-
-
-
- ASYNC .. AWAIT Statement
-
- Purpose
- ASYNC and AWAIT are strictly speaking not statements, but modifiers.
-
- ASYNC is a method modifier used to indicate that a method or function contains asynchronous code.
-
- AWAIT is used before an expression to indicate that an operation may take a while to process.
-
- The compiler will (behind the scenes) construct a complicated mechanism in which the body of the method is split into a part before and after the await. When the expression returns, the code jumps to the point where it has to continue. As such, this belongs to the JUMP statements.
- Example
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_AVERAGE.xml b/docs/Help_Spanish/Topics/command_AVERAGE.xml
deleted file mode 100644
index 596db108f5..0000000000
--- a/docs/Help_Spanish/Topics/command_AVERAGE.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
- AVERAGE Command
-
- AVERAGE command
- Calculatingaverages
- Commands
- Databases
- Recordscalculating averages
-
-
-
- AVERAGE Command
-
-
- Purpose
- Calculate the average of one or more numeric expressions to variables for a range of records in the current database file.
- Syntax
- AVERAGE <nValueList> TO <idVarList> [<Scope>] [WHILE <lCondition>] [FOR <lCondition>]
- Arguments
- <nValueList>A list of the numeric values to average for each record processed.
-
- TO <idVarList>A list of receiving variable or field names which will contain the average results. Variables that either do not exist or are not visible are created as private variables. <idVarList> must contain the same number of elements as <nValueList>.
-
-
-
-
- Description
- Zero (0) values are counted in the AVERAGE unless explicitly ruled out with a FOR condition.
- Examples
- This example averages a single numeric field using a condition to select a subset of records from the database file:
-
- USE sales NEW AVERAGE Amount TO nAvgAmount FOR Branch = "100"
-
- The next example finds the average date for a range of dates:
-
- AVERAGE (SaleDate - CToD("00/00/00")) ;
- TO nAvgDays FOR !Empty(SaleDate)
- dAvgDate := CToD("00/00/00") + nAvgDays
-
- See Also
- COUNT, DBEval(), SUM, TOTAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_BACKSLASH.xml b/docs/Help_Spanish/Topics/command_BACKSLASH.xml
deleted file mode 100644
index a463f75934..0000000000
--- a/docs/Help_Spanish/Topics/command_BACKSLASH.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- \|\\ Statement
-
- \|\\ statement
- Displayingoutput
- Statements
- Terminal window
-
-
-
- \|\\ Statement
-
- Purpose
- Prints or displays lines of text
- Syntax
- \ TextLine \\ TextLine
- Arguments
- \ TextLineWhen you use \, the text line is preceded by a carriage return and a line feed.
- \\ TextLineWhen you use \\, the text line is not preceded by a carriage return and a line feed. Any spaces preceding \ and \\ are not included in the output line, but spaces following \ and \\ are included. You can embed an expression in the text line. If the expression is enclosed in the text merge delimiters (<< >> by default) and SET TEXTMERGE is ON, the expression is evaluated and its value is output as text.
-
-
- Description
- The \ and \\ commands facilitate text merge in X#. Text merge makes it possible for you to output text to a file to create form letters or programs.
- Use \ and \\ to output a text line to the current text-merge output file and the screen. SET TEXTMERGE is used to specify the text merge output file. If text merge is not directed to a file, the text line is output only to the main Visual FoxPro window or the active user-defined output window. SET TEXTMERGE NOSHOW suppresses output to the main Visual FoxPro window or the active user-defined window.
-
- Examples
- This example displays a record from a database file using ? and ?? statements with PadR() to assure column alignment:
-
- CLOSEDATABASES OPEN DATABASE (C:\Test\Data\testdata') USE Customer // Open customer table SET TEXTMERGE ON SET TEXTMERGE TO letter.txt \<<CDOW(DATE( ))>>, <<CMONTH(DATE( ))>> \\ <<DAY(DATE( ))>>, <<YEAR(DATE( ))>> \ \ \Dear <<contact>> \Additional text \ \Thank you, \ \XYZ Corporation CLOSE ALL
-
- See Also
- SET TEXTMERGE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_BEGIN-CHECKED.xml b/docs/Help_Spanish/Topics/command_BEGIN-CHECKED.xml
deleted file mode 100644
index 5f61924490..0000000000
--- a/docs/Help_Spanish/Topics/command_BEGIN-CHECKED.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- BEGIN (UN)CHECKED
-
- BEGIN
- BEGIN CHECKED
- BEGIN UNCHECKED
- CHECKED
- END
- END CHECKED
- END UNCHECKED
- UNCHECKED
-
-
-
- BEGIN (UN)CHECKED
-
- Purpose
- The BEGIN (UN)CHECKED and END (UN)CHECKED keywords mark a block of statements that are compiled with overflow checking enabled or disabled.
- Syntax
- BEGIN CHECKED statements END CHECKED
BEGIN UNCHECKED statements END CHECKED
- Arguments
-
- statementsOne or more statements or expressions that are compiled with the specified overflow checking
- Remarks
-
- BEGIN CHECKED ... END CHECKED ensures that a block of code is compiled with a clear overflow checking option, regardless of the compiler option -ovf.
-
- BEGINCHECKED LOCAL intValue asINT LOCAL dwordValue asDWORD intValue := -1 dwordValue := (DWORD) intValue // Overflow error ENDCHECKED
BEGINUNCHECKED LOCAL intValue asINT LOCAL dwordValue asDWORD intValue := -1 dwordValue := (DWORD) intValue // NO Overflow error, dwordValue now has the value UInt32.MaxValue ENDUNCHECKED
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_BEGIN-FIXED.xml b/docs/Help_Spanish/Topics/command_BEGIN-FIXED.xml
deleted file mode 100644
index 51275eefc5..0000000000
--- a/docs/Help_Spanish/Topics/command_BEGIN-FIXED.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- BEGIN FIXED
-
- BEGIN
- BEGIN FIXED
- END
- END FIXED
- FIXED
-
-
-
- BEGIN FIXED
-
- Purpose
- The BEGIN FIXED and END FIXED keyword prevent the garbage collector from relocating a movable variable. The BEGIN FIXED statement is only allowed in an unsafe context.
-
- The fixed statement sets a pointer to a managed variable and "pins" that variable during the execution of the statement. Pointers to movable managed variables are useful only in a fixed context. Without a fixed context, garbage collection could relocate the variables unpredictably. The X# compiler only lets you assign a pointer to a managed variable in a fixed statement.
- You can initialize a pointer by using an array, a string, a fixed-size buffer, or the address of a variable.
- Syntax
- BEGIN FIXED declaration statements END FIXED
- Arguments
- declarationDeclaration of a variable and assignment that is visible only inside the statement block between BEGIN and END
- statementsCode including one or more statements that may contain unsafe code.
-
- Example
-
- UNSAFEFUNCTION Start ASVOID VAR s := "SDRS" BEGINFIXEDLOCAL p := s ASCHARPTR VAR i := 0 WHILE p[i] != 0 p[i++]++ END ENDFIXED Console.WriteLine(s) Console.Read() RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/command_BEGIN-LOCK.xml b/docs/Help_Spanish/Topics/command_BEGIN-LOCK.xml
deleted file mode 100644
index 0619aa76a5..0000000000
--- a/docs/Help_Spanish/Topics/command_BEGIN-LOCK.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
- BEGIN LOCK
-
- BEGIN
- BEGIN LOCK
- END
- END LOCK
- LOCK
-
-
-
- BEGIN LOCK
-
- Purpose
- The BEGIN LOCK and END LOCK keywords mark a block of statements as a critical section.
- Syntax
- BEGIN LOCK object statements END LOCK
- Arguments
-
- objectAn expression that evaluates to an object reference that is used as a locking object.
- statementsOne or more statements or expressions that are guarded by a mutual exclusion lock on the object specified in object.
- Remarks
-
- BEGIN LOCK ... END LOCK insures that multiple threads cannot execute the statements within the block at the same time. If one thread is executing code within the block, any other thread that attempts to enter the block will be suspended until the thread that is executing leaves the block.
- The object used as the locking object must be a reference type, it cannot be a value type and the expression cannot evaluate to NULL or a runtime error will occur.
- BEGIN LOCK ... END LOCK uses Monitor.Enter() and Monitor.Exit() to acquire and release a lock on the specified object. The following example:
-
- BEGINLOCK lockObj ? "In guarded block" ENDLOCK
- is equivalent to:
- System.Threading.Monitor.Enter( lockObj ) TRY ? "In guarded block" FINALLY System.Threading.Monitor.Exit( lockObj ) ENDTRY
-
-
- Using BEGIN LOCK ... END LOCK is recommended over using the Monitor class directly because the code is more concise and insures that the monitor object is released, even if an exception occurs within the guarded block.
- BEGIN LOCK ... END LOCK provides functionality similar to the Windows API functions EnterCriticalSection() and LeaveCriticalSection(). However, instead of using an object created by InitializeCriticalSection(), any instance of a reference type may be used for the locking object.
- Please see the documentation for the System.Threading.Monitor class for more information.
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_BEGIN-SCOPE.xml b/docs/Help_Spanish/Topics/command_BEGIN-SCOPE.xml
deleted file mode 100644
index f5b186e72b..0000000000
--- a/docs/Help_Spanish/Topics/command_BEGIN-SCOPE.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- BEGIN SCOPE
-
- BEGIN
- BEGIN SCOPE
- END
- END SCOPE
- SCOPE
-
-
-
- BEGIN SCOPE
-
- Purpose
- The BEGIN SCOPE and END SCOPE keyword pairs declare a scope of visibility and lifetime of LOCAL variables.
- Syntax
- BEGIN SCOPE statements END SCOPE
-
- Arguments
- statementsCode including one or more LOCAL declarations.
- Remarks
- BEGIN SCOPE...END SCOPE are used within a function/member body to define an area of restricted scope for LOCAL variables. Attempting to use a LOCAL variable that is declared with a BEGIN SCOPE...END SCOPE block outside the scope, results in a compiler error.
-
- Example
-
- FUNCTION Test() ASVOID BEGINSCOPE LOCAL n ASINT n++ ? n ENDSCOPE // n does not exist here
-
-
diff --git a/docs/Help_Spanish/Topics/command_BEGIN-SEQUENCE.xml b/docs/Help_Spanish/Topics/command_BEGIN-SEQUENCE.xml
deleted file mode 100644
index 008ba508d2..0000000000
--- a/docs/Help_Spanish/Topics/command_BEGIN-SEQUENCE.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
- BEGIN SEQUENCE
-
- BEGIN
- BEGIN SEQUENCE
- END
- END SEQUENCE
- FINALLY
- RECOVER
- SEQUENCE
- USING
-
-
-
- BEGIN SEQUENCE
-
- Purpose
- The BEGIN SEQUENCE keyword declares the beginning of an exception handling block.
- Syntax
- BEGIN SEQUENCE tryStatements [RECOVER [USING localVariable] recoveryStatements ] [FINALLY finallyStatements ] END [SEQUENCE]
- where:
- tryStatementsOne or more statements or expressions that may cause an exception to be thrown.
- localVariableA local variable that will receive the exception thrown by any code between the BEGIN SEQUENCE and RECOVER statements. This must be a variable typed as USUAL.
- recoveryStatementsOne or more statements or expressions that will execute if an exception is thrown by any of the tryStatements.
- finallyStatementsOne or more statements or expressions that will always execute regardless of whether an exception is thrown or not.
-
- Remarks
- BEGIN SEQUENCE ... END SEQUENCE is a control structure used for exception and runtime error handling. It delimits a block of statements defining a discrete operation, including invoked procedures and functions.
- When an exception is thrown anywhere in the block of statements following the BEGIN SEQUENCE statement up to the corresponding RECOVER statement, control branches to the program statement immediately following the RECOVER statement. If a RECOVER statement is not specified, control branches to the statement following the FINALLY statement, terminating the sequence. If a FINALLY statement is not specified, control branches to the statement following the END SEQUENCE statement, terminating the sequence.
- If control reaches a RECOVER statement without an exception being thrown, control branches to the statement following the FINALLY statement. If a FINALLY statement is not specified, control branches to the statement following the END SEQUENCE statement, terminating the sequence.
- The RECOVER statement optionally receives an exception thrown by a statement in the tryStatements block. This is usually an error object, generated and returned by the current error handling block defined by ErrorBlock(). If an error object is returned, it can be sent messages to query information about the error. With this information, a runtime error can be handled within the context of the operation rather than in the current runtime error handler.
- The FINALLY statement block is useful for cleaning up any resources allocated in the BEGIN SEQUENCE block. Control is always passed to the FINALLY block (if present) regardless of how the BEGIN SEQUENCE block exits.
- You cannot RETURN, LOOP, or EXIT between a BEGIN SEQUENCE and RECOVER statement. From within the RECOVER and FINALLY statement blocks however, you can LOOP, EXIT, BREAK, or RETURN, since the sequence is essentially completed at that point. Using LOOP from within the RECOVER statement block is useful for re-executing the sequence statement block.
- BEGIN SEQUENCE ... END SEQUENCE control structures can be nested to any depth.
- The CanBreak() function returns TRUE if execution is within any BEGIN SEQUENCE block.
- Example
-
- FUNCTION Start() ASVOID LOCAL x := 4, y := 0 ASINT BEGINSEQUENCE ? x / y RECOVER ? "oops" FINALLY ? "in finally block" ENDSEQUENCE RETURN
-
- See Also
- BREAK THROW TRY-CATCH-FINALLY
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_BEGIN-UNSAFE.xml b/docs/Help_Spanish/Topics/command_BEGIN-UNSAFE.xml
deleted file mode 100644
index 66217eef4d..0000000000
--- a/docs/Help_Spanish/Topics/command_BEGIN-UNSAFE.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- BEGIN UNSAFE
-
- BEGIN
- BEGIN UNSAFE
- END
- END UNSAFE
- UNSAFE
-
-
-
- BEGIN UNSAFE
-
- Purpose
- The BEGIN UNSAFE and END UNSAFE keyword pairs declare a scope of code that contains unsafe statements, such as typed pointers.
- Syntax
- BEGIN UNSAFE statements END UNSAFE
- Arguments
- statementsCode including one or more statements that may contain unsafe code.
-
- Example
-
- FUNCTION Start() ASVOID LOCAL a ASINT[] a := <INT>{1,2,3,4,5} BEGINUNSAFE LOCAL p ASINTPTR p := @a FORVAR i := 1 to 5 ? p[i] NEXT ENDUNSAFE RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/command_BEGIN-USING.xml b/docs/Help_Spanish/Topics/command_BEGIN-USING.xml
deleted file mode 100644
index fc9b3a2751..0000000000
--- a/docs/Help_Spanish/Topics/command_BEGIN-USING.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- BEGIN USING
-
- BEGIN
- BEGIN USING
- END
- END USING
- USING
-
-
-
- BEGIN USING
-
- Purpose
- The BEGIN USING and END USING keyword declare a block of code that ensures the correct use of disposable objects.
-
- Syntax
- BEGIN USING declaration statements END USING
- Arguments
- declarationDeclaration of a variable and assignment that is visible only inside the statement block between BEGIN and END
- statementsCode including one or more statements that may contain unsafe code.
-
- Description
- When the lifetime of an IDisposable object is limited to a single method, you should declare and instantiate it in the using statement. The using statement calls the Dispose method on the object in the correct way, and (when you use it as shown earlier) it also causes the object itself to go out of scope as soon as Dispose is called. Within the using block, the object is read-only and cannot be modified or reassigned.
-
- Example
-
- BEGINUSINGVAR oTest := Test{} oTest:DoSomething() ENDUSING
- this is the equivalent of:
- VAR oTest := Test{} TRY oTest:DoSomething() FINALLY IF oTest != NULL_OBJECT ((IDisposable)oTest):Dispose() ENDIF ENDTRY
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_BEGIN_SEQUENCE.xml b/docs/Help_Spanish/Topics/command_BEGIN_SEQUENCE.xml
deleted file mode 100644
index e588ad94e7..0000000000
--- a/docs/Help_Spanish/Topics/command_BEGIN_SEQUENCE.xml
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
- BEGIN SEQUENCE Statement
-
- BEGIN SEQUENCE statement
- Branching
- BREAK statement
- END SEQUENCE statement
- Program control
- RECOVER statement
- RECOVER USING statement
- Statements
-
-
-
- BEGIN SEQUENCE Statement
-
- Purpose
- Defines a sequence of statements for a BREAK.
- Syntax
- BEGIN SEQUENCE <Statements>... [BREAK [<uValue>]] <Statements>... [RECOVER [USING <idVar>]] <Statements>... END [SEQUENCE]
- Arguments
- BREAK <uValue>Branches execution to the statement immediately following the nearest RECOVER statement if one is specified, or the nearest END SEQUENCE statement. <uValue> is the value returned into the <idVar> specified in the USING clause of the RECOVER statement.
-
- RECOVER USING <idVar>
- A recover point in the SEQUENCE construct where control branches after a BREAK statement. If this clause is specified, <idVar> receives the value returned by the BREAK statement. In general, this is an error object. <idVar> must be a declared variable and cannot be strongly typed.
-
- ENDThe end point of the SEQUENCE control structure. If no RECOVER statement is specified, control branches to the first statement following the END statement after a BREAK.
- Description
- BEGINSEQUENCE...END is a control structure used for exception and runtime error handling. It delimits a block of statements defining a discrete operation, including invoked procedures and functions. With the exception of the BREAK statement, the entire construct must fall within the same entity definition.
-
- When a BREAK is encountered anywhere in a block of statements following the BEGINSEQUENCE statement up to the corresponding RECOVER statement, control branches to the program statement immediately following the RECOVER statement. If a RECOVER statement is not specified, control branches to the statement following the END statement, terminating the SEQUENCE. If control reaches a RECOVER statement without encountering a BREAK, it branches to the statement following the corresponding END.
-
- The RECOVER statement optionally receives a parameter passed by a BREAK statement that is specified with a return value. This is usually an error object, generated and returned by the current error handling block defined by ErrorBlock(). If an error object is returned, it can be sent messages to query information about the error. With this information, a runtime error can be handled within the context of the operation rather than in the current runtime error handler.
-
- You cannot RETURN, LOOP, or EXIT between a BEGINSEQUENCE and RECOVER statement
-
- Control structures can be nested to any depth. he only requirement is that each control structure be properly nested.
- Examples
- This code fragment demonstrates a SEQUENCE construct in which the BREAK occurs within the current procedure:
-
- BEGINSEQUENCE <Statements>... IF lBreakCond BREAK ENDIF RECOVER <Recovery Statements>... END
<Recovery Statements>...
-
- This example demonstrates an error handler returning an error object to the variable specified in the USING clause of the RECOVER statement:
-
- LOCAL oLocal, bLastHandler // Save current and set new error handler bLastHandler := ErrorBlock({|oErr| ; MyHandler(oErr, TRUE)})
BEGINSEQUENCE . . <Operation that might fail>... . RECOVERUSING oLocal
// Send messages to oLocal & handle the error ? "Error: " IF oLocal:GenCode != 0 ?? oLocal:Description ENDIF . . . END
FUNCTION MyHandler(oError, lLocalHandler) // Handle locally returning the error object IF lLocalHandler BREAK oError ENDIF <Other statements to handle the error>...
-
- This example re-executes a SEQUENCE statement block by issuing a LOOP from within the RECOVER statement block:
-
- DOWHILE TRUE BEGINSEQUENCE
<Operation that may fail>...
RECOVER IF PrintRecover() // Repeat the SEQUENCE statement block LOOP ENDIF END EXIT// Escape from the operation
ENDDO
- See Also
- _Break(), CanBreak(), Error Class, ErrorBlock(), RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_BREAK.xml b/docs/Help_Spanish/Topics/command_BREAK.xml
deleted file mode 100644
index 66c4306d80..0000000000
--- a/docs/Help_Spanish/Topics/command_BREAK.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- BREAK statement
-
- BREAK
-
-
-
- BREAK statement
-
- Purpose
- The BREAK statement raises a runtime exception.
- Syntax
- BREAK [expression ]
- Arguments
- expression An optional expression to throw.
- Remarks
- BREAK throws a runtime exception, causing execution to branch to the nearest RECOVER, CATCH or FINALLY block in a BEGIN SEQUENCE-RECOVER USING or TRY construct. If execution is not within a BEGIN SEQUENCE or TRY construct, the application will terminate.
- The specified expression will be evaluated and received by the nearest RECOVER USING statement, if any, as a value of type USUAL. If the nearest RECOVER statement does not have a USING clause, the result of expression is discarded.
- If expression is not specified, it defaults to NIL.
- Example
- FUNCTION foo LOCAL e ASUSUAL BEGINSEQUENCE bar( 1 ) RECOVERUSING e ? "An exception has occurred, exception value is:", e ENDSEQUENCE
FUNCTION bar( x ) IF Valtype(x) != STRING BREAK "Argument not a string!" ENDIF ... RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/command_CANCEL.xml b/docs/Help_Spanish/Topics/command_CANCEL.xml
deleted file mode 100644
index e63f367c34..0000000000
--- a/docs/Help_Spanish/Topics/command_CANCEL.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- CANCEL Command
-
- CANCEL command
- Closingfiles
- Commands
- Filesclosing
- Program control
- QUIT command
-
-
-
- CANCEL Command
-
-
- Purpose
- Terminates the application, closes all open files, and returns control to the operating system.
- Syntax
- CANCEL | QUIT
- Description
- You can use either command from anywhere in an application. A RETURN executed from the Start() routine performs the same action.
- Notes
- Usage: Both commands can be used from anywhere in an application. A RETURN executed at the highest level procedure or a BREAK, with no pending SEQUENCE, can also be used to QUIT an application.
- Examples
- This example uses QUIT in a dialog box:
-
- IF DialogYesNo(10, 10, "Quit application", ; BG+/B,B/W", 2) QUIT ENDIF
-
- See Also
- BEGIN SEQUENCE, ErrorLevel(), RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_CLASS.xml b/docs/Help_Spanish/Topics/command_CLASS.xml
deleted file mode 100644
index 907e3f28a7..0000000000
--- a/docs/Help_Spanish/Topics/command_CLASS.xml
+++ /dev/null
@@ -1,97 +0,0 @@
-
-
-
- CLASS Statement (All dialects)
-
- Binding of instance variables
- CLASS
- Class namesdeclaring
- CLASS statement
- Classes
- Classes
- Classesdeclaring Class namesinheritanceobject instantiation
- Compile-time declaration
- Declaration statements
- END CLASS
- Entity declaration
- EXPORT clause
- EXPORT INSTANCE clause
- HIDDEN clause
- HIDDEN INSTANCE clause
- IMPLEMENTS
- INHERIT
- INHERIT clause
- INSTANCE clause
- Instance variables
- Instance variables
- Instance variables
- Instance variablesbindingdeclaringexportinghiding
- Object instantiation
- PROTECT clause
- PROTECT INSTANCE clause
- Statements
- STATIC CLASS statement
-
-
-
- CLASS Statement (All dialects)
-
- Purpose
- Declare a class name to the compiler.
- Syntax
- [Attributes] [Modifiers] [RECORD] CLASS <idClass> [INHERIT <idClass>] [IMPLEMENTS <idInterface>[, <IdInterface2>,..]
- [ClassMembers]
- END CLASS
- Arguments
-
- RECORDThe record modifier declares a special class that has value equality. See the topic about records
-
-
- INHERIT <idClass>The name of an existing class (called a superclass) from which the new class inherits methods and instance variables (with the exception of HIDDEN).
-
- IMPLEMENTS <idInterface>The name(s) of the interface(s) that this class implements.
-
- ClassMembersThis can be any of Instance Variables, ACCESS, ASSIGN, CONSTRUCTOR, DESTRUCTOR, EVENT, METHOD, OPERATOR, PROPERTY.
- Description
- After the class name is declared to the compiler, it is followed by 0 or more instance variable declaration statements. You use a class name to declare variables (see GLOBAL and LOCAL statements in this guide) designed to hold instances of a specific class, to instantiate instances of the class, and to define methods (see the METHOD statement in this guide) and subclasses for the class.
- Notes
- Binding of instance variables: Instance variables can be either early or late bound, depending on how you declare them and how you use them.
-
- Early binding happens if the memory location of a variable is known at compile time. The compiler knows exactly how to reference the variable and can, therefore, generate code to do so.
-
- Late binding is necessary if the memory location of a variable is unknown at compile time. The compiler cannot determine from the program source code exactly where the variable is or how to go about referencing it, so it generates code to look the symbol up in a table. The lookup is performed at runtime.
-
- Since there is no need for a runtime lookup with early bound instance variables, using them instead of late bound variables will significantly improve the performance of your application. The following table summarizes the binding and visibility issues for the four types of instance variables:
-
- Variable TypeBindingVisibility
- EXPORTEarly, if possibleApplication-wide for CLASS and module-wide for STATIC CLASS
- INSTANCEAlways lateIn class and subclasses
- HIDDENAlways earlyIn class only
- PROTECTAlways earlyIn class and subclasses
-
- Object instantiation: Once you declare a class, you create instances of the class using the class name followed by the instantiation operators, {}. The syntax is as follows:
-
- <idClass>{[<uArgList>]}
-
- where <uArgList> is an optional comma-separated list of values passed as arguments to a special method called Init() (see the METHOD statement in this guide for more information on the Init() method).
-
- Accessing instance variables: The syntax to access an exported instance variable externally (i.e., from any entity that is not a method of its class) is as follows:
-
- <idObject>:<idVar>
-
- You can access non-exported instance variables only from methods in which they are visible. Within a method, you use the following syntax for accessing all instance variables:
-
- [SELF:]<idVar>
-
- The SELF: prefix is optional, except in the case of an access/assign method (see the ACCESS and ASSIGN statement entries in this guide for more information and the METHOD statement for more information on SELF).
- Instance variables are just like other program variables. You can access them anywhere in the language where an expression is allowed.
-
- The prefix [STATIC] is no longer supported by <%APP%>.
- Examples
- The following example defines two classes, one of which inherits values from the other, and demonstrates how to create a class instance with initial values for the instance variables:
-
- FUNCTION Start() LOCAL oCust AS Customer oCust := Customer{"Louis",92.07.22,"GA",987} oCust:DisplayAll() ? oCust:Name ...
// Declare Person class
CLASS Person EXPORT Name ASSTRING INSTANCE Birth ASDATE
// Declare Customer class to inherit from Person
CLASS Customer INHERIT Person PROTECT CustNum ASSHORTINT INSTANCE Address ASSTRING
// Declare method to initialize instance variables // Note that cName and dBirth are available to the // Customer class, even though they are not declared // as part of the class — they are inherited from Person
METHOD Init(cOne, dTwo, cThree, nFour); CLASS Customer Name := cOne Birth := dTwo Address := cThree CustNum := nFour RETURNSELF
// Declare method to display all instance variables
METHOD DisplayAll()CLASS Customer ?"Name: ", Name ?"Birth Date: ", Birth ?"Address: ", Address ?"Number: ", CustNum
- See Also
- ACCESS, ASSIGN, CONSTRUCTOR, DESTRUCTOR, EVENT, METHOD, OPERATOR, PROPERTY
-
-
diff --git a/docs/Help_Spanish/Topics/command_CLASS_Fox.xml b/docs/Help_Spanish/Topics/command_CLASS_Fox.xml
deleted file mode 100644
index ff729b9989..0000000000
--- a/docs/Help_Spanish/Topics/command_CLASS_Fox.xml
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
- CLASS Statement (FoxPro dialect)
-
- Binding of instance variables
- CLASS
- Class namesdeclaring
- CLASS statement
- Classes
- Classes
- Classesdeclaring Class namesinheritanceobject instantiation
- Compile-time declaration
- Declaration statements
- DEFINE
- END DEFINE
- ENDDEFINE
- Entity declaration
- EXPORT clause
- EXPORT INSTANCE clause
- HIDDEN clause
- HIDDEN INSTANCE clause
- INHERIT clause
- INSTANCE clause
- Instance variables
- Instance variables
- Instance variables
- Instance variablesbindingdeclaringexportinghiding
- Object instantiation
- OLEPUBLIC
- PROTECT clause
- PROTECT INSTANCE clause
- Statements
- STATIC CLASS clause
-
-
-
- CLASS Statement (FoxPro dialect)
-
-
- Purpose
- Declare a class name to the compiler.
- Syntax
- [Attributes] DEFINE [Modifiers] CLASS <idClass> [AS <idParentClass>] [OF <classLib>] [OLEPUBLIC] [ClassMembers]
- (ENDDEFINE | END DEFINE)
- Arguments
-
-
-
- AS <idParentClass>The name of an existing class (called a superclass) from which the new class inherits methods and instance variables. The AS <idParent> clause is mandatory when compiled with /fox1+, and optional when compiled with /fox1-. When compiled with /fox1+, the compiler assumes that the parent class is either the Custom class or a class derived from the Custom class.
- OF <classLib>This clause is parsed but ignored in X#.
-
- OLEPUBLICThis clause is parsed but ignored in X#.
-
- ClassMembers
- Fields and Properties
- IMPLEMENTS Clause
- ADD OBJECT Clause
- COMMAttrib Clause
- FUNCTIONS and PROCEDURES
-
-
-
- Examples
-
- See Also
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_CLASS_Xpp.xml b/docs/Help_Spanish/Topics/command_CLASS_Xpp.xml
deleted file mode 100644
index 92ab6088db..0000000000
--- a/docs/Help_Spanish/Topics/command_CLASS_Xpp.xml
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
- CLASS Statement (Xbase++ dialect)
-
- Binding of instance variables
- CLASS
- Class namesdeclaring
- CLASS statement
- Classes
- Classes
- Classesdeclaring Class namesinheritanceobject instantiation
- Compile-time declaration
- Declaration statements
- ENDCLASS
- Entity declaration
- EXPORT clause
- EXPORT INSTANCE clause
- FROM
- HIDDEN clause
- HIDDEN INSTANCE clause
- IMPLEMENTS
- INHERIT clause
- INSTANCE clause
- Instance variables
- Instance variables
- Instance variables
- Instance variablesbindingdeclaringexportinghiding
- Object instantiation
- PROTECT clause
- PROTECT INSTANCE clause
- SHARING
- Statements
- STATIC CLASS clause
-
-
-
- CLASS Statement (Xbase++ dialect)
-
- Purpose
- Declare a class name to the compiler.
- Syntax
- [Attributes] [Modifiers] CLASS <idClass> [FROM <idParentClass>] [SHARING <idParentClass,...>] [IMPLEMENTS <idInterface>[, <IdInterface2>,..]
- [ClassMembers]
- ENDCLASS
- [CLASS] METHOD [<ClassName>:] <MethodName> [( [<Parameters,...>] )]
- [<Body>]
-
- Arguments
- AttributesAn optional list of one or more attributes that describe meta-information for am entity, such as, for example, the [TestMethod] attribute on a method containing tests in a MsTest class library. Please note that Attributes must be on the same line or suffixed with a semi-colon when they are written on the line above that keyword.
-
- ModifiersAn optional list of modifiers that specify the visibility or scope of the entity; allowed values are STATIC, FREEZE and FINAL.
-
-
- FROM <idParentClass>The name of an existing class (called a superclass) from which the new class inherits methods and instance variables (with the exception of HIDDEN). X# does NOT allow multiple inheritance.
-
- SHARING <idParentClass>This clause is not supported by X#.
-
- IMPLEMENTS <idInterface>The name(s) of the interface(s) that this class implements.
-
- ClassMembersThis may be a list of variable declarations, method declarations and inline method implementations.
-
- [CLASS] METHODThis implements one or more methods outside of the class declaration. The CLASS keyword indicates that it is a STATIC method, as opposed to an INSTANCE method.
- ClassMembers
- Fields
- Method Declarations
- Method Implementation
-
- See Also
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_CLEAR_ALL.xml b/docs/Help_Spanish/Topics/command_CLEAR_ALL.xml
deleted file mode 100644
index ea3b1f201e..0000000000
--- a/docs/Help_Spanish/Topics/command_CLEAR_ALL.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- CLEAR ALL Command
-
- CLEAR ALL command
- Closingfiles
- Commands
- Databases
- Filesclosing
- Releasing variables
- Variablesreleasing
- Work areasclearing
-
-
-
- CLEAR ALL Command
-
-
- Purpose
- Release all public and private variables, close all open database, index, alternate, and memo files in all active work areas, and select work area 1.
-
- Note: CLEAR ALL is a compatibility command and is no longer recommended. It is superseded by the command or function that performs the specific action you need. See the list below.
- Syntax
- CLEAR ALL
- Notes
- Declared Variables: CLEAR ALL does not release declared variables or constants.
- You can close files associated with work areas with one of the various forms of the CLOSE command. You can release private and public variables using the RELEASE command, although explicitly releasing variables is discouraged in most cases.
-
- See Also
- CLEAR MEMORY, CLOSE, DBCloseArea(), FClose(), RELEASE, Select(),
-
-
diff --git a/docs/Help_Spanish/Topics/command_CLEAR_MEMORY.xml b/docs/Help_Spanish/Topics/command_CLEAR_MEMORY.xml
deleted file mode 100644
index 9ca07c0650..0000000000
--- a/docs/Help_Spanish/Topics/command_CLEAR_MEMORY.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- CLEAR MEMORY Command
-
- CLEAR MEMORY command
- Clearing memory
- Commands
- Deletingmemory variables
- Memory
- Memoryclearingdeleting variables
-
-
-
- CLEAR MEMORY Command
-
-
-
- Purpose
- Deletes both public and private memory variables from the memory variable table.
- Syntax
- CLEAR MEMORY
- Description
- This command operates in contrast to RELEASE ALL, which does not actually delete public and private memory variables but assigns NIL to those with scope limited to the current procedure. CLEAR MEMORY is the only way to delete all public memory variables from current memory. Declared variables and constants, however, are unaffected by CLEAR MEMORY.
-
- See Also
- MemClear(), RELEASE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_CLOSE.xml b/docs/Help_Spanish/Topics/command_CLOSE.xml
deleted file mode 100644
index e69e581286..0000000000
--- a/docs/Help_Spanish/Topics/command_CLOSE.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- CLOSE Command
-
- CLOSE ALL command
- CLOSE ALTERNATE command
- CLOSE command
- CLOSE DATABASES command
- CLOSE FORMAT command
- CLOSE INDEXES command
- Closingfiles
- Commands
- Databases
- Filesclosing
- Index/order
-
-
-
- CLOSE Command
-
-
- Purpose
- Close specified file type.
- Syntax
- CLOSE [<xcAlias> | ALL | ALTERNATE | DATABASES | INDEXES]
- Arguments
- <xcAlias>The alias identifier for the work area where all files are closed.
-
- ALLCloses database and index files in all work areas, releasing all active filters, relations, and format definitions.
-
- ALTERNATECloses the currently open alternate file.
-
- DATABASESCloses all database, memo, and associated index files in all work areas, and releases all active filters and relations. It does not, however, have any effect on the active format.
-
- INDEXESCloses all index files and clears the order list in the current work area.
- Description
- CLOSE with no option closes the current database and associated files. A number of other operations close files as a side effect, but it is always a good idea to explicitly close files when you are finished using them.
-
- See Also
- DBCloseArea(), FClose(), SET INDEX, USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_COMMIT.xml b/docs/Help_Spanish/Topics/command_COMMIT.xml
deleted file mode 100644
index a48ff03813..0000000000
--- a/docs/Help_Spanish/Topics/command_COMMIT.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- COMMIT Command
-
- Commands
- COMMIT ALL command
- COMMIT command
- Concurrency control
- Databases
- Flushing updates
- Updatesflushing
-
-
-
- COMMIT Command
-
-
- Purpose
- Flush all pending updates in all work areas.
- Syntax
- COMMIT [ALL]
- Description
- COMMIT causes all pending updates to all work areas to be written to disk. It is functionally equivalent to DBCommit() for every occupied work area. COMMIT ALL is functionally equivalent to DBCommitAll().
- All updated database and order buffers are written to disk, and a OS Commit request is issued for all files associated with all work areas.
- Notes
- Shared mode: COMMIT makes database updates visible to other processes. To insure data integrity, issue DBCommit() before an unlock operation.
- Examples
- In this example, COMMIT forces a write to disk after a series of memory variables are assigned to field variables:
-
- USE sales EXCLUSIVENEW
APPENDBLANK REPLACE Sales->Name WITH "Jones" REPLACE Sales->Amount WITH 123.45 COMMIT
-
- See Also
- DBCommit(), DBCommitAll(), GO, SKIP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_CONSTRUCTOR.xml b/docs/Help_Spanish/Topics/command_CONSTRUCTOR.xml
deleted file mode 100644
index 3169c0eb62..0000000000
--- a/docs/Help_Spanish/Topics/command_CONSTRUCTOR.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- ACCESS CONSTRUCTOR
-
- Compile-time declaration
- CONSTRUCTOR statement
- Declaration statements
- Entity declaration
- Statements
-
-
-
- CONSTRUCTOR Statement
-
- Purpose
- Declare a special method that is automatically invoked when a type is instantiated.
- Syntax
- [Attributes] [Modifiers] CONSTRUCTOR[([<idParam> [AS | REF|OUT|IN <idType>] [, ...])]
- [=> <expression>]
- CRLF
- [<Body>]
- [END CONSTRUCTOR]
- Arguments
-
-
-
-
- END CONSTRUCTOROptional end clause to indicate the end of the CONSTRUCTOR entity
-
- See Also
- ASSIGN, CLASS, METHOD
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_CONTINUE.xml b/docs/Help_Spanish/Topics/command_CONTINUE.xml
deleted file mode 100644
index 620b65b30e..0000000000
--- a/docs/Help_Spanish/Topics/command_CONTINUE.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
- CONTINUE Command
-
- Commands
- CONTINUE command
- Databases
- Recordsmatching
- Resuming locate conditions
- Work areaslocate conditions
-
-
-
- CONTINUE Command
-
-
- Purpose
- Resume a pending locate.
- Syntax
- CONTINUE
- Description
- CONTINUE searches from the current record position for the next record meeting the most recent locate condition executed in the current work area. (You can set the locate condition with the LOCATE command or with the VODBLocate() or VODBSetLocate() functions.)
-
- The search terminates when a match is found or end of file is encountered. If CONTINUE is successful, the matching record becomes the current record and Found() returns TRUE; if unsuccessful, Found() returns FALSE.
- Each work area can have an active locate condition. A locate condition remains pending until a new one is specified.
- Notes
- Scope and WHILE condition: The scope and WHILE condition of the locate condition are ignored; only the for condition is used with CONTINUE. If you are using a LOCATE command with a while condition and want to continue the search for a matching record, use SKIP and then repeat the original LOCATE command, adding REST as the scope.
- Examples
- This example scans records in SALES.DBF for a particular salesman and displays a running total sales amount:
-
- LOCAL nRunTotal := 0 USE sales NEW LOCATEFOR Sales->Salesman = "1002" DOWHILE Found() ? Sales->SalesName, nRunTotal += Sales->Amount CONTINUE ENDDO
-
- This example demonstrates how to continue if the pending LOCATE scope contains a WHILE condition:
-
- LOCAL nRunTotal :=0 USE sales INDEX salesman NEW SEEK "1002" LOCATE REST WHILE Sales->Salesman ="1002"; FOR Sales->Amount >5000 DOWHILE Found() ? Sales->Salesname, nRunTotal += Sales->Amount SKIP LOCATE REST WHILE Sales->Salesman ="1002"; FOR Sales->Amount >5000 ENDDO
-
- See Also
- DbContinue(), DbLocate(), EoF(), Found(), LOCATE, SEEK
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_COPY_FILE.xml b/docs/Help_Spanish/Topics/command_COPY_FILE.xml
deleted file mode 100644
index a7a0c6b93e..0000000000
--- a/docs/Help_Spanish/Topics/command_COPY_FILE.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
- COPY FILE Command
-
- Commands
- COPY FILE command
- Copyingfiles
- Filescopying
-
-
-
- COPY FILE Command
-
-
- Purpose
- Copy a file to a new file or to a device.
- Syntax
- COPY FILE <xcSourceFile> TO <xcTargetFile> | <xcDevice>
- Arguments
- <xcSourceFile>The name of the source file to copy, including an optional drive, directory, and extension.
- If <xcSourceFile> does not exist, a runtime error is raised. If it exists, this command attempts to open the file in shared mode and, if successful, it proceeds. If access is denied because, for example, another process has exclusive use of the file, NetErr() is set to TRUE.
-
- TO <xcTargetFile>The name of the target file, including an optional drive, directory, and extension.
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
- See SetDefault() and SetPath() for file searching and creation rules. This command does not supply a default extension for either file name.
-
- TO <xcDevice>The name of the target device specified without a trailing colon. When you specify one of the following device names: PRN, LPT1, LPT2, LPT3, COM1, or COM2; COPY FILE searches the Windows section of WIN.INI for a Device entry to use for the printing device. If there is no Device entry, it looks for a Devices entry and presents the user with a list box of devices from which to choose.
- Examples
- This example copies a file to a new file, then tests for the existence of the new file:
-
- COPY FILE test.prg TO real.prg ? File("real.prg") // Result: TRUE
-
- The next example prints the contents of a file by copying it to the default device:
-
- COPY FILE real.prg TO PRN
-
- See Also
- COPY TO, FCopy(),DELETE FILE, RENAME, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_COPY_STRUCTURE.xml b/docs/Help_Spanish/Topics/command_COPY_STRUCTURE.xml
deleted file mode 100644
index 4614a33e83..0000000000
--- a/docs/Help_Spanish/Topics/command_COPY_STRUCTURE.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- COPY STRUCTURE Command
-
- Commands
- COPY STRUCTURE command
- Copyingstructures
- Creatingfiles
- Databases
- Filescreating
- Structurescopying
-
-
-
- COPY STRUCTURE Command
-
-
- Purpose
- Create an empty database file with field definitions from the current database file.
- Syntax
- COPY STRUCTURE [FIELDS <idFieldList>] TO <xcTargetFile>
- Arguments
- FIELDS <idFieldList>The set of fields to copy to the new database structure in the order specified. The default is all fields.
-
- TO <xcTargetFile>The name of the target database file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD .
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
- Examples
- In this example, COPY STRUCTURE creates a temporary file. After the user enters data into the temporary file, the master database file is updated with the new information:
-
- USE sales NEW COPYSTRUCTURETO temp USE temp NEW lMore := TRUE DOWHILE lMore APPENDBLANK @ 10, 10 GET Temp->Salesman @ 11, 11 GET Temp->Amount READ IF Updated() SELECT sales APPENDBLANK REPLACE Sales->Salesman WITH Temp->Salesman REPLACE Sales->Amount WITH Temp->Amount SELECT Temp ZAP ELSE lMore := FALSE ENDIF ENDDO CLOSEDATABASES
-
- See Also
- COPY STRUCTURE EXTENDED, CREATE, DbCopyStruct(), SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_COPY_STRUCTURE_EXTENDE.xml b/docs/Help_Spanish/Topics/command_COPY_STRUCTURE_EXTENDE.xml
deleted file mode 100644
index c64fb8ebda..0000000000
--- a/docs/Help_Spanish/Topics/command_COPY_STRUCTURE_EXTENDE.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-
-
-
- COPY STRUCTURE EXTENDED Command
-
- Commands
- COPY STRUCTURE EXTENDED command
- Copyingstructures
- Databases
- Structurescopying
-
-
-
- COPY STRUCTURE EXTENDED Command
-
-
- Purpose
- Copy the field definitions in a database file structure to a structure-extended file as data.
- Syntax
- COPY STRUCTURE EXTENDED TO <xcTargetFile>
- Arguments
- TO <xcTargetFile>The name of the target structure-extended database file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD .
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
- Description
- COPY STRUCTURE EXTENDED creates a database file whose containing the structure of the current database file, with a record for the definition of each field.
- The structure-extended database file has the following structure:
-
- Field NameTypeLengthDecimals
- Field_NameCharacter10
- Field_TypeCharacter1
- Field_LenNumeric30
- Field_DecNumeric30
-
- Used in application programs, COPY STRUCTURE EXTENDED permits you to create or modify the structure of a database file programmatically. To create a new database file from the structure-extended file, use CREATE FROM. If you need an empty structure-extended file, use CREATE.
- Notes
- Character field lengths greater than 255: Field lengths greater than 255 are represented as a combination of the Field_Dec and Field_Len fields. After performing COPY STRUCTURE EXTENDED, you can use the following formula to determine the length of any character field:
-
- nFieldLen := IIf((Field_Type ="C".AND.; Field_Dec !=0), Field_Dec *256+; Field_Len, Field_Len)
- Examples
- This example creates STRUC.DBF from SALES.DBF as a structure-extended file, then lists the contents of STRUC.DBF to illustrate the typical layout of field definitions:
-
- USE sales NEW COPY STRUCTURE EXTENDED TO struc USE struc NEW LIST Field_Name, Field_Type, Field_Len, Field_Dec
// Result: 1 BRANCHC30 2 SALESMANC40 3 CUSTOMERC40 4 PRODUCTC250 5 AMOUNTN82 6 NOTESC0125 // Field length is 32,000 characters
-
- See Also
- COPY STRUCTURE, CREATE, CREATE FROM, FieldName(), DbCopyXStruct(), SetDefault(), SetPath(), Type()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_COPY_TO.xml b/docs/Help_Spanish/Topics/command_COPY_TO.xml
deleted file mode 100644
index 1acb5a9f93..0000000000
--- a/docs/Help_Spanish/Topics/command_COPY_TO.xml
+++ /dev/null
@@ -1,101 +0,0 @@
-
-
-
- COPY TO Command
-
- Commands
- COPY TO command
- Copyingrecords
- Databases
- Exportingrecords
- Records
- Recordscopyingexporting
-
-
-
- COPY TO Command (non FoxPro)
-
-
- Purpose
- Export records to a new database or text file.
- Syntax
- COPY TO <xcTargetFile> [FIELDS <idFieldList>] [<Scope>] [WHILE <lCondition>] [FOR <lCondition>] [SDF] | [DELIMITED [WITH BLANK | <xcDelimiter>]] | [VIA <cDriver>] [INHERIT FROM <acRDDs>]
- Arguments
- TO <xcTargetFile>The name of the target file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD. For text files, it is .TXT.
-
- If <xcTargetFile> does not exist, it will be created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
-
-
-
-
-
- SDFA System Data Format file with format specifications as shown in the table below. Records and fields are fixed length.
-
- File ElementFormat
- Character fieldsPadded with trailing blanks
- Date fieldsyyyymmdd
- Logical fieldsT or F
- Memo fieldsIgnored
- Numeric fieldsPadded with leading blanks for zeros
- Field separatorNone
- Record separatorCarriage return/linefeed
- End of file marker1A hex or Chr(26)
-
- DELIMITED [WITH <xcDelimiter>]
- A text file in which character fields are enclosed in double quotation marks (the default delimiter) or the specified <xcDelimiter>. Fields and records are of variable length, and the formatting specifications are shown in the table below:
-
- File ElementFormat
- Character fieldsDelimited, with trailing blanks truncated
- Date fieldsyyyymmdd
- Logical fieldsT or F
- Memo fieldsIgnored
- Numeric fieldsLeading zeros truncated
- Field separatorComma
- Record separatorCarriage return/linefeed
- End of file marker1A hex or Chr(26)
-
- DELIMITED WITH BLANK
- A text file in which fields are separated by one space and character fields are not enclosed in delimiters. The format specifications are shown in the table below:
-
- File ElementFormat
- Character fieldsNot delimited, trailing blanks truncated
- Date fieldsyyyymmdd
- Logical fieldsT or F
- Memo fieldsIgnored
- Numeric fieldsLeading zeros truncated
- Field separatorSingle blank space
- Record separatorCarriage return/linefeed
- End of file marker1A hex or Chr(26)
-
- Warning! If the DELIMITED WITH clause is specified on a COPY TO command line, it must be the last clause specified.
-
- VIA <cDriver>The name of the RDD that will service the work area. If unspecified, the default RDD as determined by RDDSetDefault() is used.
-
- INHERIT FROM <acRDDs>
- A one-dimensional array with the names of RDDs from which the main RDD inherits special functionality. This allows you to use RDDs with special capabilities, like encryption or decryption, in different work areas with different database drivers. These RDDs overlay special functions of the main RDD (specified with the VIA clause). If multiple RDDs (specified with this INHERIT FROM clause) implement the same function, the function associated with the last RDD in the list takes precedence.
- Notes
- Deleted records: If SetDeleted() is FALSE, deleted records in the source file are copied to <xcTargetFile>, where they retain their deleted status.
-
- Visibility: If SetDeleted() is TRUE, however, deleted records are not visible and are, therefore, not processed Similarly, filtered records (with DbSetFilter() or a conditional controlling order) are not processed.
- Examples
- This example demonstrates copying to another database file:
-
- USE sales NEW COPY TO temp
-
- This example demonstrates the layout of an SDF file with four fields, one for each data type:
-
- USE testdata NEW COPY NEXT1TO temp SDF TYPE temp.txt // Result: Character 12.0019890801T
-
- The next example demonstrates the layout of a DELIMITED file:
-
- COPY NEXT1TO temp DELIMITED TYPE temp.txt // Result: "Character",12.00,19890801,T
-
- Finally, this example demonstrates the layout of a DELIMITED file WITH a different delimiter:
-
- COPY NEXT1TO temp DELIMITED WITH' TYPE temp.txt // Result: 'Character',12.00,19890801,T
-
- See Also
- APPEND FROM, COPY FILE, COPY STRUCTURE, DbCopy(), DbCopyDelim(), DbCopySDF(), RDDSetDefault(), SetDefault(), SetPath(), SetDeleted()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_COPY_TO_ARRAY.xml b/docs/Help_Spanish/Topics/command_COPY_TO_ARRAY.xml
deleted file mode 100644
index adbd8be432..0000000000
--- a/docs/Help_Spanish/Topics/command_COPY_TO_ARRAY.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- COPY TO ARRAY Command
-
- Commands
- COPY TO ARRAY command
- Copyingrecords
- Databases
- Records
- Recordscopying
-
-
-
- COPY TO ARRAY Command (FoxPro)
-
-
-
- Purpose
- Copies data from the currently selected table to an array.
- Syntax
- COPY TO ARRAY <ArrayName> [FIELDS FieldList | FIELDS LIKE <Skeleton> | FIELDS EXCEPT <Skeleton>] [<Scope>] [WHILE <lCondition>] [FOR <lCondition>] [NOOPTIMIZE]
- Arguments
- <ArrayName>Specifies the name of the array that contains the data to be copied to the new records. New records are added to the table until all rows in the array are appended.
-
-
-
-
-
- NOOPTIMIZEThis clause is parsed but not yet supported.
-
- See Also
- APPEND FROM ARRAY, GATHER, SCATTER
-
-
diff --git a/docs/Help_Spanish/Topics/command_COPY_TO_FoxPro.xml b/docs/Help_Spanish/Topics/command_COPY_TO_FoxPro.xml
deleted file mode 100644
index 0ebb6336e0..0000000000
--- a/docs/Help_Spanish/Topics/command_COPY_TO_FoxPro.xml
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
- COPY TO Command (FoxPro)
-
- Commands
- COPY TO command
- Copyingrecords
- Databases
- Exportingrecords
- Records
- Recordscopyingexporting
-
-
-
- COPY TO Command (FoxPro)
-
-
- Purpose
- Export records to a new database or text file.
- Syntax
- COPY TO <xcTargetFile> [DATABASE <DbName> [NAME <LongName>] [FIELDS FieldList | FIELDS LIKE <Skeleton> | FIELDS EXCEPT <Skeleton>] [<Scope>] [FOR <lCondition>] [WHILE <lCondition> ] [ [WITH] CDX ] | [ [WITH] PRODUCTION ] [NOOPTIMIZE] [ [TYPE] [ FOXPLUS | FOX2X | DIF | MOD | SDF | SYLK | WK1 | WKS | WR1 | WRK | CSV | XLS | XL5 | DELIMITED [ WITH <Delim> | WITH BLANK | WITH TAB | WITH CHARACTER <cDelim> ] ] ] [AS <nCodePage>]
- Arguments
- TO <xcTargetFile>The name of the target file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD. For text files, it is .TXT.
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
- DATABASE <DbName>Specifies a database to which the new table is added. NOT SUPPORTED AT THIS MOMENT
- NAME <LongName>Specifies a long name for the new table. Long names can contain up to 128 characters and can be used instead of short file names in the database. NOT SUPPORTED AT THIS MOMENT
-
-
-
-
-
- DELIMITED WITH <Delim>Indicates that character fields are separated by a character other than the quotation mark.
- DELIMITED WITH BLANK Specifies files that contain fields separated by spaces instead of commas.
- DELIMITED WITH TAB Specifies files that contain fields separated by tabs rather than commas.
- WITH CHARACTER <cDelim>Specifies files that contain fields all enclosed by the character specified with Delimiter. If Delimiter is a semicolon (the character used in Visual FoxPro to indicate command line continuation), enclose the semicolon in quotation marks. You can also specify the BLANK and TAB keywords for Delimiter. The WITH Delimiter clause can be combined with the WITH CHARACTER clause.
-
- TYPESpecifies the file type if the file you create is not an XBase table. Although you must specify a file type, you do not need to include the TYPE keyword.
- From the various types that FoxPro allows, only the following ones are currently supported in X#:
- SDFAn SDF file is an ASCII text file in which records have a fixed length and end with a carriage return and line feed. Fields are not delimited. The file name extension is assumed to be .txt for SDF files.
- CSVA comma-separated value file. A CSV file has field names as the first line in the file; the field names are ignored when the file is imported. The file name extension is assumed to be .csv for CSV files. FOXPLUSVisual FoxPro memo files have a different structure than FoxBASE memo files. If your source table contains a memo field, include the FOXPLUS clause to create a table that can be used in FoxBASE+. The Visual FoxPro memo field cannot contain binary data because FoxBASE+ does not support binary data in memo fields.
- FOX2XCreates a new table that can be opened in earlier versions of FoxPro (versions 2.0, 2.5, and 2.6).
- OTHERNOT SUPPORTED AT THIS MOMENT
- AS <nCodePage>Specifies the codepage to use for the target file. NOT SUPPORTED AT THIS MOMENT
-
- Notes
- Deleted records: If SetDeleted() is FALSE, deleted records in the source file are copied to <xcTargetFile>, where they retain their deleted status.
-
- Visibility: If SetDeleted() is TRUE, however, deleted records are not visible and are, therefore, not processed. Similarly, filtered records (with DbSetFilter() or a conditional controlling order) are not processed.
- Examples
- This example demonstrates copying to another database file:
-
- USE sales NEW COPY TO temp
-
- This example demonstrates the layout of an SDF file with four fields, one for each data type:
-
- USE testdata NEW COPY NEXT1TO temp SDF TYPE temp.txt // Result: Character 12.0019890801T
-
- The next example demonstrates the layout of a DELIMITED file:
-
- COPY NEXT1TO temp DELIMITED TYPE temp.txt // Result: "Character",12.00,19890801,T
-
- Finally, this example demonstrates the layout of a DELIMITED file WITH a different delimiter:
-
- COPY NEXT1TO temp DELIMITED WITH' TYPE temp.txt // Result: 'Character',12.00,19890801,T
-
- See Also
- APPEND FROM, COPY FILE, COPY STRUCTURE, DbCopy(), DbCopyDelim(), DbCopySDF(), RDDSetDefault(), SetDefault(), SetPath(), SetDeleted()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_COUNT.xml b/docs/Help_Spanish/Topics/command_COUNT.xml
deleted file mode 100644
index 3a4ce026a5..0000000000
--- a/docs/Help_Spanish/Topics/command_COUNT.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
- COUNT Command
-
- Commands
- COUNT command
- Counting records
- Databases
- Recordscounting
-
-
-
- COUNT Command
-
-
- Purpose
- Tally the number of records from the current work area that match the specified record scope and condition, and place the result in the specified variable.
- Syntax
- COUNT TO <idVar> [<Scope>] [WHILE <lCondition>] [FOR <lCondition>]
- Arguments
- TO <idVar>The variable or field that holds the COUNT result. A variable that either does not exist or is invisible is created as a private variable.
-
-
-
-
- Examples
- This example demonstrates a COUNT using a particular Branch in SALES.DBF:
-
- USE sales NEW COUNTTO nBranchCnt FOR Branch = 100 ? nBranchCnt // Result: 4
-
- The next example tallies the number of records in SALES.DBF whose Branch has the value of 100 and assigns the result to the Count field in BRANCH.DBF for branch 100:
-
- USE branch INDEX branch NEW SEEK 100 USE sales INDEX salesbranch NEW SEEK 100 COUNTTO Branch->Count WHILE Sales->Branch = 100
-
- See Also
- AVERAGE, DBEval(), SUM, TOTAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_CREATE.xml b/docs/Help_Spanish/Topics/command_CREATE.xml
deleted file mode 100644
index e817bdbcf5..0000000000
--- a/docs/Help_Spanish/Topics/command_CREATE.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- CREATE Command
-
- Commands
- CREATE command
- Creatingfiles
- Databases
- Filescreating
-
-
-
- CREATE Command
-
-
- Purpose
- Create an empty structure-extended file.
- Syntax
- CREATE <xcTargetFile> [NEW] [ALIAS <xcAlias>] [VIA <cDriver>]
- Arguments
- <xcTargetFile>The name of the empty structure-extended database file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD. After the file is created, it remains open in the mode specified by the SetExclusive() flag for the work area.
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
-
- The structure of <xcTargetFile> is the same as the structure generated by COPY STRUCTURE EXTENDED, which you can refer to for more details.
-
- NEWSelects the next unoccupied work area before opening <xcTargetFile>. If this clause is not specified, the current work area is used.
-
- ALIAS <xcAlias>An identifier name to associate with the work area when <xcTargetFile> is opened. If this clause is not specified, the alias defaults to the database file name. Duplicate alias names are not allowed within a single application.
-
- VIA <cDriver>The name of the RDD that will service the work area. If not specified, the default RDD as determined by RDDSetDefault() is used.
- Notes
- Unlike COPY STRUCTURE EXTENDED, the file created by CREATE is empty. You must add records to the structure-extended file before you can use it to create a new database file with CREATE FROM.
- Examples
- This example creates a new structure-extended file, places the definition of one field into it, then creates a new database file from the extended structure:
-
- CREATE tempstru APPEND BLANK REPLACE Field_Name WITH"Name",; Field_Type WITH"C",; Field_Len WITH25,; Field_Dec WITH0 CLOSE CREATE newfile FROM tempstru
-
- See Also
- COPY STRUCTURE EXTENDED, CREATE FROM, DbCopyStruct(), DbCreate(), RDDSetDefault(),SetDefault(), SetPath(), SetExclusive()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_CREATE_FROM.xml b/docs/Help_Spanish/Topics/command_CREATE_FROM.xml
deleted file mode 100644
index 52b3a3b2bd..0000000000
--- a/docs/Help_Spanish/Topics/command_CREATE_FROM.xml
+++ /dev/null
@@ -1,67 +0,0 @@
-
-
-
- CREATE FROM Command
-
- Arrayscreating files from
- Commands
- Copyingarrays
- CREATE FROM command
- Creatingfiles
- Databases
- Filescreating
-
-
-
- CREATE FROM Command
-
-
- Purpose
- Produce a new database file with the field definitions taken from the contents of a structure-extended file.
- Syntax
- CREATE <xcTargetFile> FROM <xcSourceFile> [NEW] [ALIAS <xcAlias>] [VIA <cDriver>]
- Arguments
- <xcTargetFile>The name of the target database file to create, including an optional drive, directory, and extension. After the file is created, it remains open in the mode specified by the SetExclusive() flag for the work area.
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
-
- <xcSourceFile>The name of a structure-extended file to use as the structure definition for the new database file, including an optional drive, directory, and extension.
-
- If <xcSourceFile> does not exist, a runtime error is raised. If it exists, this command attempts to open the file in shared mode and, if successful, it proceeds. If access is denied because, for example, another process has exclusive use of the file, NetErr() is set to TRUE.
-
- See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD.
-
- To qualify as a structure-extended file, the structure of the database file must be the same as the structure generated by COPY STRUCTURE EXTENDED, which you can refer to for more details.
-
- Note: For data dictionary applications, you can have additional fields within the structure-extended file to describe the extended field attributes. For example, you can have fields to describe such field attributes as a description, key flag, label, color, picture, and a validation expression for the VALID clause. CREATE FROM creates the new database file from the required fields only, ignoring all other fields in the extended structure. Moreover, it is not sensitive to the order of the required fields.
-
- NEWSelects the next unoccupied work area before opening <xcTargetFile>. If this clause is not specified, the current work area is used.
-
- ALIAS <xcAlias>An identifier name to associate with the work area when <xcTargetFile> is opened. If this clause is not specified, the alias defaults to the database file name. Duplicate alias names are not allowed within a single application.
-
- VIA <cDriver>The name of the RDD that will service the work area. If not specified, the default RDD as determined by RDDSetDefault() is used.
- Notes
- Character field lengths greater than 255: There are two methods for creating a character field with a length greater than 255 digits:
-
-
Specify the field length using both the Field_Len and Field_Dec fields according to the following formulation:
-
_FIELD->Field_Len := <nLength> % 256
-
_FIELD->Field_Dec := Integer(<nLength> / 256)
-
-
-
-
Modify the structure of the structure-extended file by changing the length of Field_Len to 5, then specify the actual field length.
-
- Examples
- This example is a procedure that simulates an interactive CREATE utility:
-
- FUNCTION Start() CreateDatabase("newfile")
FUNCTION CreateDatabase(cNewDbf) // Create empty structure-extended file CREATE tmpext USE tmpext lMore :=TRUE DOWHILE lMore // Input new field definitions APPEND BLANK CLEAR @5,0 SAY "Name.....: " GET Field_Name @6,0 SAY "Type.....: " GET Field_Type @7,0 SAY "Length...: " GET Field_Len @8,0 SAY "Decimals.: " GET Field_Dec READ lMore :=(!EMPTY(Field_Name)) ENDDO
// Remove all blank records DELETE ALL FOREMPTY(Field_Name) PACK CLOSE
// Create new database file CREATE (cNewDbf) FROM tmpext ERASE tmpext.dbf
-
- The next example creates a new definition in a structure-extended file for a character field with a length of 4000 characters:
-
- APPEND BLANK REPLACE Field_Name WITH"Notes",; Field_Type WITH"C",; Field_Len WITH4000%256,; Field_Dec WITHINTEGER(4000/256)
-
- See Also
- COPY STRUCTURE, COPY STRUCTURE EXTENDED, CREATE, DbCopyXStruct(), DbCreate(), RDDSetDefault(), SetDefault(), SetExclusive(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DECLARE.xml b/docs/Help_Spanish/Topics/command_DECLARE.xml
deleted file mode 100644
index 63cc597f1b..0000000000
--- a/docs/Help_Spanish/Topics/command_DECLARE.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- DECLARE / DIMENSION Statement
-
- Declaration statements
- DECLARE
- DECLARE statement
- DIMENSION
- Runtime declaration
- Statements
-
-
-
- DECLARE/DIMENSION Statement
-
-
-
- Purpose
- Creates and initializes private variables of the FoxPro array type. Note: Dimension and Declare are synonyms.
-
- DIMENSION <arrayName> ( <nRows> [, <nColumns>] ) [, <arrayName> ( <nRows> [, <nColumns>] ) ] // FoxPro dialect only DIMENSION <arrayName> [ <nRows> [, <nColumns>] ] [, <arrayName> [ <nRows> [, <nColumns>] ] ] // FoxPro dialect only DECLARE <arrayName> ( <nRows> [, <nColumns>] ) [, <arrayName> ( <nRows> [, <nColumns>] ) ] // FoxPro dialect only DECLARE <arrayName> [ <nRows> [, <nColumns>] ] [, <arrayName> [ <nRows> [, <nColumns>] ] ] // FoxPro dialect only
-
- Arguments
- arrayName>Variable name of array. The array will have the dimensions as declared with <nRows> and <nColumns>. The array may be declared with parentheses as delimiters but also with square brackets. <nColumns> is optional. We recommend the use of square brackets.
- See Also
- PUBLIC, LOCAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DECLARE_METHOD.xml b/docs/Help_Spanish/Topics/command_DECLARE_METHOD.xml
deleted file mode 100644
index 370e8495c9..0000000000
--- a/docs/Help_Spanish/Topics/command_DECLARE_METHOD.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- DECLARE METHOD Statement
-
- Declaration statements
- DECLARE METHOD statement
- Runtime declaration
- Statements
-
-
-
- DECLARE METHOD Statement
-
- Purpose
- Forward declare a method, access or assign.
- Description
- DECLARE METHOD, DECLARE ASSIGN and DECLARE ACCESS are recognized by the X# compiler but no longer needed, so they are ignored.
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DEFAULT.xml b/docs/Help_Spanish/Topics/command_DEFAULT.xml
deleted file mode 100644
index 99437b09dc..0000000000
--- a/docs/Help_Spanish/Topics/command_DEFAULT.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- DEFAULT Command
-
- Commands
- Data type/parameter checking
- DEFAULT command
- NILsassigning default values
-
-
-
- DEFAULT Command
-
-
- Purpose
- Assigns a default value to a NIL argument.
- Syntax
- DEFAULT <idVar> TO <uDefault> [, <idVar> TO <uDefault>...]
- Description
- DEFAULT is functionally equivalent to Default(), except that DEFAULT lets you assign multiple default values.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DEFINE.xml b/docs/Help_Spanish/Topics/command_DEFINE.xml
deleted file mode 100644
index d0c60eeee2..0000000000
--- a/docs/Help_Spanish/Topics/command_DEFINE.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-
-
-
- DEFINE Statement
-
- Compile-time declaration
- Constantsdeclaring
- Declaration statements
- Define
- DEFINE statement
- Entity declaration
- Statements
- STATIC DEFINE statement
-
-
-
- DEFINE Statement
-
- Purpose
- Declare a constant name and its value to the compiler.
- Syntax
- [Modifiers] DEFINE <idConstant> := <uValue> [AS <idType>]
- Arguments
-
- <idConstant>A valid identifier name for the constant. A constant is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a constant and a global variable, for example, with the same name.
-
- <uValue>A constant value that is assigned to <idConstant>. This value can be a literal representation of one of the data types listed below or a simple expression involving only operators, literals, and other DEFINE constants; however, more complicated expressions (including class instantiation) are not allowed.
-
-
-
- Description
- Once the constant name and value is declared and initialized with the DEFINE statement, you cannot change the value of <idConstant> without provoking a compiler error. The constant value <uValue> will be used whenever the <idConstant> identifier name is encountered in your application.
-
- You can hide a constant name from a routine by declaring a variable with the same name (with LOCAL, MEMVAR, or FIELD). The search order for a variable name is as follows:
- 1.LOCALs, local parameters, MEMVARs, and FIELDs;
- 2.SELF instance variables (i.e., without <idObject>: prefix in class methods);
- 3.GLOBALs and DEFINEs.
-
- Tip: You can perform a conditional build based on the value of a DEFINE constant. See the #ifdef and #ifndef statements in this chapter for more information and examples.
- Examples
- The following example assigns an application name to the constant cAppName. This value is then displayed at the beginning and end of the application run:
-
- DEFINE cAppName := "Accounts Payable" ... FUNCTION Start() ? "Start of ", cAppName, " application." ... ? "End of ", cAppName, " application."
- See Also
- #ifdef, #ifndef, GLOBAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DELEGATE.xml b/docs/Help_Spanish/Topics/command_DELEGATE.xml
deleted file mode 100644
index be35d6d6e5..0000000000
--- a/docs/Help_Spanish/Topics/command_DELEGATE.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
- DELEGATE Statement
-
- DELEGATE
- reference type
-
-
-
- DELEGATE Statement
-
- Purpose
- Declare a delegate to the compiler.
- Syntax
- [Attributes] [Modifiers] DELEGATE <idDelegate>
- [Typeparameters]
- [([<idParam> [AS | REF|OUT|IN <idType>] [, ...])]
- [AS <idType>]
- [TypeparameterConstraints]
- Arguments
-
- <idDelegate>A valid identifier name for the delegate. Delegate names must be unique within a namespace.
-
-
-
-
- Description
- A delegate is a reference type that encapsulates a function or method. Delegates are similar to function pointers in native code languages such as Visual Objects, C and C++, but unlike function pointers, delegates are object-oriented, secure and type-safe.
- The DELEGATE statement declares a special type of class which is partially implemented by the compiler, and partially implemented by the CLR. All delegates inherit from System.MulticastDelegate.
- Every delegate has a signature, which is a combination of its parameter and return value types.
- Instantiation
- You can explicitly call the delegate constructor like:
- f := MyDelegate{ NULL, @SomeClass.Test() }
- for static methods :
- f := MyDelegate{ SELF, @SomeClass.Test() }
-
- for instance methods, it is also possible to write:
- f := SomeClass.Test
- for static methods:
- f := SELF:Test
- Example
- DELEGATE MyDelegate( x ASSTRING ) ASSTRING
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DELETE.xml b/docs/Help_Spanish/Topics/command_DELETE.xml
deleted file mode 100644
index c99f774c93..0000000000
--- a/docs/Help_Spanish/Topics/command_DELETE.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
- DELETE Command
-
- Commands
- Databasesrecords
- DELETE command
- Deleting
- Recordsdeleting
-
-
-
- DELETE Command
-
-
- Purpose
- Tag records so they can be filtered with SetDeleted(TRUE), queried with Deleted(), or physically removed from the database file with PACK.
- Syntax
- DELETE [<Scope>] [WHILE <lCondition>] [FOR <lCondition>] [[IN|ALIAS] <workarea>]
- Arguments
-
-
-
-
-
- Description
- This command merely marks the records for deletion. To permanently remove records that are marked for deletion, PACK the file. Before packing, you can reinstate deleted records with RECALL.
- Notes
- Visibility:If the current record is deleted and SetDeleted() is TRUE, it will be visible until the record pointer is moved.
-
- Display of delete marker:Display commands, such as LIST and DISPLAY, identify deleted records with an asterisk character (*).
-
- Deleting all records:To permanently remove all records from a database file regardless of their delete status, ZAP the file.
-
- Shared mode:For a shared database, this command requires all records that it operates on to be locked. You can accomplish this using one or more record locks or a file lock, depending on the scope of the command.
- Examples
- This example demonstrates use of the FOR clause to mark a set of records for deletion:
-
- USE sales INDEX salesman NEW DELETE ALL FOR Inactive
-
- See Also
- DbDelete(), DBRLock(), Deleted(), FLock(), PACK, RECALL, RLock(), SetDeleted(), ZAP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DELETE_FILE.xml b/docs/Help_Spanish/Topics/command_DELETE_FILE.xml
deleted file mode 100644
index 7f1bcbd4cf..0000000000
--- a/docs/Help_Spanish/Topics/command_DELETE_FILE.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- DELETE FILE Command
-
- Commands
- DELETE FILE command
- Deletingfiles
- Filesdeleting
-
-
-
- DELETE FILE Command
-
-
- Purpose
- Remove a file from disk.
- Syntax
- DELETE FILE | ERASE <xcSourceFile>
- Arguments
- <xcSourceFile>The name of the file to delete, including an optional drive, directory, and extension. SetDefault() and SetPath() do not affect this command. It assumes the current Windows drive and directory if none is specified. No default extension is supplied.
-
- Warning! Files must be closed before deleting them.
- Examples
- This example removes a specified file from disk then tests to see if the file was removed:
-
- ? File("temp.dbf")// Result: TRUE DELETE FILE temp.dbf ? File("temp.dbf")// Result: FALSE
-
- See Also
- CurDir(),FErase(),File(), USE, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DELETE_TAG.xml b/docs/Help_Spanish/Topics/command_DELETE_TAG.xml
deleted file mode 100644
index 4244b6d3f4..0000000000
--- a/docs/Help_Spanish/Topics/command_DELETE_TAG.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- DELETE TAG Command
-
- Commands
- DELETE TAG command
- Deleting
- Deleting
- Index filesdeleting
- Index/orderindex filesorders
- Ordersdeleting
-
-
-
- DELETE TAG Command
-
-
- Purpose
- Delete one or more orders from open index files.
- Syntax
- DELETE TAG <xcOrder> [IN <xcIndexFile>] [, <xcOrder> [IN <xcIndexFile>]...]
- Arguments
- <xcOrder>The name of the order to be removed. If <xcOrder> is a NULL_STRING or spaces, it is ignored. If <xcOrder> cannot be found, a runtime error is raised.
-
- IN <xcIndexFile>The name of an open index file, including an optional drive and directory (no extension should be specified). Use this argument to avoid ambiguity when multiple orders with the same name exist in different index files.
- If <xcIndexFile> is not open in the current process or work area, a runtime error is raised.
- Description
- DELETE TAG requires that the current database be open in exclusive mode. If this condition is not met when DELETE TAG is invoked, a runtime error is raised.
-
- If you specify an index file name, DELETE TAG deletes the indicated order from that file. Otherwise, the command searches all index files open in the current work area and deletes the first occurrence of <xcOrder> that is found.
- If the controlling order is deleted, the database reverts to its natural order and DbSetFilter() scoping.
-
- Note: The RDD determines the order capacity of an index file, and DELETE TAG is supported only by RDDs with multiple-order capabilities. For single-order index files, you must delete the entire file.
- Examples
- This example illustrates how to delete selected orders from an index file:
-
- USE customer VIA "DBFMDX" NEW Customer->DBSetIndex("customer")
// Delete the Cust01 and Cust02 orders from the // Customer index file DELETETAG Cust01 IN customer, Cust02 IN customer // or // Customer->DBDeleteOrder("Cust01", "customer") // Customer->DBDeleteOrder("Cust02", "customer")
-
- See Also
- DBCreateIndex(), DbCreateOrder(), DbDeleteOrder(), INDEX, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DESTRUCTOR.xml b/docs/Help_Spanish/Topics/command_DESTRUCTOR.xml
deleted file mode 100644
index bf9bb47f56..0000000000
--- a/docs/Help_Spanish/Topics/command_DESTRUCTOR.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- DESTRUCTOR Statement
-
- Compile-time declaration
- Declaration statements
- DESTRUCTOR statement
- Entity declaration
- Statements
-
-
-
- DESTRUCTOR Statement
-
- Purpose
- Declare a special method that is automatically invoked when the Garbage Collector frees up the memory used by an object which is not needed anymore.
- Syntax
- [Attributes] [Modifiers] DESTRUCTOR [()]
- [=> <expression>]
- CRLF
- [<Body>]
- [END DESTRUCTOR]
- Arguments
-
-
-
- END DESTRUCTOROptional end clause to indicate the end of the DESTRUCTOR entity
-
- See Also
- ASSIGN, CLASS, METHOD
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DIR.xml b/docs/Help_Spanish/Topics/command_DIR.xml
deleted file mode 100644
index 9e438d89a2..0000000000
--- a/docs/Help_Spanish/Topics/command_DIR.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- DIR Command
-
- Commands
- DIR command
- Displayingfile listing
- Filesdisplaying
-
-
-
- DIR Command
-
-
- Purpose
- Display a listing of files.
- Syntax
- DIR [<xcFileSpec>]
- Arguments
- <xcFileSpec>The file specification for the directory search. Besides a file name, this specification may also include an optional drive, directory, and extension. The file name and extension may include the standard wildcard characters (* and ?). If you do not specify a drive and directory, this function respects SetDefault().
-
- If the argument is omitted, the default file specification is *.DBF.
-
- If <xcFileSpec> is not specified, the listing includes the file name, date of last update, and number of records. Otherwise, it includes the file name, extension, number of bytes, and date of last update.
- Notes
- To save the directory listing in an array, use Directory() instead of Dir().
- Examples
- This example displays all files, all database files, and all text files in the current directory:
-
- cFilespec := "*.*" DIR (cFilespec)// Display all files DIR// Display all .dbf files DIR *.txt// Display all text files
-
- See Also
- ADir(), Directory(), SetDefault()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DO.xml b/docs/Help_Spanish/Topics/command_DO.xml
deleted file mode 100644
index d3f99ef41c..0000000000
--- a/docs/Help_Spanish/Topics/command_DO.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- DO Statement
-
- Branching
- DO statement
- Program control
- Statements
-
-
-
- DO Statement
-
- Purpose
- Calls a procedure or function, and optionally passes arguments to the called routine.
- Syntax
- DO <idProcedure> [WITH <uValueArgList>]
- Arguments
- <idProcedure>The name of the procedure or function to execute.
-
- WITH <uValueArgList>A comma-separated list of arguments to pass to <idProcedure>.
- Description
- DO performs the same action as a function or procedure specified on a line by itself with the exception that variables other than field variables are passed by reference as the default. In order to pass a field variable as an argument, enclose it in parentheses, unless you declare it with the FIELD statement or specify it with an alias.
- Examples
- This example executes a procedure with no parameters:
- DO AcctsRpt AcctsRpt()// Preferred method
- The next example executes a procedure passing two constants:
- DO QtrRpt WITH"2nd","Sales Division" // Preferred method QtrRpt("2nd","Sales Division")
- In this example, a procedure is executed with the first argument passed by value and the second passed by reference:
- nNumber :=12 DO YearRpt WITH nNumber +12, nNumber // Preferred method YearRpt(nNumber +12,@nNumber)
- Here, a procedure is invoked with skipped arguments embedded in the list of arguments:
- DO DisplayWindow WITH,,,,"My Window" // Preferred method DisplayWindow(,,,,"My Window")
- See Also
- FIELD, FUNCTION, LOCAL, PARAMETERS, PRIVATE, PROCEDURE, PUBLIC, RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DO_CASE.xml b/docs/Help_Spanish/Topics/command_DO_CASE.xml
deleted file mode 100644
index bf07b683e2..0000000000
--- a/docs/Help_Spanish/Topics/command_DO_CASE.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- DO CASE Statement
-
- Branching
- CASE statement
- Conditional execution
- DO CASE statement
- ENDCASE statement
- OTHERWISE statement
- Program control
- Statements
-
-
-
- DO CASE Statement
-
- Purpose
- Conditionally executes a block of statements.
- Syntax
- DO CASE CASE <lCondition> <Statements>... [CASE <lCondition>] <Statements>... [OTHERWISE] <Statements>... END[CASE]
- Arguments
- <lCondition>If this expression evaluates to TRUE, the statements following it up until the next CASE, OTHERWISE, or ENDCASE are executed. Afterwards, control branches to the statement following the next ENDCASE statement.
- OTHERWISEIf all preceding CASE conditions evaluate to FALSE, the statements following the OTHERWISE up until the next ENDCASE are executed. Afterwards, control branches to the statement following the next ENDCASE statement.
- Description
- DO CASE works by branching to the statement following the first CASE <lCondition> that evaluates to TRUE. If all CASE conditions evaluate to FALSE, it branches to the statement following the OTHERWISE statement (if specified).
- Execution proceeds until the next CASE, OTHERWISE, or ENDCASE is encountered, and control then branches to the first statement following the next ENDCASE statement.
- Control structures can be nested to any depth. The only requirement is that each control structure be properly nested.
- Note: DO CASE...ENDCASE is identical to IF...ELSEIF...ENDIF, with neither syntax having a performance advantage over the other.
- Examples
- This example uses DO CASE in a menu structure to branch control based on user selection:
- FUNCTION ActonChoice(nChoice asLONG) ASVOID DOCASE CASE nChoice = 0 RETURN CASE nChoice = 1 ChoiceOne() CASE nChoice = 2 ChoiceTwo() ENDCASE
- See Also
- BEGIN SEQUENCE, DO WHILE, FOR, FOREACH IF SWITCH
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_DO_WHILE.xml b/docs/Help_Spanish/Topics/command_DO_WHILE.xml
deleted file mode 100644
index d2917020a7..0000000000
--- a/docs/Help_Spanish/Topics/command_DO_WHILE.xml
+++ /dev/null
@@ -1,58 +0,0 @@
-
-
-
- DO WHILE Statement
-
- Branching
- Conditional execution
- DO WHILE statement
- ENDDO statement
- EXIT statement
- LOOP statement
- Looping
- Program control
- Statements
-
-
-
- DO WHILE Statement
-
- Purpose
- Executes a loop while a condition is TRUE.
- Syntax
- [DO] WHILE <lCondition>
- <Statements>...
- [EXIT]
- <Statements>...
- [LOOP]
- <Statements>...
- END[DO]
- Arguments
- <lCondition>The logical control expression for the DO WHILE loop.
-
-
- Description
- When the condition evaluates to TRUE, control passes into the structure and proceeds until an EXIT, LOOP, or ENDDO is encountered. ENDDO returns control to the DO WHILE statement and the process repeats itself. If the condition evaluates to FALSE, the DO WHILE construct terminates and control passes to the statement immediately following the ENDDO.
-
- Use EXIT to terminate a DO WHILE structure based on a condition other than the DO WHILE condition. LOOP, by contrast, prevents execution of statements within a DO WHILE based on an intermediate condition, and returns to the most recent DO WHILE statement.
-
- Control structures can be nested to any depth. The only requirement is that each control structure be properly nested.
- Examples
- This example demonstrates a typical control structure for a simple grouped report:
-
- LOCAL cOldSalesman, nTotalAmount USE sales INDEX salesman NEW DOWHILE.NOT.EOF() cOldSalesman := Sales->Salesman nTotalAmount :=0 DOWHILE cOldSalesman = Sales->Salesman ; .AND.(.NOT.EOF()) ? Sales->Salesman, Sales->Amount nTotalAmount := nTotalAmount + Sales->Amount SKIP ENDDO ?"Total: ", nTotalAmount,"for", cOldSalesman ENDDO CLOSE sales
- This code fragment demonstrates how LOOP can be used to provide an intermediate processing condition:
-
- DOWHILE <lCondition> <Initial Processing>... IF <Intermediate Condition> LOOP ENDIF <Continued Processing>... ENDDO
- The next example demonstrates the use of DO WHILE to emulate a "repeat until looping" construct:
-
- LOCAL lMore :=TRUE DOWHILE lMore <Statements>... lMore := <lCondition> ENDDO
-
- Here, a DO WHILE loop moves sequentially through a database file:
-
- DOWHILE.NOT.EOF() <Statements>... SKIP ENDDO
- See Also
- BEGIN SEQUENCE, DBEval(), DO CASE, FOR, IF, RETURN, EXIT, LOOP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_ENUM.xml b/docs/Help_Spanish/Topics/command_ENUM.xml
deleted file mode 100644
index 63ce64501d..0000000000
--- a/docs/Help_Spanish/Topics/command_ENUM.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- ENUM Statement
-
- ENUM
- enumeration
- enumeration members
-
-
-
- ENUM Statement
-
- Purpose
- Declare an enumeration to the compiler.
- Syntax
- [attributes] [Modifiers]
- ENUM <idEnumName> [AS type]
- memberName [:= value]
- [...]
- END [ENUM]
-
- Arguments
-
- idEnumA valid identifier name for the enum. Enum names must be unique within a namespace.
-
- AS type The data type of the enumeration members (optional).
-
- memberName The name(s) of the enumeration members.
-
- Description
- A type declared with the ENUM keyword is an "enumeration" type, a type that consists of a set of named constants which are called the enumerator list. Enumeration types implicitly inherit from System.Enum.
-
- An enumeration type has an underlying type, which is the type of the items in the enumerator list. The default underlying type is INT; if the AS clause is specified, then the type can be any signed or unsigned integral type, except System.Char.
-
- By default, the first member in the enumerator list has a value of 0. The value of every other member is the value of the previous member plus 1. An element's value can be explicitly set to any value in the range of the underlying type by using the assignment operator (:=), followed by either a literal integer value, or an expression that resolves to an integer value at compile time. Two or more members can explicitly set to the same value.
-
- The default value for an ENUM E is the expression (E)0., which may or may not represent a member of the enum type, depending on whether or not a member having the value of 0 exists.
-
- Enumeration members are referenced by specifying the name of the enumeration type and the name of the member, separated by a period. If the enumeration type was declared in the namespace currently being compiled, the name of the enumeration type is sufficient. Otherwise, either the fully-qualified name of the enumeration must be used (e.g. System.Windows.Forms.MessageBoxButtons), or the namespace must be imported using the USING directive.
-
- The System.FlagsAttribute attribute may be placed on an ENUM to indicate that the elements of the enum may be combined using a bitwise OR operation.
-
- The enum name may include one or more namespace names, separated by periods. If no period is found in the enum name, then the default namespace is assumed. The default namespace is the base name of the output assembly name, unless explicitly overridden by the /ns compiler option.
-
- Example
- ENUM days Sunday // 0 Monday // 1 Tuesday // 2 Wednesday // 3 Thursday // 4 Friday // 5 Saturday // 6 ENDENUM
FUNCTION example1() ASVOID LOCAL i ASINT i := (INT) days.Friday ? days.Friday, i // prints: Friday 5 ENUM direction north // has default value of 0 east := 90 south := 180 west := 270 ENDENUM
FUNCTION example2( x AS direction ) ASVOID IF x == direction.north goNorth() ELSEIF x == direction.east goEast() ELSEIF x == direction.south goSouth() ELSEIF x == direction.west goWest() ELSE Debug.Assert( "Unknown value for direction" ) ENDIF [System.FlagsAttribute]; ENUM CarOptions SunRoof := 0x1 Spoiler := 0x2 FogLights := 0x4 TintedWindows := 0x8 ENDENUM
FUNCTION example3() ASVOID LOCAL options AS CarOptions options := CarOptions.SunRoof | CarOptions.FogLights ? options // prints: SunRoof, FogLights ? (INT) options // prints: 5
- In the first and third examples, note that using the ? statement on an enum type prints out the textual value of the enum. This is because the names of the enum members are stored in the assembly's metadata, and the ToString() method in System.Enum (which every enum type inherits from) uses the metadata to obtain and return the name of the enum member, rather than its underlying numerical value.
-
- Also note that even though the textual names of the enum members are returned from Enum.ToString(), the compiler uses the literal numeric values in the compiled code. So the expression IF x == direction.north for example actually compiles as IF x == 0, because the mapping between enumeration members and their underlying values occurs at compile time, not at runtime. This makes using enumeration types as efficient as #define, while providing much higher level of type safety and compile time error checking. However, this also means that changing the values of enum members can cause existing code that uses the enum to break unless it is recompiled.
-
- Notes
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_ERASE.xml b/docs/Help_Spanish/Topics/command_ERASE.xml
deleted file mode 100644
index 6f6d53802f..0000000000
--- a/docs/Help_Spanish/Topics/command_ERASE.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- ERASE Command
-
- Commands
- Deletingfiles
- ERASE command
- Filesdeleting
-
-
-
-
- ERASE Command
-
-
- Purpose
- Remove a file from disk.
- Syntax
- ERASE | DELETE FILE <xcSourceFile>
- Description
- ERASE is the same as DELETE FILE. See DELETE FILE for a complete explanation of this command.
-
- See Also
- DELETE FILE, FErase()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_EVENT.xml b/docs/Help_Spanish/Topics/command_EVENT.xml
deleted file mode 100644
index d1c4e33860..0000000000
--- a/docs/Help_Spanish/Topics/command_EVENT.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- EVENT Statement
-
- Access() Methods
- Compile-time declaration
- Declaration statements
- Entity declaration
- EVENT statement
- Statements
-
-
-
- EVENT Statement
-
- Purpose
- Declare an event to a class, which can be used to notify other classes or objects when something of interest occurs.
- Syntax
- [Attributes] [Modifiers] EVENT<idName>
- [AS <idType>] [<idConvention>]CRLF
- [
- [ REMOVE <Expression> ] [ADD <Expression>]
- | [ ADD <Body > END ADD]
- | [ ADD => <expression>]
- | [REMOVE <Body > END REMOVE]
- | [REMOVE => <expression>]
- END EVENT
- ]
- Arguments
-
- <idName>A valid identifier name for the event that you are defining. Like other methods, events are entities. Event names must be unique within a class, but can share the same name as other entities in your application.
-
-
-
-
-
-
- Description
-
- There are three types of event declarations:
-
-
Single line declaration without ADD / REMOVE accessors;
-
Single line declaration with ADD / REMOVE accessors;
-
Multi-line declaration with ADD accessor block and/or REMOVE accessor bock.
-
- See Also
- ASSIGN, CLASS, METHOD
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_EXIT.xml b/docs/Help_Spanish/Topics/command_EXIT.xml
deleted file mode 100644
index bb6eeb8fa1..0000000000
--- a/docs/Help_Spanish/Topics/command_EXIT.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- EXIT Statement
-
- EXIT statement
-
-
-
- EXIT Statement
-
- Purpose
- Unconditionally branches control from within a FOR, FOREACH , REPEAT or DO WHILE statement to the statement immediately following the corresponding ENDDO or NEXT statement.
- Syntax
- EXIT
- Remarks
- The EXIT statement is only valid within a DO WHILE, FOR ... NEXT, FOREACH .. NEXT or REPEAT .. UNTIL construct. An EXIT statement outside of either construct will raise a compile time error.
- See Also FOR FOREACH DO WHILE REPEAT UNTIL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_EXTERNAL.xml b/docs/Help_Spanish/Topics/command_EXTERNAL.xml
deleted file mode 100644
index 0f69abde88..0000000000
--- a/docs/Help_Spanish/Topics/command_EXTERNAL.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- EXTERNAL Command
-
- Compiledeclaration
- Declaration statements
- EXTERNAL statement
- Program control
- Statements
-
-
-
- EXTERNAL Command
-
-
-
- Purpose
- Declares a list of routines (procedures or functions) to be linked into the application.
- Syntax
- EXTERNAL <idRoutineList>
- Arguments
- <idRoutineList>A comma-separated list of routine names to link. The names should not include parentheses.
- Description
- EXTERNAL is a declaration statement that specifies one or more routines to be linked into the application. It should be placed after the variable declaration statements (such as LOCAL).
-
- During the compilation of X# source code, all explicit references to routines are automatically linked. In some instances, however, there can be no references made to a routine until runtime. EXTERNAL resolves this by forcing the named routines to be linked even if they are not explicitly referenced in the source code. This is important in several instances:
-
-
Routines referenced in macro expressions or variables
-
Functions used in index keys and not otherwise referenced in the source code
-
-
- Examples
- This example forces the code for HardCR(), Tone(), MemoTran(), and StrTran() to be linked into the application, regardless of whether these functions are referenced explicitly in the source code:
-
- EXTERNAL HardCR, Tone, MemoTran, StrTran
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_FIELD.xml b/docs/Help_Spanish/Topics/command_FIELD.xml
deleted file mode 100644
index 7c0767b0be..0000000000
--- a/docs/Help_Spanish/Topics/command_FIELD.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- FIELD Statement
-
- Compiledeclaration
- Databases
- Declaration statements
- FIELD statement
- Statements
- Variable declaration
-
-
-
- FIELD Statement
-
- Purpose
- Declares one or more database field names to be used by the current routine.
- Syntax
- FIELD <idFieldList> [IN <idAlias>]
- Arguments
- <idFieldList>A list of names to declare as fields to the compiler.
-
- IN <idAlias>An alias to assume when there are unaliased references to the names specified in the <idFieldList>.
- Description
- When you use the FIELD statement to declare fields, unaliased references to variables in <idFieldList> are treated as if they were preceded by the special field alias (_FIELD->) or <idAlias>-> if the IN clause is specified.
-
- Like other variable declaration statements (i.e., LOCAL and MEMVAR), you must place FIELD statements before any executable statements (including PRIVATE, PUBLIC, and PARAMETERS) in the routine you are defining. The FIELD statement has no effect on the macro operator, which always assumes memory variables.
-
- The FIELD statement neither opens a database file nor verifies the existence of the specified fields. It is useful primarily to ensure correct references to fields that are known to exist at runtime. Attempting to access the fields when the associated database is not in use will raise a runtime error.
- Examples
- This function includes statements to declare database field names in both the current and Employee work areas:
-
- FUNCTION DisplayRecord() FIELD CustNo, OrderNo, Orders FIELD EmpName, EmpCode IN Employee USE employee NEW USE orders NEW ? CustNo// Refers to Orders->CustNo ? EmpName// Refers to Employee->EmpName CLOSE orders CLOSE employee
- See Also
- DBFieldInfo(), LOCAL, MEMVAR, STATIC
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_FIND.xml b/docs/Help_Spanish/Topics/command_FIND.xml
deleted file mode 100644
index 3136a8a1c9..0000000000
--- a/docs/Help_Spanish/Topics/command_FIND.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- FIND Command
-
- Commands
- Databases
- FIND command
- Index/order
-
-
-
- FIND Command
-
-
- Purpose
- Search an order for the first key matching the specified string, position the record pointer to the corresponding record, and set the Found() flag.
-
- Note:FIND is a compatibility command and is no longer recommended. It is superseded by SEEK. See SEEK for more information.
- Syntax
- FIND <xcKeyValue>
- Arguments
- <xcKeyValue>Part or all of the order key of a record to search for. When an expression is specified instead of a literal string, FIND is equivalent to SEEK.
- Description
- If SetSoftSeek() is FALSE and FIND does not find a record, the record pointer is positioned to LastRec() + 1, EOF() returns TRUE, and Found() returns FALSE.
-
- If SetSoftSeek() is TRUE and FIND does not find a record, the record pointer is positioned to the record with the next greater key value, and Found() returns FALSE. In this case, EOF() returns TRUE only if there are no keys in the index greater than the search argument.
-
- If the record is found, Found() is set to TRUE and the record pointer is positioned on the found record.
- Examples
- These examples show simple FIND results:
-
- USE sales INDEX branch NEW FIND ("500") ? Found(),EOF(),RECNO()// Result: FALSE TRUE 85 FIND 200 ? Found(),EOF(),RECNO()// Result: TRUE FALSE 5 FIND "100" ? Found(),EOF(),RECNO()// Result: TRUE FALSE 1
-
- See Also
- EoF(),Found(), RecNo(), SEEK, SET INDEX, SET ORDER, SetSoftSeek()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_FOR.xml b/docs/Help_Spanish/Topics/command_FOR.xml
deleted file mode 100644
index a48ad54b7f..0000000000
--- a/docs/Help_Spanish/Topics/command_FOR.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-
-
-
- FOR Statement
-
- Branching
- Conditional execution
- EXIT statement
- FOR statement
- LOOP statement
- NEXT statement
- Program control
- Statements
-
-
-
- FOR Statement
-
- Purpose
- Executes a block of statements a specified number of times.
- Syntax
- FOR [<idCounter> := <nStart> | VAR <idCounter> := <nStart> | LOCAL <idCounter> := <nStart> AS <idType> ] [TO | UPTO | DOWNTO] <nEnd> [STEP <nDelta>] <Statements>... [EXIT] <Statements>... [LOOP] NEXT
- Note
- In the FoxPro and Xbase++ dialect, ENDFOR is allowed as alternative for NEXT
- Arguments
- <idCounter>The name of the loop control or counter variable. IF a LOCAL or VAR clause is included, the local is created for the duration of the loop. With the VAR clause, the datatype is inferred from the usage.
-
-
- <nStart>The initial value assigned to <idCounter>. If the loop is counting up, <nStart> must be less than <nEnd>. If the loop is counting down, <nStart> must be greater than <nEnd>.
-
- TO <nEnd>The final value of <idCounter>. The TO clause can be used for counting up or down, depending on whether the STEP clause gives a positive or negative value for <nDelta>. Note, however, that your code will be more efficient if you avoid the TO clause and specify UPTO or DOWNTO instead.
-
- UPTO <nEnd>The final value of <idCounter>. The UPTO clause is used for counting up.
-
- DOWNTO <nEnd>The final value of <idCounter>. The DOWNTO clause is used for counting down.
-
- STEP <nDelta>The amount <idCounter> is changed for each iteration of the loop. If used with the TO clause, <nDelta> can be either positive or negative. With UPTO and DOWNTO, <nDelta> should be positive. If the STEP clause is not specified, <idCounter> is incremented (or decremented in the case of DOWNTO) by one for each iteration of the loop.
-
-
- Description
- The control structure loops from the initial value of <idCounter> to the boundary specified by <nEnd>, moving through the range of values of the control variable for an increment specified by <nDelta>. All expressions in the FOR statement are re-evaluated for each iteration of the loop. The <nStart> and <nEnd> values, therefore, can be changed as the control structure operates.
-
- A FOR loop operates until <idCounter> is greater than or less than <nEnd> (depending on whether you are counting up or down) or an EXIT statement is encountered. Control then branches to the statement following the corresponding NEXT statement. If a LOOP statement is encountered, control branches back to the current FOR statement.
- Control structures can be nested to any depth. The only requirement is that each control structure be properly nested.
-
- Tip: Although FOR loops are useful for traversing arrays (as demonstrated in the examples below), your code will be more efficient if there is a corresponding array function designed to do what you want.
- Examples
- This example traverses an array in ascending order:
-
- nLenArray := ALen(aArray) FOR i := 1 UPTO nLenArray <Statements>... NEXT
-
- To traverse an array in descending order:
-
- nLenArray := ALen(aArray) FOR i := nLenArray DOWNTO 1 <Statements>... NEXT
- See Also
- AEval(), BEGIN SEQUENCE, DO CASE, DO WHILE, IF, EXIT, LOOP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_FOREACH.xml b/docs/Help_Spanish/Topics/command_FOREACH.xml
deleted file mode 100644
index 2d3e96902b..0000000000
--- a/docs/Help_Spanish/Topics/command_FOREACH.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- FOREACH Statement
-
- Branching
- Conditional execution
- EXIT statement
- FOREACH statement
- LOOP statement
- NEXT statement
- Program control
- Statements
-
-
-
- FOREACH Statement
-
- Purpose
- Executes a block of statements for all elements in a collection.
- Syntax
- FOREACH [IMPLIED <idElement> | VAR <idElement> | <idElement> AS <idType>] IN <container> <Statements>... [EXIT] <Statements>... [LOOP] NEXT
- Note
- In the FoxPro dialect, FOR EACH is also allowed as two separate words.
- In the FoxPro and Xbase++ dialect, ENDFOR is allowed as an alternative for NEXT.
- Arguments
- <idElement>The name of the variable that will receive the values of the elements in <container> When the IMPLIED or VAR clause is used, the datatype of the variable is inferred from the container. When the AS <idType> clause is used, this will be the datatype of the variable.
-
-
- <container>A DotNet object that supports IEnumerable(), such as a XBase array, .Net array or a collection like List<>.
-
-
- Description
- The FOREACH statement is a convenient way to enumerate variable in an array or collection.
- Preferably, the iteration variable should not be changed inside the loop. A compiler warning will be shown when you do this.
- It is also not recommended to change the container in the loop as this may often result in a runtime error.
- See Also
- AEval(), BEGIN SEQUENCE, DO CASE, DO WHILE, IF, EXIT, LOOP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_FUNCTION.xml b/docs/Help_Spanish/Topics/command_FUNCTION.xml
deleted file mode 100644
index a2bf240a87..0000000000
--- a/docs/Help_Spanish/Topics/command_FUNCTION.xml
+++ /dev/null
@@ -1,122 +0,0 @@
-
-
-
- FUNCTION Statement
-
- Compiledeclaration
- Declaration statements
- Entity declaration
- FUNCTION
- FUNCTION statement
- Statements
- STATIC FUNCTION statement
- Strong typingdefined
-
-
-
- FUNCTION Statement
-
- Purpose
- Declare a function name and an optional list of local variable names to the compiler. When used inside a FoxPro DEFINE CLASS .. ENDDEFINE this declares a method.
- Syntax
- [Attributes] [Modifiers] FUNCTION <idFunction>
- [Typeparameters]
- [([<idParam> [AS | REF|OUT|IN <idType>] [, ...])]
- [AS <idType>]
- [TypeparameterConstraints]
- [<idConvention>]
- [EXPORT LOCAL]
- [DLLEXPORT STRING_CONST]
- [=> <expression>]
- CRLF
- [<Body>]
- [ENDFUNC | END FUNCTION]
- Arguments
-
-
- Please note that functions and procedures used as class members in FoxPro compatible classes can have more modifiers.
-
- <idFunction>A valid identifier name for the function. A function is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a function and a class, for example, with the same name.
-
-
-
-
- ENDFUNC | END FUNCTIONThese (optional) keywords indicate the logical end of the function.
- Description
- A function is a subprogram comprised of a set of declarations and statements to be executed whenever you refer to <idFunction>, followed by a pair of parentheses (see Notes section, below).
-
- Functions and procedures (see the PROCEDURE statement in this guide) are the basic procedural programming units. You will use them in your applications to organize computational blocks of code.
-
- STATIC FUNCTION allows you to limit the visibility of a function name to the current module, thereby restricting access to the function. This feature is useful when designing a module that will contain some public routines (i.e., with application-wide visibility) and others that are strictly support routines (i.e., only needed by other routines in the same module).
-
- Simply declare all support functions using STATIC FUNCTION. Doing this gives you two immediate advantages. First, no other module in the application will inadvertently call one of your support routines. Second, since static references are resolved at compile time and public references are resolved at link time, there is no possibility of a name conflict. For example, if you have a static Service() function declared in module X and a public Service() function declared in module Y, all references to Service() in X execute the static version and all other references to Service() in the application execute the public version.
- Notes
- The Start() function: All applications must either have one function or procedure named Start(). FUNCTION Start() serves as the start-up routine when the application is executed. Start() must be declared without parameters or with an string array parameter and must either have an Int return value or of type Void.
-
- Exporting locals through code blocks: When you create a code block, you can access local variables defined in the creating entity within the code block definition without having to pass them as parameters (i.e., local variables are visible to the code block). Using this fact along with the fact that you can pass a code block as a parameter, you can export local variables. For example:
-
- FUNCTION One()EXPORTLOCAL LOCAL nVar :=10ASINT, cbAdd ASCODEBLOCK cbAdd :={|nValue| nValue + nVar} ? NextFunc(cbAdd)// Result: 210
FUNCTION NextFunc(cbAddEmUp) RETURN(EVAL(cbAddEmUp,200))
-
- When the code block is evaluated in NextFunc(), nVar, which is local to function One(), becomes visible, even though it is not passed directly as a parameter.
-
- Calling a function:The syntax to call a function is as follows:
-
- <idFunction>([<uArgList>])
-
- where <uArgList> is an optional comma-separated list of arguments to pass to the named function. The function receives the arguments in the order passed using the parameter variables specified as part of the function declaration.
- Note that, although the parentheses are not required in the FUNCTION statement, if the function has no parameters, they are always required in the invocation.
-
- You can call a function within an expression or as a program statement. If called as a program statement, the return value is ignored.
-
- You can also call a function as an aliased expression, as in:
- <idAlias>-><idFunction>([<uArgList>])
- When you do this, the work area associated with <idAlias> is selected, the function is executed, and the original work area is reselected. You can specify an aliased expression as a program statement, as you would any other expression.
-
- A function can call itself recursively. This means you can refer to a function in its own <FunctionBody>.
- The specific manner in which you call a function depends on the calling convention (<idConvention>) that you specify (either explicitly or implicitly) when you declare the function.
-
- CLIPPER calling convention: If you declare the function without any data types in the parameter list, the function uses the CLIPPER calling convention by default. You can also specify the CLIPPER calling convention in the FUNCTION declaration statement, providing that you do not use strong typing in the parameter list.
- Although it does not allow strongly typed parameters, the CLIPPER calling convention supports strong typing of the function return value.
-
- With the CLIPPER calling convention, the number of parameters declared for the function does not have to match the number of arguments passed when you call the function. You can skip any argument by leaving it out of the list (specifying two consecutive commas), or by omitting it from the end of the list. For example:
-
- FUNCTION Start() MyFunc(1,,3)// Skip second argument MyFunc(1,2)// Skip final argument
FUNCTION MyFunc(x, y, z)
- ...
-
- A parameter not receiving a value is automatically initialized to NIL by the function so that you can check for skipped arguments. You can use PCount() to help determine the number of arguments passed — this function returns the position of the last argument passed.
-
- Any parameter specified in a CLIPPER function can receive arguments passed by value or reference — the semantics are determined when the function is called rather than when it is declared. The default method for expressions and variables is by value. All variables except field variables, when prefaced with the reference operator (@), are passed by reference. Field variables cannot be passed by reference and are always passed by value.
-
- STRICT calling convention: If you declare the function with any data types in the parameter list, the function uses the STRICT calling convention by default. You can also specify the STRICT calling convention in the FUNCTION declaration statement.
-
- Using the STRICT calling convention, you give up many of the features allowed with the CLIPPER calling convention, but you gain in compilation speed, application integrity, and execution speed by strongly typing the parameters and return value and declaring the passing semantics of the function.
-
- STRICT functions do not support a variable number of arguments, PCount(), or the ability to be used in macro expressions.
-
- Like CLIPPER functions, STRICT functions allow the calling semantics to be determined when the function is called, but only for polymorphic parameters (i.e., those not strongly typed). When a parameter is typed, the calling semantics are also declared depending on whether you use the AS or the REF keyword. AS means that the parameter must be passed by value and REF means that it must be passed by reference (with the reference operator (@)).
-
- PASCAL calling convention: To specify this calling convention, use PASCAL as the last keyword in the FUNCTION declaration statement. Syntactically, the PASCAL calling convention is identical to STRICT and the usage restrictions are the same, but internally it is handled differently. It is identical to the Microsoft Pascal calling convention, and its primary use is for low-level interfacing with Windows.
-
- CALLBACK calling convention: To specify this calling convention, use CALLBACK as the last keyword in the FUNCTION declaration statement. This is a special PASCAL calling convention with Windows prologue and epilogue. It is used for low-level interfacing with Windows.
-
- Parameters: As an alternative to specifying parameters in the FUNCTION declaration statement, you can use a PARAMETERS statement to specify them. This practice, however, is not recommended, because it is less efficient and provides no compile-time integrity validation. See the PARAMETERS statement in this guide for more information.
- Examples
- This example demonstrates a function that formats numeric values as currency:
-
- FUNCTION Start() ? Currency(1000)// Result: $1,000.00
FUNCTION Currency(nNum) LOCAL cNum IF nNum < 0 cNum := Transform(-1* nNum,; "999,999,999,999.99") cNum := PadL("($"+LTRIM(cNum)+")",; LEN(cNum)) ELSE cNum := Transform(nNum,; "999,999,999,999.99") cNum := PadL("$"+LTRIM(cNum),; LEN(cNum)) ENDIF RETURN cNum
-
- The next example demonstrates a function that takes a string formatted as a comma-separated list and returns an array with one element per item:
-
- aList := ListAsArray("One, Two") // Result: {"One", "Two"}
FUNCTION ListAsArray(cList) LOCAL nPos LOCAL aList :={}// Define an empty array DOWHILE(nPos :=AT(",", cList))!=0 // Add a new element AADD(aList,SUBSTR(cList,1, nPos -1)) cList :=SUBSTR(cList, nPos +1) ENDDO AADD(aList, cList) RETURN aList// Return the array
- This example checks for a skipped argument by comparing the parameter to NIL:
-
- FUNCTION MyFunc(param1,param2,param3) IF param2 =NIL param2 :="default value" ENDIF...
-
- Here the Currency() function (defined above) is used as an aliased expression:
-
- USE invoices NEW USE customer NEW ? Invoices->Currency(Amount)
- See Also
- FIELD, LOCAL, MEMVAR, METHOD, PROCEDURE, RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_Fox_AddObject.xml b/docs/Help_Spanish/Topics/command_Fox_AddObject.xml
deleted file mode 100644
index a1fb3d9a4e..0000000000
--- a/docs/Help_Spanish/Topics/command_Fox_AddObject.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- ADD OBJECT Clause
-
- ADD OBJECT
-
-
-
- FoxPro ADD OBJECT Clause
-
-
- Purpose
- Adds objects from other classes to the class definition.
- Syntax
- ADD OBJECT [Modifiers] <ObjectName> AS <idType> [NOINIT] [WITH <Propertylist>]]
- Arguments
- ModifiersAn optional list of modifiers that specify the visibility or scope of the entity, such as PUBLIC, PROTECTED, HIDDEN, INTERNAL.
-
- <ObjectName>A valid identifier name for the fields or properties to declare.
-
-
- NOINITThis clause is not supported.
-
- WITH <PropertyList>Specifies a list of properties and their values for the object that you add to the class definition.
-
- The object will be instantiated and added to the list of "child objects" in the class. Also, a property will be created with the name and type specified in the ADD OBJECT clause.
- Notes
- The way in which properties are implemented depends on the value of the /fox1 compiler switch. When this switch is enabled, then all properties will read/write from a property collection that is declared in the Custom Object. When this switch is NOT enabled, then 'normal' auto properties will be declared with a backing field in this class.
-
-
diff --git a/docs/Help_Spanish/Topics/command_Fox_CommAttrib.xml b/docs/Help_Spanish/Topics/command_Fox_CommAttrib.xml
deleted file mode 100644
index beece901fa..0000000000
--- a/docs/Help_Spanish/Topics/command_Fox_CommAttrib.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- Class Members
-
-
- FoxPro COMAttrib clause
-
-
- Purpose
- Declare COM attributes (not supported).
- Syntax
- PEMName_COMATTRIB = nFlags | DIMENSION PEMName_COMATTRIB[numElements]
- [PEMName_COMATTRIB[1] = nFlags
- PEMName_COMATTRIB[2] = cHelpString
- PEMName_COMATTRIB[3] = cPropertyCapitalization
- PEMName_COMATTRIB[4] = cPropertyType
- PEMName_COMATTRIB[5] = nOptionalParams]]
-
- This clause is not supported in X#.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_Fox_FunctionProcedure.xml b/docs/Help_Spanish/Topics/command_Fox_FunctionProcedure.xml
deleted file mode 100644
index 0c8a10c77f..0000000000
--- a/docs/Help_Spanish/Topics/command_Fox_FunctionProcedure.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
- FUNCTION and PROCEDURE
-
- _ACCESS
- _ASSIGN
- ENDFUNC
- ENDPROC
- FUNCTION
- HELPSTRING
- NODEFAULT
- PROCEDURE
- THIS_ACCESS
-
-
-
- FoxPro FUNCTION and PROCEDURE definition clauses
-
-
- Purpose
- Defines method and event functions and procedures for the class definition.
- Syntax
- [Modifiers] FUNCTION | PROCEDURE Name[_ACCESS |_ASSIGN]
- ([cParamName | cArrayName[] [AS Type][@]]) [AS Type]
- [HELPSTRING cHelpString] | THIS_ACCESS(cMemberName) [NODEFAULT]
- cStatements
- [ENDFUNC | ENDPROC]]
-
- See the topics for FUNCTION and PROCEDURE for more details.
- Arguments
- _ACCESSThe _ACCESS or _ASSIGN suffixes specify to create an Access or Assign method for a property with the same name.
- _ASSIGN
-
- HELPSTRINGThe HELPSTRING clause is not supported in X#.
-
- THIS_ACCESSThe THIS_ACCESS clause is not supported in X#.
-
- NODEFAULTThe NODEFAULT clause is not supported in X#.
-
- ENDFUNC This may also be written as END FUNCTION.
-
- ENDPROC This may also be written as END PROCEDURE.
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_Fox_Implements.xml b/docs/Help_Spanish/Topics/command_Fox_Implements.xml
deleted file mode 100644
index 7c2e456a7b..0000000000
--- a/docs/Help_Spanish/Topics/command_Fox_Implements.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- IMPLEMENTS clause
-
- EXCLUDE
- IMPLEMENTS
- IN TypeLib
-
-
-
- FoxPro IMPLEMENTS clause
-
-
- Purpose
- Declare an interface that the clause implements.
- Syntax
-
- IMPLEMENTS <idInterface> [EXCLUDE] IN TypeLib | TypeLibGUID | ProgID ]
- Arguments
-
- IMPLEMENTS <idInterface>The name(s) of the interface(s) that this class implements.
-
- EXCLUDEThis clause is not supported.
-
- IN [Typelib etc]This clause is not supported.
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_Fox_Properties.xml b/docs/Help_Spanish/Topics/command_Fox_Properties.xml
deleted file mode 100644
index 95f4f53811..0000000000
--- a/docs/Help_Spanish/Topics/command_Fox_Properties.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- Properties and Fields
-
-
- Properties and Fields (FoxPro class syntax)
-
-
- Purpose
- Declare fields and/or properties with optional initial values.
- Syntax
- [FIELD] [modifiers] <IdName>, <IdName> ...] [AS <idType>]
- [[.]Object.] <IdName> = <Expression> ...]
-
- Both syntaxes to declare and/or initialize properties are supported.
- We have added an optional AS DataType clause. We have also added an optional FIELD clause that allows you to declare fields (opposed to properties).
- Arguments
-
- FIELD When you include the FIELD keyword, the names will be the names of fields in the class.
-
- ModifiersAn optional list of modifiers that specify the visibility or scope of the property, such as PUBLIC,. PROTECTED, HIDDEN.
-
- <IdName>A valid identifier name for the fields or properties to declare.
-
-
- ExpressionThe initial value to assign to the field/property.
- Notes
-
- The way in which properties are implemented depends on the value of the /fox1 compiler switch. When this switch is enabled, then all properties will read/write from a property collection that is declared in the Custom Object. When this switch is NOT enabled, then 'normal' auto properties will be declared with a backing field in this class.
-
-
diff --git a/docs/Help_Spanish/Topics/command_GLOBAL.xml b/docs/Help_Spanish/Topics/command_GLOBAL.xml
deleted file mode 100644
index 007d3a989b..0000000000
--- a/docs/Help_Spanish/Topics/command_GLOBAL.xml
+++ /dev/null
@@ -1,68 +0,0 @@
-
-
-
- GLOBAL Statement
-
- Arraysdeclaring
- Compiledeclaration
- Declaration statements
- GLOBAL
- GLOBAL statement
- Statements
- STATIC GLOBAL statement
-
-
-
- GLOBAL Statement
-
- Purpose
- Declare a variable or array that is available to the entire application or module.
- Syntax
- [Modifiers] GLOBAL <idVar> [:= <uValue>] [AS | IS <idType>]
- [Modifiers] GLOBAL DIM <ArraySpec> AS | IS <idType>
- Arguments
-
- <idVar>A valid identifier name for the variable. A global variable is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a global variable and a function, for example, with the same name.
-
- <uValue>A constant value that is assigned to <idVar>. This value can be a literal representation of one of the data types listed below or a simple expression involving only operators, literals, and DEFINE constants; however, more complicated expressions (including class instantiation) are not allowed.
-
- Note: Although <uValue> can be a literal array, it must be one-dimensional. Multi-dimensional literal arrays are not allowed. For example, {1, 2, 3} is allowed, but { {1, 2, 3}, {4, 5, 6}, {7, 8, 9} } is not.
-
- Note: Although the Chr() function cannot be used in <uValue>, the _Chr() operator can. _Chr() is otherwise identical in functionality to Chr().
-
- If <uValue> is not specified, the initial value of the variable depends on the data type you declare (e.g., NIL if you do not use strong typing, 0 for AS INT, etc.).
-
-
- DIM <ArraySpec>The specification for a dimensioned array to declare.
-
- <ArraySpec>The specification for a dynamic array to declare.
-
- In both cases, <ArraySpec> is one of the following:
-
- <idArray>[<nElements>, <nElements>, <nElements>]
- <idArray>[<nElements>][<nElements>][<nElements>]
- All dimensions except the first are optional.
-
- <idArray> is a valid identifier name for the array to declare. For dynamic arrays, array elements are initialized to NIL. For dimensioned arrays, the initial value of the elements depends on the data type as explained above for <uValue>.
-
- <nElements> defines the number of elements in a particular dimension of an array. The number of dimensions is determined by how many <nElements> arguments you specify.
-
- <nElements> can be a literal numeric representation or a simple numeric expression involving only operators, literals, and DEFINE constants; however, more complicated expressions (such as function calls) are not allowed.
-
-
-
-
- Notes
- Search order for variables: You can hide a global variable name from a routine by declaring another variable with the same name (with LOCAL, MEMVAR, or FIELD). The search order for a variable name is as follows:
- 1.LOCALs, local parameters, MEMVARs, and FIELDs.
- 2.SELF instance variables (i.e., without <idObject>: prefix in class methods).
- 3.GLOBALs and DEFINEs.
- Examples
- The following example illustrates using the GLOBAL statement to create a global variable, a global dimensioned array, and a global dynamic array. The dynamic array, since it is declared with STATIC GLOBAL, is visible only in the current module:
-
- GLOBAL cAppName :="Accounts Payable"ASSTRING GLOBALDIM aiValues[2][10]ASINT STATICGLOBAL aPoly[100] ... FUNCTION Start() ?"Start of ", cAppName," application." AFill(aPoly,0) ... ?"End of ", cAppName," application."
- See Also
- DEFINE, LOCAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_GO.xml b/docs/Help_Spanish/Topics/command_GO.xml
deleted file mode 100644
index 7298c631d7..0000000000
--- a/docs/Help_Spanish/Topics/command_GO.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- GO Command
-
- Commands
- Databases
- Findingspecific records
- GO BOTTOM command
- GO command
- GO TOP command
- GOTO command
- Recordspointing to
-
-
-
- GO Command
-
-
- Purpose
- Move the pointer to the specified record.
- Syntax
- GO[TO] <uRecID> | TOP | BOTTOM [[IN|ALIAS] <workarea>]
- Arguments
- <uRecID>The record to go to. The data type and interpretation of <uRecID> is determined by the RDD. For .DBF files, it is the record number. If <uRecID> does not exist, the work area is positioned to LastRec() + 1, and both EoF() and BoF() return TRUE.
-
- TOPSpecifies the first logical record in the current work area.
-
- BOTTOMSpecifies the last logical record in the current work area.
-
-
- Notes
- Visibility:Even though a particular record may not be visible (because, for example, of DbSetFilter(), SetDeleted(TRUE), or a conditional controlling order), you can still go to that record.
- Examples
- This example saves the current record number, searches for a key, then restores the record pointer to the saved position:
-
- FUNCTION KeyExists(uKeyExpr) LOCAL nSavRecord :=RECNO() // Save the current record pointer position LOCAL lFound
GOTO nSavRecord// Restore the record pointer // position
RETURN lFound
-
- See Also
- DbGoTo(), DbSetFilter(), DBSetRelation(), LastRec(), RecNo(), SetDeleted() , SET RELATION, SKIP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_IF.xml b/docs/Help_Spanish/Topics/command_IF.xml
deleted file mode 100644
index f70fb8f412..0000000000
--- a/docs/Help_Spanish/Topics/command_IF.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- IF Statement
-
- Branching
- Conditional execution
- ELSE statement
- ELSEIF statement
- END statement
- ENDIF statement
- IF statement
- Program control
- Statements
-
-
-
- IF Statement
-
- Purpose
- Conditionally executes a block of statements.
- Syntax
- IF <lCondition> [THEN] <Statements>... [ELSEIF <lCondition>] <Statements>... [ELSE] <Statements>... END[IF]
- Arguments
- [THEN]The THEN keyword is optional and has been added because Visual FoxPro allows this keyword.
-
- <lCondition>If this expression evaluates to TRUE, the statements following it up until the next ELSEIF, ELSE, or ENDIF are executed. Afterward, control branches to the statement following the next ENDIF statement.
-
- ELSEIf all preceding IF and ELSEIF conditions evaluate to FALSE, the statements following the ELSE up until the next ENDIF are executed. Afterward, control branches to the statement following the next ENDIF statement.
- Description
- IF works by branching to the statement following the first <lCondition> that evaluates to TRUE. If all conditions evaluate to FALSE, it branches to the statement following the ELSE statement (if specified). Execution proceeds until the next ELSEIF, ELSE, or ENDIF is encountered, and control then branches to the first statement following the next ENDIF statement.
-
- Control structures can be nested to any depth. The only requirement is that each control structure be properly nested.
-
- Note: IF...ELSEIF...ENDIF is identical to DO CASE...ENDCASE, with neither syntax having a performance advantage over the other. The IF construct is also similar to the IIf() operator which can be used within expressions.
- Examples
- This example evaluates a number of conditions using an IF...ELSEIF...ENDIF construct:
-
- LOCAL nNumber := 0
IF nNumber < 50 ? "Less than 50" ELSEIF nNumber = 50 ? "Is equal to 50" ELSE ? "Greater than 50" ENDIF
- See Also
- BEGIN SEQUENCE, DO CASE, DO WHILE, FOR, IIf()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_IFDEF.xml b/docs/Help_Spanish/Topics/command_IFDEF.xml
deleted file mode 100644
index e081580583..0000000000
--- a/docs/Help_Spanish/Topics/command_IFDEF.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- #ifdef Statement
-
- #else statement
- #endif statement
- #ifdef statement
- Buildingcode
- Codebuilding
- Program control
- Statements
-
-
-
- #ifdef Statement
-
- Purpose
- Builds a section of code if a constant exists that is not equal to FALSE or 0.
-
- Syntax
- #ifdef <idConstant> <Statements>... [#else] <Statements>... #endif
- Arguments
- <idConstant>The name of a constant whose existence is being verified.
-
- Description
- #ifdef...#endif lets you perform a conditional build by identifying a section of source code to include if a specified constant exists and is not equal to FALSE or 0. The #else statement specifies the code to include if the #ifdef condition fails, and the #endif terminates the conditional build block.
- Note: You can use #ifdef with compiler entities other than constants, such as functions and globals. In these cases, the statement tests for existence only, and does not look at the value of the entity.
-
- Examples
- This code fragment is a general skeleton for a conditional build with #ifdef. Because the lDemo constant is defined as TRUE, the code between the #ifdef and #endif statements will be built:
-
- DEFINE lDemo :=TRUE FUNCTION Start() #IFDEF lDemo <Demo-specific statements>... #ENDIF ...
- To build the real (non-demo) version of this application, you would change the DEFINE statement to:
- DEFINE lDemo :=FALSE
-
- See Also
- #ifndef, DEFINE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_IFNDEF.xml b/docs/Help_Spanish/Topics/command_IFNDEF.xml
deleted file mode 100644
index 30c3178a73..0000000000
--- a/docs/Help_Spanish/Topics/command_IFNDEF.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- #ifndef Statement
-
- #else statement
- #endif statement
- #ifndef statement
- Buildingcode
- Codebuilding
- Program control
- Statements
-
-
-
- #ifndef Statement
-
- Purpose
- Builds a section of code if a constant is FALSE, 0, or not defined.
- Syntax
- #ifndef <idConstant> <Statements>... [#else] <Statements>... #endif
- Arguments
- <idConstant>The name of a constant whose absence is being verified.
- Description
- #ifndef...#endif lets you perform a conditional build by identifying a section of source code to include if a specified constant is defined as FALSE, 0 or is not defined. The #else statement specifies the code to include if the #ifndef condition fails, and the #endif terminates the conditional build block.
- Note: You can use #ifndef with compiler entities other than constants, such as functions and globals. In these cases, the statement tests for existence only, and does not look at the value of the entity.
-
- Examples
- This code fragment is a general skeleton for a conditional build with #ifndef. Since the constant lDebug is set to FALSE, the code between the #ifndef and #else statements will be built, and the code between the #else and #endif statements will be ignored:
-
- DEFINE lDebug :=FALSE
FUNCTION Start() #IFNDEF lDebug <Optimized version OF code>... #ELSE <Debugging version OF code>... #ENDIF
-
- Changing the DEFINE statement as follows will build the code between the #else and #endif statements instead.
- DEFINE lDebug :=TRUE
- See Also
- #ifdef, DEFINE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_INDEX.xml b/docs/Help_Spanish/Topics/command_INDEX.xml
deleted file mode 100644
index 888a54c8e6..0000000000
--- a/docs/Help_Spanish/Topics/command_INDEX.xml
+++ /dev/null
@@ -1,101 +0,0 @@
-
-
-
- INDEX Command
-
- Commands
- Creatingfiles
- Databases
- Filescreating
- INDEX command
- Index filescreating
- Index/order
- Orderscreating
-
-
-
- INDEX Command
-
-
- Purpose
- Create an index file and add an order to it.
- Syntax
- INDEX ON <uKeyValue> [TAG <xcOrder>] [TO <xcIndexFile>] [<Scope>] [WHILE <lCondition>] [FOR <lCondition>] [EVAL <cbEval> [EVERY <nInterval>] [UNIQUE] [ASCENDING | DESCENDING] [USECURRENT] [ADDITIVE] [CUSTOM] [NOOPTIMIZE]
-
- Note: Although both the TAG and the TO clauses are optional, you must specify at least one of them.
- Arguments
- <uKeyValue>The order key expression. The data type of the key expression and all other limitations, including the length of the key and the key expression, are determined by the RDD.
-
- TAG <xcOrder>The name of the order to be created. For single-order index files, the default order name is the file name without an extension or path. For multiple-order index files, the order name is required.
-
- TO <xcIndexFile>The name of the target index file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension is determined by the RDD and can be obtained using DBOrderInfo(DBOI_INDEXEXT).
-
- In RDDs that support production indexes, the production index file is assumed if <xcIndexFile> is not specified.
-
- If <xcIndexFile> does not exist, it is created.
-
- If <xcIndexFile> exists, the INDEX command must first obtain exclusive use of the file. If the attempt is unsuccessful because, for example, the file is open by another process, NetErr() is set to TRUE.
-
- If the attempt is successful and the RDD specifies that index files can only contain a single order, the current contents of the file are erased before the new order is added to it. If the RDD specifies that index files can contain multiple orders, <xcOrder> is added to <xcIndexFile> if it does not already exist; otherwise it is replaced.
-
- <Scope>The portion of the current database file to process. The default scope is all records. INDEX ignores the DbSetFilter() and SetDeleted() settings, as well as any filter imposed by the current controlling order.
-
- The scope is not stored in the index file and is not used for re-indexing or update purposes.
-
- WHILE <lCondition>A condition that each record within the scope must meet, starting with the current record. As soon as the while condition fails, the process terminates. If no <Scope> is specified, having a while condition changes the default scope to the rest of the records in the file.
-
- The while condition is not stored in the index file and is not used for re-indexing or update purposes.
-
- FOR <lCondition>A condition that each record within the scope must meet in order to be processed. If a record does not meet the specified condition, it is ignored and the next record is processed. Duplicate key values are not added to the index file when a for condition is used.
-
- Unlike the while condition and the scope, the for condition is stored as part of the index file and is used when updating or rebuilding the order with DbReindex() or REINDEX. Any limitations on the for condition are determined by the RDD.
-
- Note: If no <Scope>, while condition, or for condition is specified, the index uses the condition specified by DBSetOrderCondition(), if any.
-
- EVAL <cbEval>A code block that is evaluated at intervals specified by EVERY <nInterval>. The default interval is 1. This is useful in producing a status bar or odometer that monitors the ordering progress. The return value of <cbEval> must be a logical value. If <cbEval> returns FALSE, indexing halts.
-
- EVERY <nInterval>A numeric expression that determines the number of times <cbEval> is evaluated. This option offers a performance enhancement by evaluating the condition at intervals instead of for every record processed. The EVERY keyword is ignored if you specify no EVAL clause.
-
- UNIQUECreates the order with uniqueness as an attribute, which means that only those records with unique key values will be included in the order. If UNIQUE is not specified, SetUnique() is used to determine the order's uniqueness attribute (refer to SetUnique() for more information on how unique orders are maintained). Note that keys from deleted records are also included in the index, and may hide keys from non-deleted records.
-
- ASCENDINGSpecifies that the keys should be sorted in increasing order. If neither ASCENDING nor DESCENDING is specified, ASCENDING is assumed.
-
- DESCENDINGSpecifies that the keys should be sorted in decreasing order. Using this keyword is the same as specifying the Descend() function within <uKeyValue>, but without the performance penalty during order updates. If you create a DESCENDING index, you will not need to use the Descend() function during a SEEK.
-
- Whether an order is ascending or descending is an attribute that is stored in the index file and used for re-indexing and update purposes.
-
- USECURRENTSpecifies that only records in the controlling order — and within the current range as specified by OrdSetScope() — will be included in this order. This is useful when you have already created a conditional order and want to reorder the records which meet that condition, and/or to further restrict the records meeting a condition. If not specified, all records in the database file are included in the order.
-
- ADDITIVESpecifies that any open orders should remain open. If not specified, all open orders are closed before creating the new one. Note, however, that the production index file is never closed.
-
- CUSTOMFor RDDs that support them, CUSTOM specifies that a custom built order will be created. A custom built order is initially empty, giving you complete control over order maintenance. The system does not automatically add and delete keys from a custom built order. Instead, you explicitly add and delete keys using OrdKeyAdd() and OrdKeyDel(). This capability is excellent for generating pick lists of specific records and other custom applications.
-
- NOOPTIMIZESpecifies that the FOR condition will be optimized. If NOOPTIMIZE is not specified, the FOR condition will be optimized if the RDD supports optimization.
- Description
- After it is created (or replaced), the new order is added to the order list for the work area. Other orders already associated with the work area, including the controlling order, are unaffected.
- If no order list exists for the work area, the type of RDD determines how the controlling order is set. For RDDs that support only single-order index files (such as DBFNTX), the controlling order is set to the order in the specified index file. For RDDs that support multi-order index files (such as DBFMDX), the controlling order is normally set to the first order in the index file.
- Notes
- RDD support: Not all RDDs support all aspects of the INDEX command.
- Examples
- The following example creates a single-order index based on the Acct field:
-
- USE customer NEW INDEXON Customer->Acct TO CuAcct
-
- This example creates a conditional order based on a for condition. This index will contain only records whose TransDate is greater than or equal to January 1, 1999:
-
- USE invoice NEW INDEXON Invoice->TransDate TO InDate ; FOR Invoice->TransDate >= CTOD("01/01/2020")
-
- The next example creates an order in a multiple-order index file:
-
- USE customer NEW VIA "DBFMDX" INDEXON Customer->Acct TAG CuAcct TO customer
-
- This example creates an order that calls a routine MyMeter() during its creation:
-
- DEFINE Mtr_Increment := 10
FUNCTION Start() USE customer NEW INDEXON Customer->Acct TO CuAcct EVAL ; {|| MyMeter() } EVERY Mtr_Increment
RETURN TRUE
-
-
- See Also
- CLOSE, DToS(), DBCreateIndex(), DbCreateOrder()DbOrderInfo(), DbSeek(), DbSetIndex(), DbSetOrder(), DbSetOrderCondition(), DbReindex(), OrdCondSet(), OrdKeyAdd()OrdKeyDel(), OrdScope(), REINDEX, SEEK, SET INDEX, SET ORDER,SetDefault(), SetPath()SORT, Soundex()USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_INTERFACE.xml b/docs/Help_Spanish/Topics/command_INTERFACE.xml
deleted file mode 100644
index b9fd1c93af..0000000000
--- a/docs/Help_Spanish/Topics/command_INTERFACE.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
- INTERFACE Statement
-
- Binding of instance variables
- Class namesdeclaring
- Classes
- Classes
- Classesdeclaring Class namesinheritanceobject instantiation
- Compile-time declaration
- Declaration statements
- END INTERFACE
- Entity declaration
- INHERIT clause
- INTERFACE
- INTERFACE statement
-
-
-
- INTERFACE Statement
-
- Purpose
- Declare a interface name to the compiler.
- Syntax
- [Attributes] [Modifiers] INTERFACE <idInterface> [INHERIT <idInterface>] [InterfaceMembers]
- END INTERFACE
- Arguments
-
-
- <idInterface>A valid identifier name for the class. A class is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a class and a global variable, for example, with the same name.
-
- INHERIT <idInterface>The name of an existing class (called a superclass) from which the new class inherits methods and instance variables (with the exception of HIDDEN).
-
- InterfaceMembersThis can be any of ACCESS, ASSIGN, METHOD, OPERATOR, PROPERTY, EVENT
- Description
- Notess
- See Also
- ACCESS, ASSIGN, CLASS, EVENT, METHOD, OPERATOR, PROPERTY, STRUCTURE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_Instance_Variable.xml b/docs/Help_Spanish/Topics/command_Instance_Variable.xml
deleted file mode 100644
index b0e40b5d58..0000000000
--- a/docs/Help_Spanish/Topics/command_Instance_Variable.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- Instance Variables
-
- Instance Variables
-
-
-
- Instance Variables
-
- Purpose
- Declare fields/ instance variables with optional initial values.
- Syntax
-
- [Attributes] [Modifiers] [INSTANCE] [DIM] <idVar>[ [ <dimensions> ] ] [:= <uValue>] [, ...] [AS <idType>] [, ...]]
- Arguments
-
- DIMAn optional keyword that specifies that you want to create a variable of a (.Net) array type.
-
- INSTANCEAn optional keyword that you have to use when no modifiers are used. Without modifier the fields will become PUBLIC.
-
- <idVar>A valid identifier name for the field to declare.
-
- [<dimensions>]The initial dimensions for a variable of type array. This may be used with the DIM keyword, in which case it is a .Net array, or without the DIM keyword, in which case it is a VO compatible dynamic array.
-
- <uValue>The initial value to assign to the variable.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_JOIN.xml b/docs/Help_Spanish/Topics/command_JOIN.xml
deleted file mode 100644
index 2dbcef8f91..0000000000
--- a/docs/Help_Spanish/Topics/command_JOIN.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-
- JOIN Command
-
- Commands
- Creatingfiles
- Databases
- Filescreating
- JOIN command
-
-
-
- JOIN Command
-
-
- Purpose
- Create a new database file by merging selected records and fields from two work areas based on a specified condition.
- Syntax
- JOIN WITH <xcAlias> TO <xcTargetFile> FOR <lCondition> [FIELDS <idFieldList>]
- Arguments
- WITH <xcAlias>The alias identifier for the work area to merge with the current work area. If there is no open database associated with <xcAlias>, a runtime error is raised.
-
- TO <xcTargetFile>The name of the target database file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD .
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
-
- FOR <lCondition>A condition that is processed for each visible record in the current work area using every visible record in the WITH work area. If a record meets the condition, a new record is written to <xcTargetFile>. If a record does not meet the specified condition, it is ignored and the next record is processed.
-
- Warning! The number of records processed will be the LastRec() of the primary work area multiplied by the LastRec() of the secondary work area. For example, if you have two database files with 100 records each, the number of records JOIN processes is the equivalent of sequentially processing a single database file of 10,000 records. Therefore, use this command carefully.
-
- FIELDS <idFieldList>The projection of fields from both work areas into the new database file. To specify fields in the secondary work area, reference them with the alias operator (->). If the FIELDS clause is not specified, all fields from the current work area are included in the target database file.
- Notes
- Deleted records: If SetDeleted() is FALSE, deleted records in both source files are processed, but their deleted status is not retained in <xcTargetFile>; thus, no record in the target file is marked for deletion, regardless of its deleted status in the source files.
- Visibility:If SetDeleted() is TRUE, deleted records (in both files) are not visible and are, therefore, not processed. Similarly, records that are filtered (with DbSetFilter() or a conditional controlling order) are not processed.
- Examples
- This example joins the CUSTOMER.DBF with INVOICES.DBF to produce PURCHASES.DBF:
-
- USE invoices NEW USE customer NEW JOIN WITH Invoices TO purchases; FOR Last = Invoices->Last; FIELDS First, Last, Invoices->Number,; Invoices->Amount
-
- See Also
- DbJoin(), SET RELATION, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_LOCAL-FUNCTION.xml b/docs/Help_Spanish/Topics/command_LOCAL-FUNCTION.xml
deleted file mode 100644
index cfd293ac79..0000000000
--- a/docs/Help_Spanish/Topics/command_LOCAL-FUNCTION.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-
- LOCAL FUNCTION
-
- END FUNCTION
- LOCAL FUNCTION
-
-
-
- LOCAL FUNCTION
-
- Purpose
- Declare a local function.
- Syntax
- [Modifiers] LOCAL FUNCTION <idFunction>
- [Typeparameters]
- [([<idParam> [AS | REF|OUT|IN <idType>] [, ...])]
- [AS <idType>]
- [TypeparameterConstraints]
- [=> <expression>]
- CRLF
- [<Body>]
- END FUNCTION
- Arguments
-
- [Modifiers]The only valid modifiers for a local function are UNSAFE and/or ASYNC.
-
- <idFunction>A valid identifier name for the function. A function is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a function and a class, for example, with the same name.
-
-
-
-
- END FUNCTIONThese mandatory keywords indicate the logical end of the function.
- Description
- A local function is defined as a nested function inside a containing member.The END FUNCTION is mandatory so the compiler knows where the function ends and its surrounding container continues.
- In the example below, the WAIT command is part of the Start() function and will be executed after result of the call to Fact() is shown.
- Example
- FUNCTION Start ASVOID ? Fact(10) LOCALFUNCTION Fact(nNum ASLONG) ASLONG IF nNum == 1 RETURN 1 ENDIF RETURN nNum * Fact(nNum-1) ENDFUNCTION WAIT RETURN
-
- See Also
- FIELD, LOCAL, MEMVAR, METHOD, PROCEDURE, RETURN, FUNCTION
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_LOCAL-PROCEDURE.xml b/docs/Help_Spanish/Topics/command_LOCAL-PROCEDURE.xml
deleted file mode 100644
index 84fdab7bf7..0000000000
--- a/docs/Help_Spanish/Topics/command_LOCAL-PROCEDURE.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-
- LOCAL PROCEDURE
-
- END PROCEDURE
- LOCAL PROCEDURE
-
-
-
- LOCAL PROCEDURE
-
- Purpose
- The LOCAL PROCEDURE keyword declares a local procedure.
- Syntax
- [Modifiers] LOCAL PROCEDURE <idFunction>
- [Typeparameters]
- [([<idParam> [AS | REF|OUT|IN <idType>] [, ...])]
- [TypeparameterConstraints]
- [=> <expression>]
- CRLF
- [<Body>]
- END PROCEDURE
- Arguments
-
- [Modifiers]The only valid modifiers for a local function are UNSAFE and/or ASYNC.
-
- <idFunction>A valid identifier name for the function. A function is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a function and a class, for example, with the same name.
-
-
-
-
- END PROCEDUREThese mandatory keywords indicate the logical end of the function.
- Description
- A local function is defined as a nested function inside a containing member. The END PROCEDURE is mandatory so the compiler knows where the function ends and its surrounding container continues.
- In the example below, the WAIT command is part of the Start() function and will be executed after the call to Log(3).
-
- Example
- FUNCTION Start ASVOID Log(1) Log(2) Log(3) LOCALPROCEDURE Log(nNum ASLONG) ? nNum RETURN ENDPROCEDURE WAIT RETURN
-
- See Also
- FIELD, LOCAL, MEMVAR, METHOD, PROCEDURE, RETURN, PROCEDURE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_LOCAL.xml b/docs/Help_Spanish/Topics/command_LOCAL.xml
deleted file mode 100644
index 0279b280d8..0000000000
--- a/docs/Help_Spanish/Topics/command_LOCAL.xml
+++ /dev/null
@@ -1,89 +0,0 @@
-
-
-
- LOCAL Statement
-
- Arrayscreatingdeclaring
- Creatingarraysvariables
- Declaration statements
- LOCAL statement
- Statements
- STATIC LOCAL statement
- Variable declaration
- Variablescreatingdeclaring
-
-
-
- LOCAL Statement
-
- Purpose
- Declares and initializes local variables and arrays.
-
- Syntax
- [STATIC] LOCAL <idVar> [:= <uValue>] [,...] [AS | IS <idType>] [, ...] [STATIC] LOCAL DIM <ArraySpec> [, ...] AS | IS <idType> [, ...] [STATIC] LOCAL <ArraySpec> [, ...] [AS ARRAY] [, ...] LOCAL ARRAY <arrayName> ( <nRows> [, <nColumns>] ) [, <arrayName> ( <nRows> [, <nColumns>] ) ] // FoxPro dialect only LOCAL ARRAY <arrayName> [ <nRows> [, <nColumns>] ] [, <arrayName> [ <nRows> [, <nColumns>] ] ] // FoxPro dialect only
-
- Note: The LOCAL statement is shown using several syntax diagrams for convenience. You can declare variables, dynamic arrays, and dimensioned arrays using a single LOCAL statement if each definition is separated by a comma.
-
- Arguments
- STATICCauses the local variable to retain its value across invocations of the declaring entity but does not affect its visibility.
-
-
- Description
- LOCAL is a declaration statement that declares one or more variables or arrays as local to the current routine (i.e., function, method, or procedure). Like other variable declaration statements (such as FIELD and MEMVAR), you must place LOCAL statements before any executable statements (including PRIVATE, PUBLIC, and PARAMETERS) in the routine you are defining.
-
- Local variable declarations hide all inherited private variables, visible public variables, instance variables, global variables, and constants with the same name. The search order for a variable name is as follows:
- 1.LOCALs, local parameters, MEMVARs, and FIELDs
- 2.SELF instance variables (i.e., without <idObject>: prefix in class methods)
- 3.GLOBALs and DEFINEs
-
- A LOCAL statement that declares a variable name which is already declared within the same routine (with FIELD, LOCAL, or MEMVAR) causes a compiler error.
-
- Local variables are visible only within the current routine, and unlike private variables, are not visible within invoked routines. If a routine is invoked recursively, each recursive activation creates a new set of local variables.
-
- Unless you specify the STATIC keyword, local variables are created automatically each time the routine in which they were declared begins executing. They continue to exist and retain their values until the declaring routine returns control to the routine that invoked it.
-
- The STATIC keyword serves as a lifetime modifier for a local variable, preventing the variable from being released from memory when the creating entity returns to its calling routine.
-
- Important! When an application containing static variable declarations is invoked, the variables are created and initialized before the beginning of program execution. Thus, initial values are assigned only once per application run, not each time the creator is called.
-
- Notes
- Local parameters: The FUNCTION, METHOD, and PROCEDURE statements allow you to declare a list of local parameters enclosed in parentheses following the entity name. For example:
-
- FUNCTION <idFunction>(<idParamList>)
-
- Exporting locals through code blocks: When you create a code block, you can access local variables defined in the creating entity within the code block definition without passing them as parameters (because local variables are visible to the code block). This, along with the fact that you can pass a code block as a parameter, allows you to export local variables. For example:
-
- FUNCTION One() LOCAL nVar := 10 ASINT, cbAdd AS CODEBLOCK cbAdd := {|nValue| nValue + nVar} ? NextFunc(cbAdd) // Result: 210
FUNCTION NextFunc(cbAddEmUp) RETURN EVAL(cbAddEmUp, 200)
-
- When the code block is evaluated in NextFunc(), nVar, which is local to function One(), becomes visible even though it is not passed directly as a parameter.
-
- Macro expressions: You cannot refer to local variables within macro variables and expressions. If you refer to a local variable within a macro variable, a private or public variable with the same name will be referenced instead. If no such variable exists, a runtime error will be raised.
- Type of a local variable: Since Type() uses the macro operator (&) to evaluate its argument, you cannot use it to determine the type of a local variable or an expression containing a local variable reference. You can, however, use ValType() which evaluates its argument and returns the type of the return value
- Memory files: You cannot SAVE or RESTORE local variables.
-
- Examples
- The following example declares two local arrays and two local variables:
-
- LOCAL aArray1[20,10], aArray2[20][10], var1, var2
-
- This example declares two local variables with initializers. The first is initialized to a date value and the second to an array:
-
- LOCAL dWhen :=TODAY() LOCAL aVegies :={"Tomato","Chickadee","Butterbean"}
-
- In this example, the variable x and the dimensioned array z are typed as INT, while the variables cName and cAddr are typed as STRING:
-
- LOCAL x,DIM z[100]ASINT, cName, cAddr ASSTRING
-
- The next example declares static variables both with and without initializers:
-
- STATICLOCAL aArray1[20,10], aArray2[20][10] STATICLOCAL cVar, cVar2 STATICLOCAL cString :="my string", var STATICLOCAL aArray :={1,2,3}
-
- Here a static variable is manipulated within a function. In this example, a count variable increments itself each time the function is called:
-
- FUNCTION MyCounter(nNewValue) // Initial value assigned once STATICLOCAL nCounter :=0 IF nNewValue !=NIL // New value for nCounter nCounter := nNewValue ELSE // Increment nCounter ++nCounter ENDIF RETURN nCounter
-
- See Also
- FIELD, FUNCTION, DEFINE, GLOBAL, MEMVAR, METHOD, PROCEDURE, STATIC, DIMENSION, DECLARE, PUBLIC
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_LOCATE.xml b/docs/Help_Spanish/Topics/command_LOCATE.xml
deleted file mode 100644
index 861e931d16..0000000000
--- a/docs/Help_Spanish/Topics/command_LOCATE.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- LOCATE Command
-
- Commands
- Databases
- Findingrecords
- LOCATE command
- Recordsfinding
-
-
-
- LOCATE Command
-
-
- Purpose
- Search for the first record in the current work area that matches the specified condition and scope.
- Syntax
- LOCATE [<Scope>] FOR <lCondition> [WHILE <lCondition>]
- Arguments
-
-
-
- Description
- LOCATE evaluates each visible record within the scope using the for condition. As soon as a record meets the condition, the process terminates, leaving the record pointer on the matching record and setting the Found() flag to TRUE. If the for condition is FALSE for all records in the scope, the Found() flag is set to FALSE, and the position of the record pointer depends on the scope.
-
- Each work area has its own locate condition which remains active until you execute another locate operation (for example, with LOCATE or DBLocate()), reset the locate condition (for example, with VODBSetLocate()), or terminate the application.
- Notes
- CONTINUE: Once you locate a record and have processed it, you can resume the search from the current record pointer position with CONTINUE (or DBContinue()). Both the <Scope> and the while condition, however, apply only to the initial locate operation and are not known by subsequent continue operations. To continue a pending locate with a scope or while condition, use SKIP then LOCATE REST WHILE <lCondition> instead of CONTINUE as shown in the example below.
- Examples
- These examples show typical LOCATE constructs:
-
- USE sales INDEX salesman LOCATE FOR Branch ="200" ? Found(),EOF(),RECNO()// Result: TRUE FALSE 5 LOCATE FOR Branch ="5000" ? Found(),EOF(),RECNO()// Result: FALSE TRUE 85
-
- The next example shows a LOCATE with a WHILE condition that is continued by using LOCATE REST:
-
- SEEK "Bill" LOCATE FOR Branch ="200"WHILE Salesman ="Bill" DOWHILE Found() ? Branch, Salesman SKIP LOCATE REST FOR Branch ="200"WHILE; Salesman ="Bill" ENDDO
-
- See Also
- CONTINUE, DbContinue(), DbLocate(), EoF(), Found(), RecNo(), SEEK, DbSetFilter()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_LOOP.xml b/docs/Help_Spanish/Topics/command_LOOP.xml
deleted file mode 100644
index 2290ae776d..0000000000
--- a/docs/Help_Spanish/Topics/command_LOOP.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- LOOP Statement
-
- LOOP statement
-
-
-
- LOOP Statement
-
- Purpose
- The LOOP statement causes control to jump back to the beginning of the innermost FOR, FOREACH , REPEAT or DO WHILE statement.
- Syntax
- LOOP
- Remarks
- The LOOP statement is only valid within a DO WHILE, FOR ... NEXT, FOREACH .. NEXT or REPEAT .. UNTIL construct. A LOOP statement outside of either construct will raise a compile time error.
- See Also DO WHILE FOR
- FOREACH REPEAT UNTIL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_LPARAMETERS.xml b/docs/Help_Spanish/Topics/command_LPARAMETERS.xml
deleted file mode 100644
index 35340023b5..0000000000
--- a/docs/Help_Spanish/Topics/command_LPARAMETERS.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- LPARAMETERS Statement
-
- Declaration statements
- LOCAL statement
- LPARAMETERS statement
- Statements
- Variable declaration
- Variablesdeclaring
-
-
-
- LPARAMETERS Statement
-
-
-
- The LPARAMETERS statement is identical to the PARAMETERS statement. The Variables however will be created as LOCAL variables and not as Dynamic Memory Variables and the optional <Type> clause is respected.
- Purpose
- Creates local variables to receive passed values or references.
- Syntax
- LPARAMETERS <idParameterList> LPARAMETERS <Parameter1> [ AS <Type> [ OF <ClassLibrary> ] ] [, <Parameter2> [ AS <Type> [ OF <ClassLibrary> ] ] ]
-
- Arguments
- <idParameterList>One or more parameter variables separated by commas. These variables are used to receive arguments that you pass when you call the routine. The variables will be dynamic memory variables.
-
- The <ClassLibrary> is ignored but the <Type> is enforced.
- Description
- When a LPARAMETERS statement executes, all variables in the parameter list are created as local variables.
- Parameters can also be declared as local variables if specified as a part of the PROCEDURE or FUNCTION declaration statement (see example below). Parameters specified in this way are referred to as formal parameters. Note that you cannot specify both formal parameters and a PARAMETERS statement within a procedure or function definition.
- Attempting to do this results in a compiler error.
- The number of receiving variables does not have to match the number of arguments passed by the calling routine. If you specify more arguments than parameters, the extra arguments are ignored. If you specify fewer arguments than parameters, the extra parameters are created with a NIL value. If you skip an argument, the corresponding parameter is initialized to NIL.
- The PCount() function returns the position of the last argument passed in the list of arguments. This is different than the number of parameters passed, since it includes skipped parameters.
- Examples
- This function receives values passed into private parameters with a PARAMETERS statement:
- FUNCTION MyFunc() LPARAMETERS cOne, cTwo, cThree ? cOne, cTwo, cThree
- The next example is identical, but receives values passed into local variables, declared within the FUNCTION declaration:
- FUNCTION MyFunc(cOne, cTwo, cThree) ? cOne, cTwo, cThree
- See Also
- PARAMETERS
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_MEMVAR.xml b/docs/Help_Spanish/Topics/command_MEMVAR.xml
deleted file mode 100644
index 1367ff0f9f..0000000000
--- a/docs/Help_Spanish/Topics/command_MEMVAR.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- MEMVAR Statement
-
- Compiledeclaration
- Declaration statements
- Memory variable
- MEMVAR statement
- Statements
- Variable declaration
-
-
-
- MEMVAR Statement
-
-
- Purpose
- Declares one or more memory variable names to be used by the current routine.
- Syntax
- MEMVAR <idMemvarList>
- Arguments
- <idMemvarList>A list of public and private variable names to declare to the compiler.
- Description
- When you use the MEMVAR statement to declare variables, unaliased references to variables in <idMemvarList> are treated as if they were preceded by the special memory variable alias (_MEMVAR->).
-
- Like other variable declaration statements (such as LOCAL and FIELD), you must place MEMVAR statements before any executable statements (including PRIVATE, PUBLIC, and PARAMETERS) in the routine you are defining. The MEMVAR statement has no effect on the macro operator, which always assumes memory variables.
-
- The MEMVAR statement neither creates the variables nor verifies their existence. Its primary purpose is to ensure correct references to variables that are known to exist at runtime. Attempting to access variables before they are created will raise a runtime error.
- Examples
- This example demonstrates the relationship between a private and field variable with the same name. The private variable is declared with the MEMVAR statement:
-
- FUNCTION Example() MEMVAR Amount, Address PRIVATE Amount := 100 USE customer NEW
? Amount // Refers to Amount private variable ? Customer->Amount// Refers to Amount field variable
-
- See Also
- FIELD, LOCAL, PARAMETERS, PRIVATE, PUBLIC, STATIC
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_METHOD.xml b/docs/Help_Spanish/Topics/command_METHOD.xml
deleted file mode 100644
index 532c5280f3..0000000000
--- a/docs/Help_Spanish/Topics/command_METHOD.xml
+++ /dev/null
@@ -1,109 +0,0 @@
-
-
-
- METHOD Statement
-
- Classesdeclaring() Methods
- Compiledeclaration
- Declaration statements
- Entity declaration
- METHOD statement
- Statements
- Strong typingdefined
-
-
-
- METHOD Statement
-
- Purpose
- Declare a method name and an optional list of local variable names.
- Syntax
- [Attributes] [Modifiers] METHOD <idMethod>
- [Typeparameters]
- [([<idParam> [AS | REF|OUT|IN <idType>] [, ...])]
- [AS <idType>]
- [TypeparameterConstraints]
- [<idConvention>] [CLASS <idClass>]
- [=> <expression>] CRLF
- [<Body>]
- [END METHOD]
- Arguments
-
- <idMethod>A valid identifier name for the method. Method names must be unique within a class, but can share the same name as other entities (including access and assign methods) in your application.
-
-
-
-
- Description
- A method is a subprogram comprised of a set of declarations and statements to be executed whenever you refer to the method using the message send operator, as in:
-
- <idObject>:<idMethod>([<uArgList>])
-
- Or:
-
- SELF:<idMethod>([<uArgList>])
-
- Classes, instance variables (see the CLASS statement in this guide), and methods, are the basic object-oriented programming units. You will use methods in your applications to organize computational blocks of code for a specific class of objects.
- Notes
- VO Compatibility:
-
- VO has 2 special method names for constructing and destructing class objects: Init() and Axit(). In X#, these methods should be named CONSTRUCTOR and DESTRUCTOR.
- If you compile with compiler option /vo1 then you can still use the 'old' names. The compiler will then automatically map the Init() method to constructor and the Axit() method to destructor. This is NOT recommended.
-
- The Init() method: If you define a method named Init(), it is called automatically when you create an instance of the class to which the method belongs. Arguments listed within the instantiation operators ({}) are passed as parameters to the Init() method. Common uses for the Init() method are to initialize instance variables, allocate memory needed by the object, register the object, create subsidiary objects, and set up relationships between objects.
-
- The Axit() method: You do not need to de-allocate memory used by objects because the garbage collector takes care of this for you automatically. However, in some cases, an object can manage other resources that do need proper disposition. For example, if an object opens a database only for its own use, it should close it when it is finished and make the work area available for other uses.
-
- If you register an object with the RegisterAxit() function, for example in the Init() method, and provide a method named Axit(), this Axit() method will automatically be called by the garbage collector just before the object is destroyed. Thus, in the Axit() method you can close databases, de-allocate memory, or close communications links.
-
- NoIVarGet()/NoIVarPut() methods: If you define methods named NoIVarGet() and NoIVarPut(), they will automatically be invoked if an instance variable that does not exist is referenced. They are called with the instance variable name as a parameter, in the form of a symbol and, in the case of NoIVarPut(), with the assigned value. his feature is useful in detecting and preventing a runtime error and for creating virtual variables dynamically at runtime. For example, the DBServer class uses this technique to make the database fields appear to be exported instance variables of a database object:
-
- METHOD NoIVarGet(symFieldName) CLASS DBServer BEGINSEQUENCE RETURN FieldGetAlias(symAlias, symFieldName) RECOVER // Pass it up if it was not a field name SUPER:NoIVarGet(symFieldName) ENDSEQUENCE
METHOD NoIVarPut(symFieldName, uValue) ; CLASS DBServer BEGINSEQUENCE RETURN FieldGetAlias(symAlias, ; symFieldName, uValue) RECOVER // Pass it up if it was not a field name SUPER:NoIVarPut(symFieldName, uValue) ENDSEQUENCE
FUNCTION DatabaseTest() LOCAL oDBServer AS DBServer oDBServer := DBServer{"customer"} ? oDBCustomer:CustName oDBCustomer:ZipCode := "12345"
-
- The NoMethod() method:If you define a method named NoMethod(), it will automatically be invoked if a method name that you invoke within the same class cannot be found. The arguments passed will be the same as the original method. This feature is useful in detecting and preventing a runtime error when a method cannot be found. Use the NoMethod() function to find out the name of the method that could not be found.
-
- Exporting locals through code blocks: When you create a code block, you can access local variables defined in the creating entity within the code block definition without having to pass them as parameters (i.e., local variables are visible to the code block). Using this fact along with the fact that you can pass a code block as a parameter, you can export local variables. For example:
-
- METHOD One()CLASS MyClass EXPORTLOCAL LOCAL nVar :=10ASINT, cbAdd ASCODEBLOCK cbAdd :={|nValue| nValue + nVar}
?SELF:Two(cbAdd)// Result: 210
METHOD Two(cbAddEmUp)CLASS MyClass RETURNEVAL(cbAddEmUp,200)
- When the code block is evaluated in Two(), nVar, which is local to method One(), becomes visible, even though it is not passed directly as a parameter.
-
- Invoking methods: The syntax to invoke a method of an object is as follows:
- <idObject>:<idMethod>([<uArgList>])
- where <uArgList> is an optional comma-separated list of arguments to pass to the named method. <idObject> identifies the object to whom the method invocation is to be sent; to refer to the same object within a method you use SELF: or SUPER: (see note below) instead of <idObject>:.
-
- You can invoke a method within an expression or as a program statement. If called as a program statement, the return value is ignored.
-
- You can also use a method invocation as an aliased expression by prefacing it with an alias and enclosing it in parentheses:
-
- <idAlias>->(<idObject>:<idMethod>([<uArgList>]))
-
- When you do this, the work area associated with <idAlias> is selected, the method is executed, and the original work area is reselected. You can specify an aliased expression as a program statement, as you would any other expression.
- A method can call itself recursively. This means you can refer to a method in its own <MethodBody>.
-
-
- The visibility of typed methods can also be influenced by using the HIDDEN and PROTECT modifiers as in their use with instance variables. SUPER calls of HIDDEN methods in parent classes cannot be done by methods of the sub-classes.
-
- Calling convention: Methods use the CLIPPER calling convention, unless they are strongly typed. See the FUNCTION statement in this guide for more information.
-
- SELF and SUPER: SELF is a special variable that contains a reference to the object that is the receiver of a message (a message is sent to an object each time you use the send operator to invoke a method or access an instance variable). Whenever a message is sent to an object, a reference to the object is placed in SELF before the corresponding method is invoked. Within methods of the class, you must use SELF with the message send operator (:) to send messages to the current object. Using SELF: to access instance variables is optional; see the ACCESS and ASSIGN entries in this guide for details on when it is required (it is always allowed).
-
- SUPER is another special variable that contains a reference to the class that is the nearest ancestor of the method lookup. It passes a message up the inheritance tree to the appropriate superclass and is meaningful only if the current object's class inherits from another class. You can use SUPER with the message send operator (:) to refer directly to a method defined in a superclass. If you redefine a method in a subclass (by creating a method with the same name as one in a superclass), SUPER is the only way you can override the redefined method with the superclass version.
- SUPER: is useful when defining a subclass which adds some unique behavior, but nonetheless inherits standard behavior from its superclass. For example:
-
- CLASS Person PROTECT cName ASSTRING, symName ASSYMBOL
CLASS Customer INHERIT Person PROTECT wCustNo ASDWORD
METHOD Init(cFirstName, cLastName, nCustNo); CLASS Customer SUPER:Init(cFirstName, cLastName) wCustNo := nCustNo
-
- The SELF and SUPER variables are allowed only in method definitions. SELF is the default return value for all methods.
-
- Parameters: As an alternative to specifying method parameters in the METHOD declaration statement, you can use a PARAMETERS statement to specify them. This practice, however, is not recommended, because it is less efficient and provides no compile-time integrity validation. See the PARAMETERS statement in this guide for more information.
-
- Methods with single expression instead of main body
- Methods (and every other entity type that can contain code) may include code as a single expression, using the => operator in the same line of code that defines the entity, instead of using a regular body. The single expression may or may not return a value:
- METHOD SimpleMethod() AS VOID => SELF:CallAnotherMethod() METHOD SimpleMethodWithReturnValue() AS INT => SELF:nSomeIvar + 1
- Examples
- This example creates a class of two-dimensional coordinates with methods to initialize the coordinates, draw a grid, and plot the point:
-
- FUNCTION Start() LOCAL oPointSet AS Point2D oPointSet := Point2D{2,3} oPointSet:ShowGrid() oPointSet:Plot()
CLASS Point2D// Define Point2D class INSTANCE x, y ASINT
METHOD Init(iRow, iCol)CLASS Point2D x := iRow y := iCol RETURNSELF
METHOD Plot()CLASS Point2D @ x +11, y +36 SAY CHR(249)
METHOD ShowGrid()CLASS Point2D LOCAL iCounter ASINT CLS FOR iCounter :=1TO21 IF iCounter =11 @ iCounter,1 SAY REPLICATE(CHR(196),71) @ iCounter,36 SAY CHR(197) ELSE @ iCounter,36 SAY CHR(179) ENDIF NEXT
- See Also
- ACCESS, ASSIGN, CLASS, FUNCTION, PROPERTY, OPERATOR, CONSTRUCTOR, DESTRUCTOR, EVENT
-
-
diff --git a/docs/Help_Spanish/Topics/command_NOP.xml b/docs/Help_Spanish/Topics/command_NOP.xml
deleted file mode 100644
index 638c3947e5..0000000000
--- a/docs/Help_Spanish/Topics/command_NOP.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- NOP Statement
-
- Closing files
- Commands
- Filesclosing
- NOP Statement
- Program control
-
-
-
- NOP Statement
-
- Purpose
- The NOP statement inserts an empty statement in the code
- Syntax
- NOP
- Remarks
- The NOP statement is an empty statement. It can be used to indicate that a certain code section is left intentionally empty
- Examples
- FUNCTION Start(aArgs asstring[]) ASVOID IF aArgs != NULL .AND. aArgs:Length > 0 ? "You passed ", aArgs:Length, "command line parameters" ELSE NOP// This indicates that the else branch is not forgotten but intentionally empty ENDIF ..... RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/command_NOTE.xml b/docs/Help_Spanish/Topics/command_NOTE.xml
deleted file mode 100644
index 67e1afc895..0000000000
--- a/docs/Help_Spanish/Topics/command_NOTE.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- Comments
-
- && characters
- * character
- /* characters
- // characters
- Addingcomments
- Commands
- Commentsadding
- NOTE command
-
-
-
- Comments
-
- Purpose
- X# has many comment formats.
- Syntax
- /* this is a multiline comment */ // this is a single line comment. && this is a single line comment. It may appear after other statements on a line. * this is also a comment. The * must be the first non white-space character on the line.
- Description
- X# has many different comment formats.
- Examples
- These examples show the various comment symbols:
-
- // This is a comment /* This is a comment */ * This is a comment && This is a comment
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_OPERATOR.xml b/docs/Help_Spanish/Topics/command_OPERATOR.xml
deleted file mode 100644
index 5838a73a39..0000000000
--- a/docs/Help_Spanish/Topics/command_OPERATOR.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- OPERATOR Statement
-
- Compile-time declaration
- Declaration statements
- Entity declaration
- OPERATOR statement
- Statements
-
-
-
- OPERATOR Statement
-
- Purpose
- Declare an operator method for a class which defines how standard operators like "+", "-", "++" etc operate when used with instances of the class as arguments
- Syntax
- [Attributes] [Modifiers] OPERATOR <operatortype>
- [([<idParam> [AS | REF <idType>] [, ...])]
- [AS <idType>]
- [=> <expression>]
- CRLF
- [<Body>]
- [END OPERATOR]
- Arguments
-
-
-
-
- END OPERATOROptional end clause to indicate the end of the OPERATOR entity.
-
- See Also
- ASSIGN, CLASS, METHOD
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_PACK.xml b/docs/Help_Spanish/Topics/command_PACK.xml
deleted file mode 100644
index 95370b613d..0000000000
--- a/docs/Help_Spanish/Topics/command_PACK.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- PACK Command
-
- Commands
- Databasesrecords
- Deleting
- PACK command
- Recordsdeleting
-
-
-
- PACK Command
-
-
- Purpose
- Remove all records marked for deletion from the current database file, rebuild all active orders, and recover all physical space occupied by the deleted records. Note that this will not affect memo files. Unused space in memo files can only be recovered by using COPY.
- Syntax
- PACK [[IN|ALIAS] <workarea>]
- Arguments
-
-
- Description
- PACK is functionally equivalent to DBPack().
-
- Warning! PACK does not create backup files. You may want to make a backup of the file (using COPY FILE, for example) before issuing this command; otherwise, you will not be able to recover deleted records.
- Examples
- The following shows the result of a simple PACK:
-
- USE sales NEW ? LastRec() // Result: 84
DELETERECORD 4 PACK ? LastRec() // Result: 83
-
- See Also
- DbPack(), DELETE, Deleted(), RECALL, REINDEX, SetDeleted() , SetExclusive(), ZAP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_PARAMETERS.xml b/docs/Help_Spanish/Topics/command_PARAMETERS.xml
deleted file mode 100644
index c3d17bd1db..0000000000
--- a/docs/Help_Spanish/Topics/command_PARAMETERS.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
- PARAMETERS Statement
-
- Creatingvariables
- Declaration statements
- Memory variable
- PARAMETERS statement
- Runtime declaration
- Statements
-
-
-
- PARAMETERS Statement
-
-
- Purpose
- Creates private variables to receive passed values or references.
- Syntax
- PARAMETERS <idParameterList> PARAMETERS <Parameter1> [ AS <Type> [ OF <ClassLibrary> ] ] [, <Parameter2> [ AS <Type> [ OF <ClassLibrary> ] ] ] // FoxPro only
-
- Arguments
- <idParameterList>One or more parameter variables separated by commas. These variables are used to receive arguments that you pass when you call the routine. The variables will be dynamic memory variables.
-
- Description
- When a PARAMETERS statement executes, all variables in the parameter list are created as private variables and all public or private variables with the same names are hidden until the current procedure or function terminates. A PARAMETERS statement is an executable statement and can, therefore, occur anywhere in a procedure or function.
- Parameters can also be declared as local variables if specified as a part of the PROCEDURE or FUNCTION declaration statement (see the example). Parameters specified in this way are referred to as formal parameters. Note that you cannot specify both formal parameters and a PARAMETERS statement within a procedure or function definition.
- Attempting to do this results in a compiler error.
- The number of receiving variables does not have to match the number of arguments passed by the calling routine. If you specify more arguments than parameters, the extra arguments are ignored. If you specify fewer arguments than parameters, the extra parameters are created with a NIL value. If you skip an argument, the corresponding parameter is initialized to NIL.
- The PCount() function returns the position of the last argument passed in the list of arguments. This is different than the number of parameters passed, since it includes skipped parameters.
- Examples
- This function receives values passed into private parameters with a PARAMETERS statement:
- FUNCTION MyFunc() PARAMETERS cOne, cTwo, cThree ? cOne, cTwo, cThree
- The next example is similar, but receives values passed into local variables, by declaring the parameter variables within the FUNCTION declaration:
- FUNCTION MyFunc(cOne, cTwo, cThree) ? cOne, cTwo, cThree
- See Also
- LPARAMETERS, PRIVATE
-
-
diff --git a/docs/Help_Spanish/Topics/command_PRIVATE.xml b/docs/Help_Spanish/Topics/command_PRIVATE.xml
deleted file mode 100644
index 44bc801cc4..0000000000
--- a/docs/Help_Spanish/Topics/command_PRIVATE.xml
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
- PRIVATE statement
-
- Arrayscreating
- Creatingvariables
- Declaration statements
- Memory variable
- PRIVATE statement
- Runtime declaration
- Statements
-
-
-
- PRIVATE Statement
-
-
- Purpose
- Creates variables and arrays visible within current and invoked routines.
- Syntax
- PRIVATE <idVar> [:= <uValue>] | <ArraySpec> [, ...] PRIVATE <idVar> [:= <uValue>] [AS <Type> [OF <ClassLibrary>] ] // FoxPro dialect
- Arguments
- <idVar>A valid identifier name for the private variable to create.
-
- <uValue>The initial value to assign to the variable. If not specified, the variable is initialized to NIL.
-
- <ArraySpec>The specification for a dynamic array to create. <ArraySpec> is one of the following:
- <idArray>[<nElements>, <nElements>, <nElements>]
- <idArray>[<nElements>][<nElements>][<nElements>]
- All dimensions except the first are optional.
- <idArray> is a valid identifier name for the array to create. Array elements are initialized to NIL.
- <nElements> defines the number of elements in a particular dimension of an array. The number of dimensions is determined by how many <nElements> arguments you specify.
-
-
- Description
- PRIVATE is an executable statement, meaning it must be specified it after any variable declaration statements (such as FIELD, LOCAL, and MEMVAR) in the routine being defined.
-
- Warning! Any reference to a variable created with this statement will produce a compiler error unless the Undeclared Variables compiler option is checked.
-
- When you create a private variable or array, any existing and visible private or public variables with the same name are hidden until the current routine terminates or the private variable is explicitly released.
-
- Attempting to specify a private variable that conflicts with a visible declared variable (such as LOCAL, GLOBAL, or DEFINE) with the same name is not recognized by the compiler as an error, because PRIVATE is not a compiler declaration statement. Instead, the declared variable will hide the public variable at runtime, making the public variable inaccessible until the declared variable is released.
-
- In class methods, instance variables (except for access/assign variables) are always more visible than private variables with the same name. To access a private variable within a method when there is a name conflict, use the _MEMVAR-> alias. For access/assign variables, use the SELF: prefix to override the name conflict with a private variable.
-
- In addition to the PRIVATE statement, you can create private variables by:
-
-
Assigning to a variable that does not exist or is not visible, which will create a private variable.
-
Receiving parameters using the PARAMETERS statement.
-
-
- Private variables are dynamically scoped. They persist until the creating routine returns to its caller or until explicitly released with CLEAR ALL or CLEAR MEMORY.
- Notes
- Compatibility: The ALL, LIKE and EXCEPT clauses of the PRIVATE statement supported by other Xbase dialects are not supported.
- Examples
- The following example creates two PRIVATE arrays and three other PRIVATE variables:
-
- PRIVATE aArray1[10], aArray2[20], var1, var2, var3
-
- The next example creates a multi-dimensional private array using each element addressing convention:
-
- PRIVATE aArray[10][10][10], aArray2[10, 10, 10]
-
- This example uses PRIVATE statements to create and initialize arrays and variables:
-
- PRIVATE aArray := { 1, 2, 3, 4 }, ; aArray2 := ArrayNew(12, 24) PRIVATE cChar := Space(10), cColor := SetColor()
- See Also
- LOCAL, MEMVAR, PARAMETERS, PUBLIC, DIMENSION, DECLARE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_PROCEDURE.xml b/docs/Help_Spanish/Topics/command_PROCEDURE.xml
deleted file mode 100644
index 2ac07ab070..0000000000
--- a/docs/Help_Spanish/Topics/command_PROCEDURE.xml
+++ /dev/null
@@ -1,93 +0,0 @@
-
-
-
- PROCEDURE Statement
-
- _INIT1
- _INIT2
- _INIT3
- Compiledeclaration
- Declaration statements
- Entity declaration
- EXIT PROCEDURE
- INIT PROCEDURE
- PROCEDURE
- PROCEDURE statement
- Statements
- STATIC PROCEDURE statement
-
-
-
- PROCEDURE Statement
-
- Purpose
- Declare a procedure name and formal parameters. When used inside a FoxPro DEFINE CLASS .. ENDDEFINE this declares a method.
- Syntax
- [Attributes] [Modifiers] PROCEDURE <idProcedure>
- [Typeparameters]
- [([<idParam> [AS | REF|OUT|IN <idType>] [, ...])]
- [AS <idType>]
- [TypeparameterConstraints]
- [<idConvention>]
- [_INIT1 | _INIT2 | _INIT3 | EXIT]
- [EXPORT LOCAL]
- [DLLEXPORT STRING_CONST]
- [=> <expression>]
- CRLF
- [<Body>]
- [ENDPROC | END PROCEDURE]
-
- Alternative INIT / EXIT Procedures
-
- [Attributes] [INIT | EXIT] PROCEDURE <idProcedure>
- [Typeparameters]
- [([<idParam> [AS | REF|OUT|IN <idType>] [, ...])]
- [AS <idType>]
- [TypeparameterConstraints]
- [<idConvention>]
- [=> <expression>]
- CRLF
- [<Body>]
- [ENDPROC | END PROCEDURE]
-
- Arguments
-
-
- Please note that functions and procedures used as class members in FoxPro compatible classes can have more modifiers.
- <idProcedure>A valid identifier name for the function. A function is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a function and a class, for example, with the same name.
-
-
- _INITn, EXITWhen an application is executed, all INIT procedures in all modules associated with the application (including libraries) are called automatically. There are three priority levels for INIT procedures indicated by the _INIT1, _INIT2, and _INIT3 keywords. _INIT1 procedures are called first, _INIT2 second, and _INIT3 third. All INIT procedures are called before the application Start() routine. EXIT procedures are called at application shutdown.
-
-
- ENDPROC | END PROCEDUREThese (optional) keywords indicate the logical end of the function.
-
- You must follow the guidelines below when specifying an INIT procedure:
-
-
No arguments are allowed
-
-
- Notes
- Please note that INIT and EXIT procedures always have an INTERNAL scope. You cannot access these from outside of the assembly where they are defined, to prevent you from accidentally calling them. If you need to call them, you may consider storing the actual code in a normal function or procedure and call that code from the INIT or EXIT procedure.
- Examples
-
- PROCEDURE First ASVOIDPASCAL_INIT1
-
- INIT procedures are necessary for having automatic initialization routines for libraries and other modules in an application besides the main startup module (i.e., the one containing the Start() routine). Although Start() routines are limited to one per application, there are no inherent limits for the total number of INIT procedures within an application.
-
- The following example shows a skeleton of a typical procedure that uses declared variables:
-
- PROCEDURE Skeleton(cName, cClassRoom, Bones, nJoints) LOCAL nCrossBones, aOnHand :={"skull","metacarpals"} STATIC nCounter :=0
<Executable Statements>...
-
- The next example determines whether an argument was skipped by comparing the parameter to NIL:
-
- PROCEDURE MyProc(param1, param2, param3) IF param2 !=NIL param2 :="default value" ENDIF <Statements>...
-
- This example invokes the procedure, UpdateAmount(), as an aliased expression:
-
- USE invoices NEW USE customer NEW Invoices->UpdateAmount(Amount + Amount * nInterest)
- See Also
- FIELD, FUNCTION, LOCAL, MEMVAR, METHOD,RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_PROPERTY.xml b/docs/Help_Spanish/Topics/command_PROPERTY.xml
deleted file mode 100644
index 4b4b28a239..0000000000
--- a/docs/Help_Spanish/Topics/command_PROPERTY.xml
+++ /dev/null
@@ -1,63 +0,0 @@
-
-
-
- PROPERTY Statement
-
- Access() Methods
- Compile-time declaration
- Declaration statements
- Entity declaration
- Instance variables
- Instance variables
- Instance variablesaccessingassigning valuesnon-exportedvirtual variables
- Methodsaccessing instance variables
- PROPERTY statement
- Statements
- Strong typingdefined
- Virtual variables
-
-
-
- PROPERTY Statement
-
- Purpose
- Declare a property to a class, which can be used for reading, writing and computing data from/to it.
- Syntax
- [Attributes] [Modifiers] PROPERTY<idName>
- [([<idParam> [AS | REF <idType>] [, ...])]
- [AS <idType>] [<idConvention>] [
- AUTO [Attributes] [Modifiers] GET | SET | INIT
- | [ [Attributes] [Modifiers] GET <Expression> ] [ [Attributes] [Modifiers] SET <Expression>] [ [Attributes] [Modifiers] INIT <Expression>]
- CRLF
- | [ [Attributes] [Modifiers] GET <Body > END GET]
- | [ [Attributes] [Modifiers] GET => <Expression>]
- | [ [Attributes] [Modifiers] SET <Body > END SET]
- | [ [Attributes] [Modifiers] SET => <Expression>]
- | [ [Attributes] [Modifiers] INIT <Body > END INIT]
- | [ [Attributes] [Modifiers] INIT => <Expression>]
- END PROPERTY
- ]
- Arguments
-
- <idName>A valid identifier name for the property that you are defining. Like other methods, properties are entities. Property names must be unique within a class, but can share the same name as other entities in your application.
-
-
-
-
-
-
- Description
- There are three types of property declarations:
-
-
Single line declaration without AUTO clause;
-
Single line declaration with GET / SET / INIT accessors;
-
Multi-line declaration with GET accessor block and/or SET/INIT accessor bock. For multi-line declarations, the END PROPERTY is mandatory.
-
-
- INIT accessor declares that a property can only be changed in the constructor of a class. A property cannot have both a SET and an INIT accessor.
-
- See Also
- ASSIGN, CLASS, METHOD
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_PUBLIC.xml b/docs/Help_Spanish/Topics/command_PUBLIC.xml
deleted file mode 100644
index c392f02e8c..0000000000
--- a/docs/Help_Spanish/Topics/command_PUBLIC.xml
+++ /dev/null
@@ -1,84 +0,0 @@
-
-
-
- PUBLIC Statement
-
- Arrayscreating
- Creating
- Creatingarraysvariables
- Declaration statements
- Memory variable
- PUBLIC statement
- Runtime declaration
- Statements
- Variablescreating
-
-
-
- PUBLIC Statement
-
-
- Purpose
- Creates variables and arrays visible to all routines in an application.
- Syntax
- PUBLIC <memVarList> PUBLIC <idVar> [:= <uValue>] | <ArraySpec> [, ...] PUBLIC <idVar> [:= <uValue>] [AS <Type> [OF <ClassLibrary>] ] // FoxPro dialect only PUBLIC ARRAY <arrayName> ( <nRows> [, <nColumns>] ) [, <arrayName> ( <nRows> [, <nColumns>] ) ] // FoxPro dialect only PUBLIC ARRAY <arrayName> [ <nRows> [, <nColumns>] ] [, <arrayName> [ <nRows> [, <nColumns>] ] ] // FoxPro dialect only
- Arguments
- <memVarList>One or more variable names separated by commas.
- <idVar>A valid identifier name for the public variable to be created. The idVar may be prefixed with an ampersand (such as PUBLIC &name). In this case, the compiler expects idVar to contain a string representing the name of the variable to be declared and initialized.
-
- <uValue>The initial value to assign to the variable. This can be any valid expression. If <uValue> is not specified, the variable is initialized to FALSE. There are exceptions: In the FoxPro dialect, the PUBLIC FOX and FOXPRO are initialized with TRUE. In other dialects, the PUBLIC CLIPPER is initialized with TRUE.
-
- <ArraySpec>The specification for a dynamic array to create. <ArraySpec> is one of the following:
- <idArray>[<nElements>, <nElements>, <nElements>]
- <idArray>[<nElements>][<nElements>][<nElements>]
- All dimensions except the first are optional.
- <idArray> is a valid identifier name for the array to create. Array elements are initialized to NIL.
- <nElements> defines the number of elements in a particular dimension of an array. The number of dimensions is determined by how many <nElements> arguments you specify.
-
- The <Type> and <ClassLibrary> clauses are ignored because dynamic memory variables are always of type USUAL
- <arrayName>Variable name of array. The array will have the dimensions specified by <nRows> and <nColumns>. The array can be declared using either parentheses or square brackets as delimiters. We recommend the use of square brackets. <nColumns> is optional.
- Description
- PUBLIC is an executable statement which means you must specify it after any variable declaration statements (i.e., FIELD, LOCAL, and MEMVAR) in the routine that you are defining.
-
- Warning! Any reference to a variable created with this statement will produce a compiler error unless the Undeclared Variables compiler option is checked.
-
- Any declared variables, such as LOCAL variables, with the same names as existing public or private variables will temporarily hide the public or private variables until the overriding variables are released or are no longer visible.
-
- An attempt to create a public variable with the same name as an existing and visible private variable is simply ignored. However, the assignment portion of the PUBLIC statement is not ignored. For example, the following lines of code change the value of the variable x but do not change its scope from private to public:
-
- PRIVATE x := 1000 ... PUBLIC x := "New value for x" ? x// Result: "New value for x"
-
- The explanation for this behavior is that, internally, the PUBLIC statement and the assignment are treated as separate statements. Thus, this code would be treated as follows:
-
- PRIVATE x := 1000 ... PUBLIC x x := "New value for x" ? x// Result: "New value for x"
-
- The PUBLIC statement is ignored, but the assignment statement is executed, changing the value of the private variable x.
-
- This behavior has an interesting repercussion when you declare a public array using a variable name that already exists as private. For example:
-
- PRIVATE x := 1000 ... PUBLIC x[10] ? x[1]// Result: NIL
-
- In this case, the PUBLIC statement is also treated as two separate statements:
-
- PRIVATE x := 1000 ... PUBLIC x x := ArrayNew(10) ? x[1]// Result: NIL
- Again, the PUBLIC statement is ignored, and the assignment changes x from a private numeric variable to a private reference to a ten element array.
-
- Attempting to specify a public variable that conflicts with a visible declared variable (for example, LOCAL, GLOBAL, or DEFINE) of the same name is not recognized by the compiler as an error, because PUBLIC is not a compiler declaration statement. Instead, the declared variable will hide the public variable at runtime. This means that you will not be able to access the public variable at all until the declared variable is released.
-
- In class methods, instance variables (with the exception of access/assign variables) are always more visible than public variables of the same name. Use the _MEMVAR-> alias to access a public variable within a method if there is a name conflict. For access/assign variables, use the SELF: prefix to override a name conflict with a public variable.
- Public variables are dynamically scoped. They exist for the duration of the application or until explicitly released with CLEAR ALL or CLEAR MEMORY.
- Notes
- PUBLIC Clipper: To include <%APP%> extensions in an application and still allow the application to run under dBASE III PLUS, the special public variable, Clipper, is initialized to TRUE when created with PUBLIC.
- Examples
- This example creates two PUBLIC arrays and one PUBLIC variable:
-
- PUBLIC aArray1[10, 10], var2 PUBLIC aArray2[20][10]
-
- The following PUBLIC statements create variables and initialize them with values:
-
- PUBLIC cString := Space(10), cColor := SetColor() PUBLIC aArray := {1, 2, 3}, ; aArray2 := ArrayNew(12, 24)
- See Also
- GLOBAL, MEMVAR, PARAMETERS, PRIVATE, DIMENSION, DECLARE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_QUESTION.xml b/docs/Help_Spanish/Topics/command_QUESTION.xml
deleted file mode 100644
index 5d6d740750..0000000000
--- a/docs/Help_Spanish/Topics/command_QUESTION.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- ?|?? Statement
-
- ?|?? statement
- Displayingoutput
- Statements
- Terminal window
-
-
-
- ?|?? Statement
-
- Purpose
- Display the results of one or more expressions, separated by a space, in the terminal window.
- Syntax
- ? | ?? [<uValueList>]
- Arguments
- <uValueList>A list of values to display. If no argument is specified with the ? statement, a carriage return/linefeed is sent to the terminal window. If you use the ?? statement without arguments, nothing happens.
- Description
- ? and ?? are synonyms for the QOut() and QQOut() functions, respectively.
- Although functionally similar to one another, ? and ?? differ slightly. ? sends a carriage return/linefeed before displaying the results of the expression list. ?? displays output at the current position. This lets you use ?? statements to display successive output on the same line.
-
- A ? or ?? statement locates the cursor or print head one position to the right of the last character displayed. Row() and Col() are updated to reflect the new cursor position.
-
- If output from a ? or ?? statement reaches the edge of the terminal window, it wraps to the next line. If the output reaches the bottom of the window, the window scrolls up one line.
- To format any expression specified, use Transform(). If you need to pad a variable length value for column alignment, use any of the Pad() functions to left-justify, right-justify, or center the value as illustrated in the examples below.
- Examples
- This example displays a record from a database file using ? and ?? statements with PadR() to assure column alignment:
-
- LOCAL nPage :=0, nLine :=99 USE salesman INDEX salesman NEW DOWHILE!EOF() IF nLine >55 IF nPage !=0 EJECT ENDIF ? PadR("Page",LTRIM(STR(++nPage)),72) ??DTOC(TODAY()) ? ? ? PadC("Sales Listing",79) ? nLine :=5 ENDIF ? Name, Address, PadR(RTrim(City)+","+ State,20), ZipCode ++nLine SKIP ENDDO CLOSE salesman
-
- See Also
- QOut(), QQOut()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_QUIT.xml b/docs/Help_Spanish/Topics/command_QUIT.xml
deleted file mode 100644
index da50fcf0a2..0000000000
--- a/docs/Help_Spanish/Topics/command_QUIT.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- QUIT Command
-
- Closing files
- Commands
- Filesclosing
- Program control
- QUIT command
-
-
-
- QUIT Command
-
-
- Purpose
- Terminates application processing, closes all open files, and returns control to the operating system.
- Syntax
- QUIT | CANCEL
- Description
- QUIT is the same as CANCEL. See CANCEL for a complete explanation of this command.
-
- See Also
- BEGIN SEQUENCE, CanBreak(), CANCEL, ErrorLevel(), RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_RECALL.xml b/docs/Help_Spanish/Topics/command_RECALL.xml
deleted file mode 100644
index ecfb3f0076..0000000000
--- a/docs/Help_Spanish/Topics/command_RECALL.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- RECALL Command
-
- Commands
- Databases
- RECALL command
- Recordsrestoring
- Restoring records
-
-
-
- RECALL Command
-
-
- Purpose
- Restore records marked for deletion in the current work area.
- Syntax
- RECALL [<Scope>] [WHILE <lCondition>] [FOR <lCondition>] [[IN|ALIAS] <workarea>
- Arguments
-
-
-
-
-
- RECALL is the inverse of the DELETE command. If SetDeleted() is TRUE, RECALL can restore the current record or a specific record if you specify a RECORD scope.
-
- Important! Once you PACK a database file, all marked records are physically removed from the file and cannot be recalled.
-
- Shared mode: For a shared database, this command requires all records that it operates on to be locked. You can accomplish this using one or more record locks or a file lock, depending on the scope of the command.
- Examples
- This example shows the results of RECALL:
-
- USE sales NEW DELETE RECORD 4 ? Deleted()// Result: TRUE RECALL ? Deleted()// Result: FALSE
-
- See Also
- DELETE, DbRecall(), Deleted(),, FLock(), PACK, RLock(), SetDeleted() , ZAP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_REINDEX.xml b/docs/Help_Spanish/Topics/command_REINDEX.xml
deleted file mode 100644
index 48d9611d9d..0000000000
--- a/docs/Help_Spanish/Topics/command_REINDEX.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-
- REINDEX Command
-
- Commands
- Databases
- Filesrebuilding index files
- Index filesrebuilding
- Index/order
- Ordersrebuilding
- REINDEX command
-
-
-
- REINDEX Command
-
-
- Purpose
- Rebuild all orders in the order list of the current work area.
- Syntax
- REINDEX [EVAL <lCondition> [EVERY <nRecords>]
- Arguments
- EVAL <cbEval>A code block that is evaluated at intervals specified by EVERY <nInterval>. The default interval is 1. This is useful in producing a status bar or odometer that monitors the ordering progress. The return value of <cbEval> must be a logical value. If <cbEval> returns FALSE, indexing halts.
-
- EVERY <nInterval>A numeric expression that determines the number of times <cbEval> is evaluated. This option offers a performance enhancement by evaluating the condition at intervals instead of for every record processed. If no EVAL clause is specified, the EVERY keyword is ignored.
- Description
- REINDEX is functionally equivalent to DbReindex().
-
- Caution! REINDEX does not recreate the header of the index file when it recreates the index. Because of this, REINDEX does not help if there is corruption of the file header. To guarantee a valid index, always use INDEX ON in place of REINDEX to rebuild damaged index files.
- Examples
- The following example re-indexes the orders in the current work area:
-
- USE sales INDEX salesman, territory NEW REINDEX
-
- This example re-indexes using a progress indicator:
-
- USE sales INDEX salesman, territory NEW REINDEX EVAL NtxProgress() EVERY 10
FUNCTION NtxProgress() LOCAL cComplete :=LTRIM(STR((RECNO()/; LastRec())*100)) @23,00 SAY "Indexing..."+ cComplete +"%" RETURNTRUE
-
-
- See Also
- DBCreateIndex(), DbCreateOrder(), DbReindex(), INDEX, PACK, SET INDEX, USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_RELEASE.xml b/docs/Help_Spanish/Topics/command_RELEASE.xml
deleted file mode 100644
index 84bfe1547d..0000000000
--- a/docs/Help_Spanish/Topics/command_RELEASE.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- RELEASE Command
-
- Clearingmemory variables
- Commands
- Deletingmemory variables
- Memory variables
- Memory variablesclearingdeleting
- RELEASE command
-
-
-
- RELEASE Command
-
-
- Purpose
- Releases public and private memory variables visible to the current routine by assigning a NIL value to them.
- Syntax
- RELEASE <idMemvarList> RELEASE ALL [LIKE | EXCEPT <Skeleton>]
- Arguments
- <idMemvarList>A list of private or public variables to release. Specifying a variable name that does not exist or is not visible raises a runtime error.
-
- ALLReleases all private variables and leaves public variables intact.
-
- LIKE | EXCEPT <Skeleton>
- Specifies a set of visible private variables to release (LIKE) or keep (EXCEPT) and leaves public variables intact. <Skeleton> can include literal characters as well as the standard wildcard characters, * and ?. If no variables match the <Skeleton>, nothing happens.
- Description
- This command does not actually delete the specified variables from memory like CLEAR ALL or CLEAR MEMORY do. Instead, it releases the value of the variables by assigning NIL to them. For this reason, variables that are hidden do not become visible until termination of the routine initiating the RELEASE operation.
-
- Note: Declared variables and constants are not affected by the RELEASE command.
-
- See Also
- CLEAR MEMORY, LOCAL, PRIVATE, PUBLIC, QUIT
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_RENAME.xml b/docs/Help_Spanish/Topics/command_RENAME.xml
deleted file mode 100644
index 005cedc678..0000000000
--- a/docs/Help_Spanish/Topics/command_RENAME.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- RENAME Command
-
- Commands
- Filesrenaming
- RENAME command
- Renamingfiles
-
-
-
- RENAME Command
-
-
- Purpose
- Change the name of a file to a new name.
- Syntax
- RENAME <xcSourceFile> TO <xcTargetFile>
- Arguments
- <xcSourceFile>The name of the source file to rename, including an optional drive, directory, and extension. If <xcSourceFile> does not exist, a runtime error is raised.
-
- TO <xcTargetFile>The name of the new file, including an optional drive, directory, and extension. If <xcTargetFile> exists or is open, RENAME does nothing.
-
- SetDefault() and SetPath() do not affect this command. It assumes the current Windows drive and directory if none is specified. No default extensions are supplied.
- Description
- If the target directory is different from the source directory, the file moves to the new directory.
-
- Warning! Files must be closed before renaming. Attempting to rename an open file will produce unpredictable results. When a database file is renamed, remember that any associated memo file must also be renamed. Failure to do so can compromise the integrity of your application.
- Examples
- This example renames a file, checking for the existence of the target file before beginning the RENAME operation:
-
- xcOldFile := "oldfile.txt" xcNewFile := "newfile.txt" IF !File(xcNewFile) RENAME (xcOldFile) TO (xcNewFile) ELSE ? "File already exists" ENDIF
-
- See Also
- COPY FILE, CurDir(), DELETE FILE, File(), FErase(), FRename(), RUN, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_REPEAT_UNTIL.xml b/docs/Help_Spanish/Topics/command_REPEAT_UNTIL.xml
deleted file mode 100644
index a9ea7131c4..0000000000
--- a/docs/Help_Spanish/Topics/command_REPEAT_UNTIL.xml
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-
- REPEAT UNTIL Statement
-
- Branching
- Conditional execution
- EXIT statement
- LOOP statement
- Looping
- Program control
- REPEAT Statement
- Statements
- UNTIL statement
-
-
-
- REPEAT UNTIL Statement
-
- Purpose
- Executes a loop until a condition is TRUE.
- Syntax
- REPEAT <Statements>... [EXIT] <Statements>... [LOOP] <Statements>... UNTIL <lCondition>
- Arguments
- <lCondition>The logical control expression for the REPEAT UNTIL loop.
-
-
- Description
- As long as the condition evaluates to FALSE then the loop will continue. When the condition evaluates to false, the REPEAT construct terminates and control passes to the statement immediately following the UNTIL.
-
- Use EXIT to terminate a REPEAT UNTIL structure based on a condition other than the REPEAT UNTIL condition. LOOP, by contrast, prevents execution of statements within a REPEAT UNTIL based on an intermediate condition, and returns to the most recent REPEAT UNTIL statement.
-
- Control structures can be nested to any depth. The only requirement is that each control structure be properly nested.
- Examples
- This example demonstrates a typical control structure for a simple grouped report:
-
- LOCAL cOldSalesman, nTotalAmount USE sales INDEX salesman NEW DOWHILE.NOT.EOF() cOldSalesman := Sales->Salesman nTotalAmount :=0 DOWHILE cOldSalesman = Sales->Salesman ; .AND.(.NOT.EOF()) ? Sales->Salesman, Sales->Amount nTotalAmount := nTotalAmount + Sales->Amount SKIP ENDDO ?"Total: ", nTotalAmount,"for", cOldSalesman ENDDO CLOSE sales
- This code fragment demonstrates how LOOP can be used to provide an intermediate processing condition:
-
- DOWHILE <lCondition> <Initial Processing>... IF <Intermediate Condition> LOOP ENDIF <Continued Processing>... ENDDO
- The next example demonstrates the use of DO WHILE to emulate a "repeat until looping" construct:
-
- LOCAL lMore :=TRUE DOWHILE lMore <Statements>... lMore := <lCondition> ENDDO
-
- Here, a DO WHILE loop moves sequentially through a database file:
-
- DOWHILE.NOT.EOF() <Statements>... SKIP ENDDO
- See Also
- BEGIN SEQUENCE, DBEval(), DO CASE, FOR, IF, RETURN, DO WHILE, EXIT, LOOP
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_REPLACE.xml b/docs/Help_Spanish/Topics/command_REPLACE.xml
deleted file mode 100644
index be7971de89..0000000000
--- a/docs/Help_Spanish/Topics/command_REPLACE.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-
-
-
- REPLACE Command
-
- Commands
- Databases
- Fieldsassigning new values
- REPLACE command
-
-
-
- REPLACE Command
-
-
- Purpose
- Assign new values to the contents of one or more fields in the current record.
- Syntax
- REPLACE <idField> WITH <uValue> [, <idField> WITH <uValue>...] [<Scope>] [WHILE <lCondition>] [FOR <lCondition>] [[IN|ALIAS] <workarea>]
- Arguments
- <idField>The name of the field variable to assign a new value. If <idField> is prefaced with an alias or declared using FIELD <idField> IN <idAlias>, the assignment takes place in the designated work area. Otherwise, the current work area is assumed.
-
- WITH <uValue>Defines the value to assign to <idField>.
-
-
-
-
-
- Description
- REPLACE performs the same function as the assignment operator (:=), except that it assumes field variables.
-
- Warning! When you REPLACE a key field, the index is updated and the relative position of the record pointer within the index is changed. This means that replacing a key field with a scope or a condition can yield an erroneous result. To update a key field, suppress the controlling order (with, for example, SET ORDER TO 0 or DBSetOrder(0)) before the REPLACE. This ensures that the record pointer moves sequentially in natural order and that all orders in the order list are updated properly.
-
- Shared mode: For a shared database, this command requires all records that it operates on to be locked. You can accomplish this using one or more record locks or a file lock, depending on the scope of the command.
- Examples
- This example shows a simple use of REPLACE:
-
- USE customer NEW APPEND BLANK USE invoices NEW APPEND BLANK
REPLACE Charges WITH Customer->Markup * Cost,; CustID WITH Customer->CustID,; Customer->TranDate WITHTODAY()
-
- Using assignment statements in place of the REPLACE command looks like this:
-
- Invoices->Charges := Customer->Markup *; Invoices->Cost Invoices->CustID := Customer->CustID Customer->TranDate :=TODAY()
-
- See Also
- COMMIT, DbRLock(), DbSetOrder(), FLock(), RLock(), SET ORDER
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_RESTORE.xml b/docs/Help_Spanish/Topics/command_RESTORE.xml
deleted file mode 100644
index 7373cf4591..0000000000
--- a/docs/Help_Spanish/Topics/command_RESTORE.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- RESTORE Command
-
- Commands
- Memory variablesrestoring
- RESTORE command
- Restoringmemory variables
-
-
-
- RESTORE Command
-
-
- Purpose
- Recreate public and private variables previously saved to a file and initialize them with their former values.
- Syntax
- RESTORE FROM <xcSourceFile> [ADDITIVE]
- Arguments
- <xcSourceFile>The name of the memory file (created, for example, with SAVE), including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension is .MEM.
-
- This command attempts to open <xcSourceFile> in shared mode. If the file does not exist, a runtime error is raised. If the file is successfully opened, the operation proceeds. If access is denied (because, for example, another process has exclusive use of the file), NetErr() is set to TRUE.
-
- ADDITIVECauses memory variables loaded from the memory file to be added to the existing pool of memory variables.
- Description
- The scope of the variable is not saved with the variable but is instead established when the variable is restored. Arrays and declared variables cannot be saved or restored.
-
- When memory variables are restored, they are recreated as private variables with the scope of the current procedure or function, unless they exist as public variables and you specify the ADDITIVE clause. If ADDITIVE is specified, public and private variables with the same names are overwritten unless hidden with PRIVATE. If ADDITIVE is not specified, all public and private variables are released before the memory file is loaded.
-
- When restoring variables that were saved in a CLIPPER program, the variable names are truncated to 10 characters. This is because CLIPPER honors only the first 10 characters and generates the .MEM file using only these characters. <%APP%>, however, honors all characters. For example, in CLIPPER, the two variable names ThisIsALongVariable and ThisIsALon refer to the same variable; this is not the case in <%APP%>.
-
- Note: Declared variables are not affected by the RESTORE command. If a variable has been declared in the current routine, and a variable with the same name is restored, only the declared variable is visible unless references to the restored variable are prefaced with the _MEMVAR-> alias.
- Examples
- This example demonstrates a typical application of SAVE and RESTORE. Here, memory variables containing screens are created using SAVE TO and RESTORE FROM:
-
- // Create and use a pseudo array of screens SAVE SCREEN TO cScreen1 SAVE ALL LIKE cScreen* TO Screens
<Statements>...
RESTORE FROM Screens ADDITIVE nNumber = "1" RESTORE SCREEN FROM ("cScreen" + nNumber)
-
- See Also
- LOCAL, PRIVATE, PUBLIC, SAVE, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_RETURN.xml b/docs/Help_Spanish/Topics/command_RETURN.xml
deleted file mode 100644
index aad7f5ba24..0000000000
--- a/docs/Help_Spanish/Topics/command_RETURN.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- RETURN Statement
-
- Closingroutines
- Program control
- RETURN statement
- Statements
-
-
-
- RETURN Statement
-
- Purpose
- Terminates a routine by returning control to the calling routine or operating system if executed from the Start() routine.
- Syntax
- RETURN [<uValue>]
- Arguments
- <uValue>May be specified in a function or method definition to designate its return value. Procedure definitions do not allow <uValue> as part of the RETURN statement. See the FUNCTION and METHOD entries in this guide for information about default return values if <uValue> is not specified.
- Description
- All private variables created and local variables declared in the current routine are released from memory when control returns.
- Examples
- These examples illustrate the general form of the RETURN statement in a procedure and in a function:
-
- PROCEDURE <idProcedure>() <Statements>... RETURN
FUNCTION <idFunction>() <Statements>... RETURN <uValue>
-
- The next example returns an array, created in a function, to a calling routine:
-
- FUNCTION PassArrayBack() PRIVATE aArray[10][10] aArray[1][1] = "myString" RETURN aArray
- See Also
- BEGIN SEQUENCE, FUNCTION, LOCAL, PRIVATE, PROCEDURE, PUBLIC, QUIT
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_RUN.xml b/docs/Help_Spanish/Topics/command_RUN.xml
deleted file mode 100644
index 8a87e88583..0000000000
--- a/docs/Help_Spanish/Topics/command_RUN.xml
+++ /dev/null
@@ -1,61 +0,0 @@
-
-
-
- RUN Command
-
- Applicationsexecuting
- Commands
- Executingapplications
- Program control
- RUN command
-
-
-
- RUN Command
-
-
- Purpose
- Executes a Windows or DOS application, a batch file, or a DOS command.
- Syntax
- RUN <xcCommandLine>
- Arguments
- <xcCommandLine>The command line is made up of two parts. The first part is one of the following:
-
-
An executable Windows or DOS program
-
A .PIF file
-
A .BAT file
-
Any resident DOS command
-
COMMAND.COM
-
-
- The second part is the command line parameters that will be passed to the specified application.
-
- NOTE: When running DOS programs, it is best to specify the file extension (for example, .EXE) rather than allow DOS to determine the default; otherwise, the RUN command will generate a temporary file named VODOSRUN.BAT to run the specified program.
- Description
- RUN executes a Windows or DOS program or a DOS command from within an application.
- The application name in <xcCommandLine> may optionally contain a path. If it does not, Windows will search for the application in the following order:
-
-
The current directory
-
The Windows directory
-
The Windows SYSTEM subdirectory
-
The directory that contains the currently executing module (.EXE or .DLL)
-
The directories in the PATH environment variable
-
All network drives
-
-
- If you use RUN to start a Windows application, the two applications will be run asynchronously. In other words, your <%APP%>application will not wait for the called application to finish but will continue to execute the instructions following the RUN command.
-
- If you specify a DOS application, a .BAT file, or a DOS command, Windows will create a DOS task and switch to it, thereby stopping your application. During the execution of the DOS task, however, the user may switch back to the calling application. The calling application will automatically resume execution after the DOS task terminates.
- If you run a DOS program, you might consider setting up a .PIF file (using the PIF Editor provided by Windows) to finetune the execution environment. For example, you might specify that the DOS application is to be executed in a window rather than in full-screen mode. If you are using a .PIF file, pass the name of the .PIF file to the RUN command instead of the name of your application or give it the same base name as your application and put it into the same directory. In the latter case, Windows will pick it up automatically if you pass the application name to the RUN command.
- Examples
- This example starts the Windows Notepad editor on a file called DATA.TXT:
-
- RUN notepad data.txt
-
- One of the options you can give your users is direct access to DOS. Do this with:
-
- RUN command.com
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SAVE.xml b/docs/Help_Spanish/Topics/command_SAVE.xml
deleted file mode 100644
index 4753c51c46..0000000000
--- a/docs/Help_Spanish/Topics/command_SAVE.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- SAVE Command
-
- Commands
- Copyingmemory variables
- Memory variables
- Memory variablescopying to disk filessaving
- SAVE command
- SAVE TO command
- Savingmemory variables
-
-
-
- SAVE Command
-
-
- Purpose
- Copy public and private memory variables visible within the current routine to a disk file.
- Syntax
- SAVE TO <xcTargetFile> [ALL [LIKE | EXCEPT <Skeleton>]
- Arguments
- <xcTargetFile>The name of the file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension is .MEM.
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
-
- ALLSaves all private and public variables.
-
- LIKE | EXCEPT <Skeleton>
- Specifies a set of visible public and private variables to save (LIKE) or exclude (EXCEPT). <Skeleton> can include literal characters as well as the standard wildcard characters, * and ?. If no variables match the <Skeleton>, nothing happens.
- Description
- The scope of the variable is not saved but is instead established when the variable is restored. Arrays and declared variables cannot be saved or restored.
- Examples
- This example saves all visible private and public variables to TEMP.MEM:
- PRIVATE cOne := "1" SAVE ALL TO temp
-
- This example saves all visible private and public variables with names beginning with c to MYVARS.MEM:
-
- SAVE ALL LIKE c* TO myvars
-
- This example saves all visible private and public variables with names that do not begin with c to MYVARS2.MEM:
-
- SAVE ALL EXCEPT c* TO myvars2
-
- See Also
- PRIVATE, PUBLIC, RESTORE, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SEEK.xml b/docs/Help_Spanish/Topics/command_SEEK.xml
deleted file mode 100644
index 336a70154b..0000000000
--- a/docs/Help_Spanish/Topics/command_SEEK.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- SEEK Command
-
- Commands
- Databases
- Findingrecords
- Index/order
- Recordsfinding
- SEEK command
-
-
-
- SEEK Command
-
-
- Purpose
- Search an order for the first key matching the specified expression, position the record pointer to the corresponding record, and set the Found() flag.
- Syntax
- SEEK <uKeyValue> [SOFTSEEK] [LAST] [[IN|ALIAS] <workarea>]
- Arguments
- <uKeyValue>An expression to match with an order key value.
-
- SOFTSEEKIf SOFTSEEK is specified (or if SetSoftSeek() is TRUE), the record pointer is positioned to the record with the next higher key value, and Found() returns FALSE after an unsuccessful SEEK. EoF() returns TRUE only if there are no keys in the order greater than <uKeyValue>.
-
- If SOFTSEEK is not specified and SetSoftSeek() is FALSE, the record pointer is positioned to LastRec() + 1, EOF() returns TRUE, and Found() returns FALSE after an unsuccessful SEEK.
-
- LASTIf LAST is specified, SEEK finds the last occurrence of the specified key value. If LAST is not specified, SEEK finds the first occurrence.
-
-
- Description
- If the SEEK is successful, Found() is set to TRUE and the record pointer is positioned to the matching record.
- Examples
- The following example searches for "Doe" using the SEEK command:
-
- USE customer NEW SET INDEX TO customer SEEK "Doe"
IF Found() . . <Statements> . ENDIF
-
- The following example performs a soft seek for "Doe", using the SOFTSEEK clause of the SEEK command. Note that the SOFTSEEK clause does not have any effect of the SetSoftSeek() flag:
-
- USE customer NEW SET INDEX TO customer
? SetSoftSeek()// FALSE SEEK "Doe" SOFTSEEK ? SetSoftSeek()// Still FALSE
IF!Found() ? Customer->Name// Returns next logical // name after "Doe" ENDIF
-
- See Also
- DbSeek(), DbSetIndex(), DbSetOrder(), SET INDEX, SET ORDER
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SELECT.xml b/docs/Help_Spanish/Topics/command_SELECT.xml
deleted file mode 100644
index 7069d548ee..0000000000
--- a/docs/Help_Spanish/Topics/command_SELECT.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-
-
-
- SELECT Command
-
- Commands
- Databases
- SELECT command
- Selectingwork areas
- Work areaschanging
-
-
-
- SELECT Command
-
-
- Purpose
- Change the current work area.
- Syntax
- SELECT <xnWorkArea> | <xcAlias>
- Arguments
- <xnWorkArea>A number from 0 to 250 that specifies the work area to select.
-
- <xcAlias>The alias identifier for the work area to select. If there is no open database file associated with the specified alias, a runtime error is raised.
- Description
- SELECT causes the specified work area to become the current work area. All subsequent database operations will apply to this work area unless another work area is explicitly specified for an operation.
- SELECT is functionally equivalent to DBSelectArea().
- Notes
- Selecting 0: Selecting work area 0 causes the lowest numbered unoccupied work area to become the current work area. Using SELECT 0 before opening a file is equivalent to USE with the NEW option.
-
- Aliased expressions: The alias operator (->) can temporarily select a work area while an expression is evaluated and automatically restore the previously selected work area afterward.
- Examples
- This example opens a series of database files by selecting each work area by number, then using each database file in that work area:
-
- SELECT 1 USE customer SELECT 2 USE invoices SELECT 3 USE parts SELECT customer
-
- To make your code independent of the work area number used, a better method is to open each database in the next available work area by specifying the NEW clause on the USE command line. In this example USE...NEW is employed instead of SELECT 0, then USE:
-
- USE customer NEW USE invoices NEW SELECT customer
-
- This code fragment changes work areas while saving the current work area name to a variable by using the Select() function. After executing an operation for the new work area, the original work area is restored:
-
- nLastArea := Select() USE newfile NEW
<Statements>...
SELECT (nLastArea)s
-
- See Also
- Alias(), DbSelectArea(), Select(), USE, Used()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_ANSI.xml b/docs/Help_Spanish/Topics/command_SET_ANSI.xml
deleted file mode 100644
index 75a1aa0061..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_ANSI.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- SET ANSI Command
-
- ANSI format
- Commands
- Converting to OEM characters
- Environment
- OEM format
- SET ANSI command
-
-
-
-
- SET ANSI Command
-
-
- Purpose
- Change the setting that determines whether database files are created using ANSI or OEM format and whether certain text file operations convert between the two character sets.
- Syntax
- SET ANSI ON | OFF | (<lToggle>)
- Arguments
- ON, OFF, lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
- Description
- SET ANSI is functionally equivalent to SetAnsi().
-
- See Also
- SetAnsi()
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_CENTURY.xml b/docs/Help_Spanish/Topics/command_SET_CENTURY.xml
deleted file mode 100644
index 10520b4ccb..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_CENTURY.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- SET CENTURY Command
-
- Commands
- Dates
- Datessettingusing century digits
- Digits
- Environmentusing century digits
- SET CENTURY command
- Settingdates
-
-
-
- SET CENTURY Command
-
-
- Purpose
- Change the setting that determines whether to include or omit century digits in the date format.
- Syntax
- SET CENTURY ON | OFF | (<lToggle>)
- Arguments
- ON, OFF, lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
- Description
- SET CENTURY is functionally equivalent to SetCentury().
-
- See Also
- CToD(), DToC(), DToS(), SetCentury(), SetDateCountry(), SetDateFormat(), SetEpoch(),Today()
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_COLLATION.xml b/docs/Help_Spanish/Topics/command_SET_COLLATION.xml
deleted file mode 100644
index f013fccd00..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_COLLATION.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- SET COLLATION Command
-
- Collating strings
- Commands
- SET COLLATION command
- Stringscollation
-
-
-
- SET COLLATION Command
-
-
- Purpose
- Change the setting that determines the internal collation routine used for string comparisons.
- Syntax
- SET COLLATION TO WINDOWS | clipper
- Description
- SET COLLATION is functionally equivalent to SetCollation(), which you can refer to for more information and examples.
-
- See Also
- SET INTERNATIONAL, SetCollation()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_COLOR.xml b/docs/Help_Spanish/Topics/command_SET_COLOR.xml
deleted file mode 100644
index 7b55db8f3c..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_COLOR.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- SET COLOR Command
-
- Colorssetting
- Commands
- SET COLOR command
- SET COLOUR command
- Settingcolors
- Terminal window
-
-
-
- SET COLOR Command
-
-
- Purpose
- Changes the setting that determines the current color for the terminal window.
- Syntax
- SET COLOR | COLOUR TO [<xcColorString>]
- Description
- SET COLOR is functionally equivalent to SetColor(). SET COLOR TO with no arguments is the same as SetColor(NULL_STRING), returning to the default color settings.
- Examples
- This example uses the unselected setting to make the current GET red on white while the rest are black on white:
- FUNCTION Start ASVOID SETCOLORTO gr+/B // Yellow on Blue CLEARSCREEN ? "Hello world"
-
- See Also
- SetColor()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DATE.xml b/docs/Help_Spanish/Topics/command_SET_DATE.xml
deleted file mode 100644
index 7782e25a82..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DATE.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- SET DATE Command
-
- Commands
- Datessetting date format
- SET DATE command
- SET DATE TO command
- Settingdate formats
-
-
-
- SET DATE Command
-
-
- Purpose
- Change the setting that determines the <%APP%> date format by selecting from a list of constants with corresponding date formats.
- Syntax
- SET DATE [TO] <kCountrySetting>
- Description
- SET DATE is functionally equivalent to SetDateCountry().
- Examples
- This example illustrates various system-defined country settings:
-
- SET DATE German ? Today()// Result: 15.10.19 SET DATE Ansi ? Today()// Result: 19.10.15
-
- See Also
- CToD(), DToC(), DToS(), SetCentury(), SetDateCountry(), SetDateFormat(), SetEpoch(),Today()
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DATE_FORMAT.xml b/docs/Help_Spanish/Topics/command_SET_DATE_FORMAT.xml
deleted file mode 100644
index cf10d2e609..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DATE_FORMAT.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- SET DATE FORMAT Command
-
- Commands
- Datessetting date format
- SET DATE FORMAT command
- Settingdate formats
-
-
-
- SET DATE FORMAT Command
-
-
- Purpose
- Change the setting that determines the <%APP%> date format.
- Syntax
- SET DATE FORMAT [TO] <cDateFormat>
- Description
- SET DATE FORMAT is functionally equivalent to SetDateFormat().
- Examples
- In this example the FORMAT clause directly specifies the date format:
-
- SET DATE FORMAT "yyyy:mm:dd" SetCentury(TRUE) ? Today()// Result: 2019:10:15
-
- See Also
- CToD(), DToC(), DToS(), SetCentury(), SetDateCountry(), SetDateFormat(), SetEpoch(),Today(),
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DECIMALS.xml b/docs/Help_Spanish/Topics/command_SET_DECIMALS.xml
deleted file mode 100644
index c9fee65bd5..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DECIMALS.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- SET DECIMALS Command
-
- Commands
- Decimalssetting number of places
- Displayingnumbers
- Environment
- SET DECIMALS command
- Settingdecimal places
-
-
-
- SET DECIMALS Command
-
-
- Purpose
- Changes the setting that determines the number of decimal places used to display numbers.
- Syntax
- SET DECIMALS TO [<nDecimals>]
- Arguments
- nDecimalsSpecifies the minimum number of decimal places to display, with a default of two. The maximum number is 18 decimal places, and the minimum is zero.
- Description
- SET DECIMALS TO with no argument is equivalent to SET DECIMALS TO 0. SET DECIMALS is functionally equivalent to SetDecimal().
-
- See Also
- SetDecimal(), SetDecimalSep(), SetFixed(),
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DEFAULT.xml b/docs/Help_Spanish/Topics/command_SET_DEFAULT.xml
deleted file mode 100644
index 673f14ba66..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DEFAULT.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- SET DEFAULT Command
-
- Commands
- Directoriessetting default
- Drivessetting default
- Environment
- SET DEFAULT command
- Setting
- Settingdefault drivesdirectories
-
-
-
- SET DEFAULT Command
-
-
- Purpose
- Change the setting that determines the <%APP%> default drive and directory.
- Syntax
- SET DEFAULT TO [<xcPathspec>]
- Description
- SET DEFAULT is functionally equivalent to SetDefault().
-
- See Also
- CurDir(), GetDefault(), GetCurPath, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DELETED.xml b/docs/Help_Spanish/Topics/command_SET_DELETED.xml
deleted file mode 100644
index 1652c938c1..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DELETED.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- SET DELETED Command
-
- Commands
- Databases
- Deleting
- Records
- Recordsdeleting
- SET DELETED command
-
-
-
- SET DELETED Command
-
-
- Purpose
- Change the setting that determines whether to ignore or include records that are marked for deletion.
- Syntax
- SET DELETED ON | OFF | (<lToggle>)
- Arguments
- ON Specifies that commands that operate on records, including records in related tables, using a scope, ignore records that are marked for deletion.
- OFFSpecifies that commands that operate on records, including records in related tables, using a scope, can access records marked for deletion. (Default)
- lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
- Description
- SET DELETED is functionally equivalent to SetDeleted().
-
- See Also
- DELETE, DbSetFilter(), Deleted(), RECALL, SET FILTER, SetDeleted()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DESCENDING.xml b/docs/Help_Spanish/Topics/command_SET_DESCENDING.xml
deleted file mode 100644
index 26ab4af470..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DESCENDING.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- SET DESCENDING Command
-
- Commands
- Databases
- Index/order
- SET DESCENDING command
-
-
-
- SET DESCENDING Command
-
-
- Purpose
- Change the descending flag of the controlling order.
- Syntax
- SET DESCENDING ON | OFF | (<lToggle>)
-
- Note: The initial default of this setting depends on whether the controlling order was created with descending as an attribute.
- Arguments
- ON
- OFF
- lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF
- Description
- SET DESCENDING is functionally equivalent to OrdDescend().
-
- See Also
- OrdDescend()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DIGITFIXED.xml b/docs/Help_Spanish/Topics/command_SET_DIGITFIXED.xml
deleted file mode 100644
index 0fa6ca4130..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DIGITFIXED.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- SET DIGITFIXED Command
-
- Commands
- Digitsfixing the number of
- Displayingnumbers
- Environment
- SET DIGITFIXED command
-
-
-
- SET DIGITFIXED Command
-
-
- Purpose
- Changes the setting that fixes the number of digits used to display numeric output.
- Syntax
- SET DIGITFIXED ON | OFF | (<lToggle>)
- Arguments
- ON
- OFF
- lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
- Description
- SET DIGITFIXED is functionally equivalent to SetDigitFixed().
-
- See Also
- SetDigitFixed()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DIGITS.xml b/docs/Help_Spanish/Topics/command_SET_DIGITS.xml
deleted file mode 100644
index 06bfa2c617..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DIGITS.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- SET DIGITS Command
-
- Commands
- Decimalssetting number of digits
- Digitssetting decimals
- Displayingnumbers
- Environment
- SET DIGITS command
-
-
-
- SET DIGITS Command
-
-
- Purpose
- Changes the setting that determines the number of digits that will be shown to the left of the decimal point when a number is displayed.
- Syntax
- SET DIGITS TO [<nDigits>]
- Description
- SET DIGITS is functionally equivalent to SetDigit().
-
- See Also
- SetDigit()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_DRIVER.xml b/docs/Help_Spanish/Topics/command_SET_DRIVER.xml
deleted file mode 100644
index 9f52e55ac6..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_DRIVER.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- SET DRIVER Command
-
- Commands
- Databases
- Driverschanging default RDD
- Environment
- RDDschanging default RDD
- SET DRIVER command
-
-
-
- SET DRIVER Command
-
-
- Purpose
- Change the default RDD for the application.
- Syntax
- SET DRIVER TO <idDriverName>
- Description
- SET DRIVER is functionally equivalent to DBSetDriver().
-
- See Also
- DbSetDriver()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_EPOCH.xml b/docs/Help_Spanish/Topics/command_SET_EPOCH.xml
deleted file mode 100644
index 6a26483687..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_EPOCH.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- SET EPOCH Command
-
- Commands
- Datessetting
- Digitsdates without century digits
- Epochsepochssetting
- SET EPOCH command
- Settingdates
-
-
-
- SET EPOCH Command
-
-
- Purpose
- Change the setting that determines how dates without century digits are interpreted.
- Syntax
- SET EPOCH TO <nYear>
- Description
- SET EPOCH is functionally equivalent to SetEpoch().
-
- See Also
- CToD(), DToC(), DToS(), SetCentury(), SetDateCountry(), SetDateFormat(), SetEpoch(),Today()
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_EXACT.xml b/docs/Help_Spanish/Topics/command_SET_EXACT.xml
deleted file mode 100644
index 5687a61428..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_EXACT.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- SET EXACT Command
-
- Commands
- Exact
- SET EXACT command
-
-
-
- SET EXACT Command
-
-
- Purpose
- Toggles and exact match for character string comparisons.
- Syntax
- SET EXACT ON | OFF | (<lToggle>)
- Arguments
- ON, OFF, lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
- Description
- SET EXACT is functionally equivalent to SetExact().
-
- See Also
- SetExact()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_EXCLUSIVE.xml b/docs/Help_Spanish/Topics/command_SET_EXCLUSIVE.xml
deleted file mode 100644
index 943d46fb1a..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_EXCLUSIVE.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- SET EXCLUSIVE Command
-
- Commands
- Concurrency control
- Databases
- Environment
- Exclusive modesetting
- Filesopening
- Modessetting
- Openingfiles
- SET EXCLUSIVE command
- Shared modesetting
-
-
-
- SET EXCLUSIVE Command
-
-
- Purpose
- Change the setting that determines whether to open database files in exclusive or shared mode.
- Syntax
- SET EXCLUSIVE ON | OFF | (<lToggle>)
- Arguments
- ON Limits accessibility of a table opened on a network to the user who opened it. The table isn't accessible to other users on the network. Unlike FLOCK( ), SET EXCLUSIVE ON also prevents all other users from having read-only access. A file can also be opened on a network for exclusive use by including the EXCLUSIVE clause with the USE command. It is not necessary to perform record or file locking on a table opened for exclusive use.
- Opening a table for exclusive use ensures that the file cannot be changed by other users. For some commands, execution is not possible until a table is opened for exclusive use. These commands are PACK, REINDEX, and ZAP.
- OFFAllows a table opened on a network to be shared and modified by any user on the network.
- lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
- Description
- SET EXCLUSIVE is functionally equivalent to SetExclusive().
- Changing the setting of SET EXCLUSIVE does not change the status of previously opened tables. For example, if a table is opened with SET EXCLUSIVE set to ON, and SET EXCLUSIVE is later changed to OFF, the table retains its exclusive-use status.
-
- See Also
- FLock(), NetErr(), RLock(), SetExclusive(), USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_FILTER.xml b/docs/Help_Spanish/Topics/command_SET_FILTER.xml
deleted file mode 100644
index dbffe04edd..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_FILTER.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- SET FILTER Command
-
- Clearing filters
- Commands
- Databases
- Filters
- Filtersclearingsetting
- SET FILTER command
- Settingfilters
-
-
-
- SET FILTER Command
-
-
- Purpose
- Set or clear a filter condition for the current work area.
- Syntax
- SET FILTER TO [<lCondition>]
- Arguments
- TO <lCondition>The condition used to filter records.
-
- SET FILTER TO without an argument clears the filter condition.
- Description
- When a filter is set, records that do not meet the filter condition are not logically visible. The filter condition can be returned as a string using the DBFilter() function.
- That is, database operations which act on logical records will not consider these records except to access them specifically by record number. So, for example, you can GOTO a filtered record or process one using the RECORD <nRecord> scope.
-
- Note: Once a filter is set, it is not activated until the record pointer is moved from its current position. You can use GO TOP to activate it.
-
- SET FILTER TO when specified with a condition is functionally equivalent to DbSetFilter() with the condition expressed as a code block and a string. SET FILTER TO with no arguments is equivalent to DBClearFilter().
-
- Tip: If the RDD you are using supports optimization, use SET OPTIMIZE to control whether the RDD will optimize the filter search based on the available orders in the work area.
- Notes
- Visibility:As with SetDeleted(), a filter has no effect on INDEX and REINDEX. To create a conditional index, use the FOR condition of the INDEX command.
- Examples
- This example filters EMPLOYEE.DBF to only those records where the age is greater than 50:
-
- USE employee INDEX name NEW SETFILTERTO Age > 50 LIST Lastname, Firstname, Age, Phone SETFILTERTO
-
- See Also
- DbClearFilter(), DbFilter(),DbSetFilter(), SET OPTIMIZE, SetDeleted()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_FIXED.xml b/docs/Help_Spanish/Topics/command_SET_FIXED.xml
deleted file mode 100644
index e2bc5f3138..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_FIXED.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- SET FIXED Command
-
- Commands
- Decimalssetting number of digits
- Digitssetting number of decimal digits
- Displayingnumbers
- Environment
- SET FIXED command
- Settingdecimal digits
-
-
-
- SET FIXED Command
-
-
- Purpose
- Changes the setting that fixes the number of decimal digits used to display numbers.
- Syntax
- SET FIXED ON | OFF | (<lToggle>)
- Arguments
- ON, OFF, lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
- Description
- SET FIXED is functionally equivalent to SetFixed().
-
- See Also
- Exp(), Log(), SetDecimal), SetFixed(), SQrt(), Val()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_INDEX.xml b/docs/Help_Spanish/Topics/command_SET_INDEX.xml
deleted file mode 100644
index 6d0f5a5a7c..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_INDEX.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-
-
-
- SET INDEX Command
-
- Commands
- Databases
- Index filesopening
- Index/order
- Openingindex files
- Ordersadding to the order list
- SET INDEX command
-
-
-
- SET INDEX Command
-
-
- Purpose
- Open one or more index files and add their orders to the order list in the current work area.
- Syntax
- SET INDEX TO [<xcIndexFileList> [ADDITIVE]]
- Arguments
- TO <xcIndexFileList>The names of the index files to open, including an optional drive, directory, and extension for each. See SetDefault() and SetPath() for file searching and creation rules. The default extension is determined by the RDD and can be obtained using DBOrderInfo(DBOI_INDEXEXT).
-
- If a file in the list does not exist, a runtime error is raised. If the file exists, this command attempts to open it in the same mode as the corresponding database file. If access is denied - because, for example, another process is using the file and this one is asking for exclusive use - NetErr() is set to TRUE. Otherwise, the file opens succesfully, and the command proceeds to the next file in the list.
-
- Concurrency conflicts with index files are rare since they should be used with only one database file. If a concurrency problem arises, it usually occurs when you attempt to open the database file.
-
- SET INDEX TO with no file name clears the current order list.
-
- ADDITIVEAdds the orders from the indicated index files to the current order list, leaving the controlling order intact. If not specified, a new order list is constructed from the indicated index files, replacing the current order list.
- Description
- If no order list exists for the work area or if SET INDEX is replacing the current order list, the type of RDD determines whether or not the controlling order is set. For RDDs that support only single-order index files (such as DBFNTX), the controlling order is set to the order in the specified index file. For RDDs that support multi-order index files (such as DBFMDX), you usually need to set the controlling order explicitly (using, for example, SET ORDER or DbSetOrder()). Otherwise, the data file may be processed in natural order even though there is an order list in effect.
-
- After the new index files are opened, the work area is positioned to the first logical record in the controlling order and all subsequent database operations process the records using the controlling order.
-
- During database processing, all orders in the order list are updated whenever a key value is added or changed, respecting any for condition or unique flag in the order. To change the controlling order without affecting the current order list, use SET ORDER or DBSetOrder(). To find out information about a particular order or index file, use DBOrderInfo().
-
- SET INDEX TO when specified with an index file list is functionally equivalent to using several DBSetIndex() function calls. If no ADDITIVE clause is specified, the command calls DBClearFilter() first.
- Examples
- This example opens a database and several associated index files:
-
- USE sales NEW SETINDEXTO sales, sales1, sales2
-
- The next example opens an index file without closing any that are already open:
-
- SETINDEXTO sales3 ADDITIVE
-
- See Also
- CLOSE, DBClearIndex(),DbOrderInfo(), DBSetIndex(), DBSetOrder(),INDEX, REINDEX, SET ORDER, SetDefault(), SetPath() USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_INTERNATIONAL.xml b/docs/Help_Spanish/Topics/command_SET_INTERNATIONAL.xml
deleted file mode 100644
index 6c992c01e9..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_INTERNATIONAL.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- SET INTERNATIONAL Command
-
- Applicationssetting international mode
- Commands
- International modesetting
- Modessetting
- SET INTERNATIONAL command
- Settinginternational mode
-
-
-
- SET INTERNATIONAL Command
-
-
- Purpose
- Change the setting that determines the international mode for the application.
- Syntax
- SET INTERNATIONAL TO WINDOWS | CLIPPER
- Description
- SET INTERNATIONAL is functionally equivalent to SetInternational(), which you can refer to for more information and examples.
-
- See Also
- SET COLLATION, SetInternational()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_MEMOBLOCK.xml b/docs/Help_Spanish/Topics/command_SET_MEMOBLOCK.xml
deleted file mode 100644
index 071b7d6eea..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_MEMOBLOCK.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- SET MEMOBLOCK Command
-
- Commands
- Databases
- Memo files
- SET MEMOBLOCK command
- Settingblock size for memo files
-
-
-
- SET MEMOBLOCK Command
-
-
- Purpose
- Change the block size for memo files.
- Syntax
- SET MEMOBLOCK TO <nSize>
- Description
- The initial memo file block size depends on the RDD. For most drivers that support the .DBT memo file format, it is 512 bytes. However, if you are using BLOB files (.DBV) via inheritance from the DBFBLOB driver, the default is 1.
- SET MEMOBLOCK is functionally equivalent to calling RDDInfo(_SET_MEMOBLOCKSIZE, <nSize>).
-
- See Also
- RDDInfo()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_OPTIMIZE.xml b/docs/Help_Spanish/Topics/command_SET_OPTIMIZE.xml
deleted file mode 100644
index d25b927ee6..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_OPTIMIZE.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- SET OPTIMIZE Command
-
- Commands
- Environment
- Filtersoptimizing
- Index/order
- Optimizing filters
- SET OPTIMIZE command
-
-
-
- SET OPTIMIZE Command
-
-
- Purpose
- Change the setting that determines whether to optimize using the open orders when processing a filtered database file.
- Syntax
- SET OPTIMIZE ON | OFF | (<lToggle>)
- Arguments
- ONTurns optimization on.
-
- OFFTurns optimization off.
-
- <lToggle>Turns optimization on if TRUE, or off if FALSE.
-
- Note: The initial default of this setting depends on the RDD. Check RDDInfo(_SET_OPTIMIZE) to find out the setting for the RDD in use for the current work area.
- Description
- For RDDs that support optimization, such as DBFCDX, SET OPTIMIZE determines whether to optimize filters based on the orders open in the current work area. If this flag is ON, the RDD will optimize the search for records that meet the filter condition to the fullest extent possible, minimizing the need to read the actual data from the database file.
- If this flag is OFF, the RDD will not optimize.
-
- See Also
- DbSetFilter(), RDDInfo(), SET FILTER
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_ORDER.xml b/docs/Help_Spanish/Topics/command_SET_ORDER.xml
deleted file mode 100644
index 2690eea7b7..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_ORDER.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- SET ORDER Command
-
- Commands
- Databases
- Index/order
- Orderssetting controlling order
- SET ORDER command
- Settingcontrolling order
-
-
-
- SET ORDER Command
-
-
- Purpose
- Set the controlling order for the current work area.
- Syntax
- SET ORDER TO [<nPosition> | TAG <xcOrder> [IN <xcIndexFile>]]
- Arguments
- <nPosition> | TAG <xcOrder>
- The name of the new controlling order, or a number representing its position in the order list. The preferred method is to use the order name, since the position may be difficult to determine using multiple-order indexes. Specifying a value of 0 has the special effect of returning the database file to its natural order. Specifying an invalid value will raise a runtime error.
-
- Note: The syntax of this command differs from other Xbase dialects where the TAG keyword is optional.
-
- IN <xcIndexFile>The name of an index file, including an optional drive and directory (no extension should be specified). Use this argument to avoid ambiguity when two or more orders with the same name exist in different index files.
-
- If <xcIndexFile> is not open in the current process or work area, a runtime error is raised.
-
- SET ORDER TO with no arguments is the same as SET ORDER TO 0.
- Description
- The controlling order determines the order in which the database file is processed. No matter which order is currently controlling the logical order of the database file, all orders in the order list are properly updated when records are added or updated. This is true even if you SET ORDER TO 0. Changing the controlling order does not move the record pointer.
-
- Before using this command, use SET INDEX or DBSetIndex() to add orders from an index file to the order list.
- SET ORDER is functionally equivalent to DBSetOrder().
- Examples
- The following example illustrates a typical use of SET ORDER to select between several orders:
-
- USE customer NEW INDEXON Lastname TO names INDEXON City + State TO region SETINDEXTO names, region // SET ORDER TOTAG "Region" ? DBOrderInfo(DBOI_EXPRESSION) // Result: City + State
SET ORDER TO 0 ? DBOrderInfo(DBOI_EXPRESSION) // Result: NULL_STRING
SET ORDER TOTAG "Names" ? DBOrderInfo(DBOI_EXPRESSION) // Result: Lastname
-
- See Also
- DbOrderInfo(), DbSeek(),DbSetIndex(), DbSetOrder(), INDEX, SEEK, SET INDEX, USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_PATH.xml b/docs/Help_Spanish/Topics/command_SET_PATH.xml
deleted file mode 100644
index 834e77e932..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_PATH.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- SET PATH Command
-
- Commands
- Environment
- Filesopening
- Openingfiles
- Pathsfor searching
- SET PATH command
- Settingsearch path
-
-
-
- SET PATH Command
-
-
- Purpose
- Change the setting that determines the <%APP%> search path for opening files.
- Syntax
- SET PATH TO [<xcPathSpecList>]
- Description
- SET PATH is functionally equivalent to SetPath(), except that semicolons are not allowed as separators in SET PATH's <xcPathSpecList>.
-
- See Also
- CurDir(), GetCurPath, SetDefault(), SetPath()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_RELATION.xml b/docs/Help_Spanish/Topics/command_SET_RELATION.xml
deleted file mode 100644
index 5a4d1dfaeb..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_RELATION.xml
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
- SET RELATION Command
-
- Commands
- Databases
- SET RELATION command
- Settingwork area relations
- Work areasrelating
-
-
-
- SET RELATION Command
-
-
- Purpose
- Link a parent work area to one or more child work areas using a key expression, record number, or numeric expression.
- Syntax
- SET RELATION TO [<uRecID> INTO <xcAlias>] [, [TO] <uRecId> INTO <xcAlias>...] [ADDITIVE] [SCOPED]
- Arguments
- TO <uRecID>Performs an <xcAlias>->DBSeek(<uRecID>) operation if the child work area has a controlling order; otherwise, performs an <xcAlias>->DBGoTo(<uRecID>) operation. The operation serves to position the child work area to a matching index key value or record number each time the record pointer moves in the parent work area.
-
- INTO <xcAlias>The alias identifier for the child work area. If there is no open database file associated with the specified alias, a runtime error is raised.
-
- ADDITIVESpecifies that relations are to be added to the existing relations in the work area. If not specified, existing relations are cleared before the new ones are set.
-
- SCOPEDCauses the SET RELATION command to map to the OrdSetRelation(). If not specified, SET RELATION maps to DBSetRelation().
-
- SET RELATION TO with no arguments clears all relations defined in the current work area.
- Description
- Each parent work area can be linked to as many as eight child work areas.
-
- Relating work areas synchronizes the child work area with the parent work area. This is achieved by automatically repositioning the child work area whenever the parent work area moves to a new record.
-
- SET RELATION TO when specified with a list of expressions and alias names is functionally equivalent to using several DBSetRelation() (or OrdSetRelation(), if SCOPED is specified) function calls. If no ADDITIVE clause is specified, the command calls DBClearRelation() first.
- Notes
- Soft seeking: Seek operations that occur as part of relational positioning are never soft seeks (they do not respect the SetSoftSeek() flag). If a relational movement is unsuccessful, the child work area is positioned to LastRec() + 1, its Found() status returns FALSE, and its EoF() status returns TRUE.
-
- Cyclical relations: Do not relate a parent work area to itself either directly or indirectly.
-
- Record number relations: To relate two work areas based on matching record numbers, use RecNo() for the SET RELATION TO expression and make sure the child work area has no active indexes.
- Examples
- This example relates three work areas in a multiple parent-child configuration with CUSTOMER related to both INVOICES and ZIP:
-
- USE invoices INDEX invoices NEW USE zip INDEX zipcode NEW USE customer NEW SET RELATION TO CustNum INTO Invoices, Zipcode INTO Zip LIST Customer, Zip->City, Invoices->Number, Invoices->Amount
-
- Sometime later, you can add a new child relation using the ADDITIVE clause, like this:
-
- USE backorder INDEX backorder NEW SELECT customer SETRELATIONTO CustNum INTO Backorder ADDITIVE
-
- See Also
- DbGoTo(), DBRelation(), DBRSelect(),, DbSeek(), DbSetIndex(), DbSetOrder() , DBSetRelation(), Found(), OrdSetRelation(), RecNo(),SET INDEX, SET ORDER, SetSoftSeek()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_SCOPE.xml b/docs/Help_Spanish/Topics/command_SET_SCOPE.xml
deleted file mode 100644
index 4fe8c2df04..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_SCOPE.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- SET SCOPE Command
-
- Commands
- Databases
- Index/order
- Scoping key values
- SET SCOPE command
-
-
-
- SET SCOPE Command
-
-
- Purpose
- Change the top boundary for scoping key values in the controlling order.
- Syntax
- SET SCOPE TO [<uNewTop> [, <uNewBottom>]]
- Arguments
- <uNewTop>The top range of key values that will be included in the controlling order's current scope. <uNewTop> can be an expression that matches the data type of the key expression in the controlling order or a code block that returns the correct data type.
-
- <uNewBottom>The bottom range of key values that will be included in the controlling order's current scope. <uNewBottom> can be an expression that matches the data type of the key expression in the controlling order or a code block that returns the correct data type.
-
- Note: If <uNewBottom> is not specified, <uNewTop> is taken for both the top and bottom range values.
- Description
- SET SCOPE, when used with no arguments, clears the top and bottom scopes; this is equivalent to OrdScope(0, NIL) followed by OrdScope(1, NIL). If <uNewTop> is specified alone, SET SCOPE sets the top and bottom scope to the indicated value (that is, OrdScope(0, <uNewTop>) followed by OrdScope(1, <uNewTop>). f both <uNewTop> and <uNewBottom> are specified, SET SCOPE sets the top and bottom scope as indicated (that is, OrdScope(0, <uNewTop>), followed by OrdScope(1, <uNewBottom>)).
-
- See Also
- OrdScope()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_SCOPEBOTTOM.xml b/docs/Help_Spanish/Topics/command_SET_SCOPEBOTTOM.xml
deleted file mode 100644
index 57cc6b26d9..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_SCOPEBOTTOM.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- SET SCOPEBOTTOM Command
-
- Commands
- Databases
- Index/order
- Scoping key values
- SET SCOPEBOTTOM command
-
-
-
- SET SCOPEBOTTOM Command
-
-
- Purpose
- Change the bottom boundary for scoping key values in the controlling order.
- Syntax
- SET SCOPEBOTTOM TO [<uNewBottom>]
- Description
- SET SCOPEBOTTOM, when used with the <uNewBottom> argument, is functionally equivalent to OrdScope(1, <uNewBottom>). SET SCOPEBOTTOM, when used with no argument, is functionally equivalent to OrdScope(1, NIL).
-
- See Also
- OrdScope()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_SCOPETOP.xml b/docs/Help_Spanish/Topics/command_SET_SCOPETOP.xml
deleted file mode 100644
index 817b4ddce5..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_SCOPETOP.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- SET SCOPETOP Command
-
- Commands
- Databases
- Index/order
- Scoping key values
- SET SCOPETOP command
-
-
-
- SET SCOPETOP Command
-
-
- Purpose
- Change the top boundary for scoping key values in the controlling order.
- Syntax
- SET SCOPETOP TO [<uNewTop>]
- Description
- SET SCOPETOP, when used with the <uNewTop> argument, is functionally equivalent to OrdScope(0, <uNewTop>). SET SCOPETOP, when used with no argument, is functionally equivalent to OrdScope(0, NIL).
-
- See Also
- OrdScope()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_SOFTSEEK.xml b/docs/Help_Spanish/Topics/command_SET_SOFTSEEK.xml
deleted file mode 100644
index 7e04661430..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_SOFTSEEK.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- SET SOFTSEEK Command
-
- Close matchesfinding
- Commands
- Databases
- Finding
- Index/order
- SET SOFTSEEK command
-
-
-
- SET SOFTSEEK Command
-
-
- Purpose
- Change the setting that determines whether a seek action will find a close match when no exact match is found.
- Syntax
- SET SOFTSEEK ON | OFF | (<lToggle>)
- Arguments
- ON
- OFF
- lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
- Description
- SET SOFTSEEK is functionally equivalent to SetSoftSeek().
-
- See Also
- DbSeek(),, Found(), SEEK, SET INDEX, SET ORDER, SET RELATION, SetSoftSeek()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SET_UNIQUE.xml b/docs/Help_Spanish/Topics/command_SET_UNIQUE.xml
deleted file mode 100644
index ea8942de4f..0000000000
--- a/docs/Help_Spanish/Topics/command_SET_UNIQUE.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- SET UNIQUE Command
-
- Commands
- Databases
- Including unique keys
- Index/order
- Orders
- SET UNIQUE command
- Settingunique record keys
-
-
-
- SET UNIQUE Command
-
-
- Purpose
- Change the setting that determines whether to include unique record keys in an order.
- Syntax
- SET UNIQUE ON | OFF | (<lToggle>)
- Arguments
- ON
- OFF
- lToggleA logical expression which must appear in parentheses. True is equivalent to ON, False to OFF.
-
- Description
- SET UNIQUE is functionally equivalent to SetUnique().
-
- See Also
- DBCreateIndex(), INDEX, PACK, REINDEX, SEEK, SetUnique()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SKIP.xml b/docs/Help_Spanish/Topics/command_SKIP.xml
deleted file mode 100644
index b7d69a31bb..0000000000
--- a/docs/Help_Spanish/Topics/command_SKIP.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- SKIP Command
-
- Commands
- Databases
- Recordsmoving pointer
- SKIP command
- Skipping records
-
-
-
- SKIP Command
-
-
- Purpose
- Move the record pointer relative to the current record.
- Syntax
- SKIP [<nRecords>] [[IN|ALIAS] <workarea>]
- Arguments
- <nRecords>The number of logical records to move, relative to the current record. A positive value means to skip forward, and a negative value means to skip backward. If <nRecords> is omitted, a value of 1 is assumed.
-
-
- Description
- SKIP is functionally equivalent to DBSkip(). Specifying the alias is like using DBSkip() in an aliased expression (such as, <xcAlias>->DBSkip(<nRecords>).
- Examples
- This example uses SKIP with various arguments and shows the result:
-
- USE customer NEW SKIP ?RECNO()// Result: 2 SKIP 10 ?RECNO()// Result: 12 SKIP -5 ?RECNO()// Result: 7
-
- This example moves the record pointer in a remote work area:
-
- USE customer NEW USE invoices NEW SKIP ALIAS customer
-
- This example prints a report using SKIP to move the record pointer sequentially through the CUSTOMER database file:
-
- LOCAL nLine :=99 USE customer NEW SET PRINTER ON DOWHILE!EOF() IF nLine >55 EJECT nLine :=1 ENDIF Customer, Address, City, State, Zip ++nLine SKIP ENDDO SET PRINTER OFF CLOSE customer
-
- See Also
- BoF(), COMMIT, DbSetFilter(), DbSkip(), EoF(), GO, LOCATE, RecNo(), SEEK, SetDeleted()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SORT.xml b/docs/Help_Spanish/Topics/command_SORT.xml
deleted file mode 100644
index 004f7539bd..0000000000
--- a/docs/Help_Spanish/Topics/command_SORT.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
- SORT Command
-
- Commands
- Databases
- Recordssorting
- SORT command
- Sorting records
-
-
-
- SORT Command
-
-
- Purpose
- Copy records from the current work area to a database file in sorted order.
- Syntax
- SORT TO <xcTargetFile> ON <idFieldList> [<Scope>] [WHILE <lCondition>] [FOR <lCondition>]
- Arguments
- TO <xcTargetFile>The name of the target database file to write the sorted records, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD.
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
-
- ON <idFieldList>The sort keys, specified as a comma-separated list of field names. You may optionally add, after each field name, /A (to sort in dictionary order), /C (to ignore capitalization), or /D (to sort in descending order). The default setting is /A.
-
-
-
-
- Description
- SORT is functionally equivalent to DBSort().
- Examples
- This example copies a mailing list using a descending sort key to a smaller list for printing:
-
- USE mailing INDEX zip SEEK "900" SORT ON Lastname /D, Firstname /D TO invite ; WHILE Zip ="900" USE invite NEW REPORT FORM rsvplist TO PRINTER
-
- See Also
- ASort(), DbSort(), FLock(), INDEX,SetDefault(), SetPath(),USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_STATIC.xml b/docs/Help_Spanish/Topics/command_STATIC.xml
deleted file mode 100644
index 21739903e6..0000000000
--- a/docs/Help_Spanish/Topics/command_STATIC.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- STATIC Statement
-
- Arraysdeclaring
- Compiledeclaration
- Declaration statements
- Statements
- STATIC LOCAL statement
- STATIC statement
- Variable declaration
-
-
-
- STATIC Statement
-
- Purpose
- Declares and initializes static variables and arrays.
- Syntax
- STATIC [LOCAL] <idVar> [:= <uValue>] [, ...] [AS | IS <idType>] [, ...] STATIC [LOCAL] DIM <ArraySpec> [, ...] AS | IS <idType> [, ...] STATIC [LOCAL] <ArraySpec> [, ...] [AS ARRAY] [, ...]
-
- Note: The STATIC statement is shown using several syntax diagrams for convenience only. You can declare variables, dynamic arrays, and dimensioned arrays using a single STATIC statement if each definition is separated by a comma.
-
-
- Description
- The STATIC keyword serves as a lifetime modifier for variables declared with the LOCAL statement, preventing them from being released from memory when the creating entity returns to its calling routine. It is listed here as a separate entry because, with the LOCAL keyword being optional, STATIC can stand alone in a routine as a variable declaration statement. Refer to the LOCAL statement for a description and notes concerning static variable declarations.
- See Also
- LOCAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_STORE.xml b/docs/Help_Spanish/Topics/command_STORE.xml
deleted file mode 100644
index aef45656a6..0000000000
--- a/docs/Help_Spanish/Topics/command_STORE.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- STORE Command
-
- Addingvalues to variables
- Commands
- Memory variable
- STORE command
-
-
-
- STORE Command
-
-
- Purpose
- Assign a value to one or more variables.
- Syntax
- STORE <uValue> TO <idVarList>
- Arguments
- <uValue>A value to assign to the specified variables.
- TO <idVarList>Defines a list of one or more variables that are assigned the value <uValue>. If any variable reference in the list is ambiguous (that is, not declared at compile time or not explicitly qualified with an alias), it is assumed to be MEMVAR. If any variable in the list is not visible or does not exist, a private variable is created using <uValue>.
- Description
- The STORE command is defined using the assignment operator (:=).
- Notes
- Assigning a value to an entire array: In <%APP%>, neither the STORE command nor the assignment operators can assign a single value to an entire array. Use the AFill() function for this purpose.
- Examples
- These statements create and assign values to undeclared private variables:
-
- STORE "string" TO cVar1, cVar2, cVar3 cVar1 := "string2" cVar2 := _MEMVAR->cVar1
-
- These statements assign multiple variables using both STORE and the inline assignment operator (:=). The methods produce identical code:
-
- STORE "value" TO cVar1, cVar2, cVar3 cVar1 := cVar2 := cVar3 := "value"
-
- These statements assign values to the same field referenced explicitly with an alias. The first assignment uses the field alias (_FIELD->), where the second uses the actual alias name:
-
- USE sales NEW STORE 1200.98 TO _FIELD->CustBal STORE 1200.98 TO Sales->CustBal
- See Also
- AFill(), , LOCAL, PRIVATE, PUBLIC, RELEASE, REPLACE, RESTORE, SAVE, STATIC
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_STRUCTURE.xml b/docs/Help_Spanish/Topics/command_STRUCTURE.xml
deleted file mode 100644
index f0cf7909b0..0000000000
--- a/docs/Help_Spanish/Topics/command_STRUCTURE.xml
+++ /dev/null
@@ -1,73 +0,0 @@
-
-
-
- STRUCTURE Statement
-
- END STRUCTURE
- STRUCTURE
-
-
-
- STRUCTURE Statement
-
- Purpose
- Declare a structure name to the compiler.
- Syntax
- [Attributes] [Modifiers] [RECORD] STRUCTURE <idStructure> [IMPLEMENTS <idInterface>[, <IdInterface2>,..]
- [StructureMembers]
- END STRUCTURE
- Arguments
-
- RECORDThe record modifier declares a special structure that has value equality. See the topic about records
-
- <idStructure>A valid identifier name for the class. A class is an entity and, as such, shares the same name space as other entities. This means that it is not possible to have a class and a global variable, for example, with the same name.
-
- IMPLEMENTS <idInterface>The name(s) of the interface(s) that this class implements.
-
- StructrureMembersThis can be any of ACCESS, ASSIGN, CONSTRUCTOR, DESTRUCTOR, EVENT, METHOD, OPERATOR, PROPERTY, just like in the CLASS declaration.
-
- In this case, the variables x and z are typed as INT, while the variables cName and cAddr are typed as STRING.
- Description
- After the structure name is declared to the compiler, it is followed by 0 or more instance variable declaration statements. You use a structure name to declare variables (see GLOBAL and LOCAL statements in this guide) designed to hold instances of a specific class, to instantiate instances of the class, and to define methods (see the METHOD statement in this guide) and subclasses for the class.
- Notes
- Binding of instance variables: Instance variables can be either early or late bound, depending on how you declare them and how you use them.
-
- Early binding happens if the memory location of a variable is known at compile time. The compiler knows exactly how to reference the variable and can, therefore, generate code to do so.
-
- Late binding is necessary if the memory location of a variable is unknown at compile time. The compiler cannot determine from the program source code exactly where the variable is or how to go about referencing it, so it generates code to look the symbol up in a table. The lookup is performed at runtime.
-
- Since there is no need for a runtime lookup with early bound instance variables, using them instead of late bound variables will significantly improve the performance of your application. The following table summarizes the binding and visibility issues for the four types of instance variables:
-
- Variable TypeBindingVisibility
- EXPORTEarly, if possibleApplication-wide for CLASS and module-wide for STATIC CLASS
- INSTANCEAlways lateIn class and subclasses
- HIDDENAlways earlyIn class only
- PROTECTAlways earlyIn class and subclasses
-
- Object instantiation: Once you declare a class, you create instances of the class using the class name followed by the instantiation operators, {}. The syntax is as follows:
-
- <idClass>{[<uArgList>]}
-
- where <uArgList> is an optional comma-separated list of values passed as arguments to a special method called Init() (see the METHOD statement in this guide for more information on the Init() method).
-
- Accessing instance variables: The syntax to access an exported instance variable externally (i.e., from any entity that is not a method of its class) is as follows:
-
- <idObject>:<idVar>
-
- You can access non-exported instance variables only from methods in which they are visible. Within a method, you use the following syntax for accessing all instance variables:
-
- [SELF:]<idVar>
-
- The SELF: prefix is optional, except in the case of an access/assign method (see the ACCESS and ASSIGN statement entries in this guide for more information and the METHOD statement for more information on SELF).
- Instance variables are just like other program variables. You can access them anywhere in the language where an expression is allowed.
-
- The prefix [STATIC] is no longer supported by <%APP%>.
- Examples
- The following example defines two classes, one of which inherits values from the other, and demonstrates how to create a class instance with initial values for the instance variables:
-
-
- See Also
- ACCESS, ASSIGN, CONSTRUCTOR, DESTRUCTOR, EVENT, METHOD, OPERATOR, PROPERTY
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SUM.xml b/docs/Help_Spanish/Topics/command_SUM.xml
deleted file mode 100644
index 1504148612..0000000000
--- a/docs/Help_Spanish/Topics/command_SUM.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- SUM Command
-
- Commands
- Databases
- Evaluating records
- Records
- Recordsevaluatingtotaling
- SUM command
- Totaling records
-
-
-
- SUM Command
-
-
- Purpose
- Total a series of numeric expressions for a range of records in the current work area, and assign the results to a series of variables.
- Syntax
- SUM <nValueList> TO <idVarList> [<Scope>] [WHILE <lCondition>] [FOR <lCondition>]
- Arguments
- <nValueList>The list of values to sum for each record processed. Note that the <nValueList> is required and not optional as it is in other dialects.
-
- TO <idVarList>Defines a list of one or more variables to assign the results of the sum. If any variable reference in the list is ambiguous (that is, not declared at compile time or not explicitly qualified with an alias), it is assumed to be MEMVAR. If any variable in the list is not visible or does not exist, a private variable is created using <uValue>.
-
-
-
-
-
- Examples
- This example illustrates the use of SUM:
-
- LOCAL nTotalPrice, nTotalAmount USE sales NEW SUM Price *.10, Amount TO nTotalPrice, nTotalAmount
? nTotalPrice// Result: 151515.00 ? nTotalAmount// Result: 150675.00
-
- See Also
- AVERAGE, COUNT, DBEval(), TOTAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_SWITCH.xml b/docs/Help_Spanish/Topics/command_SWITCH.xml
deleted file mode 100644
index 36fe5a0f44..0000000000
--- a/docs/Help_Spanish/Topics/command_SWITCH.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- SWITCH Statement
-
- Branching
- CASE statement
- Conditional execution
- OTHERWISE statement
- Program control
- Statements
- SWITCH statement
-
-
-
- SWITCH Statement
-
- Purpose
- Conditionally executes a block of statements.
- Syntax
- SWITCH <expression> CASE <constantvalue> [WHEN <whenexpression>] <Statements>... [CASE <constantvalue>] [CASE <constantvalue>] <Statements>... [CASE <constantvalue>] <Statements>... [CASE <variablename> AS <datatype>] [WHEN <whenexpression>] <Statements>... [OTHERWISE] <Statements>... END [SWITCH]
- Arguments
- <constantvalue>A constant value that can be evaluated at compile time. You can also have 2 consecutive CASE lines without statements between them. In that case, both CASE lines share the same statement block. If you want a case block without statements, then insert a NOP statement as its statement.
- <whenexpression>A logical expression that determines if the particular CASE block should be active This is sometimes called an expression filter.
- <variablename>A variable name that gets declared by the pattern matching expression
- <datatype>The data type of the variable in the pattern matching expression
-
- OTHERWISEIf none of the preceding CASE conditions match, the statements following the OTHERWISE up until the next END SWITCH are executed. Afterward, control branches to the statement following the next END SWITCH statement.
- Description
- SWITCH works by branching to the statement following the first CASE <constantvalue> that evaluates to TRUE. If all CASE conditions evaluate to FALSE, it branches to the statement following the OTHERWISE statement (if specified).
- In general, there are two types of SWITCH statements:
-
-
Switch statements with constant values (CASE <constantvalue>);
-
Switch statements with pattern matching expressions (CASE <varName> AS <datatype>).
-
- Both types of SWITCH statements can be enhanced with WHEN filters.
- If you do not have a WHEN filter, then each CASE line must be "unique", so no two CASEs can have the same constantvalue or same datatype. If you add a WHEN filter, then this is allowed.
- The compiler may (and will) rearrange the order of the CASE labels when generating code, for example to combine two CASEs with the same constant value and a WHEN filter. These may be combined into one CASE label with an embedded IF statement.
-
- Execution proceeds until the next CASE, OTHERWISE, or END SWITCH is encountered, and control then branches to the first statement following the next ENDCASE statement.
- Control structures can be nested to any depth. The only requirement is that each control structure be properly nested.
-
- Examples
- This example uses SWITCH in a menu structure to branch control based on user selection:
- FUNCTION ActonChoice(nChoice asLONG) ASVOID SWITCH nChoice CASE 0 RETURN CASE 1 ChoiceOne() CASE 2 ChoiceTwo() ENDSWITCH
- See Also
- BEGIN SEQUENCE, DO WHILE, FOR, FOREACH IF DO CASE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_TEXT.xml b/docs/Help_Spanish/Topics/command_TEXT.xml
deleted file mode 100644
index e0b413e239..0000000000
--- a/docs/Help_Spanish/Topics/command_TEXT.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- TEXT Command
-
- Commands
- Filesclosing
- Terminal window
- TEXT Statement
-
-
-
- TEXT Command
-
- Purpose
- Declares a block of text that can be assigned to a variable or send to an output device.
- There are several different variations of the TEXT Statement:
-
-
Core TEXT Command
-
Non-Code TEXT Command
-
FoxPro TEXT Command
-
-
- The different variations of the TEXT commands are implemented as User Defined commands in XSharpDefs.xh or one of the other header files.
- All of these commands map to the preprocessor directives #text and #endtext, where the actual work is done.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_THROW.xml b/docs/Help_Spanish/Topics/command_THROW.xml
deleted file mode 100644
index 40bf96cc9f..0000000000
--- a/docs/Help_Spanish/Topics/command_THROW.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- THROW Statement
-
- THROW
-
-
-
- THROW Statement
-
- Purpose
- The THROW statement raises a runtime exception.
- Syntax
- THROW [expression]
- Arguments
- expressionAn optional expression to throw.
- Remarks
- THROW throws a runtime exception, causing execution to branch to the nearest CATCH or FINALLY block in a TRY construct. If execution is not within a TRY construct, the application will terminate.
- The specified expression is passed to the CATCH statement, if any, and must be of type System.Exception or a class derived from it . See TRY-CATCH-FINALLY fro more information.
- Using THROW within a CATCH block without any arguments re-throws the exception, passing it unchanged to the next highest TRY-CATCH block.
- Example
- USING System.IO FUNCTION ReadFile( filename ASSTRING ) ASSTRING LOCAL s ASSTRING TRY s := File.ReadAllText( filename ) CATCH e AS DirectoryNotFoundException ? "Directory not found", e CATCH e AS IOException ? "IO exception occurred", e CATCH e AS UnauthorizedAccessException ? "Access denied", e CATCH ? "Some other exception" // Escalate error to next TRY-CATCH THROW FINALLY ? "All done!" ENDTRY RETURN s
-
- See Also
-
- TRY-CATCH-FINALLY
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_TOTAL.xml b/docs/Help_Spanish/Topics/command_TOTAL.xml
deleted file mode 100644
index a6617fc370..0000000000
--- a/docs/Help_Spanish/Topics/command_TOTAL.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-
-
-
- TOTAL Command
-
- Commands
- Databases
- Recordstotaling
- TOTAL command
- Totaling records
-
-
-
- TOTAL Command
-
-
- Purpose
- Summarize records in the current work area by key value to a database file.
- Syntax
- TOTAL TO <xcTargetFile> ON <uKeyValue> FIELDS <idFieldList> [<Scope>] [WHILE <lCondition>] [FOR <lCondition>]
- Arguments
- TO <xcTargetFile>The name of the target database file to write the totaled records, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules. The default extension for database files is determined by the RDD.
-
- If <xcTargetFile> does not exist, it is created. If it exists, this command attempts to open the file in exclusive mode and, if successful, the file is overwritten without warning or error. If access is denied because, for example, another process is using the file, NetErr() is set to TRUE.
-
- ON <uKeyValue>The key value used to summarize the records. To make the summarizing operation accurate, the current database file should be indexed or sorted on this expression.
-
- FIELDS <idFieldList>The list of numeric fields to total. If the FIELDS clause is not specified, no numeric fields are totaled. Instead, each numeric field in the target file contains the value for the first record in the source file matching the key value.
-
-
-
-
- Description
- TOTAL works by first copying the structure of the current database file to specified target file, except for memo fields. It then sequentially scans the current database file within the specified scope of records.
-
- As each record with a unique key value is encountered, that record is copied to the target database file. The values of numeric fields specified in the FIELDS list from successive records with the same key value are added to fields with the same names in the target file. Summation proceeds until a record with a new key value is encountered at which point the process is repeated.
-
- Important! To successfully total numeric fields, the numeric fields in the current database file structure must be large enough to hold the largest total possible for that numeric field. A runtime error will be raised if there is a numeric field overflow.
-
- TOTAL is functionally equivalent to DBTotal().
- Notes
- Deleted records: If SetDeleted() is FALSE, deleted records in the source file are processed. Records in the target file inherit the deleted status of the first matching record in the source file.
-
- Visibility: If SetDeleted() is TRUE, however, deleted records are not visible and are, therefore, not processed. Similarly, filtered records (with DbSetFilter() or a conditional controlling order) are not processed.
- Examples
- In this example, a database file is totaled on the key expression of the controlling order using a macro expression. When the macro expression is encountered, the expression is evaluated and the resulting string is substituted for the TOTAL <uKeyValue> argument:
-
- USE sales INDEX branch NEW TOTAL ON &(IndexKey(0)) FIELDS Amount TO Summary
-
- See Also
- AVERAGE, DBTotal(), INDEX, SetDefault(), SetPath(), SORT, SUM, UPDATE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_TRY_CATCH.xml b/docs/Help_Spanish/Topics/command_TRY_CATCH.xml
deleted file mode 100644
index 6830d463dc..0000000000
--- a/docs/Help_Spanish/Topics/command_TRY_CATCH.xml
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
- TRY CATCH Statement
-
- Branching
- CATCH statement
- END TRY statement
- FINALLY statement
- Program control
- Statements
- THROW statement
- TRY CATCH statement
-
-
-
- TRY CATCH Statement
-
- Purpose
- TRY, CATCH and FINALLY are used to declare an exception handling block.
-
- TRY guardedStatements [CATCH [[variableName] AS exceptionType] [WHEN whenexpression] exceptionHandlingStatements ] [FINALLY cleanupStatements ] END TRY
-
- Arguments
-
- variableNameThe name of a variable that will receive the exception. The variable name is optional. If you only specify the type then the exception will still be caught but not stored in a local variable.
- exceptionTypeThe exception type that will be caught by the CATCH block.
- whenexpressionA logical expression that determines if the particular CATCH block should be active.
- exceptionHandlingStatementsZero or more statements that handle the exception condition.
- cleanupStatementsZero or more statements that perform any necessary cleanup before the TRY block is exited..
- Remarks
- A TRY-CATCH-FINALLY block is used to trap and handle exceptions that may be thrown within a block of code. Exceptions may be generated by the CLR, the Vulcan.NET runtime library, third-party libraries or by application code using the THROW statement.
- TRY Block
- The statements within the TRY block are sometimes referred to as "guarded" statements. These are the statements that potentially can cause exceptions that you want to handle.
- CATCH Blocks
- A exception handling block may contain any number of CATCH blocks (including zero). Each CATCH block that declares a variable name and a type will receive exceptions of that type. CATCH blocks that receive exceptions implicitly declare a local variable that will contain the caught exception. This implicitly declared local variable is only valid within the scope of the CATCH block. The name given to the variable must not be the same as any explicitly declared LOCAL or parameter, or a compile-time error will occur. However, it is legal to use the same variable name in multiple CATCH blocks. Since each CATCH block's variable is only visible within its enclosing block, there is no conflict.
-
- A CATCH block may also be declared without a variable name but WITH an exception type. In that case the exception will still be caught but not stored in a local variable.
-
- A CATCH block may also be declared without any variable name and exception type. This type of CATCH block will catch any exception, and is equivalent to declaring a CATCH block with an exception type of System.Exception.
-
- If multiple CATCH blocks are declared, the order in which they appear is important. The CLR will examine the CATCH clauses in order, and invoke the first one that matches the exception being thrown. This includes not only the specific exception class that was specified, but any derived classes. For this reason, you should catch the more specific exception types before less specific ones.
-
- The exception type declared in a CATCH block must always be System.Exception, or a class derived from it.
-
- If no suitable CATCH block was declared for the exception that has been thrown, control will be passed to the next highest exception handling block. If there is no higher exception handling block, or none that can handle the exception, the application will terminate.
-
- Exceptions may be explicitly passed on to the next highest exception handling block by using the THROW keyword.
- Finally Block
- If a FINALLY block is declared, any statements within it are executed regardless of how the TRY block exits. This provides a mechanism to perform any cleanup such as releasing resources. The code within a finally block will be executed even if there is no suitable CATCH block to handle the exception.
- Compatibility Note:
- TRY-CATCH-FINALLY blocks are similar to, but much more flexible than BEGINSEQUENCE-RECOVER blocks. However, BEGINSEQUENCE and RECOVER are still supported for backward compatibility.
-
- Note that exceptions thrown with BREAK will not be caught with a TRY-CATCH-FINALLY block because the data thrown by BREAK is encapsulated in a USUAL, which does not inherit from System.Exception.
-
- However, exceptions thrown with THROW will be caught by the next highest BEGIN SEQUENCE block (if any) and the exception will be encapsulated in a USUAL if a RECOVER USING variable has been declared.
-
- Also note that the CanBreak() runtime function does not detect whether execution is currently within a TRY block. CanBreak() is provided only for compatibility with existing Visual Objects code and BEGINSEQUENCE blocks, and should not be relied upon to determine whether execution is within an exception handling block. There is no way to determine whether execution is within an exception handling block because this functionality is not present in the CLR, and execution may currently be within code that is compiled in an language other than Vulcan.NET.
- Example
- The following example tests for division by zero and catches the exception that will be thrown by the CLR if the divisor is zero. Any other exceptions would propagate to the next highest exception handling block (if any). Without the exception handling block, the application would terminate with an unhandled DivideByZeroException.
-
- FUNCTION DivisionTest( x ASINT, y ASINT ) ASINT TRY RETURN x / y CATCH e AS System.DivideByZeroException ? "Divide by zero!", e RETURN 0 ENDTRY
-
-
- The following example demonstrates multiple CATCH blocks and a FINALLY block:
-
- USING System.IO
FUNCTION ReadFile( filename ASSTRING ) ASSTRING LOCAL s ASSTRING
TRY s := File.ReadAllText( filename ) CATCH e AS DirectoryNotFoundException ? "Directory not found", e CATCH e AS IOException ? "IO exception occurred", e CATCH e AS UnauthorizedAccessException ? "Access denied", e CATCH ? "Some other exception" FINALLY ? "All done!" ENDTRY
RETURN s
- See Also
- BEGIN SEQUENCE THROW
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_UNION.xml b/docs/Help_Spanish/Topics/command_UNION.xml
deleted file mode 100644
index 0224d03038..0000000000
--- a/docs/Help_Spanish/Topics/command_UNION.xml
+++ /dev/null
@@ -1,80 +0,0 @@
-
-
-
- UNION Statement
-
- Commands
- Compiledeclaration
- END UNION
- Entity declaration
- UNION
- Union entities
- Union entitiesdeclaringspecifying members
- UNION statement
-
-
-
- UNION Statement
-
-
- Purpose
- Declare a union entity and its member names.
- Syntax
- [Modifiers] UNION <idUnion> [ALIGN 1|2|4|8]
- MEMBER <idVarList> AS | IS <idType> [ ,…]
- MEMBER DIM <ArraySpec> [ ,…] AS | IS <idType> [ ,…]
- [END UNION]
-
- Note: The MEMBER statement is shown using two syntax diagrams for convenience. You can declare variables and dimensioned arrays using a single MEMBER statement if each definition is separated by a comma.
- Arguments
-
-
- <idUnion>A valid identifier name for the union. A union is an entity and shares the same name space as other entities. This means that it is not possible to have a union and a constant, for example, with the same name.
-
- MEMBERDeclares one or more union member variables or dimensioned arrays. You can specify multiple MEMBER declarations on separate lines.
-
- <idVarList>A comma-separated list of identifier names for the union member variables.
-
- DIM <ArraySpec>The specification for a dimensioned array to use as a union member. <ArraySpec> is one of the following:
- <idArray>[<nElements>, <nElements>, <nElements>]
- <idArray>[<nElements>],[<nElements>], [<nElements>]
- All dimensions except the first are optional.
-
- <nElements> defines the number of elements in a particular dimension of an array. The number of dimensions is determined by how many <nElements> arguments you specify.
-
- <nElements> can be a literal numeric representation or a simple numeric expression involving only operators, literals, and DEFINE constants; however, more complicated expressions (such as function calls) are not allowed.
-
- AS <idType>Specifies the data type of the variable you are declaring (called strong typing). For DIM arrays, declares the data type for all array elements. The AS <idType> is required for all union members.
-
- Refer to the CLASS entry for a list of valid values for <idType>. Note that the following data types are not supported in unions because they are dynamic types that require garbage collection:
-
-
-
ARRAY
-
FLOAT
-
OBJECT
-
<idClass>
-
STRING
-
USUAL
-
-
-
-
-
- IS <idType>Specifies a union data type in which the memory needed to hold the union is allocated on the stack (i.e., <idUnion> is the only <idType> allowed with the IS keyword).
-
- ALIGN 1|2|4|8Specifies the memory alignment of the structure. The default is 4, which means that all members are aligned at DWORD boundaries, since that gives the best performance on a 32 bits platform and is also the default alignment for most C/C++ compilers. You may want to change this when you need to match a C/C++ structure that has been defined with a different alignment (the #pragma pack in a C/C++ header file).
-
- Note: The default alignment for C/C++ compilers is 4 as well, unless the structure contains doubles (REAL8 in <%APP%>). In that case the C/C++ compiler uses an alignment of 8. <%APP%> does NOT automatically choose an alignment of 8, so you must add the ALIGN 8 to your structure in these circumstances.
- Description
- UNIONs are like STRUCTUREs, but all members start at offset zero (0). In other words, assigning a value to a union member affects all other union members. As the size of the union is equal to the size of the biggest member, changing one member will change all of the others because they occupy the same memory.
-
- You use the UNION statement to mark the beginning of the definition of a union entity, followed by one or more MEMBER statements that define what the union looks like.
- Examples
- The following is a conversion example:
-
- UNION wb ALIGN1 MEMBER w ASWORD BYTE bLo ASBYTE BYTE bHi ASBYTE
FUNCTION x LOCAL u IS wb
u.w :=0x1234
? u.bLo // 52 (=0x34) ? u.bHi // 18 (=0x12)
- See Also
- STRUCTURE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_UNLOCK.xml b/docs/Help_Spanish/Topics/command_UNLOCK.xml
deleted file mode 100644
index cd8854628b..0000000000
--- a/docs/Help_Spanish/Topics/command_UNLOCK.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- UNLOCK Command
-
- Commands
- Concurrency control
- Databases
- Locking work areas
- UNLOCK ALL command
- UNLOCK command
- Work areaslocking
-
-
-
- UNLOCK Command
-
-
- Purpose
- Release all locks for a work area.
- Syntax
- UNLOCK [RECORD nRecordNumber] [[IN|ALIAS] workarea] [ALL]
-
- Arguments
- RECORD nRecordNumberReleases the record lock on record number nRecordNumber. Issuing UNLOCK RECORD nRecordNumber for a record in a table with a file lock releases the file lock.
-
- ALLReleases all record and file locks in all work areas. If not specified, only the lock in the current work area is released. ALL cannot be combined with the RECORD or IN|ALIAS clause.
- Description
- UNLOCK is functionally equivalent to DBUnlock(), and UNLOCK ALL is functionally equivalent to DBUnlockAll().
- Examples
- This example attempts an update operation that requires a record lock. If the RLock() is successful, the record is updated with a function, and the RLock() is released with UNLOCK:
-
- USE sales INDEX salesman SHARED NEW IF RLock() UpdateRecord() UNLOCK ELSE ? "Record update failed" BREAK ENDIF
-
- See Also
- DbRLock(), DbUnlock(), DbUnlockAll(), FLock(), RLock(), SetExclusive(), USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_UPDATE.xml b/docs/Help_Spanish/Topics/command_UPDATE.xml
deleted file mode 100644
index 964b508389..0000000000
--- a/docs/Help_Spanish/Topics/command_UPDATE.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- UPDATE Command
-
- Commands
- Databases
- Fieldsupdating
- UPDATE command
- Updating fields
-
-
-
- UPDATE Command
-
-
- Purpose
- Replace fields in the current work area with values from another work area, based on the specified key value.
- Syntax
- UPDATE FROM <xcAlias> ON <uKeyValue> [RANDOM]REPLACE <idField> WITH <uValue> [, <idField> WITH <uValue>...]
- Arguments
- FROM <xcAlias>The alias identifier for the work area used to update records in the current work area. If there is no open database file associated with the specified alias, a runtime error is raised.
-
- ON <uKeyValue>The expression that defines matching records in the FROM work area.
-
- REPLACE <idField>A field in the current work area to update with a new value.
-
- WITH <uValue>The value used to update the current field. You must reference any field contained in the FROM work area with the correct alias.
-
- RANDOMIf specified, the current work area must be ordered (using an index order) by <uKeyValue>, but the FROM work area records can be in any order. If not specified, both the current work area and the FROM work area must be ordered (logically or physically) by <uKeyValue>.
- Description
- UPDATE can only update records in the current work area with unique key values. When there is more than one instance of a key value, only the first record with the key value is updated. The FROM work area, however, can have duplicate key values.
-
- UPDATE is functionally equivalent to DBUpdate().
- Notes
- Deleted records: If SetDeleted() is FALSE, deleted records in both files are processed. Records in the file being updated retain their deleted status and are not affected by the deleted status of records in the FROM file.
-
- Visibility: If SetDeleted() is TRUE, however, deleted records are not visible and are, therefore, not processed. Similarly, filtered records (with DbSetFilter() or a conditional controlling order) are not processed.
-
- Shared mode: For a shared database, UPDATE requires a file lock on the current database file. The FROM database file can be open in any mode.
- Examples
- This example updates the CUSTOMER database file with outstanding invoice amounts:
-
- USE invoices NEW USE customer INDEX customer NEW UPDATEFROM Invoices ON Last; REPLACE Owed WITH Owed + Invoices->Amount RANDOM
-
- See Also
- DBCreateIndex(), DBUpdate(), FLock(), INDEX, JOIN, REPLACE, SetUnique(), SORT, TOTAL
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_USE.xml b/docs/Help_Spanish/Topics/command_USE.xml
deleted file mode 100644
index 55e163c493..0000000000
--- a/docs/Help_Spanish/Topics/command_USE.xml
+++ /dev/null
@@ -1,80 +0,0 @@
-
-
-
- USE Command
-
- Commands
- Concurrency control
- Databases
- Filesopening
- Openingfiles
- USE command
-
-
-
- USE Command
-
-
- Purpose
- Open an existing database file, its associated memo file, and optionally associated index files in the current or the next available work area.
- Syntax
- USE [<xcDataFile> [INDEX <xcIndexList>] [ALIAS <xcAlias>] [FIELDS <aFields>] [NEW] [READONLY] [EXCLUSIVE | SHARED] [VIA <cDriver>] [INHERIT <acRDDs>]]
- Arguments
- <xcDataFile>The name of the database file to open, including an optional drive, directory, and extension. If the database file has a corresponding memo file, this is also opened. The default extension for database and memo files is determined by the RDD.
-
- INDEX <xcIndexFileList>The names of the index files to open, including an optional drive, directory, and extension for each. The default extension is determined by the RDD and can be obtained using DBOrderInfo(DBOI_INDEXEXT).
-
- If you specify <xcIndexList> as an expression and the value returned is spaces or NIL, it is ignored.
-
- It is recommended that you open index files with SET INDEX or DBSetIndex() for proper resolution in case of a concurrency conflict.
-
- If the database file, its corresponding memo file, or any of the index files does not exist, a runtime error is raised. See SetDefault() and SetPath() for file searching and creation rules.
-
- ALIAS <xcAlias>An identifier name to associate with the work area when <xcDataFile> is opened. If not specified, the alias defaults to the database file name. Duplicate alias names are not allowed within a single application.
-
- FIELDS <aFields>An array containing field descriptions in the format returned by DBStruct().
-
- This argument does not apply to DBF files. It is intended for use with file formats that do not store field descriptions. For example, if you use an RDD that supports SDF or delimited files, you can use this argument to define the file structure, which can then be used with other commands or functions to access the field descriptions. Here is an example of this argument:
-
- aFields := {; {"First", "C", 35, 0}; {"Last", "C", 35, 0}; {"Birthday", "D", 8, 0}} USE Names FIELDS aFields VIA "DELIM" ? First // Return: Josie
-
- NEWSelects the next available work area before opening <xcDataFile>. If not specified, <xcDataFile> is opened in the current work area.
-
- READONLYAttempts to open <xcDataFile> with a read-only attribute, prohibiting updates to the work area. If not specified, <xcDataFile> is opened read-write, allowing updates. If <xcDataFile> cannot be accessed using the indicated attribute, a runtime error is raised.
-
- EXCLUSIVEAttempts to open <xcDataFile> for exclusive (non-shared) use. All other processes are denied access until the database file is closed.
-
- SHAREDAttempts to open <xcDataFile> for shared use.
-
- If neither SHARED nor EXCLUSIVE is specified, the USE command attempts to open <xcDataFile> in the mode indicated by the SetExclusive() flag. However, it is highly recommended that you specify the open mode as part of the USE command rather than relying on SetExclusive() to determine it for you.
-
- VIA <cDriver>The name of the RDD that will service the work area. If not specified, the default RDD as determined by RDDSetDefault() is used.
-
- INHERIT <acRDDs>A one-dimensional array with the names of RDDs from which the main RDD inherits special functionality. This allows you to use RDDs with special capabilities, like encryption or decryption, in different work areas with different database drivers. These RDDs overlay special functions of the main RDD (specified with the VIA clause). If multiple RDDs (specified with this INHERIT clause) implement the same function, the function associated with the last RDD in the list takes precedence.
-
- USE specified with no arguments closes the database file open in the current work area.
- Description
- The USE command attempts to open <xcDataFile> (and its associated .DBF file, if any) in the indicated mode. If the file is successfully opened, the operation proceeds to open any indicated index files in the same mode — any files that were already open in the work area are closed. The first order in the first index file in the list becomes the controlling order.
-
- If access is denied because, for example, another process has exclusive use of the database file, NetErr() is set to TRUE but no runtime error is raised. For this reason, it is recommended that you open index files as a separate operation (with SET INDEX or DBSetIndex()). Otherwise, a runtime error will result when the USE command tries to open the first index file in the list because the database file will not be open.
- When a database file is first opened, the record pointer is positioned at the first logical record in the file (record one if there is no controlling order).
-
- If the database file is opened in shared mode, other processes can have concurrent access to the file and responsibility for data integrity falls on the application program. File and record locking (using, FLock(), RLock(), or DBRLock()) are the basic means of denying other processes access to a particular file or record.
-
- Refer to the CLOSE command for information on how to close files of all types.
-
- USE is functionally equivalent to DBUseArea().
- Examples
- This example opens a shared database file with associated index files. If NetErr() returns FALSE, indicating the USE was successful, the indexes are opened:
-
- USE accounts SHARED NEW IF !NetErr() SETINDEXTO acctnames, acctzip ELSE ? "File open failed" BREAK ENDIF
-
- This example opens a database file with several index files specified as extended expressions:
-
- cDataFile = "MyDbf" acIndex = {"MyIndex1", "MyIndex2", "MyIndex3"} USE (cDataFile) INDEX (acIndex[1]), ; (acIndex[2]), (acIndex[3])
-
- See Also
- CLOSE, DbSelect(), DbSetIndex(), DbSetOrder(), DbUseArea(), NetErr(), RddSetDefault()SELECT, SET INDEX, Used()
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_VAR.xml b/docs/Help_Spanish/Topics/command_VAR.xml
deleted file mode 100644
index 563047a521..0000000000
--- a/docs/Help_Spanish/Topics/command_VAR.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- VAR Statement
-
- Arrayscreatingdeclaring
- Compiledeclaration
- Creatingarraysvariables
- Declaration statements
- Statements
- VAR
- VAR statement
- Variable declaration
- Variablescreatingdeclaring
-
-
-
- VAR Statement
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_VOSTRUCT.xml b/docs/Help_Spanish/Topics/command_VOSTRUCT.xml
deleted file mode 100644
index f29d7ad2d1..0000000000
--- a/docs/Help_Spanish/Topics/command_VOSTRUCT.xml
+++ /dev/null
@@ -1,132 +0,0 @@
-
-
-
- VOSTRUCT Statement
-
- ALIGN
- Aligningstructure members
- Alignment of structures
- Compiletime declaration
- Data structuresalignmentdeclaringspecifying members
- Declaration statements
- END VOSTRUCT
- Entity declaration
- MEMBER clause
- Statements
- STATIC VOSTRUCT statement
- StructureAlignment
- VOSTRUCT
- VOSTRUCT statement
-
-
-
- VOSTRUCT Statement
-
-
- Purpose
- Declare a data structure and its member names.
- Syntax
- [Modifiers] VOSTRUCT <idStructure> [ALIGN 1|2|4|8]
- MEMBER <idVarList> AS | IS <idType> [, ...]
- MEMBER DIM <ArraySpec> [, ...] AS | IS <idType> [, ...]
- [END VOSTRUCT]
-
- Note: The MEMBER statement is shown using two syntax diagrams for convenience. You can declare variables and dimensioned arrays using a single MEMBER statement if each definition is separated by a comma.
- Arguments
-
-
- <idStructure>A valid identifier name for the structure. A structure is an entity and shares the same name space as other entities. This means that it is not possible to have a structure and a constant, for example, with the same name.
-
- MEMBERDeclares one or more structure member variables or dimensioned arrays. You can specify multiple MEMBER declarations on separate lines.
-
- <idVarList>A comma-separated list of identifier names for the structure member variables.
-
- DIM <ArraySpec>The specification for a dimensioned array to use as a structure member. <ArraySpec> is one of the following:
- <idArray>[<nElements>, <nElements>, <nElements>]
- <idArray>[<nElements>][<nElements>][<nElements>]
- All dimensions except the first are optional.
-
- <idArray> is a valid identifier name for the array to declare.
-
- <nElements> defines the number of elements in a particular dimension of an array. The number of dimensions is determined by how many <nElements> arguments you specify.
-
- <nElements> can be a literal numeric representation or a simple numeric expression involving only operators, literals, and DEFINE constants; however, more complicated expressions (such as function calls) are not allowed.
-
- AS <idType>Specifies the data type of the variable you are declaring (called strong typing). For DIM arrays, declares the data type for all array elements. The AS <idType> is required for all structure members.
-
- Refer to the CLASS entry for a list of valid values for <idType>. Note that the following data types are not supported in structures because they are dynamic types that require garbage collection:
- ARRAY
- FLOAT
- OBJECT
- <idClass>
- STRING
- USUAL
-
- IS <idType>Specifies a structure data type in which the memory needed to hold the structure is allocated on the stack (i.e., <idStructure> is the only <idType> allowed with the IS keyword).
-
- ALIGN 1|2|4|8Specifies the memory alignment of the structure. The default alignment is based on the size of the structure members. See the paragraph about alignment below.
- You may want to change this when you need to match a C/C++ structure that has been defined with a different alignment (the #pragma pack in a C/C++ header file).
- .
- Notes
- AS vs. IS: Once you have defined a structure, you can use its name to declare variables (see GLOBAL and LOCAL statements in this guide) designed to hold instances of a specific structure. When you declare a structure variable, you have the choice of using AS or IS typing. The difference between these two declaration methods is as follows:
-
-
IS automatically allocates the memory needed to hold the structure on the stack and de-allocates the memory when the declaring entity returns.
-
AS requires that you allocate memory using MemAlloc() when you initialize structure variables. You must also de-allocate the memory used by the structure variable using MemFree() before the declaring entity returns.
-
-
- Important! IS typing is much simpler than AS typing, and in most cases should satisfy your requirements for using structures. AS typing is recommended for experienced systems programmers who can, for various reasons, object to using the stack in this manner.
-
- Allocating substructures: An interesting property of a structure is that it can contain other structures as members but, if you type these substructures using AS, you must allocate and de-allocate memory for them. This is true regardless of whether the containing structure is typed with AS or IS:
-
- VOSTRUCT SysOne MEMBER iAlpha ASINT MEMBER pszName ASPSZ
VOSTRUCT SysTwo MEMBER iBeta ASINT MEMBER strucOne AS SysOne
FUNCTION UseStruct() LOCAL strucVar AS SysTwo strucVar := MemAlloc(_SizeOf(SysTwo)) strucVar.strucOne := MemAlloc(_SizeOf(SysOne)) ... MemFree(strucVar.strucOne) MemFree(strucVar)
-
- To simplify your programming, it makes sense to use IS for declaring substructures. Then, the memory for the substructure will be allocated and de-allocated with the memory for its containing structure:
- VOSTRUCT SysTwo MEMBER iBeta ASINT MEMBER strucOne IS SysOne
FUNCTION UseStruct() LOCAL strucVar AS SysTwo strucVar := MemAlloc(_SizeOf(SysTwo)) ... MemFree(strucVar)
-
- Accessing structure members: Structure variables are complex, the components being members that you declare within the structure. To access a structure member, use the dot operator (.) as follows:
-
- <idStructVar>.<idMember>
-
- Where <idStructVar> is a variable name or dimensioned array element that you have previously declared using a structure name, and <idMember> is a variable name or dimensioned array element declared within the VOSTRUCT definition as a MEMBER.
-
- Examples
- This example illustrates IS structure typing. No allocation is necessary but you must pass the structure by reference to calls.
-
- VOSTRUCT SysOne // Define SysOne data structure MEMBER iAlpha ASINT MEMBER pszName ASPSZ
FUNCTION Tester(strucSysOne AS SysOne) ASINT RETURN strucSysOne.iAlpha
FUNCTION UseStruct() LOCAL strucVar IS SysOne strucVar.iAlpha := 100 ? Tester(@strucVar) ...
-
- This example illustrates AS structure typing. This requires memory allocation and deallocation:
-
- VOSTRUCT SysOne // Define SysOne data structure MEMBER iAlpha ASINT MEMBER pszName ASPSZ
FUNCTION Tester(strucSysOne AS SysOne) ASINT RETURN strucSysOne.iAlpha
FUNCTION UseStruct() LOCAL strucVar AS SysOne strucVar := MemAlloc(_SizeOf(SysOne)) strucVar.iAlpha := 100 ? Tester(strucVar) ... MemFree(strucVar)
-
- With MEMBER, you can list several groups of variable and array names separated by commas and followed by an AS | IS <idType> clause to indicate that all names listed are to be typed as indicated. In this example, the variable x and the dimensioned array z are typed as INT, while the variables ptrX and ptrY are typed as PTR.
-
- VOSTRUCT SysOne // Define SysOne data structure MEMBER x, DIM z[100] ASINT, ptrX, ptrY ASPTR
-
- Default VoStruct Alignment
- You can choose to specify an alignment clause in the structure definition or let <%app%> determine the best alignment for you.
- The default alignment uses the following mechanism:
-
-
Each member of a size <= 8 gets a memory address inside its structure that is a multiple of its size. So WORD and SHORT members get aligned on EVEN boundaries, DWORD, LONG, PTR, PSZ members get aligned to 4-byte boundaries and REAL8 members get aligned to 8- byte boundaries. Byte members are not aligned, they can appear everywhere in the structure.
-
The total size of the structure is aligned to the size of the largest member. This is done to make sure that a dim array of structures (multiple structures adjacent in memory) also align properly.
-
When a structure contains an sub-structure (an IS declaration), the alignment of the outer structure uses the information from the inner structure.
-
-
- With manual (explicit) alignment, each element of the structure is aligned to a memory address that is a multiple of the alignment specified.
-
- Some examples of automatic alignment:
-
- VOSTRUCT test1 // Offset MEMBER W AS WORD // 0 MEMBER dw ASDWORD// 4 MEMBER b AS BYTE // 8 // Total size of structure = 12 bytes (largest element = 4, so padded to 12) // Memory layout of structure // 0123|4567|8901 // WW..|DWDW|B... // // WW = Word // DWDW = Dword // B = Byte // . = Padding
VOSTRUCT test1 // Offset MEMBER W AS WORD // 0 MEMBER r8 ASREAL8// 8 MEMBER b AS BYTE // 16 // Total size of structure = 24 bytes (largest element = 8, so padded to 24) // Memory layout of structure // 01234567|89012345|67890123 // WW......|R8R8R8R8|B.......
-
- Explicit (manual ) Structure Alignment
- In some situations you need to match a structure declaration from a C/C++ header file that has explicit alignment. Then you need to add the ALIGN clause to your structure declaration.
- This forces the compiler to align the structure elements to a multiple of the specified size.
- An alignment of 1 tells the compiler NOT to use padding, but to align all elements of a structure next to each other. This is the most compact option, but may be slower.
-
-
- Some examples of explicit alignment:
- VOSTRUCT test1 ALIGN 1 // Offset MEMBER W AS WORD // 0 MEMBER r8 ASDWORD// 2 MEMBER b AS BYTE // 6 // Total size of structure = 7 bytes (multiple of 1) // Memory layout of structure // 01|2345|6 // WW|DWDW|B // // WW = Word // DWDW = Dword // B = Byte // . = Padding
VOSTRUCT test1 ALIGN 2 // Offset MEMBER W AS WORD // 0 MEMBER dw ASDWORD// 2 MEMBER b AS BYTE // 6 // Total size of structure = 8 bytes ( multiple of 2) // Memory layout of structure // 01|23|45|67 // WW|DW|DW|B. VOSTRUCT test1 ALIGN 4 // Offset MEMBER W AS WORD // 0 MEMBER r8 ASDWORD// 4 MEMBER b AS BYTE // 8 // Total size of structure = 12 bytes (multiple of 4) // Memory layout of structure // 0123|4567|8901 // WW..|DWDW|B...
VOSTRUCT test1 ALIGN 8 // Offset MEMBER W AS WORD // 0 MEMBER r8 ASDWORD// 8 MEMBER b AS BYTE // 16 // Total size of structure = 24 bytes (multiple of 8) // Memory layout of structure // 01234567|89012345|67890123 // WW......|DWDW....|B.......
- See Also
- GLOBAL, LOCAL, MemAlloc(), MemFree(),, UNION
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_WAIT.xml b/docs/Help_Spanish/Topics/command_WAIT.xml
deleted file mode 100644
index 39bbb7a12c..0000000000
--- a/docs/Help_Spanish/Topics/command_WAIT.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- WAIT Command
-
- Commands
- Terminal window
- WAIT command
- Wait states
-
-
-
- WAIT Command
-
-
- Purpose
- Displays a prompt after sending a carriage return/linefeed to the terminal window, then waits for a key to be pressed.
-
- Note: WAIT is a compatibility command and is no longer recommended.
- Syntax
- WAIT [<uValuePrompt>] [TO <idVar>]
- Arguments
- <uValuePrompt>An optional prompt displayed before the input area. If omitted, "Press any key to continue..." is displayed. Specify NULL_STRING if you do not want to display a prompt.
-
- TO <idVar>The variable that will hold input from the keyboard. If there is no variable named <idVar> that is visible to the current routine, a private variable is created. <idVar> is assigned the keystroke as a string. If an Alt or Ctrl key combination is pressed, WAIT assigns Chr(0) to <idVar>.
-
- Non-alphanumeric values entered by pressing an Alt+key combination assign the specified character. If the character can be displayed, it is echoed to the screen.
- Example
- This example illustrates how to store the WAIT keystroke as an array element:
-
- FUNCTION Start ASVOID LOCAL aVar[2] WAIT "Press a key..." TO aVar[1] ? aVar[1] // Result: key pressed in // Response to WAIT ? aVar[2] // Result: NIL ? ValType(aVar) // Result: A ? ValType(aVar[1]) // Result: C
-
- See Also
- ACCEPT
-
-
diff --git a/docs/Help_Spanish/Topics/command_WITH.xml b/docs/Help_Spanish/Topics/command_WITH.xml
deleted file mode 100644
index 241272edd8..0000000000
--- a/docs/Help_Spanish/Topics/command_WITH.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- WITH command
-
-
- WITH command
-
- Purpose
- Specifies multiple properties for an object.
- Syntax
- WITH ObjectName [cStatements] or [:Statements] END WITH
- Arguments
- ObjectName Specifies the name of the object. ObjectName can be the name of the object or a reference to the object.
-
-
diff --git a/docs/Help_Spanish/Topics/command_XPP_Methods.xml b/docs/Help_Spanish/Topics/command_XPP_Methods.xml
deleted file mode 100644
index 874f0c1a84..0000000000
--- a/docs/Help_Spanish/Topics/command_XPP_Methods.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- METHOD Implementation
-
- ACCESS
- ACCESS METHOD
- ASSIGN METHOD
- CLASS METHOD
- END METHOD
- METHOD
-
-
-
- METHOD implementations (Xbase ++ dialect)
-
-
- Purpose
- Provide the implementation for methods that are forward defined between CLASS .. ENDCLASS.
- Syntax
-
- [Attributes] [ACCESS | ASSIGN] [Modifiers] METHOD [<ClassName>:] <MethodName>[ [([<idParam> [AS|REF|OUT|IN <idType>] [, ...])] ) [AS <idType>] [=> <expression>] CRLF
- [<Body>] [END METHOD]?
- Arguments
- ModifiersAn optional list of one or more modifiers. CLASS, STATIC, ABSTRACT, UNSAFE, ASYNC, EXTERN STATIC is a synonym for CLASS.
-
-
- ACCESS | ASSIGNDeclares that this method implements a Getter or Setter for a property.This must also be defined as ACCESS or ASSIGN in the class declaration.
-
-
- ClassNameThe name of the class in which the class method is declared. When only one class is declared in the PRG file, the class name is optional. Otherwise, <ClassName>: is required.
-
- <idMethod>A valid identifier name for the method. Method names must be unique within a class, but can share the same name as other entities (including access and assign methods) in your application.
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_Xpp_Classmembers.xml b/docs/Help_Spanish/Topics/command_Xpp_Classmembers.xml
deleted file mode 100644
index 3e518416dc..0000000000
--- a/docs/Help_Spanish/Topics/command_Xpp_Classmembers.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-
-
-
- METHOD Declarations
-
- ACCESS
- ACCESS METHOD
- ASSIGN METHOD
- CLASS METHOD
- END METHOD
- METHOD
-
-
-
- Method declarations (Xbase++ dialect)
-
-
- Purpose
- Declare and implement methods for a class, both for instances and the class itself.
- Syntax
- Method forward declaration
- [Modifiers] METHOD <MethodName,...> [IS <MethodName>] [IN <SuperClass>]
-
- Access/Assign method forward declaration
- [Attributes] ACCESS ASSIGN [CLASS] METHOD <MethodName> [VAR <VarName>] [AS <idType>]
- [Attributes] ACCESS | ASSIGN [CLASS] METHOD <MethodName> [VAR <VarName>] [AS <idType>]
-
- Method inline declaration
- [Attributes] INLINE [CLASS] METHOD <MethodName>[ [([<idParam> [AS|REF|OUT|IN <idType>] [, ...])] ) [AS <idType>] [=> <expression>] CRLF
- [<Body>] [END METHOD]
- Arguments
- ModifiersAn optional list of modifiers that specify info about the method. (DEFERRED , FINAL , INTRODUCE , OVERRIDE , CLASS , SYNC, NEW, STATIC, ASYNC, UNSAFE, EXTERN).
-
- <MethodName,...> A comma-separated list with the names of the instance methods being declared.The name for a method follows the same convention as function and variable names. It must begin with an underscore or a letter and must contain alpha numeric characters.
-
- IS <MethodName>The IS methodname clause is not supported by X#.
-
- IN <SuperClass>The IN Superclass clause is not supported (and not needed) by X#.
-
-
- CLASSOptional modifier that specify that the declaration is for a class level method or class level property.
-
- ACCESS ASSIGNDeclares a Get/Set method for a property. You can use one or both of these keywords.
-
- <VarName>The Get/Set method may have a different name than the property that they implement.
-
-
- INLINESpecifies that the whole method is included between the CLASS .. ENDCLASS keywords (other methods are so called forward declarations).
-
-
-
-
-
- Note
- The visibility of a method is determined by the visibility attribute set with one of the statements EXPORTED:, PROTECTED:, HIDDEN: or INTERNAL:.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_Xpp_InstanceVariables.xml b/docs/Help_Spanish/Topics/command_Xpp_InstanceVariables.xml
deleted file mode 100644
index aab315964f..0000000000
--- a/docs/Help_Spanish/Topics/command_Xpp_InstanceVariables.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- Fields
-
- ASSIGNMENT
- CLASS VAR
- VAR
-
-
-
- Fields (Xbase++ class syntax)
-
-
- Purpose
- Declare fields/ instance variables with optional initial values
- Syntax
- [Visibility :]
- [CLASS|STATIC] VAR <idVar,...> [IS <Name>] [IN <SuperClass>] [AS <idType>]
- [SHARED]
- [READONLY]
- [ASSIGNMENT HIDDEN | PROTECTED | EXPORTED] [NOSAVE]
- Arguments
- VisibilityThis sets the visibility for the variables on the line following the statement. This can be HIDDEN ,PROTECTED, EXPORTED or INTERNAL.The default visibility is HIDDEN.
-
- CLASS | STATICDeclares that this is a class level field.
-
- <idVar>A valid identifier name for the field to declare.
-
- IS .. IN ..This clause is not supported in X#
-
-
- SHAREDThis clause is not supported in X#.
-
- READONLYDeclares this field as Readonly. It must be initialized in the (class) constructor.
-
- ASSIGNMENT ..This clause is not supported in X#
-
- NOSAVEThis sets the [NonSerializable] attribute on the field.
- Note
- Xbase++ has a complicated set of rules on how to control read/write access to fields. In .Net we simply use the Visibility.
-
-
diff --git a/docs/Help_Spanish/Topics/command_YIELD.xml b/docs/Help_Spanish/Topics/command_YIELD.xml
deleted file mode 100644
index 92e4264462..0000000000
--- a/docs/Help_Spanish/Topics/command_YIELD.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- YIELD Statement
-
- YIELD
-
-
-
- YIELD Statement
-
- Purpose
- Using the yield keyword in a statement indicates that the method, operator, or get accessor in which it appears is an iterator.
- Syntax
- YIELD RETURN <expression> YIELD (EXIT|BREAK)
- Arguments
- YIELD RETURNYou use YIELD RETURN <expression> to return each element one at a time.
-
- YIELD [BREAK|EXIT]You use YIELD BREAK or YIELD EXIT to end the iteration.
- Examples
-
-
-
diff --git a/docs/Help_Spanish/Topics/command_ZAP.xml b/docs/Help_Spanish/Topics/command_ZAP.xml
deleted file mode 100644
index 17a1bbfd2d..0000000000
--- a/docs/Help_Spanish/Topics/command_ZAP.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- ZAP Command
-
- Commands
- Databasesrecords
- Deleting
- Recordsdeleting
- ZAP command
-
-
-
- ZAP Command
-
-
- Purpose
- Permanently remove all records from database file in the current work area.
- Syntax
- ZAP [[IN|ALIAS] <workarea>]
- Arguments
-
-
- Description
- ZAP is functionally equivalent to DBZap().
-
- See Also
- DBZap(), DELETE, PACK, USE
-
-
-
diff --git a/docs/Help_Spanish/Topics/command__DLL.xml b/docs/Help_Spanish/Topics/command__DLL.xml
deleted file mode 100644
index c885804c30..0000000000
--- a/docs/Help_Spanish/Topics/command__DLL.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- _DLL Statement
-
- _DLL statement
- Compile-time declaration
- Declaration statements
- DLLsdeclaring
- Dynamic linking
- Entity declaration
- Statements
-
-
-
- _DLL Statement
-
- Purpose
- Declare an entity defined in a DLL to the compiler.
- Syntax
- [Attributes] [Modifiers] _DLL FUNCTION | PROCEDURE [([<idParam> [AS | REF <idType>] [, ...])] [AS <idType>] [<idConvention>] :<idDLL>.<idEntity> [CharSet= AUTO|ANSI|UNICODE]
- Arguments
- <idEntity>The name or number of the entity as defined in the DLL. This is normally, but not necessarily, the same as the entity name defined in <EntityDeclaration>, which may define an alias by which the entity is called in your application. <idEntity> must be part of the public protocol of the DLL identified by <idDLL>. IdEntity may also be specified as a literal string. This should be done to specify names of exported functions in DLLs that contain characters that are not allowed as part of an identifier in X#.
-
-
- <idDLL>The name of the DLL file that contains the entity definition, specified without an extension or path name (that is, its base name). A .DLL extension is assumed (with some exceptions determined by Windows that may have an .EXE extension), and the rules used to search for the file at runtime are explained in the Description section below.
-
- CharsetOptionally specifies which character set string parameters have
- Description
- _DLL declares an entity that is used by your application but defined in a DLL. This statement tells the compiler not only the location and name (or number) of the DLL entity, but also its calling convention (that is, what parameters it expects and the type of value that it returns). When you declare an entity with the _DLL statement, it also indicates to the compiler that the entity has no additional source code following its declaration.
- Once declared, the entity may be called in your application in the standard way.
-
- Warning: Entity names contained within the _DLL statement are case sensitive. This is in direct contradiction to the X# compiler which is not case sensitive but is consistent with Windows calling protocols. For this reason, you must take extra care if Case Sensitization is turned on or you have the Caps Lock on.
- Examples
- The following examples illustrate _DLL declarations for two Windows API functions:
- _DLLFUNCTION MessageBeep(siLevel ASSHORTINT) ASVOID PASCAL:User.MessageBeep
_DLLFUNCTION MessageBox(hwndParent ASPTR, pszText ASPSZ, pszCapt ASPSZ, dwFlags ASDWORD) ; ASLONG PASCAL:User.MessageBox // You can also declare a function with "normal" string parameters if you want. Add the ANSI or UNICODE clause to indicate which version you want to call. _DLLFUNCTION MessageBox(hwndParent ASPTR, pszText ASSTRING, pszCapt ASSTRING, dwFlags ASDWORD) ; ASLONG PASCAL:User.MessageBox ANSI
- See Also
- ACCESS, ASSIGN, FUNCTION, METHOD, PROCEDURE
-
-
-
diff --git a/docs/Help_Spanish/Topics/compat-FoxPro.xml b/docs/Help_Spanish/Topics/compat-FoxPro.xml
deleted file mode 100644
index cdc50ec97b..0000000000
--- a/docs/Help_Spanish/Topics/compat-FoxPro.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-
-
-
- Differences with FoxPro
-
-
- Differences with FoxPro
-
- Compiler
-
-
-
- Operation
-
-
- Difference
-
-
-
-
- Bracketed strings
-
-
- The preprocessor in FoxPro translates #defines inside bracketed strings. X# does not touch the contents of bracketed strings in the preprocessor.
-
- The [] operator on usuals does not work with numeric usuals in X#.
-
-
-
- Runtime functions
-
-
-
- Function
-
-
- Difference
-
-
-
-
- FErase()
-
-
- Returns a LOGIC in X# and a Number Xbase++.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/debugger-Globals-Window.xml b/docs/Help_Spanish/Topics/debugger-Globals-Window.xml
deleted file mode 100644
index 0f64c3297c..0000000000
--- a/docs/Help_Spanish/Topics/debugger-Globals-Window.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Globals Window
-
-
- Globals Window
-
- On the Globals window, you can see a global variables in your app and the referenced class libraries that are loaded from your app.
-
-
-
- When your app does not include the X# runtime, a message will be shown that the runtime has not been loaded:
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/debugger-Publics-and-Privates-Window.xml b/docs/Help_Spanish/Topics/debugger-Publics-and-Privates-Window.xml
deleted file mode 100644
index 02848e0176..0000000000
--- a/docs/Help_Spanish/Topics/debugger-Publics-and-Privates-Window.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Publics and Privates Window
-
-
- Publics and Privates Window
-
- On this window, you will see the publics and privates available at the current line of your source code:
-
-
- You can use the checkboxes on the top to filter which type of variables you want to display.
-
- When your app does not include the X# runtime, a message will be shown that the runtime has not been loaded:
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/debugger-Settings-Window.xml b/docs/Help_Spanish/Topics/debugger-Settings-Window.xml
deleted file mode 100644
index 9ce2afb524..0000000000
--- a/docs/Help_Spanish/Topics/debugger-Settings-Window.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Settings Window
-
-
- Settings Window
-
- On this window, you will see the various settings at the current line of your source code, and for the current thread.
- You can sort these by name or by number.
-
-
-
- When your app does not include the X# runtime, a message will be shown that the runtime has not been loaded:
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/debugger-Toolbar-and-Menu.xml b/docs/Help_Spanish/Topics/debugger-Toolbar-and-Menu.xml
deleted file mode 100644
index 9069396baa..0000000000
--- a/docs/Help_Spanish/Topics/debugger-Toolbar-and-Menu.xml
+++ /dev/null
@@ -1,71 +0,0 @@
-
-
-
- Toolbar and Menu
-
-
- Toolbar and Menu
-
- When the Visual Studio integration for XSharp is installed, you will have a new menu entry when debugging. This menu entry can be found in the Debug menu and is called "XSharp".
- From that menu, you can open four different windows with XSharp-specific information.
-
-
Globals
-
Publics and Privates
-
Workareas
-
Settings
-
-
- These windows are shown as pane windows in the lower half of the debugger.
- The locations of these windows are (initially) associated with existing Visual Studio windows in the following way
-
-
-
-
- Window
-
-
- Associated with
-
-
-
-
- Globals
-
-
- Watch window
-
-
-
-
- Publics and Privates
-
-
- Output window
-
-
-
-
- Workareas
-
-
- Autos window
-
-
-
-
- Settings
-
-
- Callstack window
-
-
-
-
- If you move these windows to another location, Visual Studio will remember that new location.
-
-
- There is also an X# Debugger toolbar with buttons for these windows.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/debugger-Workareas-window.xml b/docs/Help_Spanish/Topics/debugger-Workareas-window.xml
deleted file mode 100644
index b15b1129dd..0000000000
--- a/docs/Help_Spanish/Topics/debugger-Workareas-window.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Workareas window
-
-
- Workareas window
-
- On this window, you will see the workareas open at the current line of your source code, for the current thread.
- The currently selected areas are marked with a checkbox.
-
-
-
- In the future we may extend this window, so you can see the properties of an area (such as BoF(), EoF() and RecNo()) and/or the field names and their values for the current record.
-
- When your app does not include the X# runtime, a message will be shown that the runtime has not been loaded:
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/dialect_All-Non-Core-dialects.xml b/docs/Help_Spanish/Topics/dialect_All-Non-Core-dialects.xml
deleted file mode 100644
index 6628b90c2b..0000000000
--- a/docs/Help_Spanish/Topics/dialect_All-Non-Core-dialects.xml
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
-
- All Non Core dialects
-
-
- All Non Core dialects
-
- The compiler and runtime have the following "special" behavior when compiling for any of the non-core dialects:
- Compiler
-
-
Allows "garbage" after keywords such as NEXT, ENDDO, etc.
-
-
-
Does not allows the DOT ('.') operator to call Instance methods.
-
-
-
Requires a reference to the XSharp.Core and XSharp.RT DLLs.
-
String Comparisons are mapped to a function in the XSharp runtime.
-
-
-
NULL_STRING is compiled into either "" or NULL, depending on the compiler option -vo2.
-
-
-
Supports literal symbols (#SomeName).
-
-
-
The String "=" operator is mapped to a function in the XSharp runtime.
-
-
-
The X# specific types such as DATE, ARRAY, SYMBOL, FLOAT, and USUAL, are not supported, but required a reference to the runtime.
-
Adds support for Dynamic Memory Variables and Undeclared variables.
-
-
-
Single quotes are used for String literals (except in Vulcan). Character literals must be prefixed with a c, like this: cChar := c'A'.
-
Allow the use of ASend() to call methods for each element inside a X# array.
-
The '=' operator may be used for assigns but will generate a warning when used.
-
Adds support for BEGIN SEQUENCE .. END SEQUENCE.
-
Adds support for the ALIAS (->) operator.
-
Adds support for the FIELD statement.
-
Adds support for the Macro compiler and &(variable) syntax.
-
Adds support for the ARRAY OF <type> syntax.
-
-
-
The compiler generated functions class is called: <AssemblyName>.Functions (DLLs) for functions and globals; <AssemblyName>.Exe.Functions (EXEs) for functions and globals;
-
- <AssemblyName>.Exe.$<ModuleName>$.Functions for static functions and globals.
-
-
The compiler adds several attributes (defined in XSharp.Core) to describe the default namespace and compiler version.
-
The compiler generates code for EXE files that set several properties in the Runtimestate to match compiler options and the dialect of the main app.
-
-
-
Procedures cannot return values.
-
Adds support for untyped variables and return values.
-
Adds support for untyped function and method parameters (the so-called Clipper calling convention).
-
Adds support for late bound code (requires the -lb compiler option).
-
Adds support for INIT and EXIT procedures.
-
Adds support for Codeblocks (untyped Lambda expressions with an array of USUAL parameters and a USUAL return value).
-
Allows skipping arguments in method calls. Skipped arguments are assumed to be NIL.
-
- Runtime
-
-
The default RDD all except the FoxPro dialect is DBFNTX.
-
-
-
diff --git a/docs/Help_Spanish/Topics/dialect_Core.xml b/docs/Help_Spanish/Topics/dialect_Core.xml
deleted file mode 100644
index fea76fd862..0000000000
--- a/docs/Help_Spanish/Topics/dialect_Core.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
- Core
-
- Core
-
-
-
- Core
-
- The compiler and runtime have the following "special" behavior when compiling for the "Core" dialect.
- Compiler
-
-
Does NOT allow 4 letter abbreviations of keywords.
-
Allows the DOT ('.') operator to call Instance methods.
-
Single quotes are used for Character literals.
-
-
-
String Comparisons are mapped to the String.Compare() method in the .Net runtime.
-
The String "=" operator is not supported.
-
The String "-" operator is not supported.
-
Anything that requires runtime support, such as the X# specific types (DATE, ARRAY, SYMBOL, FLOAT and USUAL) and dynamic memory variables, is not supported.
-
Supports the use of '@' to retrieve the address of a variable. This may also be used for REF variables if the compiler option -vo7 is used.
-
-
-
The '=' operator may be used for assigns but will generate a warning when used.
-
The compiler generated functions class is called:
-
- Functions for normal functions and globals;
- X$<ModuleName>$Functions for static functions and globals.
-
-
Procedures cannot return values.
-
Does not allow skipping arguments in method calls.
-
-
- Runtime
-
-
The Core dialect does not require a runtime. However, you can still link to XSharp.Core and XSharp.RDD and call methods and functions in these assemblies.
-
-
-
diff --git a/docs/Help_Spanish/Topics/dialect_FoxPro.xml b/docs/Help_Spanish/Topics/dialect_FoxPro.xml
deleted file mode 100644
index ff65bb9736..0000000000
--- a/docs/Help_Spanish/Topics/dialect_FoxPro.xml
+++ /dev/null
@@ -1,74 +0,0 @@
-
-
-
- FoxPro
-
- &&
- '@'
- \\
- _ACCESS
- _ASSIGN
- 4 letter abbreviations
- DBFVFP
- DEFINE CLASS
- DIMENSION
- ENDFOR
- FOR EACH
- FoxPro
- LPARAMETERS
- TEXT
- THIS
-
-
-
- FoxPro
-
- This dialect shares the features of "All Non Core Dialects".
- The compiler and runtime have the following "special" behavior when compiling for the "FoxPro" dialect:
- Compiler
-
-
Allows 4 letter abbreviations of some older keywords.
-
-
-
Allows "&&" as same line comment characters, just like "//".
-
-
-
Allows the DOT ('.') operator to call Instance methods.
-
-
-
The '@' operator is only used to pass variables by reference.
-
-
-
Allows ENDFOR instead of NEXT and FOR EACH instead of FOREACH.
-
-
-
The '=' operator will NOT generate a warning when used as assignment operator.
-
-
-
Adds several keywords such as THIS (as alias for SELF).
-
Adds support for CursorName.FieldName syntax.
-
Adds support for M.VariableName syntax.
-
Adds the DIMENSION statement syntax.
-
Adds the LPARAMETERS statement.
-
Adds the TEXT .. ENDTEXT statement.
-
Adds the \\ and \\\ statement.
-
Adds the "= <Expression>" command.
-
Adds the FoxPro specific DEFINE CLASS syntax to define classes, including the use of FUNCTION and PROCEDURE to define methods inside a class and the use of the _ACCESS and _ASSIGN suffixes on the names of these functions and procedures to declare access/assign methods.
-
Procedures may return values, and therefore, they are just like Functions.
-
-
-
Allows code before the first entity in a source file. This will be compiled into a function with the same name as the PRG file.
-
Adds support for the DoDefault() pseudo function.
-
The NIL keyword in FoxPro has the property 'unitialized' but a value of FALSE.
-
- Runtime
-
-
The default RDD in the FoxPro dialect is DBFVFP.
-
The MemoWrit() function adds an extra ^Z character to the end of file. MemoRead() removes this character when it finds it.
-
The DBF() function returns the full name of the file.
-
The _MRelease() function does not clear the memory variables but completely releases them.
-
New memory variables are always filled with a value of FALSE.
-
When comparing an initialized USUAL value with an unitialized value, an error will be generated in the FoxPro dialect. The other dialects will simply return FALSE.
-
-
-
diff --git a/docs/Help_Spanish/Topics/dialect_Harbour.xml b/docs/Help_Spanish/Topics/dialect_Harbour.xml
deleted file mode 100644
index c35ad919ba..0000000000
--- a/docs/Help_Spanish/Topics/dialect_Harbour.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- Harbour
-
- '@'
- 4 letter abbreviations
- Harbour
- IIF
-
-
-
- Harbour
-
- This dialect shares the features of "All Non Core Dialects".
- The compiler and runtime have the following "special" behavior when compiling for the "Harbour" dialect:
- Compiler
-
-
Allows 4 letter abbreviations of some older keywords.
-
-
-
The '@' operator is only used to pass variables by reference.
-
-
-
Allows IIF() expressions with a missing element, for example IIF(someCondition,DoSomething(),). The compiler will insert a NIL for a missing entry.
-
-
- Runtime
-
-
diff --git a/docs/Help_Spanish/Topics/dialect_VO.xml b/docs/Help_Spanish/Topics/dialect_VO.xml
deleted file mode 100644
index 20c7a8826b..0000000000
--- a/docs/Help_Spanish/Topics/dialect_VO.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- Visual Objects
-
- &&
- __VO__
- _WINBOOL
- 4 letter abbreviations
- PSZ
- UNION
- Visual Objects
- VOSTRUCT
-
-
-
- Visual Objects
-
- This dialect shares the features of "All Non Core Dialects".
- The compiler and runtime have the following "special" behavior when compiling for the "Visual Objects" dialect:
- Compiler
-
-
Allows 4 letter abbreviations of some older keywords.
-
Allows "&&" as same line comment characters, just like "//".
-
When a reference to XSharp.VO is added, certain VO-specific functions, such as RtRegString(), are enabled.
-
-
-
Supports the use of '@' to retrieve the address of a variable. This may also be used for REF variables if the compiler option -vo7 is used.
-
The preprocessor adds a define __VO__ with a value of TRUE.
-
Adds the VOSTRUCT and UNION entity types.
-
Uses the _WINBOOL type for logical values inside VOSTRUCT and UNION entities.
-
The indexer on PSZ types start with element 1. PLEASE NOTE that this is different from the Vulcan Dialect!
-
- Runtime
-
-
When running in Ansi more (SetAnsi(TRUE), which is the default), the DBF header for DBFNTX gets the Ansi bit set.
-
-
-
diff --git a/docs/Help_Spanish/Topics/dialect_Vulcan.xml b/docs/Help_Spanish/Topics/dialect_Vulcan.xml
deleted file mode 100644
index 4bfd7537cd..0000000000
--- a/docs/Help_Spanish/Topics/dialect_Vulcan.xml
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
-
- Vulcan
-
- '@'
- __VULCAN__
- _WINBOOL
- PSZ
- UNION
- VOSTRUCT
- Vulcan
-
-
-
- Vulcan
-
- This dialect shares the features of "All Non Core Dialects".
-
-
-
-
- Please note that in XSharp 3 the Vulcan dialect is only supported with the XSharp Runtime DLLs. Support for "Bring Your Own Runtime" is no longer available Also the compiler no longer automatically reads the setting for the location for the Vulcan Include files from the registry. If you use these files you need to make sure that the location where the files are stored is included in your project settings.
-
-
-
-
- The compiler and runtime have the following "special" behavior when compiling for the "Vulcan" dialect:
- Compiler
-
-
Does NOT allows 4 letter abbreviations of keywords.
-
-
-
Does NOT support Memory variables.
-
-
-
Does NOT allow && as same line comment characters (&& means .AND. in Vulcan).
-
-
-
Single quotes are used for Character literals.
-
-
-
Supports the use of '@' to retrieve the address of a variable. This may also be used for REF variables if the compiler option -vo7 is used.
-
-
-
NULL_STRING is compiled into either "" or NULL depending on the compiler option -vo2.
-
-
-
The preprocessor adds a define __VULCAN__ with a value of TRUE.
-
-
-
Adds the VOSTRUCT and UNION entity types.
-
-
-
Uses the _WINBOOL type for logical values inside VOSTRUCT and UNION entities.
-
-
-
The indexer on PSZ types start with element 0. PLEASE NOTE that this is different from the VO Dialect!
-
- Runtime
-
-
When running in Ansi more (SetAnsi(TRUE), which is the default), the DBF header for DBFNTX gets the Ansi bit set.
-
The NoMethod() method gets an extra 1st parameter that contains the name of the method that was called.
-
-
-
diff --git a/docs/Help_Spanish/Topics/dialect_XPP.xml b/docs/Help_Spanish/Topics/dialect_XPP.xml
deleted file mode 100644
index 273ac16404..0000000000
--- a/docs/Help_Spanish/Topics/dialect_XPP.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
- Xbase++
-
- &&
- '@'
- __XPP__
- ENDFOR
- Xbase++
-
-
-
- Xbase++
-
- This dialect shares the features of "All Non Core Dialects".
- The compiler and runtime have the following "special" behavior when compiling for the "Xbase++" dialect:
- Compiler
-
-
Allows 4 letter abbreviations of those keywords where this is also supported in Xbase++.
-
-
-
Allows "&&" as same line comment characters, just like "//".
-
-
-
The '@' operator is only used to pass variables by reference.
-
The preprocessor adds a define __XPP__ with a value of TRUE.
-
-
-
Allows ENDFOR instead of NEXT.
-
-
-
Adds the Xbase++ specific CLASS syntax to define classes.
-
The entry point to the code is the main() function or main() procedure.
-
- Runtime
-
-
FieldGet() and FieldPut() will not throw an error when writing to non existing field Positions.
-
If you use the index operator on a usual which contains a string, you will receive the 1 based substring of the value.
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Blocks.xml b/docs/Help_Spanish/Topics/editor-Blocks.xml
deleted file mode 100644
index ebe8f4baa2..0000000000
--- a/docs/Help_Spanish/Topics/editor-Blocks.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Blocks
-
- Blocks
-
-
-
- Blocks
-
- Visual Studio makes it easy to select, cut, copy, and paste sections of your code. Rectangular blocks of code can be highlighted and selected by using Alt + Drag on the code block. The formatting within the block selection is retained when pasting the block.
-
- Block selections can also be used to edit text on multiple lines simultaneously. A zero-width block selection allows you to place the caret in front of multiple lines at once, enabling you to type identical text across several lines:
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Brace-matching.xml b/docs/Help_Spanish/Topics/editor-Brace-matching.xml
deleted file mode 100644
index 1658feef5a..0000000000
--- a/docs/Help_Spanish/Topics/editor-Brace-matching.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Brace matching
-
- Brace matching
-
-
-
- Brace matching
-
- When using Visual Studio, if your cursor is next to a brace, it will highlight the corresponding opening or closing brace on screen.
-
- The color for the brace matching can be set in the Tools/Options dialog under the Environment/Fonts and Colors node.
- The X# specific colors all start with the text "X#".
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Code-Completion.xml b/docs/Help_Spanish/Topics/editor-Code-Completion.xml
deleted file mode 100644
index a48272df93..0000000000
--- a/docs/Help_Spanish/Topics/editor-Code-Completion.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- Code Completion
-
- Code Completion
-
-
-
- Code Completion
-
- IntelliSense is an invaluable resource while coding. It provides information about available members of a type and displays parameter details for different method overloads. You can also use IntelliSense to complete a word once you have typed enough characters to make it unambiguous.
-
- As you type, IntelliSense displays Quick Info about the query symbol.
- To insert the rest of the word query using IntelliSense's word completion feature, press Tab.
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Formatting-code.xml b/docs/Help_Spanish/Topics/editor-Formatting-code.xml
deleted file mode 100644
index 3774effb9d..0000000000
--- a/docs/Help_Spanish/Topics/editor-Formatting-code.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Indenting code
-
- Formatting code
-
-
-
- Indenting code
-
- Visual studio automatically formats your code, so that you have a clearer overview of your code, and which parts do what.
- This only happens if you have set the Indenting option on the Tabs page to "Smart".
- The formatting rules are defined on the Indentation page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Goto-definition.xml b/docs/Help_Spanish/Topics/editor-Goto-definition.xml
deleted file mode 100644
index fe903bb443..0000000000
--- a/docs/Help_Spanish/Topics/editor-Goto-definition.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Go to definition
-
- Goto definition
-
-
-
- Go to definition
-
- The Visual Studio editor makes it easy to inspect the definition of a type, method, etc. One way to do this is by navigating to the file that contains the definition, for example, by selecting Go to Definition or pressing F12 on any reference to the symbol.
- To do this, right-click on any occurrence of string and choose Peek Definition from the content menu, or press Alt+F12.
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Highlighting-Errors.xml b/docs/Help_Spanish/Topics/editor-Highlighting-Errors.xml
deleted file mode 100644
index 19b5836011..0000000000
--- a/docs/Help_Spanish/Topics/editor-Highlighting-Errors.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- Highlighting Errors
-
- Highlighting Errors
-
-
-
- Highlighting Errors
-
- Currently, errors are not highlighted in the source code editor. This is planned for a future version of X#.
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Inactive-conditional-regions.xml b/docs/Help_Spanish/Topics/editor-Inactive-conditional-regions.xml
deleted file mode 100644
index 68fc549502..0000000000
--- a/docs/Help_Spanish/Topics/editor-Inactive-conditional-regions.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Inactive conditional regions
-
- Inactive conditional regions
-
-
-
- Inactive conditional regions
-
- If you use conditional compilation with #ifdef .. #endif regions, the inactive regions will be visible with different color in the editor.
- Below is a piece of code from the CDX RDD. The CHECKVERSIONS define is not defined, so there is an inactive region in the editor, which is shown in light gray.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Keyword-Coloring.xml b/docs/Help_Spanish/Topics/editor-Keyword-Coloring.xml
deleted file mode 100644
index 8b70d1f7c8..0000000000
--- a/docs/Help_Spanish/Topics/editor-Keyword-Coloring.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- Keyword Coloring
-
- Keyword Coloring
-
-
-
- Keyword Coloring
-
- Visual studio gives keywords and other parts of the syntax colors based on their purpose. The following items are supported by X#:
-
-
- Keywords
- Identifiers
- Comments (single line, multi line, etc.)
- Operators (+. -, := etc.)
- Strings (also for Char constants)
- Numbers (also for date and datetime literals)
- Literals(NIL, Symbols, _AND, _OR, _NOT, _XOR)
- Preprocessor keywords
- * contents of Text .. EndText
- Inactive/Hidden code inside #IFDEF
- * Highlighted Word
-
-
- * These are special XSharp colors. The other colors take the default Visual Studio editor colors for that category.
-
-
- You can change the options for this by going to Tools > Options > .
- Note that your settings will reset if you switch your color scheme in Visual Studio.
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Parameter-Tips.xml b/docs/Help_Spanish/Topics/editor-Parameter-Tips.xml
deleted file mode 100644
index 7248c4011e..0000000000
--- a/docs/Help_Spanish/Topics/editor-Parameter-Tips.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Parameter Tips
-
- Parameter Tips
-
-
-
- Parameter Tips
-
- Parameter Info provides information about the number, names, and types of parameters required by a method, attribute generic type parameter.
- The parameter in bold indicates the next parameter that is required as you type the function. For overloaded functions, you can use the Up and Down arrow keys to view alternative parameter information for the function overloads.
-
- When you annotate functions and parameters with XML Documentation comments, the comments will display as Parameter Info. For more information, see Supply XML code comments.
- You can manually invoke Parameter Info by choosing Edit > IntelliSense > Parameter Info, by pressing Ctrl+Shift+Space, or by choosing the Parameter Info button on the editor toolbar.
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Peek-definition.xml b/docs/Help_Spanish/Topics/editor-Peek-definition.xml
deleted file mode 100644
index a6b24683fc..0000000000
--- a/docs/Help_Spanish/Topics/editor-Peek-definition.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Peek definition
-
- Peek definition
-
-
-
- Peek definition
-
- The Visual Studio editor makes it easy to inspect the definition of a type, method, etc. One way is to navigate to the file that contains the definition, for example, by choosing Peek Definition anywhere the symbol is referenced.
- To do this, right-click on any occurrence of string and choose Peek Definition from the content menu, or press Alt+F12.
- A pop-up window appears with the definition of the String class. You can scroll within the pop-up window, or even peek at the definition of another type from the peeked code.
- Close the peeked definition window by choosing the small box with an "x" at the top right of the pop-up window.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Quick-Info.xml b/docs/Help_Spanish/Topics/editor-Quick-Info.xml
deleted file mode 100644
index 103dcca486..0000000000
--- a/docs/Help_Spanish/Topics/editor-Quick-Info.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- Quick Info
-
- Quick Info
-
-
-
- Quick Info
-
- Quick Info displays the complete declaration for any identifier in your code. Quick Info also appears when selecting a member from the List Members box.
-
- You can manually invoke Quick Info by choosing Edit > IntelliSense > Quick Info, by pressing Ctrl+I, or by choosing the Quick Info button on the editor toolbar.
-
- If a function is overloaded, IntelliSense may not display information for all forms of the overload.
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Regions.xml b/docs/Help_Spanish/Topics/editor-Regions.xml
deleted file mode 100644
index 84a7874816..0000000000
--- a/docs/Help_Spanish/Topics/editor-Regions.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- Regions
-
- Regions
-
-
-
- Regions
-
- To unclutter your view of the code, click the small gray box with a minus sign in the margin of the first line of the constructor, or place the cursor anywhere within the constructor code and press Ctrl+M, Ctrl+M.
-
- The code block will collapse, showing only the first line followed by an ellipsis. To expand the code block again, click the same gray box, which now has a plus sign, or press Ctrl+M, Ctrl+M again. This feature is called Outlining and is especially useful when collapsing long methods or entire classes.
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/editor-Snippets.xml b/docs/Help_Spanish/Topics/editor-Snippets.xml
deleted file mode 100644
index 9fdcb73f38..0000000000
--- a/docs/Help_Spanish/Topics/editor-Snippets.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- Snippets
-
- Snippets
-
-
-
- Snippets
-
- Visual Studio provides useful code snippets that you can use to quickly and easily generate commonly used code blocks.
- To do this, place your cursor just above the final closing brace in the file. A pop-up dialog box appears with information about the code snippet.
-
- You can fill in the yellow sections, press tab to switch between these sections.
-
- You can look at the available code snippets for X# by choosing Edit > IntelliSense > Insert Snippet or right-click > Snippet > Insert Snippet or pressing Ctrl+K, Ctrl+X.
- The list includes snippets for creating a class, a constructor, a for loop, an if or switch statement, and more.
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-ASTYPE.xml b/docs/Help_Spanish/Topics/new-feat-ASTYPE.xml
deleted file mode 100644
index 70bdc580f3..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-ASTYPE.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- ASTYPE
-
-
- ASTYPE
-
- We have added a new keyword that allows you to cast a value to a type with type, just like the C# "as" keyword:
-
- FUNCTION Test (oVar as ParentClass) LOCAL oChild := oVar ASTYPE ChildClass IF (oChild != NULL_OBJECT) DoSomething() ENDIF
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-ASYNC-AWAIT.xml b/docs/Help_Spanish/Topics/new-feat-ASYNC-AWAIT.xml
deleted file mode 100644
index 7ad2e15c91..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-ASYNC-AWAIT.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- ASYNC - AWAIT
-
-
- ASYNC - AWAIT
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Anonymous-Classes.xml b/docs/Help_Spanish/Topics/new-feat-Anonymous-Classes.xml
deleted file mode 100644
index f2267235ce..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Anonymous-Classes.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- Anonymous Types
-
-
- Anonymous Types
-
- Anonymous types provide a convenient way to encapsulate a set of read-only properties into a single object without having to explicitly define a type first. The type name is generated by the compiler and is not available at the source code level. The type of each property is inferred by the compiler.
-
- The syntax for an anonymous class is :
-
- VAR o := CLASS { Name := "test", Value := "something" }
- In LINQ this may lead to:
-
- VAR result := from c in db.Customers where c.Orders.Count > 0 ; selectCLASS{ ID := C.CustomerID, Name := C.CustomerName, OrderCount := C.Orders.Count}
- In this case, the object will have the properties ID, Name and OrderCount (all explicitely given).
-
- If you select named properties from another object you can omit the <Name> := part. In that case, the compiler will simply use the same name:
-
- VAR result := from c in db.Customers where c.Orders.Count > 0 ; selectCLASS{ C.CustomerID, C.CustomerName, OrderCount := C.Orders.Count}
-
- In this case, the anonymous class will have the properties CustomerID, CustomerName (inherited from C) and OrderCount (explicitely given).
-
- Anonymous types contain one or more public read-only properties. No other kinds of class members, such as methods or events, are valid. The expression that is used to initialize a property cannot be null, an anonymous function, or a pointer type.
-
- The most common scenario is to initialize an anonymous type with properties from another type. In the following example, assume that a class exists that is named Product. Class Product includes Color and Price properties, together with other properties that you are not interested in. Variable products is a collection of Product objects. The anonymous type declaration starts with the new keyword. The declaration initializes a new type that uses only two properties from Product. This causes a smaller amount of data to be returned in the query.
-
- If you do not specify member names in the anonymous type, the compiler gives the anonymous type members the same name as the property being used to initialize them. You must provide a name for a property that is being initialized with an expression, as shown in the previous example. In the following example, the names of the properties of the anonymous type are Color and Price.
-
- var productQuery := ; from prod in products ; selectCLASS { prod:Color, prod:Price }
foreachvar v in productQuery Console.WriteLine("Color={0}, Price={1}", v:Color, v:Price) next
- Typically, when you use an anonymous type to initialize a variable, you declare the variable as an implicitly typed local variable by using var. The type name cannot be specified in the variable declaration because only the compiler has access to the underlying name of the anonymous type.
- Remarks
-
- Anonymous types are class types that derive directly from object, and that cannot be cast to any type except object. The compiler provides a name for each anonymous type, although your application cannot access it. From the perspective of the common language runtime (CLR), an anonymous type is no different from any other reference type.
-
- If two or more anonymous object initializers in an assembly specify a sequence of properties that are in the same order and that have the same names and types, the compiler treats the objects as instances of the same type. They share the same compiler-generated type information.
-
- You cannot declare a field, a property, an event, or the return type of a method as having an anonymous type. Similarly, you cannot declare a formal parameter of a method, property, constructor, or indexer as having an anonymous type. To pass an anonymous type, or a collection that contains anonymous types, as an argument to a method, you can declare the parameter as type object. However, doing this defeats the purpose of strong typing. If you need to store query results or pass them outside the method boundary, consider using an ordinary named struct or class instead of an anonymous type.
-
- Because the Equals and GetHashCode methods on anonymous types are defined in terms of the Equals and GetHashCode methods of the properties, two instances of the same anonymous type are equal only if all their properties are equal.
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Anonymous-Methods.xml b/docs/Help_Spanish/Topics/new-feat-Anonymous-Methods.xml
deleted file mode 100644
index a20c2a15b7..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Anonymous-Methods.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Anonymous Methods
-
-
- Anonymous Methods
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-BEGIN-CHECKED.xml b/docs/Help_Spanish/Topics/new-feat-BEGIN-CHECKED.xml
deleted file mode 100644
index 7f0665a43e..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-BEGIN-CHECKED.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- BEGIN CHECKED
-
- BEGIN
- CHECKED
-
-
-
- BEGIN CHECKED
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-BEGIN-FIXED.xml b/docs/Help_Spanish/Topics/new-feat-BEGIN-FIXED.xml
deleted file mode 100644
index 67f2505c3a..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-BEGIN-FIXED.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- BEGIN FIXED
-
- BEGIN
- FIXED
-
-
-
- BEGIN FIXED
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-BEGIN-UNCHECKED.xml b/docs/Help_Spanish/Topics/new-feat-BEGIN-UNCHECKED.xml
deleted file mode 100644
index 0610bd471b..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-BEGIN-UNCHECKED.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- BEGIN UNCHECKED
-
- BEGIN
- UNCHECKED
-
-
-
- BEGIN UNCHECKED
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-BEGIN-UNSAFE.xml b/docs/Help_Spanish/Topics/new-feat-BEGIN-UNSAFE.xml
deleted file mode 100644
index 332dc7ae3b..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-BEGIN-UNSAFE.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- BEGIN UNSAFE
-
- BEGIN
- UNSAFE
-
-
-
- BEGIN UNSAFE
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-BEGIN-USING.xml b/docs/Help_Spanish/Topics/new-feat-BEGIN-USING.xml
deleted file mode 100644
index 62ee75a4b0..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-BEGIN-USING.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- BEGIN USING
-
- BEGIN
- USING
-
-
-
- BEGIN USING
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Collection-Initializers.xml b/docs/Help_Spanish/Topics/new-feat-Collection-Initializers.xml
deleted file mode 100644
index 48cf5710bb..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Collection-Initializers.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- Collection Initializers
-
-
- Collection Initializers
-
- Collection initializers allow you to fill a collection with a list of values.
- In the background, the compiler will generate code that calls the Add method of the collection.
- The example below creates a list of Integers, Strings and Persons.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Conditional-Access-Expression.xml b/docs/Help_Spanish/Topics/new-feat-Conditional-Access-Expression.xml
deleted file mode 100644
index d35c7cde74..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Conditional-Access-Expression.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Conditional Access Expression
-
-
- Conditional Access Expression
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Creating-Generic-Classes.xml b/docs/Help_Spanish/Topics/new-feat-Creating-Generic-Classes.xml
deleted file mode 100644
index 3621db89dd..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Creating-Generic-Classes.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- Creating Generic Classes
-
- Generic
-
-
-
- Creating Generic Classes
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-DEFAULT-Expressions.xml b/docs/Help_Spanish/Topics/new-feat-DEFAULT-Expressions.xml
deleted file mode 100644
index f882178a44..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-DEFAULT-Expressions.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- DEFAULT Expressions
-
- DEFAULT
-
-
-
- DEFAULT Expressions
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-EVENT-(Add-and-Remove).xml b/docs/Help_Spanish/Topics/new-feat-EVENT-(Add-and-Remove).xml
deleted file mode 100644
index cf4921d20b..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-EVENT-(Add-and-Remove).xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- EVENT (Add and Remove)
-
- ADD
- EVENT
- REMOVE
-
-
-
- EVENT (Add and Remove)
-
- XSharp now supports an extended Event syntax. Both a single line syntax is supported as a multi line:
- Old style syntax
-
- [Attributes] [Modifiers] EVENT [<ExplicitInterface>.] <Id> AS <Type> // Old Style
- Single Line syntax with explicit expressions
-
- [Attributes] [Modifiers] EVENT [<ExplicitInterface>.] <Id> AS <Type> [ADD <ExpressionList] [REMOVE <ExpressionList] // Single Line
- Multi line syntax with explicit expressions
- [Attributes] [Modifiers] EVENT [<ExplicitInterface>.] <Id> AS <Type> // Multi line
ADD <Statements> END [ADD] REMOVE <Statements> END [REMOVE] END [EVENT]
-
- Example
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Expression-IS-Type.xml b/docs/Help_Spanish/Topics/new-feat-Expression-IS-Type.xml
deleted file mode 100644
index b5cbfb2b14..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Expression-IS-Type.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- Expression IS Type
-
- IS
-
-
-
- Expression IS Type
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Initializers.xml b/docs/Help_Spanish/Topics/new-feat-Initializers.xml
deleted file mode 100644
index ddab96d8f9..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Initializers.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
- Initializers
-
-
- Initializers
-
- USING System USING System.Collections.Generic USING System.Linq USING System.Text
FUNCTION Start() ASVOID LOCAL oList AS List<Int> // The next line creates the collection and adds 5 elements // Note the double curly braces: // The first pair calls the default constructor of the List<> Class // The second pair of curly braces surrounds the list of values Console.WriteLine("Collection Initializers") oList := List<Int>{} {1,2,3,4,5} FOREACHVAR i IN oLIst Console.WriteLine(i) NEXT VAR oCompass := List<String>{}{"North", "East", "South", "West"} FOREACHVAR sDirection in oCompass Console.WriteLine(sDirection) NEXT Console.ReadLine() // Now an example of an Object Initializer // Note that the object has no constructor // We are assigning the values directly to the properties // This will only work if there are public properties // Again there are double curly braces: // The first pair calls the default constructor of the Person class // The second pair of curly braces surrounds the list of name-value pairs
Console.WriteLine("Object Initializer") VAR oPerson := Person{}{FirstName := "John", LastName := "Smith"} ? oPerson:Name Console.ReadLine() // Combine the two Var oPeople := List<Person> {} {; Person{}{FirstName := "John", LastName := "Smith"}, ; Person{}{FirstName := "Jane", LastName := "Doe"} ; } Console.WriteLine("Collection and Object Initializers") FOREACHvar oP in oPeople Console.WriteLine(oP:Name) NEXT Console.ReadLine() RETURN
PUBLICCLASS Person PROPERTY FirstName ASSTRINGAUTO PROPERTY LastName ASSTRINGAUTO PROPERTY Name ASSTRINGGET FirstName+" "+LastName ENDCLASS
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Interpolated-Strings.xml b/docs/Help_Spanish/Topics/new-feat-Interpolated-Strings.xml
deleted file mode 100644
index e30a5b669b..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Interpolated-Strings.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Interpolated Strings
-
- ei"..."
- i"..."
- ie"..."
- Interpolated
- String
-
-
-
- Interpolated Strings
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-LINQ.xml b/docs/Help_Spanish/Topics/new-feat-LINQ.xml
deleted file mode 100644
index 0a3f8869ac..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-LINQ.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- LINQ Query Expressions
-
- LINQ
-
-
-
- LINQ Query Expressions
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-NOP.xml b/docs/Help_Spanish/Topics/new-feat-NOP.xml
deleted file mode 100644
index 1451649706..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-NOP.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- NOP
-
- NOP
-
-
-
- NOP
-
- The NOP keyword allows you to define a line of code that does nothing but satisfies the compiler, so it will not complain about missing code.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-Object-Initializers.xml b/docs/Help_Spanish/Topics/new-feat-Object-Initializers.xml
deleted file mode 100644
index 4e14d19e8c..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-Object-Initializers.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- Object Initializers
-
-
- Object Initializers
-
- Object Initializers allow you to instantiate an object and assign values to its properties in one line of code. The example below uses object initializers to set the FirstName and LastName property of the Person object:
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-PROCEDURE-inside-CLASS.xml b/docs/Help_Spanish/Topics/new-feat-PROCEDURE-inside-CLASS.xml
deleted file mode 100644
index a880c0aedd..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-PROCEDURE-inside-CLASS.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- PROCEDURE inside CLASS
-
- PROCEDURE
- STATIC METHOD
-
-
-
- PROCEDURE inside CLASS
-
- Enter topic text here.
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-SWITCH.xml b/docs/Help_Spanish/Topics/new-feat-SWITCH.xml
deleted file mode 100644
index 616d4a3560..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-SWITCH.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- SWITCH
-
- SWITCH
-
-
-
- SWITCH
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-USING.xml b/docs/Help_Spanish/Topics/new-feat-USING.xml
deleted file mode 100644
index 4300b6e249..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-USING.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- USING
-
- USING
-
-
-
- USING
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-VAR.xml b/docs/Help_Spanish/Topics/new-feat-VAR.xml
deleted file mode 100644
index 01adfae1ee..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-VAR.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- VAR
-
- VAR
-
-
-
- VAR
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-XBase-class-declarations.xml b/docs/Help_Spanish/Topics/new-feat-XBase-class-declarations.xml
deleted file mode 100644
index 59c9445073..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-XBase-class-declarations.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- Xbase++ class declarations
-
-
- Xbase++ class declarations
-
- As of build 2.0.0.8, X# also support Xbase++ style class declarations. Of course, we have added strong typing to the language definition to make the code run faster.
- Full documentation will be included in one of the next builds. The code below shows the Xbase++ support in action:
-
- CLASS Developer classvar list asarray// class vars are like static variables. classVAR nextid asint classvar random as Random PROTECTED: VAR id asintNOSAVE// the Nosave clause will mark the field with the [NonSerialized] attribute EXPORTED: VAR FirstName asstring VAR LastName asstring VAR Country asstring // The inline prefix in the next line is needed when declaring a method inside the class .. endclass block. INLINEMETHOD initClass() // The Xbase++ equivalent of the Static constructor list := {} nextid := 1 random := Random{} RETURN
INLINEMETHOD Init(cFirst asstring , cLast asstring, cCountry asstring) // Init is the constructor // you can use :: instead of SELF: ::FirstName := cFirst ::LastName := cLast ::Country := cCountry ::id := nextid nextid += 1 aadd(list, SELF) RETURN
INLINEMethod SayHello() asSTRING if ::Age < 40 RETURN "Hello, I am " + ::FirstName+ " from "+::Country else RETURN "Hello, I am mr " + ::LastName+ " from "+::Country+" but you can call me "+::FirstName endif
INLINEMETHOD Fire() as logic local nPos asdword nPos := Ascan(list, SELF) if nPos > 0 aDel(list, nPos) ASize(list, aLen(list)-1) return true endif return false // the next block contains forward declarations. The methods has to be declared below the class .. endclass block
// SYNC method makes sure that only one thread can run this code at the same time SYNCMETHOD LivesIn // ACCESS indicates a PROPERTY GET // ASSIGN indicates a PROPERTY SET ACCESSCLASSMETHOD Length asdword ACCESSMETHOD Age asint ENDCLASS
// This is the implementation of LivesIn. SYNC does not have to be repeated here METHOD LivesIn(cCountry asstring) as logic return lower(::Country) == lower(cCountry)
// This is the implementation of the AGE Property. ACCESS does not have to be repeated here METHOD Age() asint local nAge asint nAge := random:@@Next(25,60) return nAge
// This is the implementation of the Length Property. ACCESS does not have to be repeated. CLASS however must be specified. CLASSMETHOD Length as dwor return ALen(list) // the entry point is Main() like in Xbase++ function Main(a) asint local oDeveloper as Developer local aDevs := {} asarray local i asint if PCount() > 0 ? "Parameters" for i := 1 to PCount() ? _GetFParam(i) next endif // create a new object with Xbase++ Syntax. Developer{} would have worked as well. aadd(aDevs, Developer():New("Chris", "Pyrgas", "Greece")) aadd(aDevs, Developer():New("Nikos", "Kokkalis","Greece")) aadd(aDevs, Developer():New("Fabrice", "Foray","France")) aadd(aDevs, Developer():New("Robert", "van der Hulst","The Netherlands")) ? "# of devs before", Developer.Length for i := 1 to alen(aDevs) oDeveloper := aDevs[i] ? "Fields", oDeveloper:FirstName, oDeveloper:LastName, oDeveloper:Country ? "FullName",oDeveloper:FullName() ? oDeveloper:SayHello() ? "Greece ?", oDeveloper:LivesIn("Greece") ? "Fired", oDeveloper:Fire() ? "# of devs after firing", oDeveloper:FirstName, Developer.Length next _wait() RETURN PCount()
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/new-feat-YIELD.xml b/docs/Help_Spanish/Topics/new-feat-YIELD.xml
deleted file mode 100644
index 0c92a93a46..0000000000
--- a/docs/Help_Spanish/Topics/new-feat-YIELD.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- YIELD
-
- EXIT
- RETURN
- YIELD
-
-
-
- YIELD EXIT and YIELD RETURN
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/operator_IIF.xml b/docs/Help_Spanish/Topics/operator_IIF.xml
deleted file mode 100644
index cbb669b653..0000000000
--- a/docs/Help_Spanish/Topics/operator_IIF.xml
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-
- IIF Operator
-
-
- IIF Operator
-
- The IIF operator returns one of two values, depending on an expression that returns a value of type LOGIC. The IIF operator is of the form:
-
-
- Remarks
-
- conditionExpression may be any expression that returns a value of type LOGIC, or a type that can be implicitly converted to LOGIC.
- If conditionExpression evaluates to TRUE, trueExpression is evaluated and is the result. If conditionExpression evaluates to FALSE, falseExpression is evaluated and is the result. Only one of the two expressions is ever evaluated.
-
- The return type of the IIF operator is determined by the following rules:
- Given:
-
-
tT is the type of trueExpression
-
tF is the type of falseExpression
-
tR is the return type of the IIF expression
-
-
-
-
If tT and tF are the same type, tR is that type.
-
If tT and/or tF is USUAL, then tT or tF is converted to USUAL if necessary, and tR is USUAL.
-
If tT can be implicitly converted to tF, tR is tF.
-
If tF can be implicitly converted to tT, tR is tT.
-
If tT can be implicitly converted to tF and tF can be implicitly converted to tT, then tR is ambiguous and a compiler error is raised.
-
If tT cannot be implicitly converted to tF and tF cannot be implicitly converted to tT, then tR is indeterminate and a compiler error s raised. Note that if tT and tF are VOID, tR is VOID and the IIF operator cannot be used as an operand in another expression, or as a function or method parameter. In this case, the IIF operator is essentially the same as an IF...ELSE...ENDIF construct and can only be used in stand-alone expression statements.
-
- In cases 5 and 6, it may be possible to resolve the error by specifying an explicit cast on trueExpression or falseExpression.
-
- This behavior is different than in some other XBase dialects In these dialects the return is usually determined by the following rules
-
-
If tT and tF are the same type, tR is that type.
-
Otherwise, tT and tR are implicitly converted to USUAL and tR is USUAL.
-
-
- You can use the /vo10 compiler option to enable this behavior in X#, but this is only recommended for code originally written in other environments, such as Visual Objects.
-
- Note
- For compatibility with Visual Objects and several other dialects the IF() operator is also supported.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-At.xml b/docs/Help_Spanish/Topics/opt-At.xml
deleted file mode 100644
index 3d53314c67..0000000000
--- a/docs/Help_Spanish/Topics/opt-At.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- @
-
- @ compiler option
-
-
-
- @
-
- The @ option lets you specify a file that contains compiler options and source code files to compile.
- Syntax
- @response_file
- Arguments
- response_fileA file that lists compiler options or source code files to compile.
- Remarks
- The compiler options and source code files will be processed by the compiler just as if they had been specified on the command line.
-
- To specify more than one response file in a compilation, specify multiple response file options. For example:
-
-
- @file1.rsp @file2.rsp
-
- In a response file, multiple compiler options and source code files can appear on one line. A single compiler option specification must appear on one line (cannot span multiple lines). Response files can have comments that begin with the # symbol.
-
- Specifying compiler options from within a response file is just like issuing those commands on the command line. See Building from the Command Line for more information.
-
- The compiler processes the command options as they are encountered. Therefore, command line arguments can override previously listed options in response files. Conversely, options in a response file will override options listed previously on the command line or in other response files.
-
- X# provides the xsc.rsp file, which is located in the same directory as the xsc.exe file. See -noconfig for more information on xsc.rsp.
-
- This compiler option cannot be set in the Visual Studio development environment, nor can it be changed programmatically.
- Example
-
- The following are a few lines from a sample response file:
-
-
- # build the first output file -target:exe -out:MyExe.exe source1.prg source2.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-_analyzer.xml b/docs/Help_Spanish/Topics/opt-_analyzer.xml
deleted file mode 100644
index 5661ccdc74..0000000000
--- a/docs/Help_Spanish/Topics/opt-_analyzer.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- -analyzer, -a
-
- -a
- -analyzer
-
-
-
- -analyzer, -a
-
- Run the analyzers from this assembly.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-additionalfile.xml b/docs/Help_Spanish/Topics/opt-additionalfile.xml
deleted file mode 100644
index 51328f4c1d..0000000000
--- a/docs/Help_Spanish/Topics/opt-additionalfile.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- -additionalfile
-
- -additionalfile
-
-
-
- -additionalfile
-
- The -additionalfile command line option allows you to include extra files in the assembly. To support this scenario, the X# compiler can accept additional, non-source text files as inputs.
-
- Syntax
- -additionalfile:file
- For example, an analyzer may enforce that a set of banned terms is not used within a project, or that every source file has a certain copyright header. The terms or copyright header could be passed to the analyzer as an additional file, rather than being hard-coded in the analyzer itself.
- Example
- On the command line, additional files can be passed using The -additionalfile option. For example:
-
-
- xsc alpha.prg -additionalfile:terms.txt
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-addmodule.xml b/docs/Help_Spanish/Topics/opt-addmodule.xml
deleted file mode 100644
index d0e012d5ea..0000000000
--- a/docs/Help_Spanish/Topics/opt-addmodule.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- -addmodule
-
- -addmodule
-
-
-
- -addmodule
-
- This option adds a module that was created with the target:module switch to the current compilation.
- Syntax
- -addmodule:file[;file2]
- Arguments
- file, file2An output file that contains metadata. The file cannot contain an assembly manifest. To import more than one file, separate file names with either a comma or a semicolon.
- Remarks
- All modules added with -addmodule must be in the same directory as the output file at run time. That is, you can specify a module in any directory at compile time but the module must be in the application directory at run time. If the module is not in the application directory at run time, you will get a TypeLoadException.
-
- A file cannot contain an assembly. For example, if the output file was created with -target:module, its metadata can be imported with -addmodule.
-
- If the output file was created with a -target option other than -target:module, its metadata cannot be imported with -addmodule but can be imported with -reference.
-
- This compiler option is unavailable in Visual Studio; a project cannot reference a module. In addition, this compiler option cannot be changed programmatically.
- Example
-
- Compile source file input.prg and add metadata from metad1.netmodule and metad2.netmodule to produce out.exe:
-
- xsc -addmodule:metad1.netmodule;metad2.netmodule -out:out.exe input.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-allowdot.xml b/docs/Help_Spanish/Topics/opt-allowdot.xml
deleted file mode 100644
index cafc9970da..0000000000
--- a/docs/Help_Spanish/Topics/opt-allowdot.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- -allowdot
-
- -allowdot
-
-
-
- -allowdot
-
- The -allowdot compiler option allows you to control if the DOT (".") operator should be allowed to access instance members.
-
-
The default for the Core and FoxPro dialects is /allowdot+
-
The default for the other dialects is /allowdot-
-
- Syntax
- -allowdot[+ | -]
- Arguments
- + | - Specifying +, or just -
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
Change "Allow DOT for instance members" value of checkbox.
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-allowoldstyleassignments.xml b/docs/Help_Spanish/Topics/opt-allowoldstyleassignments.xml
deleted file mode 100644
index 5fe412da18..0000000000
--- a/docs/Help_Spanish/Topics/opt-allowoldstyleassignments.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- -allowoldstyleassignments
-
-
- -allowoldstyleassignments
-
- The -allowoldstyleassignments compiler option allows you to control if the single Equals ("=") operator should be allowed to assign values.
-
-
The default for the FoxPro dialect is /allowdot+.
-
The default for the other dialects is /allowdot-.
-
- Syntax
- -allowoldstyleassignments[+ | -]
- Arguments
- + | - Specifying +, or just -
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
Change "Allow Old Style assignments" Value of checkbox.
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-appconfig.xml b/docs/Help_Spanish/Topics/opt-appconfig.xml
deleted file mode 100644
index ecac108bc7..0000000000
--- a/docs/Help_Spanish/Topics/opt-appconfig.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- -appconfig
-
- -appconfig
-
-
-
- -appconfig
-
- The -appconfig compiler option enables a X# application to specify the location of an assembly's application configuration (app.config) file to the common language runtime (CLR) at assembly binding time.
- Syntax
- -appconfig:file
- Arguments
- fileRequired. The application configuration file that contains assembly binding settings.
- Remarks
- One use of -appconfig is advanced scenarios in which an assembly has to reference both the .NET Framework version and the .NET Framework for Silverlight version of a particular reference assembly at the same time. For example, a XAML designer written in Windows Presentation Foundation (WPF) might have to reference both the WPF Desktop, for the designer's user interface, and the subset of WPF that is included with Silverlight. The same designer assembly has to access both assemblies. By default, the separate references cause a compiler error, because assembly binding sees the two assemblies as equivalent.
-
- The -appconfig compiler option enables you to specify the location of an app.config file that disables the default behavior by using a <supportPortability> tag, as shown in the following example:
- <supportPortability PKT="7cec85d7bea7798e" enable="false"/>
- The compiler passes the location of the file to the CLR's assembly-binding logic.
- Note: If you are using the Microsoft Build Engine (MSBuild) to build your application, you can set the -appconfig compiler option by adding a property tag to the .xsproj file. To use the app.config file that is already set in the project, add property tag <UseAppConfigForCompiler> to the .xsproj file and set its value to true. To specify a different app.config file, add property tag <AppConfigForCompiler> and set its value to the location of the file.
- Example
-
- The following example shows an app.config file that enables an application to have references to both the .NET Framework implementation and the .NET Framework for Silverlight implementation of any .NET Framework assembly that exists in both implementations. The -appconfig compiler option specifies the location of this app.config file.
-
-
- <configuration> <runtime> <assemblyBinding> <supportPortability PKT="7cec85d7bea7798e" enable="false"/> <supportPortability PKT="31bf3856ad364e35" enable="false"/> </assemblyBinding> </runtime> </configuration>
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-ast.xml b/docs/Help_Spanish/Topics/opt-ast.xml
deleted file mode 100644
index 53b6f2b2ec..0000000000
--- a/docs/Help_Spanish/Topics/opt-ast.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- -ast
-
- -ast
-
-
-
- -ast
-
- Tells the compiler to write abstract syntax trees for each of the source files that was processed.
- Syntax
- -ast[+|-]
- Arguments
- + | - Specifying +, or just -ast, tells the compiler to produce abstract syntax trees for each of the source files.
- Remarks
- This command line option allows you to check the code without generating a binary.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-az.xml b/docs/Help_Spanish/Topics/opt-az.xml
deleted file mode 100644
index f05d04c934..0000000000
--- a/docs/Help_Spanish/Topics/opt-az.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- -az
-
- -az
-
-
-
- -az
-
-
- The -az option specifies that array elements begin with 0, rather than with 1 (the default).
- Syntax
- -az[+|-]
- Arguments
- + | - Specifying +, or just -az, directs the compiler to use 0-based array indexing rather than 1-based indexing.
- Remarks
- This option is off by default, since it would break existing Visual Objects source code. If you prefer to use 0-based arrays with existing code written for Visual Objects, you will need to examine every place in your source code that uses arrays and manually make the appropriate adjustments.
-
- Note: This option does not affect how the assembly being compiled is used from other applications. When The -az option is not used, the compiler generates code to subtract 1 from the array index in order to provide 1-based array indexing semantics at the language level. When The -az option is used, the compiler does not adjust array indexes. Either way, the resulting arrays are always 0-based at the IL level, which allows compatibility with all other .NET languages.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
In the General section, modify the "Use Zero Based Arrays" property.
-
Click here to see the property page.
-
- Example
- FUNCTION Start() AS VOID LOCAL DIM a[1] AS INT ? a[0] -/ runtime error when -az switch is NOT used ? a[1] -/ runtime error when -az switch is used RETURN
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-baseaddress.xml b/docs/Help_Spanish/Topics/opt-baseaddress.xml
deleted file mode 100644
index e58be3f112..0000000000
--- a/docs/Help_Spanish/Topics/opt-baseaddress.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- -baseaddress
-
- -baseaddress
-
-
-
- -baseaddress
-
- The -baseaddress option lets you specify the preferred base address at which to load a DLL.
- Syntax
- -baseaddress:address
- Arguments
- addressThe base address for the DLL. This address can be specified as a decimal, hexadecimal, or octal number.
- Remarks
- The default base address for a DLL is set by the .NET Framework common language runtime.
-
- Be aware that the lower-order word in this address will be rounded. For example, if you specify 0x11110001, it will be rounded to 0x11110000.
-
- To complete the signing process for a DLL, use SN.EXE with the -R option.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-checked.xml b/docs/Help_Spanish/Topics/opt-checked.xml
deleted file mode 100644
index 401a866f58..0000000000
--- a/docs/Help_Spanish/Topics/opt-checked.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- -checked
-
- -checked
- -checked
-
-
-
- -checked
-
- The -checked option specifies whether an integer arithmetic statement that results in a value that is outside the range of the data type, and that is not in the scope of a checked or unchecked keyword, causes a run-time exception.
- Syntax
- -checked[+ | -]
- Remarks
- An integer arithmetic statement that is in the scope of a checked or unchecked keyword is not subject to the effect of the -checked option.
-
- If an integer arithmetic statement that is not in the scope of a checked or unchecked keyword results in a value outside the range of the data type, and -checked+ (/checked) is used in the compilation, that statement causes an exception at run time. If -checked- is used in the compilation, that statement does not cause an exception at run time.
-
- The default value for this option is -checked-. One scenario for using -checked- is in building large applications. Sometimes automated tools are used to build such applications, and such a tool might automatically set -checked to +. You can override the tool's global default by specifying -checked-.
-
- The VO Compatibility compiler options -ovf and -fovf both set this option.
-
- Example
-
- The following command compiles t2.prg. The use of -checked in the command specifies that any integer arithmetic statement in the file that is not in the scope of a checked or unchecked keyword, and that results in a value that is outside the range of the data type, causes an exception at run time.
-
-
- xsc t2.prg -checked
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-checksumalgorithm.xml b/docs/Help_Spanish/Topics/opt-checksumalgorithm.xml
deleted file mode 100644
index a00be184d1..0000000000
--- a/docs/Help_Spanish/Topics/opt-checksumalgorithm.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- -checksumalgorithm
-
- -checksumalgorithm
-
-
-
- -checksumalgorithm
-
- This option specifies the algorithm for calculating the source file checksum stored in PDB. Supported values are: SHA1 (default) or SHA256.
- Syntax
- -checksumalgorithm:<alg>
- Arguments
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-codepage.xml b/docs/Help_Spanish/Topics/opt-codepage.xml
deleted file mode 100644
index 655d4d54d7..0000000000
--- a/docs/Help_Spanish/Topics/opt-codepage.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- -codepage
-
- -codepage
-
-
-
- -codepage
-
- This option specifies which codepage to use during compilation if the required page is not the current default codepage for the system.
- Syntax
- -codepage:id
- Arguments
- idThe id of the code page to use for all source code files in the compilation.
- Remarks
- If you compile one or more source code files that were not created to use the default code page on your computer, you can use the -codepage option to specify which code page should be used. -codepage applies to all source code files in your compilation.
-
- If the source code files were created with the same codepage that is in effect on your computer or if the source code files were created with UNICODE or UTF-8, you need not use -codepage.
-
- See GetCPInfo for information on how to find which code pages are supported on your system.
-
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-cs.xml b/docs/Help_Spanish/Topics/opt-cs.xml
deleted file mode 100644
index 8b4c683f90..0000000000
--- a/docs/Help_Spanish/Topics/opt-cs.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- -cs
-
- -cs
-
-
-
- -cs
-
- The -cs option directs the compiler to treat all identifiers and type names as case-sensitive.
- Syntax
- -cs[+|-]
- Arguments
- +|-Specifying +, or just -cs, directs the compiler to treat all type names as case-sensitive.
- Remarks
- This option is for those users who prefer a case-sensitive language.
-
- This option can also affect case sensitivity of preprocessor symbols, depending on the state of the -vo8 compiler option; if -vo8 is enabled, then -cs controls if also preprocessor symbols are treated as case-sensitive; if -vo8 is disabled, then preprocessor symbols are always case-sensitive and the state of -cs does not affect this behavior of the preprocessor. See the topic about -vo8 for more information.
-
- This option also does not affect keywords. Keywords in X# are always case-insensitive.
- Note
- If you run the shared compiler you have to pass the -cs compiler option through the commandline and not through a response file.
- And when you mix case sensitive and not case sensitive projects then there will be two shared compiler processes running, one in case sensitive mode and the other in case insensitive mode.
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Language tab.
-
In the General section, modify the Case Sensitive Type Names property in the General.
-
Click here to see the property page.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-debug.xml b/docs/Help_Spanish/Topics/opt-debug.xml
deleted file mode 100644
index b0124a4985..0000000000
--- a/docs/Help_Spanish/Topics/opt-debug.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- -debug
-
- -d
- -debug
-
-
-
- -debug
-
- The -debug option causes the compiler to generate debugging information and place it in the output file or files.
- Syntax
- -debug[+ | -] -debug:{full | pdbonly}
- Arguments
- + | -Specifying +, or just -debug, causes the compiler to generate debugging information and place it in a program database (.pdb file). Specifying -, which is in effect if you do not specify -debug, causes no debug information to be created.
-
- full | pdbonlySpecifies the type of debugging information generated by the compiler. The full argument, which is in effect if you do not specify -debug:pdbonly, enables attaching a debugger to the running program. Specifying pdbonly allows source code debugging when the program is started in the debugger, but will only display assembler when the running program is attached to the debugger.
- Remarks
- Use this option to create debug builds. If -debug, -debug+, or -debug:full is not specified, you will not be able to debug the output file of your program.
-
- If you use -debug:full, be aware that there is some impact on the speed and size of JIT optimized code and a small impact on code quality with -debug:full. We recommend -debug:pdbonly or no PDB for generating release code.
-
- Note
- One difference between -debug:pdbonly and -debug:full is that with -debug:full the compiler emits a DebuggableAttribute, which is used to tell the JIT compiler that debug information is available. Therefore, you will get an error if your code contains the DebuggableAttribute set to false if you use -debug:full.
-
- For more information on how to configure the debug performance of an application, see Making an Image Easier to Debug.
-
- To change the location of the .pdb file, see -pdb.
-
- To set this compiler option in the Visual Studio development environment
-
-
-
Open the project's Properties page.
-
Click the Build property page.
-
Modify the Debug Info property.
-
Click here to see the property page.
-
-
- For information on how to set this compiler option programmatically, see DebugSymbols.
- Example
-
- Place debugging information in output file app.pdb:
-
-
- xsc -debug -pdb:app.pdb test.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-define.xml b/docs/Help_Spanish/Topics/opt-define.xml
deleted file mode 100644
index a9d3da55b1..0000000000
--- a/docs/Help_Spanish/Topics/opt-define.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- -define
-
- -define
-
-
-
- -define
-
- The -define compiler option defines name as a symbol in all source code files your program.
- Syntax
- -define:name[;name2]
- Arguments
- name, name2The name of one or more symbols that you want to define.
- Remarks
- The -define option has the same effect as using a #define preprocessor directive except that the compiler option is in effect for all files in the project. A symbol remains defined in a source file until an #undef directive in the source file removes the definition. When you use the -define option, an #undef directive in one file has no effect on other source code files in the project.
-
- You can use symbols created by this option with #if, #else, #elif, and #endif to compile source files conditionally.
-
- -d is the short form of -define.
-
- You can define multiple symbols with -define by using a semicolon or comma to separate symbol names. For example:
-
-
- -define:DEBUG;TUESDAY
-
- The X# compiler defines a couple of symbols automatically. See the Macros topic elsewhere in this documentation.
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
On the Build tab, type the symbol that is to be defined in the Defines for the preprocessor box. For example, if you are using the code example that follows, just type xx into the text box.
-
Click here to see the property page.
-
-
- For information on how to set this compiler option programmatically, see DefineConstants.
- Example
-
-
- -/ preprocessor_define.prg -/ compile with: -define:xx -/ or uncomment the next line -/ #define xx using System; public class Test { public static void Main() { #if (xx) Console.WriteLine("xx defined"); #else Console.WriteLine("xx not defined"); #endif } }
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-delaysign.xml b/docs/Help_Spanish/Topics/opt-delaysign.xml
deleted file mode 100644
index 5bb5982c73..0000000000
--- a/docs/Help_Spanish/Topics/opt-delaysign.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- -delaysign
-
- -delaysign
-
-
-
- -delaysign
-
- This compiler option causes the compiler to reserve space in the output file so that a digital signature can be added later.
- Syntax
- -delaysign[ + | - ]
- Arguments
- + | -Use -delaysign- if you want a fully signed assembly. Use -delaysign+ if you only want to place the public key in the assembly. The default is -delaysign-.
- Remarks
- The -delaysign option has no effect unless used with -keyfile or -keycontainer.
-
- When you request a fully signed assembly, the compiler hashes the file that contains the manifest (assembly metadata) and signs that hash with the private key. The resulting digital signature is stored in the file that contains the manifest. When an assembly is delay signed, the compiler does not compute and store the signature, but reserves space in the file so the signature can be added later.
-
- For example, using -delaysign+ allows a tester to put the assembly in the global cache. After testing, you can fully sign the assembly by placing the private key in the assembly using the Assembly Linker utility.
-
- For more information, see Creating and Using Strong-Named Assemblies and Delay Signing an Assembly.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the Properties page for the project.
-
Modify the Delay sign only property.
-
Click here to see the property page.
-
-
- For information on how to set this compiler option programmatically, see DelaySign.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-dialect.xml b/docs/Help_Spanish/Topics/opt-dialect.xml
deleted file mode 100644
index 74014bfca2..0000000000
--- a/docs/Help_Spanish/Topics/opt-dialect.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- -dialect
-
- dbase
- -dialect
- foxpro
- Harbour
- vo
- vulcan
- Xbase++
-
-
-
- -dialect
-
- The -dialect compiler option selects the dialect that the compiler should follow. Valid options are: Core, VO, Vulcan, dBase, FoxPro, xBase++ and Harbour.
- Note: There should be NO space between the colon and the dialect.
- Syntax
- -dialect: Core | VO | Vulcan | Harbour | XbasePP | FoxPro
- Arguments
- CoreUse the Core dialect. This is like C# with an xBase syntax.
- VOThis activates the VO dialect.
- VulcanThis activates the Vulcan dialect.
- HarbourThis activates the Harbour dialect.
- XBasePPThis activates the Harbour dialect.
- FoxProThis activates the FoxPro dialect.
-
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Application property page.
-
Modify the Dialect property.
-
Click here to see the property page.
-
- See the dialect topic for differences between dialects
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-doc.xml b/docs/Help_Spanish/Topics/opt-doc.xml
deleted file mode 100644
index cd3c9a34a0..0000000000
--- a/docs/Help_Spanish/Topics/opt-doc.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- -doc
-
- -doc
-
-
-
- -doc
-
- The -doc compiler option allows you to place documentation comments in an XML file.
- Syntax
- -doc:file
- Arguments
- fileThe output file for XML, which is populated with the comments in the source code files of the compilation.
- Remarks
- In source code files, documentation comments that precede the following can be processed and added to the XML file:
-
-
-
Such user-defined types as a class, delegate, or interface.
-
Such members as a field, event, property, or method.
-
-
- The source code file that contains Main is output first into the XML.
-
- To use the generated .xml file for use with the IntelliSense feature, let the file name of the .xml file be the same as the assembly you want to support and then make sure the .xml file is in the same directory as the assembly. Thus, when the assembly is referenced in the Visual Studio project, the .xml file is found as well. See Supplying Code Comments and for more information.
-
- Unless you compile with -target:module, file will contain <assembly></assembly> tags specifying the name of the file containing the assembly manifest for the output file of the compilation.
-
- Note: The -doc option applies to all input files; or, if set in the Project Settings, all files in the project. To disable warnings related to documentation comments for a specific file or section of code, use #pragma warning.
-
- See Recommended Tags for Documentation Comments for ways to generate documentation from comments in your code.
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Build tab.
-
Modify the XML documentation file property.
-
Click here to see the property page.
-
-
- For information on how to set this compiler option programmatically, see DocumentationFile.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-enforceoverride.xml b/docs/Help_Spanish/Topics/opt-enforceoverride.xml
deleted file mode 100644
index 3d70f86d1d..0000000000
--- a/docs/Help_Spanish/Topics/opt-enforceoverride.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- -enforceoverride
-
- -enforceoverride
-
-
-
- -enforceoverride
-
- This compiler option tells the compiler NOT to automatically add the OVERRIDE modifier to methods in subclasses that override virtual methods in parent classes.
- Syntax
- -enforceoverride[+ | -]
- Arguments
- + | - Specifying +, or just -
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-enforceself.xml b/docs/Help_Spanish/Topics/opt-enforceself.xml
deleted file mode 100644
index e4577d17fa..0000000000
--- a/docs/Help_Spanish/Topics/opt-enforceself.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- -enforceself
-
- -enforceself
-
-
-
- -enforceself
-
- The -enforceself compiler option allows you to control if you can access members of the SELF objects with or without the SELF: prefix. In Visual Objects and most other original languages this was not allowed. This is equivalent to /enforceself+. In .Net the default is that this is allowed. This is equivalent to /enforceself-.
- The effect of this is that the compiler may report an ambiguity when a method exists with the same name as a built in function. If you enable /enforceself then the compiler "knows" that without the SELF: prefix you intend to call the function.
- Syntax
- -enforceself[+ | -]
- Arguments
- + | - Specifying +, or just -
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-errorendlocation.xml b/docs/Help_Spanish/Topics/opt-errorendlocation.xml
deleted file mode 100644
index 3b76e2e827..0000000000
--- a/docs/Help_Spanish/Topics/opt-errorendlocation.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- -errorendlocation
-
- -errorendlocation
-
-
-
- -errorendlocation
-
- The -errorendlocation tells the compiler to Output the line and column of the end location of each error in addition to the start location of the error/.
- Syntax
- -errorendlocation
- Remarks
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically. It is enabled by default when compiling inside Visual Studio.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-errorreport.xml b/docs/Help_Spanish/Topics/opt-errorreport.xml
deleted file mode 100644
index f4aecffbd3..0000000000
--- a/docs/Help_Spanish/Topics/opt-errorreport.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- -errorreport
-
- -errorreport
-
-
-
- -errorreport
-
- This compiler option provides a convenient way to report a X# internal compiler error.
- Note: On Windows Vista and Windows Server 2008, the error reporting settings that you make for Visual Studio do not override the settings made through Windows Error Reporting (WER). WER settings always take precedence over Visual Studio error reporting settings.
- Syntax
- -errorreport:{ none | prompt | queue | send }
- Arguments
- noneReports about internal compiler errors will not be collected or sent to Microsoft.
-
- promptPrompts you to send a report when you receive an internal compiler error. Prompt is the default when you compile an application in the development environment.
-
- queueQueues the error report. When you log on with administrative credentials, you can report any failures since the last time that you were logged on. You will not be prompted to send reports for failures more than once every three days. Queue is the default when you compile an application at the command line.
-
- sendAutomatically sends reports of internal compiler errors to Microsoft. To enable this option, you must first agree to the Microsoft data collection policy. The first time that you specify -errorreport:send on a computer, a compiler message will refer you to a Web site that contains the Microsoft data collection policy.
-
- Remarks
- An internal compiler error (ICE) results when the compiler cannot process a source code file. When an ICE occurs, the compiler does not produce an output file or any useful diagnostic that you can use to fix your code.
-
- A user's ability to send reports depends on computer and user policy permissions.
-
- For more information about error debugger, see Description of the Dr. Watson for Windows (Drwtsn32.exe) Tool.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-filealign.xml b/docs/Help_Spanish/Topics/opt-filealign.xml
deleted file mode 100644
index 7e9737a028..0000000000
--- a/docs/Help_Spanish/Topics/opt-filealign.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- -filealign
-
- -filealign
-
-
-
- -filealign
-
- The -filealign compiler option lets you specify the size of sections in your output file.
- Syntax
- -filealign:number
- Arguments
- numberA value that specifies the size of sections in the output file. Valid values are 512, 1024, 2048, 4096, and 8192. These values are in bytes.
- Remarks
- Each section will be aligned on a boundary that is a multiple of The -filealign value. There is no fixed default. If -filealign is not specified, the common language runtime picks a default at compile time.
-
- By specifying the section size, you affect the size of the output file. Modifying section size may be useful for programs that will run on smaller devices.
-
- Use DUMPBIN to see information about sections in your output file.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-fovf.xml b/docs/Help_Spanish/Topics/opt-fovf.xml
deleted file mode 100644
index 2382f28af7..0000000000
--- a/docs/Help_Spanish/Topics/opt-fovf.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- -fovf
-
- -checked
- -fovf
-
-
-
- -fovf
-
- The -ovf compiler option is an alias for the -checked command line option for compatibility.
- We have added this option because Vulcan.Net also had that option.
-
- Click here to see the property page
-
-
diff --git a/docs/Help_Spanish/Topics/opt-fox1.xml b/docs/Help_Spanish/Topics/opt-fox1.xml
deleted file mode 100644
index cc6486dca2..0000000000
--- a/docs/Help_Spanish/Topics/opt-fox1.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- -fox1
-
- -fox1
-
-
-
- -fox1Classes are assumed to inherit from the Custom class
-
- The -fox1 compiler option tells the compiler that all classes with the FoxPro class syntax are assumed to inherit from the Custom class. This means:
-
-
The AS <idType> CLASS becomes mandatory.
-
The code generation for properties assumes that the class inherits from the Custom class and creates Get and Set methods that read/write the values to the properties collection inside the Custom class.
-
- Syntax
- -fox1[+ | -]
- Arguments
- + | - Specifying +, or just -
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-fox2.xml b/docs/Help_Spanish/Topics/opt-fox2.xml
deleted file mode 100644
index 8651bc2e2b..0000000000
--- a/docs/Help_Spanish/Topics/opt-fox2.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
- -fox2
-
- -fox2
-
-
-
- -fox2Compatible FoxPro Array support
-
- The -fox2 compiler option is enabled for foxpro compatible array support. It enables / disables the following features:
-
-
Assigning a single value to an array will fill the whole array with that value.
-
Support for parenthesized array access. If the compiler encounters code that might be an array access such as Foo(1,2) then it will check to see if Foo() is a local or field declared as a foxpro array. If that is the case, the array element will be accessed. If Foo is not declared, then this might be an array access for a dynamic memory variable declared outside of the scope of the current method or function. The compiler will then generate code to resolve this at runtime (just like FoxPro does)
-
- Requirements
- The -fox2 compiler options MUST be used together with the -memvar compiler option and the FoxPro dialect.
- Example
- LOCAL a Dimension a(10) a = 42 // With the /fox2 compiler option this will fill the array with 42. // Without the option the variable will be changed from an array to a number
- or
- Function Main() Dimension foo(2,5) foo = 42 // with /fox2 this fills the array ? foo(1,2) // with /fox2 this returns element 1,2. Without /fox2 this will call the Foo function below ? Foo[1,2] // this always returns element 1,2
FUNCTION Foo(n1, n2) ? n1, n2 RETURN n1 * n2
- Please note
- The fox2 compiler option generates some extra code to decide at runtime which action to take.
- It is only recommended for code that really needs this feature. You can use #pragma options to enable or disable fox2 for some source files or even some functions
-
-
diff --git a/docs/Help_Spanish/Topics/opt-fullpaths.xml b/docs/Help_Spanish/Topics/opt-fullpaths.xml
deleted file mode 100644
index cfb833e7c9..0000000000
--- a/docs/Help_Spanish/Topics/opt-fullpaths.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- -fullpaths
-
- -fullpaths
-
-
-
- -fullpaths
-
- The -fullpaths option causes the compiler to specify the full path to the file when listing compilation errors and warnings.
- Syntax
- -fullpaths
- Remarks
- By default, errors and warnings that result from compilation specify the name of the file in which an error was found. The -fullpaths option causes the compiler to specify the full path to the file.
-
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically. It is enabled by default when compiling inside Visual Studio.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-help.xml b/docs/Help_Spanish/Topics/opt-help.xml
deleted file mode 100644
index f0180595a8..0000000000
--- a/docs/Help_Spanish/Topics/opt-help.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- -help, -?
-
- -?
- -help
-
-
-
- -help, -?
-
- This option sends a listing of compiler options, and a brief description of each option, to stdout.
- Syntax
- -help -?
- Remarks
- If this option is included in a compilation, no output file will be created and no compilation will take place.
-
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-highentroyva.xml b/docs/Help_Spanish/Topics/opt-highentroyva.xml
deleted file mode 100644
index 91fff8908d..0000000000
--- a/docs/Help_Spanish/Topics/opt-highentroyva.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- -highentropyva
-
- -highentropyva
-
-
-
- -highentropyva
-
- The -highentropyva compiler option tells the Windows kernel whether a particular executable supports high entropy Address Space Layout Randomization (ASLR).
- Syntax
- -highentropyva[+ | -]
- Arguments
- + | -This option specifies that a 64-bit executable or an executable that is marked by the -platform:anycpu compiler option supports a high entropy virtual address space. The option is disabled by default. Use -highentropyva+ or -highentropyva to enable it.
- Remarks
- The -highentropyva option enables compatible versions of the Windows kernel to use higher degrees of entropy when randomizing the address space layout of a process as part of ASLR. Using higher degrees of entropy means that a larger number of addresses can be allocated to memory regions such as stacks and heaps. As a result, it is more difficult to guess the location of a particular memory region.
-
- When the -highentropyva compiler option is specified, the target executable and any modules that it depends on must be able to handle pointer values that are larger than 4 gigabytes (GB) when they are running as a 64-bit process.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-i.xml b/docs/Help_Spanish/Topics/opt-i.xml
deleted file mode 100644
index 9ec4404868..0000000000
--- a/docs/Help_Spanish/Topics/opt-i.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- -i
-
- -i
-
-
-
- -i
-
- The -i option adds a directory to the list of directories the compiler searches for include files.
- Syntax
- -i:dir
- Arguments
- dirA directory to add to list list of directories the compiler searches for include files.
- Remarks
- The compiler searches for files included with #include in the following order:
-
-
-
The current working directory
-
The include subdirectory of the Vulcan.NET installation directory (when applicable)
-
The include subdirectory of the XSharp installation directory
-
Any directories specified with -i
-
Any directories specified with the INCLUDE environment variable.
-
-
- Multiple directories can be specified by using the -i option multiple times.
- The compiler does not search for file names that are fully qualified in any location other than in the directory specified in the #include directive.
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
In the Preprocessor section, modify the "Additional include paths" property.
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-initlocals.xml b/docs/Help_Spanish/Topics/opt-initlocals.xml
deleted file mode 100644
index ec28325d86..0000000000
--- a/docs/Help_Spanish/Topics/opt-initlocals.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- -initlocals
-
- -initlocals
-
-
-
- -initlocals
-
- The -initlocals option specifies whether the compiler should automatically initialize local variables.
- Syntax
- -initlocals[+|-]
- Arguments
- + | - Specifying +, or just -ins, directs the compiler to init local variables or not.
- Remarks
- This can be used to automatically initialize all local variables and suppress compiler warnings about local variables that are not initialized.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
In the General section, modify the "Initialize Local Variables" value
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-ins.xml b/docs/Help_Spanish/Topics/opt-ins.xml
deleted file mode 100644
index 41d74e26ff..0000000000
--- a/docs/Help_Spanish/Topics/opt-ins.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- -ins
-
- -ins
-
-
-
- -ins
-
- The -ins option specifies whether the compiler should automatically include namespaces from assemblies compiled in VO/Vulcan dialect marked with the ImplicitNameSpaceAttribute.
- Syntax
- -ins[+|-]
- Arguments
- + | - Specifying +, or just -ins, directs the compiler to automatically include namespaces from assemblies marked with the VulcanImplicitNameSpaceAttribute.
- Remarks
- Class Libraries can be compiled with a special attribute:
-
-
- [assembly: VulcanImplicitNamespaceAttribute( "SomeNameSpace )]
-
- This attribute tells the compiler that classes that are placed inside that namespace should be automatically included when searching for classes, as if there was a #using SomeNameSpace statement in the source code.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
In the Namespaces section, modify the Enable Implicit Lookup of Namespaces property.
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-keycontainer.xml b/docs/Help_Spanish/Topics/opt-keycontainer.xml
deleted file mode 100644
index 5373782b06..0000000000
--- a/docs/Help_Spanish/Topics/opt-keycontainer.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- -keycontainer
-
- -keycontainer
-
-
-
- -keycontainer
-
- Specifies the name of the cryptographic key container.
- Syntax
- -keycontainer:string
- Arguments
- stringThe name of the strong name key container.
- Remarks
- When the -keycontainer option is used, the compiler creates a sharable component by inserting a public key from the specified container into the assembly manifest and signing the final assembly with the private key. To generate a key file, type sn -k file at the command line. sn -i installs the key pair into a container.
-
- If you compile with -target:module, the name of the key file is held in the module and incorporated into the assembly when you compile this module into an assembly with -addmodule.
-
- You can also specify this option as a custom attribute (System.Reflection.AssemblyKeyNameAttribute) in the source code for any Microsoft intermediate language (MSIL) module.
-
- You can also pass your encryption information to the compiler with -keyfile. Use -delaysign if you want the public key added to the assembly manifest but want to delay signing the assembly until it has been tested.
-
- For more information, see Creating and Using Strong-Named Assemblies and Delay Signing an Assembly.
-
- To set this compiler option in the Visual Studio development environment:
-
-
This compiler option is not available in the Visual Studio development environment.
-
-
- You can programmatically access this compiler option with AssemblyKeyContainerName.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-keyfile.xml b/docs/Help_Spanish/Topics/opt-keyfile.xml
deleted file mode 100644
index 105a6bb702..0000000000
--- a/docs/Help_Spanish/Topics/opt-keyfile.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- -keyfile
-
- -keyfile
-
-
-
- -keyfile
-
- This option specifies the filename containing the cryptographic key.
- Syntax
- -keyfile:file
- Arguments
- fileThe name of the file containing the strong name key.
- Remarks
- When this option is used, the compiler inserts the public key from the specified file into the assembly manifest and then signs the final assembly with the private key. To generate a key file, type sn -k file at the command line.
-
- If you compile with -target:module, the name of the key file is held in the module and incorporated into the assembly that is created when you compile an assembly with -addmodule.
-
- You can also pass your encryption information to the compiler with -keycontainer. Use -delaysign if you want a partially signed assembly.
-
- In case both -keyfile and -keycontainer are specified (either by command line option or by custom attribute) in the same compilation, the compiler will first try the key container. If that succeeds, the assembly is signed with the information in the key container. If the compiler does not find the key container, it will try the file specified with -keyfile. If that succeeds, the assembly is signed with the information in the key file and the key information will be installed in the key container (similar to sn -i) so that on the next compilation, the key container will be valid.
-
- Note that a key file might contain only the public key.
-
- For more information, see Creating and Using Strong-Named Assemblies and Delay Signing an Assembly.
- To set this compiler option in the Visual Studio development environment:
-
-
Open the Properties page for the project.
-
Click the Build property page.
-
Modify the Choose a strong name key file property.
-
Click here to see the property page.
-
-
- You can programmatically access this compiler option with AssemblyOriginatorKeyFile.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-langversion.xml b/docs/Help_Spanish/Topics/opt-langversion.xml
deleted file mode 100644
index 69b9fc16ce..0000000000
--- a/docs/Help_Spanish/Topics/opt-langversion.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- -langversion
-
- -langversion
-
-
-
- -langversion
-
- This compiler option is ignored. When compared to the C# compiler, X# always compiles in the latest language version.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-lb.xml b/docs/Help_Spanish/Topics/opt-lb.xml
deleted file mode 100644
index 4b0dd009f1..0000000000
--- a/docs/Help_Spanish/Topics/opt-lb.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- -lb
-
- -lb
-
-
-
- -lb
-
- The -lb option specifies if the compiler should allow code that uses the Late Binding mechnism to call methods and or get/set properties.
- Syntax
- -lb[+|-]
- Arguments
- + | - Specifying +, or just -lb, directs the compiler to generate a late-bound call to an instance variable or method when compiler cannot generate code for an early bound call.
- Remarks
- The X# compiler always attempts to generate early bound calls to all class methods, properties and fields. This is true even for methods referred to as "untyped" in Visual Objects. Strictly speaking, nothing is "untyped". If an early bound call cannot be generated, a compile-time error is raised.
-
- In Visual Objects, it is possible to invoke methods and access instance variables on an object without the compiler knowing the exact type of the object. This is done by using a variable of type OBJECT or USUAL to hold the object reference. The "Only Early" option in the VO Application Options dialog must not be checked in order to allow this.
-
- In addition, it is also possible to invoke a method on each element of an ARRAY. Each array element must contain an object that implements the specified method, or a runtime error will occur.
-
- The -lb option is the exact opposite of the Visual Objects Only Early option.
-
- Late binding incurs considerably more runtime overhead than early binding, and prevents compile-time parameter and return value checking. Any late-bound call has the potential to fail at runtime if the object does not support the field or property that is being accessed, the member being invoked or incorrect parameter types or count. Only use early binding for existing code or when there is no viable alternative.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
In the General section, modify the Allow Late Binding property.
-
Click here to see the property page.
-
- Example
- The following example will compile when the -lb switch is used. Without -lb, errors will be raised.
-
- Note that using late-bound calls can affect the performance of an application and raises the possibility of runtime errors that would otherwise be caught by the compiler if early binding was used. Late binding should only be used for compatibility with existing VO code.
-
-
-
-
- If The -lb option is enabled, then the above example will be compiled as if it was written:
-
-
-
- Note that while this particular example will compile and execute correctly, if the definition of CLASS foo was changed and INSTANCE i was removed or changed to a method, the example would fail at runtime. Similarly, if METHOD bar was changed or removed, the example may also fail at runtime. For this reason, late-bound programming is strongly discouraged. Consider using subclassing and inheritance instead.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-lexonly.xml b/docs/Help_Spanish/Topics/opt-lexonly.xml
deleted file mode 100644
index 2d3d3e37c4..0000000000
--- a/docs/Help_Spanish/Topics/opt-lexonly.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- -lexonly
-
- -lexonly
-
-
-
- -lexonly
-
- Runs the lexer and preprocessor on the source files
- Syntax
- -lexonly[+|-]
- Arguments
- + | - Specifying +, or just -lexonly, tells the compiler to only lex the source code and not to parse, bind and generate an output file. When combined with The -ppo option then there will be .ppo files written.
- Remarks
- This command line option allows you to check the code without generating a binary.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-lib.xml b/docs/Help_Spanish/Topics/opt-lib.xml
deleted file mode 100644
index 6e530bf07a..0000000000
--- a/docs/Help_Spanish/Topics/opt-lib.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- -lib
-
- -lib
-
-
-
- -lib
-
- The -lib option specifies the location of assemblies referenced by means of the -reference option.
- Syntax
- -lib:dir1[,dir2]
- Arguments
- dir1A directory for the compiler to look in if a referenced assembly is not found in the current working directory (the directory from which you are invoking the compiler) or in the common language runtime's system directory.
- dir2One or more additional directories to search in for assembly references. Separate additional directory names with a comma, and without white space between them.
- Remarks
- The compiler searches for assembly references that are not fully qualified in the following order:
-
-
Current working directory. This is the directory from which the compiler is invoked.
-
The common language runtime system directory.
-
Directories specified by -lib.
-
Directories specified by the LIB environment variable.
-
-
- Use -reference to specify an assembly reference.
-
- -lib is additive; specifying it more than once appends to any prior values.
-
- An alternative to using -lib is to copy into the working directory any required assemblies; this will allow you to simply pass the assembly name to -reference. You can then delete the assemblies from the working directory. Since the path to the dependent assembly is not specified in the assembly manifest, the application can be started on the target computer and will find and use the assembly in the global assembly cache.
-
- Because the compiler can reference the assembly does not imply the common language runtime will be able to find and load the assembly at runtime. See How the Runtime Locates Assemblies for details on how the runtime searches for referenced assemblies.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Property Pages dialog box.
-
Click the References Path property page.
-
Modify the contents of the list box.
-
-
- For information on how to set this compiler option programmatically, see ReferencePath.
- Example
-
- Compile t2.prg to create an .exe file. The compiler will look in the working directory and in the root directory of the C drive for assembly references.
-
-
- xsc -lib:c:\ -reference:t2.dll t2.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-link.xml b/docs/Help_Spanish/Topics/opt-link.xml
deleted file mode 100644
index e5e6c2fcb2..0000000000
--- a/docs/Help_Spanish/Topics/opt-link.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- -link
-
- -link
-
-
-
- -link
-
- Causes the compiler to make COM type information in the specified assemblies available to the project that you are currently compiling.
- Syntax
- -link:fileList -/ -or- -l:fileList
- Arguments
- fileListRequired. Comma-delimited list of assembly file names. If the file name contains a space, enclose the name in quotation marks.
- Remarks
- The -link option enables you to deploy an application that has embedded type information. The application can then use types in a runtime assembly that implement the embedded type information without requiring a reference to the runtime assembly. If various versions of the runtime assembly are published, the application that contains the embedded type information can work with the various versions without having to be recompiled. For an example, see Walkthrough: Embedding Types from Managed Assemblies.
-
- Using the -link option is especially useful when you are working with COM interop. You can embed COM types so that your application no longer requires a primary interop assembly (PIA) on the target computer. The -link option instructs the compiler to embed the COM type information from the referenced interop assembly into the resulting compiled code. The COM type is identified by the CLSID (GUID) value. As a result, your application can run on a target computer that has installed the same COM types with the same CLSID values. Applications that automate Microsoft Office are a good example. Because applications like Office usually keep the same CLSID value across different versions, your application can use the referenced COM types as long as .NET Framework 4 or later is installed on the target computer and your application uses methods, properties, or events that are included in the referenced COM types.
-
- The -link option embeds only interfaces, structures, and delegates. Embedding COM classes is not supported.
- Note
- When you create an instance of an embedded COM type in your code, you must create the instance by using the appropriate interface. Attempting to create an instance of an embedded COM type by using the CoClass causes an error.
-
- To set the -link option in Visual Studio, add an assembly reference and set the Embed Interop Types property to true. The default for the Embed Interop Types property is false.
-
- If you link to a COM assembly (Assembly A) which itself references another COM assembly (Assembly B), you also have to link to Assembly B if either of the following is true:
-
-
A type from Assembly A inherits from a type or implements an interface from Assembly B.
-
A field, property, event, or method that has a return type or parameter type from Assembly B is invoked.
-
-
- Like the -reference compiler option, the -link compiler option uses the xsc.rsp response file, which references frequently used .NET Framework assemblies. Use the -noconfig compiler option if you do not want the compiler to use the xsc.rsp file.
-
- The short form of -link is -l.
- Generics and Embedded Types
- The following sections describe the limitations on using generic types in applications that embed interop types.
- Generic Interfaces
- Generic interfaces that are embedded from an interop assembly cannot be used.
- Types That Have Generic Parameters
- Types that have a generic parameter whose type is embedded from an interop assembly cannot be used if that type is from an external assembly. This restriction does not apply to interfaces. For example, consider the Range interface that is defined in the Microsoft.Office.Interop.Excel assembly. If a library embeds interop types from the Microsoft.Office.Interop.Excel assembly and exposes a method that returns a generic type that has a parameter whose type is the Range interface, that method must return a generic interface, as shown in the code example below.
- Example
- The following code compiles source file OfficeApp.prg and reference assemblies from COMData1.dll and COMData2.dll to produce OfficeApp.exe.
-
-
- xsc -link:COMData1.dll,COMData2.dll -out:OfficeApp.exe OfficeApp.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-linkresource.xml b/docs/Help_Spanish/Topics/opt-linkresource.xml
deleted file mode 100644
index e085397844..0000000000
--- a/docs/Help_Spanish/Topics/opt-linkresource.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- -linkresource
-
- -linkresource
-
-
-
- -linkresource
-
- Creates a link to a .NET Framework resource in the output file. The resource file is not added to the output file. This differs from The -resource option which does embed a resource file in the output file.
- Syntax
- -linkresource:filename[,identifier[,accessibility-modifier]]
- Arguments
- filenameThe .NET Framework resource file to which you want to link from the assembly.
- identifier (optional)The logical name for the resource; the name that is used to load the resource. The default is the name of the file.
- accessibility-modifier
- (optional)The accessibility of the resource: public or private. The default is public.
- Remarks
- By default, linked resources are public in the assembly when they are created with the X# compiler. To make the resources private, specify private as the accessibility modifier. No other modifier other than public or private is allowed.
-
- -linkresource requires one of the -target options other than -target:module.
-
- If filename is a .NET Framework resource file created, for example, by Resgen.exe or in the development environment, it can be accessed with members in the System.Resources namespace. For more information, see System.Resources.ResourceManager. For all other resources, use the GetManifestResource* methods in the Assembly class to access the resource at run time.
-
- The file specified in filename can be any format. For example, you may want to make a native DLL part of the assembly, so that it can be installed into the global assembly cache and accessed from managed code in the assembly. The second of the following examples shows how to do this. You can do the same thing in the Assembly Linker. The third of the following examples shows how to do this. For more information, see Al.exe (Assembly Linker) and Working with Assemblies and the Global Assembly Cache
- .
- -linkres is the short form of -linkresource.
-
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically.
- Example
-
- Compile in.prg and link to resource file rf.resource:
-
-
- xsc -linkresource:rf.resource in.prg
-
- Example
-
- Compile A.prg into a DLL, link to a native DLL N.dll, and put the output in the Global Assembly Cache (GAC). In this example, both A.dll and N.dll will reside in the GAC.
-
-
- xsc -linkresource:N.dll -t:library A.prg gacutil -i A.dll
-
- Example
-
- This example does the same thing as the previous one, but by using Assembly Linker options.
-
-
- xsc -t:module A.prg al -out:A.dll A.netmodule -link:N.dll gacutil -i A.dll
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-main.xml b/docs/Help_Spanish/Topics/opt-main.xml
deleted file mode 100644
index 7311d931d0..0000000000
--- a/docs/Help_Spanish/Topics/opt-main.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
- -main
-
- -main
-
-
-
- -main
-
- This option specifies the class that contains the entry point to the program, if more than one class contains a Main method.
- Syntax
- -main:class
- Arguments
- classThe type that contains the Main method.
- Remarks
- If your compilation includes more than one type with a Main method, you can specify which type contains the Main method that you want to use as the entry point into the program.
-
- This option is for use when compiling an .exe file.
-
- To set this compiler option in the Visual Studio development environment
-
-
Open the project's Properties page.
-
Click the Application property page.
-
Modify the Startup object property.
-
Click here to see the property page
-
-
- To set this compiler option programmatically, see StartupObject.
- Example
-
-
- Compile t2.prg and t3.prg, specifying that the Main method will be found in Test2:
-
-
- xsc t2.prg t3.prg -main:Test2
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-memvar.xml b/docs/Help_Spanish/Topics/opt-memvar.xml
deleted file mode 100644
index cf4b939393..0000000000
--- a/docs/Help_Spanish/Topics/opt-memvar.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- -memvar
-
- -memvar
-
-
-
- -memvar
-
- The -memvar option tells the compiler to enable the support for 'memory variables'. This option is also needed in the FoxPro dialect if you want to make local variables visible to the macro compiler with the -fox2 compilation option.
- Syntax
- -memvar [+ | -]
- Arguments
- + | - Specifying +, or just -memvar, directs the compiler to enable support for memory variables.
-
- Remarks
- This will NOT work with the Core and Vulcan dialects.
- Enabling this option will enable the following commands in the compiler:
- MEMVAR <MemvarName,...>
- PUBLIC <MemVarName,...>
- PRIVATE <MemVarName,...>
- PARAMETERS <ParameterName,,...>
-
-
- Click here to see the property page
-
-
diff --git a/docs/Help_Spanish/Topics/opt-modernsyntax.xml b/docs/Help_Spanish/Topics/opt-modernsyntax.xml
deleted file mode 100644
index c4cbf1e3aa..0000000000
--- a/docs/Help_Spanish/Topics/opt-modernsyntax.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- -modernsyntax
-
- -modernsyntax
-
-
-
- -modernsyntax
-
- The -modernsyntax compiler option disables some legacy language features.
- These features are:
-
-
-
&& for single line comments
-
- ? Today() && Show today's date
-
-
* for whole line comments
-
- * The next line calls DoSomething() ? DoSomething()
-
-
Bracketed strings
-
- ? ["''"] // use brackets to include quotes in a literal string
-
-
Parenthesized expression lists
-
- var x := IIF(Dow() == 1, (Open(), DoSomeWork(), Close()), 42)
- These were used by some users to include more than one expression or function call on locations where a single expression was expected, such as inside an IIF() expression. If -modernsyntax is not enabled then the compiler will generate a local function with (in this example) three expression statements and insert a call to the local function in the IIF() expression.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
Change "Modern Syntax" value of checkbox.
-
Click here to see the property page.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-moduleassemblyname.xml b/docs/Help_Spanish/Topics/opt-moduleassemblyname.xml
deleted file mode 100644
index ae37f3edba..0000000000
--- a/docs/Help_Spanish/Topics/opt-moduleassemblyname.xml
+++ /dev/null
@@ -1,57 +0,0 @@
-
-
-
- -moduleassemblyname
-
- -moduleassemblyname
-
-
-
- -moduleassemblyname
-
- This option specifies an assembly whose non-public types a .netmodule can access.
- Syntax
- -moduleassemblyname:assembly_name
- Arguments
- assembly_nameThe name of the assembly whose non-public types the .netmodule can access.
- Remarks
-
- -moduleassemblyname should be used when building a .netmodule, and where the following conditions are true:
-
-
-
The .netmodule needs access to non-public types in an existing assembly.
-
You know the name of the assembly into which the .netmodule will be built.
-
The existing assembly has granted friend assembly access to the assembly into which the .netmodule will be built.
-
-
- For more information on building a .netmodule, see -target:module.
-
- For more information on friend assemblies, see Friend Assemblies.
-
- This option is not available from within the development environment; it is only available when compiling from the command line.
-
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically.
- Example
-
- This sample builds an assembly with a private type, and that gives friend assembly access to an assembly called csman_an_assembly.
-
-
- -/ moduleassemblyname_1.prg -/ compile with: -target:library using System; using System.Runtime.CompilerServices;
Console.WriteLine("An_Internal_Class.Test called"); } }
-
- Example
-
- This sample builds a .netmodule that accesses a non-public type in the assembly moduleassemblyname_1.dll. By knowing that this .netmodule will be built into an assembly called csman_an_assembly, we can specify -moduleassemblyname, allowing the .netmodule to access non-public types in an assembly that has granted friend assembly access to csman_an_assembly.
-
-
- -/ moduleassemblyname_2.prg -/ compile with: -moduleassemblyname:csman_an_assembly -target:module -reference:moduleassemblyname_1.dll class B { public void Test() { An_Internal_Class x = new An_Internal_Class(); x.Test(); } }
-
- Example
-
- This code sample builds the assembly csman_an_assembly, referencing the previously-built assembly and .netmodule.
-
-
- -/ csman_an_assembly.prg -/ compile with: -addmodule:moduleassemblyname_2.netmodule -reference:moduleassemblyname_1.dll class A { public static void Main() { B bb = new B(); bb.Test(); } }
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-modulenamestring.xml b/docs/Help_Spanish/Topics/opt-modulenamestring.xml
deleted file mode 100644
index 13c862ef6a..0000000000
--- a/docs/Help_Spanish/Topics/opt-modulenamestring.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- -modulename
-
- -modulename
-
-
-
- -modulename:<string>
-
- This option specifies the name of the source module.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-namedargs.xml b/docs/Help_Spanish/Topics/opt-namedargs.xml
deleted file mode 100644
index 432b8d5b50..0000000000
--- a/docs/Help_Spanish/Topics/opt-namedargs.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- -namedargs
-
- -namedargs
-
-
-
- -namedargs
-
- This option specifies whether to allow named arguments in the parser or not.
- Syntax
- -namedargs [+ | -]
- Arguments
- + | - Specifying +, or just -namedargs, directs the compiler to allow namedarguments. Specifying - directs the compiler to NOT use named arguments.
-
- Remarks
- The default = + for the Core dialect and - for all other dialects. So -namedargs- only is useful in combination with the Core dialect.
-
- Note: If you enable this option, then quite often existing code such as the code below will produce compiler errors. That is why we have disabled named arguments for most dialects.
- FUNCTION Start asVOID LOCAL a ASARRAY -/ When named arguments are enabled then the compiler will complain that there is no parameter named "a" for the Empty function IF !Empty( a := SomeFunctionThatReturnsAnArray()) -/ do something ENDIF RETURN
- Click here to see the property page
-
-
diff --git a/docs/Help_Spanish/Topics/opt-noconfig.xml b/docs/Help_Spanish/Topics/opt-noconfig.xml
deleted file mode 100644
index 1879627c2e..0000000000
--- a/docs/Help_Spanish/Topics/opt-noconfig.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- -noconfig
-
- -noconfig
- xsc.rsp
-
-
-
- -noconfig
-
- The -noconfig option tells the compiler not to compile with the xsc.rsp file, which is located in and loaded from the same directory as the xsc.exe file.
- Syntax
- -noconfig
- Remarks
- The xsc.rsp file references all the assemblies shipped with the .NET Framework. The actual references that the Visual Studio .NET development environment includes depend on the project type.
-
- You can modify the xsc.rsp file and specify additional compiler options that should be included in every compilation from the command line with xsc.exe (except the -noconfig option).
-
- The compiler processes the options passed to the xsc command last. Therefore, any option on the command line overrides the setting of the same option in the xsc.rsp file.
-
- If you do not want the compiler to look for and use the settings in the xsc.rsp file, specify -noconfig.
-
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically.
-
- The current contents of xsc.rsp is:
- # Copyright (c) XSharp BV. All Rights Reserved.
# This file contains command-line options that the X# # command line compiler (XSC) will process as part # of every compilation, unless the "/noconfig" option # is specified.
# Reference the common Framework libraries /r:Accessibility.dll /r:Microsoft.CSharp.dll /r:System.Configuration.dll /r:System.Configuration.Install.dll /r:System.Core.dll /r:System.Data.dll /r:System.Data.DataSetExtensions.dll /r:System.Data.Linq.dll /r:System.Data.OracleClient.dll /r:System.Deployment.dll /r:System.Design.dll /r:System.DirectoryServices.dll /r:System.dll /r:System.Drawing.Design.dll /r:System.Drawing.dll /r:System.EnterpriseServices.dll /r:System.Management.dll /r:System.Messaging.dll /r:System.Runtime.Remoting.dll /r:System.Runtime.Serialization.dll /r:System.Runtime.Serialization.Formatters.Soap.dll /r:System.Security.dll /r:System.ServiceModel.dll /r:System.ServiceModel.Web.dll /r:System.ServiceProcess.dll /r:System.Transactions.dll /r:System.Web.dll /r:System.Web.Extensions.Design.dll /r:System.Web.Extensions.dll /r:System.Web.Mobile.dll /r:System.Web.RegularExpressions.dll /r:System.Web.Services.dll /r:System.Windows.Forms.dll /r:System.Workflow.Activities.dll /r:System.Workflow.ComponentModel.dll /r:System.Workflow.Runtime.dll /r:System.Xml.dll /r:System.Xml.Linq.dll
-
-
diff --git a/docs/Help_Spanish/Topics/opt-noinit.xml b/docs/Help_Spanish/Topics/opt-noinit.xml
deleted file mode 100644
index 27538e49a4..0000000000
--- a/docs/Help_Spanish/Topics/opt-noinit.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- -noinit
-
- $Exit
- $Init1
- $Init2
- $Init3
- EXIT PROCEDURE
- INIT PROCEDURE
- -noinit
-
-
-
- -noinit
-
- Suppress generation of empty $Init1() and $Exit() functions.
-
- Background info
- The X# compiler generates special functions in each assembly that are used to call INIT procedures and EXIT procedures.
- There are three levels of INIT procedures.
- For each of these three levels, a special function is created: $Init1(), $Init2() and $Init3(). For EXIT procedures the compiler creates a function $Exit().
- The functions $Init2() and $Init3() are only created when needed.
- The functions $Init1() and $Exit() are always created.
-
- When you compile an EXE with X# then the compiler generates code that calls the $Init1(), $Init2() and $Init3() functions in all referenced assemblies at startup and the $Exit() functions at shutdown.
-
- This mechanism also guarantees that classes in referenced assemblies are available at runtime, even when you have not explicitly referenced them in your code, so you can instantiate these classes with CreateInstance().
-
- The compiler option -noinit suppresses the generation of empty $Init1() and $Exit() functions. As a result there will be no hard link to external assemblies if you do not reference code from these assemblies.
- If you use these compiler option with an assembly that only contains DEFINES then the defines will be resolved at compile time and you will not need to include the assembly at runtime (unless these defines contain values that need to be resolved at runtime, such as symbols or date values).
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-nologo.xml b/docs/Help_Spanish/Topics/opt-nologo.xml
deleted file mode 100644
index b5fd8b459e..0000000000
--- a/docs/Help_Spanish/Topics/opt-nologo.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- -nologo
-
- -nologo
-
-
-
- -nologo
-
- The -nologo option suppresses display of the sign-on banner when the compiler starts up and display of informational messages during compiling.
- Syntax
- -nologo
- Remarks
-
- This option is not available from within the development environment; it is only available when compiling from the command line.
-
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-nostddefs.xml b/docs/Help_Spanish/Topics/opt-nostddefs.xml
deleted file mode 100644
index 8f3dfb55ed..0000000000
--- a/docs/Help_Spanish/Topics/opt-nostddefs.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- -nostddefs
-
- -nostddefs
-
-
-
- -nostddefs
-
- The -nostddefs option prevents the compiler from using the preprocessor directives in XSharpDefs.xh.
- Syntax
- -nostddefs[+|-]
- Arguments
- + | - Specifying +, or just -nostddefs, prevents the compiler from using the preprocessor directives in XSharpDefs.xh.
- Remarks
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
In the Preprocessor section, modify the "Suppress standard header file" property.
-
Click here to see the property page.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-nostdlib.xml b/docs/Help_Spanish/Topics/opt-nostdlib.xml
deleted file mode 100644
index 4cade77566..0000000000
--- a/docs/Help_Spanish/Topics/opt-nostdlib.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- -nostdlib
-
- -nostdlib
-
-
-
- -nostdlib
-
- -nostdlib prevents the import of mscorlib.dll, which defines the entire System namespace.
- Syntax
- -nostdlib[+ | -]
- Remarks
- Use this option if you want to define or create your own System namespace and objects.
-
- If you do not specify -nostdlib, mscorlib.dll will be imported into your program (same as specifying -nostdlib-). Specifying -nostdlib is the same as specifying -nostdlib+.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-nowarn.xml b/docs/Help_Spanish/Topics/opt-nowarn.xml
deleted file mode 100644
index ae9050f3e2..0000000000
--- a/docs/Help_Spanish/Topics/opt-nowarn.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- -nowarn
-
- -nowarn
-
-
-
- -nowarn
-
- The -nowarn option lets you suppress the compiler from displaying one or more warnings. Separate multiple warning numbers with a comma.
- Syntax
- -nowarn:number1[,number2,...]
- Arguments
- number1, number2Warning number(s) that you want the compiler to suppress.
- Remarks
- You should only specify the numeric part of the warning identifier. For example, if you want to suppress XS0028, you could specify -nowarn:28.
-
- To set this compiler option in the Visual Studio development environment
-
-
Open the project's Properties page.
-
Click the Build property page.
-
Modify the "Suppress Specific Warnings" property.
-
Click here to see the property page
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-nowin32manifest.xml b/docs/Help_Spanish/Topics/opt-nowin32manifest.xml
deleted file mode 100644
index dbb5a49016..0000000000
--- a/docs/Help_Spanish/Topics/opt-nowin32manifest.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- -nowin32manifest
-
- -nowin32manifest
-
-
-
- -nowin32manifest
-
- Use the -nowin32manifest option to instruct the compiler not to embed any application manifest into the executable file.
- Syntax
- -nowin32manifest
- Remarks
- When this option is used, the application will be subject to virtualization on Windows Vista unless you provide an application manifest in a Win32 Resource file or during a later build step.
-
- Click here to see the property page
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-ns.xml b/docs/Help_Spanish/Topics/opt-ns.xml
deleted file mode 100644
index 2aab77099e..0000000000
--- a/docs/Help_Spanish/Topics/opt-ns.xml
+++ /dev/null
@@ -1,64 +0,0 @@
-
-
-
- -ns
-
- -ns
-
-
-
- -ns
-
- The -ns option explicitly specifies the default namespace for all types that do not have an explicit namespace in their name.
- Syntax
- -ns[: ]namespaceName
- Arguments
- namespaceNameThe name of the default namespace for all types declared in the application or class library.
- Remarks
- If the -ns option is not specified, then types that are not prefixed with a namespace and types that are not in a BEGIN NAMESPACE .. END NAMESPACE construct will be compiled as so-called global types.
-
- The -ns option will work on the following types:
-
-
-
Classes
-
Interfaces
-
Structures
-
Vostructs
-
Delegates
-
-
- Namespace names must follow the same rules for program identifiers: they must begin with an uppercase or lowercase letter or an underscore, followed by zero or more uppercase or lowercase letters, numbers or underscores. All other characters are illegal, and will raise a compile-time error.
-
- The default namespace is used for any declared types that do not have an explicit namespace in their name.
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language tab.
-
Change the value of the "Prefix classes with default namespace" property.
-
Click here to see the property page.
-
The build system will then generate a command line option that combines this property with the Default Namespace that is specified on the Application Tab of the project properties.
-
- Example
-
- When the following code is compiled without -ns compiler option the following types will be produced:
-
-
Customer
-
Point
-
MyProject.Customer
-
MyProject.Data.Customer
-
-
- CLASS Customer . . END CLASS
STRUCT Point . . END STRUCT
ENUM CustomerType . END ENUM
CLASS MyProject.Customer . . END CLASS
BEGIN NAMESPACE MyProject.Data CLASS Customer . . END CLASS END NAMESPACE
-
-
- If you compile the same code with a -ns:MyNameSpace option the following types will be produced:
-
-
-
MyNameSpace.Customer
-
MyNameSpace.Point
-
MyProject.Customer
-
MyProject.Data.Customer
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-optimize.xml b/docs/Help_Spanish/Topics/opt-optimize.xml
deleted file mode 100644
index 8f275ed96e..0000000000
--- a/docs/Help_Spanish/Topics/opt-optimize.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- -optimize
-
- -optimize
-
-
-
- -optimize
-
- The -optimize option enables or disables optimizations performed by the compiler to make your output file smaller, faster, and more efficient.
- Syntax
- -optimize[+ | -]
- Remarks
- -optimize also tells the common language runtime to optimize code at runtime.
-
- By default, optimizations are disabled. Specify -optimize+ to enable optimizations.
-
- When building a module to be used by an assembly, use the same -optimize settings as those of the assembly.
-
- -o is the short form of -optimize.
-
- It is possible to combine the -optimize and -debug options.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Build property page.
-
Modify the "Optimize" property.
-
Click here to see the property page.
-
- Example
-
- Compile t2.prg and enable compiler optimizations:
-
- xsc t2.prg -optimize
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-out.xml b/docs/Help_Spanish/Topics/opt-out.xml
deleted file mode 100644
index 8be53a5b45..0000000000
--- a/docs/Help_Spanish/Topics/opt-out.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- -out
-
- -out
-
-
-
- -out
-
- The -out option specifies the name of the output file.
- Syntax
- -out:filename
- Arguments
- filenameThe name of the output file created by the compiler.
- Remarks
- On the command line, it is possible to specify multiple output files for your compilation. The compiler expects to find one or more source code files following the -out option. Then, all source code files will be compiled into the output file specified by that -out option.
-
- Specify the full name and extension of the file you want to create.
-
- If you do not specify the name of the output file:
-
-
-
An .exe will take its name from the source code file that contains the Main method.
-
A .dll or .netmodule will take its name from the first source code file.
-
-
- A source code file used to compile one output file cannot be used in the same compilation for the compilation of another output file.
-
- When producing multiple output files in a command line compilation, keep in mind that only one of the output files can be an assembly and that only the first output file specified (implicitly or explicitly with -out) can be the assembly.
-
- Any modules produced as part of a compilation become files associated with any assembly also produced in the compilation. Use ildasm.exe to view the assembly manifest to see the associated files.
-
- The -out compiler option is required in order for an exe to be the target of a friend assembly.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Application property page.
-
Modify the Application Name property.
-
Click here to see the property page.
-
-
- To set this compiler option programmatically: the OutputFileName is a read-only property, which is determined by a combination of the project type (exe, library, and so forth) and the assembly name. Modifying one or both of these properties will be necessary to set the output file name.
- Example
-
- Compile t.prg and create output file t.exe, as well as build t2.prg and create module output file mymodule.netmodule:
-
-
- xsc t.prg -out:mymodule.netmodule -target:module t2.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-ovf.xml b/docs/Help_Spanish/Topics/opt-ovf.xml
deleted file mode 100644
index 5a32f74870..0000000000
--- a/docs/Help_Spanish/Topics/opt-ovf.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- -ovf
-
- -checked
- -ovf
-
-
-
- -ovf
-
- The -ovf compiler option is an alias for the -checked command line option for compatibility.
- We have added this option because Vulcan.Net also had that option.
-
- Click here to see the property page
-
-
diff --git a/docs/Help_Spanish/Topics/opt-parallel.xml b/docs/Help_Spanish/Topics/opt-parallel.xml
deleted file mode 100644
index 6b7fe06b91..0000000000
--- a/docs/Help_Spanish/Topics/opt-parallel.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- -parallel
-
- -parallel
-
-
-
- -parallel
-
- Specifies whether to use concurrent build (+).
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-parseonly.xml b/docs/Help_Spanish/Topics/opt-parseonly.xml
deleted file mode 100644
index 2776cbe5d6..0000000000
--- a/docs/Help_Spanish/Topics/opt-parseonly.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- -parseonly
-
- -parseonly
-
-
-
- -parseonly
-
- Performs a syntax check on the input files only. Does not produce the output exe, dll or pdb.
- Syntax
- -parseonly[+|-]
- Arguments
- + | - Specifying +, or just -parseonly, tells the compiler to only parse the source code and not to bind and generate an output file. When combined with the -ppo option, there will be .ppo files written.
- Remarks
- This command line option allows you to check the code without generating a binary.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-pathmap.xml b/docs/Help_Spanish/Topics/opt-pathmap.xml
deleted file mode 100644
index 9454361984..0000000000
--- a/docs/Help_Spanish/Topics/opt-pathmap.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- -pathmap
-
- -pathmap
-
-
-
- -pathmap
-
- Specifies a mapping for source path names output by the compiler.
-
- Syntax
- -pathmap:path1=sourcePath1,path2=sourcePath2
- Arguments
- path1 The full path to the source files in the current environment.
- sourcePath1 The source path substituted for path1 in any output files.
-
- To specify multiple mapped source paths, separate each with a comma.
-
- Remarks
-
- The compiler writes the source path into its output for the following reasons:
-
-
The source path is substituted for an argument when the CallerFilePathAttribute is applied to an optional parameter.
-
The source path is embedded in a PDB file.
-
The path of the PDB file is embedded into a PE (portable executable) file.
-
-
- This option maps each physical path on the machine where the compiler runs to a corresponding path that should be written in the output files.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-pdb.xml b/docs/Help_Spanish/Topics/opt-pdb.xml
deleted file mode 100644
index a097e05145..0000000000
--- a/docs/Help_Spanish/Topics/opt-pdb.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- -pdb
-
- -pdb
-
-
-
- -pdb
-
- The -pdb compiler option specifies the name and location of the debug symbols file.
- Syntax
- -pdb:filename
- Arguments
- filenameThe name and location of the debug symbols file.
- Remarks
- When you specify -debug , the compiler will create a .pdb file in the same directory where the compiler will create the output file (.exe or .dll) with a file name that is the same as the name of the output file.
-
- -pdb allows you to specify a non-default file name and location for the .pdb file.
-
- This compiler option cannot be set in the Visual Studio development environment, nor can it be changed programmatically.
- Example
-
- Compile t.prg and create a .pdb file called tt.pdb:
-
- xsc -debug -pdb:tt t.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-platform.xml b/docs/Help_Spanish/Topics/opt-platform.xml
deleted file mode 100644
index 0891f3f748..0000000000
--- a/docs/Help_Spanish/Topics/opt-platform.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-
-
-
- -platform
-
- -platform
-
-
-
- -platform
-
- Specifies which version of the common language runtime (CLR) can run the assembly.
- Syntax
- -platform:string
- Arguments
- stringanycpu (default), anycpu32bitpreferred, ARM, x64, x86, or Itanium.
- Remarks
-
-
anycpu (default) compiles your assembly to run on any platform. Your application runs as a 64-bit process whenever possible and falls back to 32-bit when only that mode is available.
-
anycpu32bitpreferred compiles your assembly to run on any platform. Your application runs in 32-bit mode on systems that support both 64-bit and 32-bit applications. You can specify this option only for projects that target the .NET Framework 4.5.
-
-
-
ARM compiles your assembly to run on a computer that has an Advanced RISC Machine (ARM) processor.
-
x64 compiles your assembly to be run by the 64-bit common language runtime on a computer that supports the AMD64 or EM64T instruction set.
-
x86 compiles your assembly to be run by the 32-bit, x86-compatible common language runtime.
-
Itanium compiles your assembly to be run by the 64-bit common language runtime on a computer with an Itanium processor.
-
-
- On a 64-bit Windows operating system:
-
-
-
Assemblies compiled with -platform:x86 execute on the 32-bit CLR running under WOW64.
-
A DLL compiled with the -platform:anycpu executes on the same CLR as the process into which it is loaded.
-
Executables that are compiled with the -platform:anycpu execute on the 64-bit CLR.
-
Executables compiled with -platform:anycpu32bitpreferred execute on the 32-bit CLR.
-
-
- The anycpu32bitpreferred setting is valid only for executable (.EXE) files, and it requires the .NET Framework 4.5.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the Properties page for the project.
-
Click the Build property page.
-
Modify the Platform target property and, for projects that target the .NET Framework 4.5, select or clear the Prefer 32-bit check box.
-
Click here to see the property page.
-
- Example
-
- The following example shows how to use the -platform option to specify that the application should be run by the 64-bit CLR on a 64-bit Windows operating system.
-
- xsc -platform:anycpu filename.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-ppo.xml b/docs/Help_Spanish/Topics/opt-ppo.xml
deleted file mode 100644
index 5331f74722..0000000000
--- a/docs/Help_Spanish/Topics/opt-ppo.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- -ppo
-
- -ppo
-
-
-
- -ppo
-
- The -ppo option directs the compiler to write the output of the preprocessor to a file.
- Syntax
- -ppo [+ | -]
- Arguments
- + | - Specifying +, or just -ppo, directs the compiler to write the output of the preprocessor to a file. When ppo is not enabled, the compiler will delete any existing ppo files that match input file names.
- Remarks
- Each source file will be written to a file with the same base name and an extension of .ppo, in the same directory as the source file. If a .ppo file already exists, it will be overwritten without warning.
- Tip:
- .ppo files can be viewed within Visual Studio. After enabling the -ppo option and rebuilding the project, select any node in the project in Solution Explorer, click the Show All Files button in the Solution Explorer toolbar, then double click the desired .ppo file node.
-
- To view a .prg and .ppo file side-by-side to compare them, right-click the document tab in either the .prg or .ppo file and click New Vertical Tab Group.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page (see How to: Set Build Properties).
-
Click the Build tab.
-
In the General section, modify the "Generate preprocessor output"property.
-
Click here to see the property page.
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-preferreduilang.xml b/docs/Help_Spanish/Topics/opt-preferreduilang.xml
deleted file mode 100644
index c321ef911e..0000000000
--- a/docs/Help_Spanish/Topics/opt-preferreduilang.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- -preferreduilang
-
- -preferreduilang
-
-
-
- -preferreduilang
-
- By using the -preferreduilang compiler option, you can specify the language in which the X# compiler displays output, such as error messages.
- Syntax
- -preferreduilang: language
- Arguments
- languageThe language name of the language to use for compiler output.
- Remarks
- The preferreduilang compiler option is recognized but ignored. The X# compiler only works in the english language (for now?).
-
-
diff --git a/docs/Help_Spanish/Topics/opt-recurse.xml b/docs/Help_Spanish/Topics/opt-recurse.xml
deleted file mode 100644
index 0e8ee18b7f..0000000000
--- a/docs/Help_Spanish/Topics/opt-recurse.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- -recurse
-
- -recurse
-
-
-
- -recurse
-
- The -recurse option enables you to compile source code files in all child directories of either the specified directory (dir) or of the project directory.
- Syntax
- -recurse:[dir\]file
- Arguments
- dir (optional)The directory in which you want the search to begin. If this is not specified, the search begins in the project directory.
- fileThe file(s) to search for. Wildcard characters are allowed.
- Remarks
- The -recurse option lets you compile source code files in all child directories of either the specified directory (dir) or of the project directory.
- You can use wildcards in a file name to compile all matching files in the project directory without using -recurse.
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically.
- Example
-
- Compiles all X# files in the current directory:
-
- xsc *.prg
-
- Compiles all of the X# files in the dir1\dir2 directory and any directories below it and generates dir2.dll:
-
-
- xsc -target:library -out:dir2.dll -recurse:dir1\dir2\*.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-reference.xml b/docs/Help_Spanish/Topics/opt-reference.xml
deleted file mode 100644
index 0be5a87c53..0000000000
--- a/docs/Help_Spanish/Topics/opt-reference.xml
+++ /dev/null
@@ -1,68 +0,0 @@
-
-
-
- -reference
-
- -reference
-
-
-
- -reference
-
- The -reference option causes the compiler to import public type information in the specified file into the current project, thus enabling you to reference metadata from the specified assembly files.
- Syntax
- -reference:[alias=]filename -reference:filename
- Arguments
- filenameThe name of a file that contains an assembly manifest. To import more than one file, include a separate -reference option for each file.
- aliasA valid X# identifier that will represent a root namespace that will contain all namespaces in the assembly.
- Remarks
- To import from more than one file, include a -reference option for each file.
-
- The files you import must contain a manifest; the output file must have been compiled with one of the -target options other than -target:module.
-
- -r is the short form of -reference.
-
- Use -addmodule to import metadata from an output file that does not contain an assembly manifest.
-
- If you reference an assembly (Assembly A) that references another assembly (Assembly B), you will need to reference Assembly B if:
-
-
-
A type you use from Assembly A inherits from a type or implements an interface from Assembly B.
-
You invoke a field, property, event, or method that has a return type or parameter type from Assembly B.
-
-
- Use -lib to specify the directory in which one or more of your assembly references is located. The -lib topic also discusses the directories in which the compiler searches for assemblies.
-
- In order for the compiler to recognize a type in an assembly, and not in a module, it needs to be forced to resolve the type, which you can do by defining an instance of the type. There are other ways to resolve type names in an assembly for the compiler - for example, if you inherit from a type in an assembly, the type name will then be recognized by the compiler.
-
- Sometimes it is necessary to reference two different versions of the same component from within one assembly. To do this, use the alias suboption on the -reference switch for each file to distinguish between the two files. This alias will be used as a qualifier for the component name, and will resolve to the component in one of the files.
-
- The xsc response (.rsp) file, which references commonly used .NET Framework assemblies, is used by default. Use -noconfig if you do not want the compiler to use xsc.rsp.
-
- Note
- In Visual Studio, use the Add Reference dialog box.
- Example
-
- This example shows how to use the extern alias feature.
-
- You compile the source file and import metadata from grid.dll and grid20.dll,which have been compiled previously. The two DLLs contain separate versions of the same component, and you use two -reference with alias options to compile the source file. The options look like this:
-
- -reference:GridV1=grid.dll and -reference:GridV2=grid20.dll
-
- This sets up the external aliases "GridV1" and "GridV2," which you use in your program by means of an extern statement:
-
-
- extern alias GridV1; extern alias GridV2; -/ Using statements go here.
-
- Once this is done, you can refer to the grid control from grid.dll by prefixing the control name with GridV1, like this:
-
-
- GridV1::Grid
-
- In addition, you can refer to the grid control from grid20.dll by prefixing the control name with GridV2 like this:
-
-
- GridV2::Grid
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-refonly.xml b/docs/Help_Spanish/Topics/opt-refonly.xml
deleted file mode 100644
index 173b1e5c32..0000000000
--- a/docs/Help_Spanish/Topics/opt-refonly.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- -refonly
-
- -refonly
-
-
-
- -refonly
-
- The -refonly option indicates that the primary output should be a reference assembly rather than an implementation assembly. The -refonly parameter silently disables outputting PDBs, as reference assemblies cannot be executed.
- Syntax
- -refonly
- Metadata-only assemblies replace method bodies with a single throw null body but include all members except anonymous types. The use of throw null bodies (rather than having no bodies) ensures that PEVerify can run and pass, thereby validating the completeness of the metadata.
-
- Reference assemblies include an assembly-level ReferenceAssembly attribute. This attribute may be specified in source, in which case the compiler does not need to synthesize it. Due to this attribute, runtimes refuse to execute reference assemblies, though they can still be loaded in reflection-only mode. Tools reflecting on assemblies must load reference assemblies in reflection-only; otherwise, the runtime will throw a type-load error.
-
- Reference assemblies also remove metadata (private members) from metadata-only assemblies, with the following distinctions:
-
-
A reference assembly contains references only for elements required by the API surface. The real assembly might include additional references for implementation-specific purposes.
-
Private function members (methods, properties, and events) are removed if their removal does not impact compilation observably. If no InternalsVisibleTo attributes are present, the same applies to internal function members.
-
However, all types, including private or nested ones, are retained in reference assemblies. All attributes, including internal ones, are preserved.
-
All virtual methods are kept. Explicit interface implementations are kept. Explicitly implemented properties and events are kept, as their accessors are virtual (and are therefore kept).
-
All fields within a structure are retained. (This aspect may be subject to refinement in future versions post-C#-7.1).
-
-
- The -refonly and -refout options are mutually exclusive.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-refout.xml b/docs/Help_Spanish/Topics/opt-refout.xml
deleted file mode 100644
index 711a3b3354..0000000000
--- a/docs/Help_Spanish/Topics/opt-refout.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- -refout
-
- -refout
-
-
-
- -refout
-
- The -refout option specifies a file path in which the reference assembly should be output. This translates to metadataPeStream in the Emit API.
- Syntax
- -refout:filepath
- Arguments
- filepathThe name and path of the output file created by the compiler.
- Remarks
- The filename should generally match that of the primary assembly. The recommended convention (used by MSBuild) is to place the reference assembly in a "ref/" sub-folder relative to the primary assembly.
- Metadata-only assemblies have their method bodies replaced with a single throw null body, but include all members except anonymous types. The reason for using throw null bodies, as opposed to no bodies, is to enable PEVerify to run and pass, thereby validating the completeness of the metadata.
-
- Reference assemblies include an assembly-level ReferenceAssembly attribute. This attribute may be specified in source, in which case the compiler will not need to synthesize it. Because of this attribute, runtimes will refuse to load reference assemblies for execution, although they can still be loaded in reflection-only mode. Tools that reflect on assemblies should ensure they load reference assemblies as reflection-only; otherwise, they will receive a typeload error from the runtime.
-
- Reference assemblies further remove metadata (private members) from metadata-only assemblies:
-
-
A reference assembly contains references only for elements required by the API surface. The real assembly might include additional references for implementation-specific purposes.
-
Private function members (methods, properties, and events) are removed if their removal does not impact compilation observably. If no InternalsVisibleTo attributes are present, the same applies to internal function members.
-
However, all types, including private or nested ones, are retained in reference assemblies. All attributes, including internal ones, are preserved.
-
All virtual methods are kept. Explicit interface implementations are kept. Explicitly implemented properties and events are kept, as their accessors are virtual (and are therefore kept).
-
All fields within a structure are retained.
-
-
- The -refout and -refonly options are mutually exclusive.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-resource.xml b/docs/Help_Spanish/Topics/opt-resource.xml
deleted file mode 100644
index a6f4ddda68..0000000000
--- a/docs/Help_Spanish/Topics/opt-resource.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- -resource
-
- -resource
-
-
-
- -resource
-
- Embeds the specified resource into the output file.
- Syntax
- -resource:filename[,identifier[,accessibility-modifier]]
- Arguments
- filenameThe .NET Framework resource file that you want to embed in the output file.
-
- identifier (optional)The logical name for the resource; the name that is used to load the resource. The default is the name of the file name.
-
- accessibility-modifier (optional)The accessibility of the resource: public or private. The default is public.
- Remarks
- Use -linkresource to link a resource to an assembly and not add the resource file to the output file.
-
- By default, resources are public in the assembly when they are created by using the X# compiler. To make resources private, specify private as the accessibility modifier. No other accessibility other than public or private is allowed.
-
- If filename is a .NET Framework resource file created, for example, by Resgen.exe or in the development environment, it can be accessed with members in the System.Resources namespace. For more information, see System.Resources.ResourceManager. For all other resources, use the GetManifestResource* methods in the Assembly class to access the resource at run time.
-
- -res is the short form of -resource.
-
- The order of the resources in the output file is determined from the order specified on the command line.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Add a resource file to your project.
-
Select the file that you want to embed in Solution Explorer.
-
Select Build Action for the file in the Properties window.
-
Set Build Action to Embedded Resource.
-
-
- For information about how to set this compiler option programmatically, see BuildAction.
- Example
-
- Compile in.prg and attach resource file rf.resource:
-
-
- xsc -resource:rf.resource in.prg
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-ruleset.xml b/docs/Help_Spanish/Topics/opt-ruleset.xml
deleted file mode 100644
index d1c16c10a6..0000000000
--- a/docs/Help_Spanish/Topics/opt-ruleset.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- -ruleset
-
- -ruleset
-
-
-
- -ruleset
-
- Specifies a ruleset file that disables specific diagnostics.
- Syntax
- -ruleset:filename
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-shared.xml b/docs/Help_Spanish/Topics/opt-shared.xml
deleted file mode 100644
index 24a133436f..0000000000
--- a/docs/Help_Spanish/Topics/opt-shared.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- -shared
-
- /shared
- pipename
-
-
-
- -shared
-
- Uses the shared compiler process (XSCompiler.exe) to compile the project. This process caches type information so repeated compilations will be faster.
- Syntax
- /shared[: pipeName]
- Arguments
- pipeNameThis optional parameter specifies the pipename that the compiler uses to communicate between the foreground process (xsc.exe) and the background compiler (xscompiler.exe).
- Remarks
- This command line option is useful to speed up compilation
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Build tab.
-
Check or uncheck the "Use Shared compiler" option.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-showincludes.xml b/docs/Help_Spanish/Topics/opt-showincludes.xml
deleted file mode 100644
index 6aea821c22..0000000000
--- a/docs/Help_Spanish/Topics/opt-showincludes.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- -showincludes
-
- -showincludes
-
-
-
- -showincludes
-
- The -showincludes option causes the compiler to output the names of #include files as they are processed.
- Syntax
- -showincludes[+|-]
- Arguments
- + | - Specifying +, or just -showincludes, causes the compiler to output the names of #include files as they are processed.
- Remarks
- This option is useful in order to determine the files the compiler is processing as a result of an #include directive. Nested include files are also displayed.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-snk.xml b/docs/Help_Spanish/Topics/opt-snk.xml
deleted file mode 100644
index e996ee4bbe..0000000000
--- a/docs/Help_Spanish/Topics/opt-snk.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- -snk
-
- -keyfile
- -snk
-
-
-
- -snk
-
- The -snk compiler option is an alias for the -keyfile option, for compatibility.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-stddefs.xml b/docs/Help_Spanish/Topics/opt-stddefs.xml
deleted file mode 100644
index 42c5d8b7fc..0000000000
--- a/docs/Help_Spanish/Topics/opt-stddefs.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- -stddefs
-
- -stddefs
-
-
-
- -stddefs
-
- Overrides the name of the standard defines file (default = XSharpDefs.xh).
- Syntax
- -stddefs:filepath
- Arguments
- filepathThe name and path of the header file to use instead of XSharpDefs.Xh. When no path is included, the compiler will use the Includepath specified from the commandline (-i).
-
-
- Click here to see the property page.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-subsystemversion.xml b/docs/Help_Spanish/Topics/opt-subsystemversion.xml
deleted file mode 100644
index 134cfa0210..0000000000
--- a/docs/Help_Spanish/Topics/opt-subsystemversion.xml
+++ /dev/null
@@ -1,111 +0,0 @@
-
-
-
- -subsystemversion
-
- -subsystemversion
-
-
-
- -subsystemversion
-
- Specifies the minimum version of the subsystem on which the generated executable file can run, thereby determining the versions of Windows on which the executable file can run. Most commonly, this option ensures that the executable file can leverage particular security features that are not available with older versions of Windows.
-
- Note
- To specify the subsystem itself, use the -target compiler option.
- Syntax
- -subsystemversion:major.minor
-
- Parameters
- major.minorThe minimum required version of the subsystem, as expressed in a dot notation for major and minor versions. For example, you can specify that an application cannot run on an operating system that is older than Windows 7 if you set the value of this option to 6.01, as the table later in this topic describes. You must specify the values for major and minor as integers.
-
- Leading zeroes in the minor version do not change the version, but trailing zeroes do. For example, 6.1 and 6.01 refer to the same version, but 6.10 refers to a different version. We recommend expressing the minor version as two digits to avoid confusion.
- Remarks
- The following table lists common subsystem versions of Windows:
-
-
-
-
- Windows version
-
-
- Subsystem version
-
-
-
-
- Windows 2000
-
-
- 5.00
-
-
-
-
- Windows XP
-
-
- 5.01
-
-
-
-
- Windows Server 2003
-
-
- 5.02
-
-
-
-
- Windows Vista
-
-
- 6.00
-
-
-
-
- Windows 7
-
-
- 6.01
-
-
-
-
- Windows Server 2008
-
-
- 6.01
-
-
-
-
- Windows 8
-
-
- 6.02
-
-
-
- Default values
- The default value of the -subsystemversion compiler option depends on the conditions in the following list:
-
-
-
The default value is 6.02 if any compiler option in the following list is set:
-
-
-
-target:appcontainerexe
-
-target:winmdobj
-
-platform:arm
-
-
-
The default value is 6.00 if you are using MSBuild, are targeting .NET Framework 4.5, and have not set any of the compiler options that were specified earlier in this list.
-
The default value is 4.00 if none of the previous conditions is true.
-
- Setting this option
- To set the -subsystemversion compiler option in Visual Studio, you must open the .xsproj file and specify a value for the SubsystemVersion property in the MSBuild XML. You cannot set this option in the Visual Studio IDE.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-target.xml b/docs/Help_Spanish/Topics/opt-target.xml
deleted file mode 100644
index 46db305f29..0000000000
--- a/docs/Help_Spanish/Topics/opt-target.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- -target
-
- -target
-
-
-
- -target
-
- The -target compiler option can be specified in one of four forms:
-
- -target:appcontainerexeTo create an .exe file for Windows 8.x Store apps.
- -target:exeTo create an .exe file.
- -target:libraryTo create a code library.
- -target:moduleTo create a module.
- -target:winexeTo create a Windows program.
- -target:winmdobjTo create an intermediate .winmdobj file.
-
- Unless you specify -target:module, -target causes a .NET Framework assembly manifest to be placed in an output file. For more information, see Assemblies in the Common Language Runtime and Common Attributes.
- The assembly manifest is placed in the first .exe output file in the compilation or in the first DLL, if there is no .exe output file. For example, in the following command line, the manifest will be placed in 1.exe:
-
- xsc -out:1.exe t1.prg -out:2.netmodule t2.prg
-
- The compiler creates only one assembly manifest per compilation. Information about all files in a compilation is placed in the assembly manifest. All output files except those created with -target:module can contain an assembly manifest. When producing multiple output files at the command line, only one assembly manifest can be created and it must go into the first output file specified on the command line. No matter what the first output file is (/target:exe, -target:winexe, -target:library or -target:module), any other output files produced in the same compilation must be modules (/target:module).
-
- If you create an assembly, you can indicate that all or part of your code is CLS compliant with the CLSCompliantAttribute attribute.
-
- // target_clscompliant.prg [assembly:System.CLSCompliant(true)] // specify assembly compliance [System.CLSCompliant(false)]; // specify compliance for an element CLASS TestClass
PUBLICSTATICMETHOD Start ASVOID RETURN ENDCLASS
-
- For more information about setting this compiler option programmatically, see OutputType.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-touchedfiles.xml b/docs/Help_Spanish/Topics/opt-touchedfiles.xml
deleted file mode 100644
index de4da8890d..0000000000
--- a/docs/Help_Spanish/Topics/opt-touchedfiles.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- -touchedfiles
-
- -touchedfiles
-
-
-
- -touchedfiles
-
- The -touchedfiles compiler option allows you to declare a file in which the compiler will list which files have been touched during the compilation process.
- Syntax
- -touchedfiles:filename
- Remarks
- The compiler will produce 2 output files:
-
- filename.readThis lists all the files that were read by the compiler
- filename.writeThis lists all the files that were written by the compiler. That includes the exe, pdb, ppo etc.
-
- The file names in both files are all capitalized and in alphabetical order.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-undeclared.xml b/docs/Help_Spanish/Topics/opt-undeclared.xml
deleted file mode 100644
index c32a7811fe..0000000000
--- a/docs/Help_Spanish/Topics/opt-undeclared.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- -undeclared
-
- -undeclared
-
-
-
- -undeclared
-
- The -undeclared option tells the compiler to enable the support for 'undeclared variables'.
- Syntax
- -undeclared [+ | -]
- Arguments
- + | - Specifying +, or just -undeclared, directs the compiler to enable the support for 'undeclared variables'
- Remarks
- This will NOT work with the Core and Vulcan dialects.
- When the compiler detects an 'unknown identifier', it will assume that this is either a field in the current work area or a memory variable.
- The compiler option will only have effect when you also enabled -memvar.
-
- Click here to see the property page
-
-
diff --git a/docs/Help_Spanish/Topics/opt-unsafe.xml b/docs/Help_Spanish/Topics/opt-unsafe.xml
deleted file mode 100644
index f3b311e02f..0000000000
--- a/docs/Help_Spanish/Topics/opt-unsafe.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- -unsafe
-
- -unsafe
-
-
-
- -unsafe
-
- The -unsafe compiler option allows code that uses the unsafe keyword to compile.
- Syntax
- -unsafe
- Remarks
- For more information about unsafe code, see Unsafe Code and Pointers.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Language property page.
-
Set the Allow Unsafe Code property in the General Section.
-
Click here to see the property page.
-
- Example
- Compile in.prg for unsafe mode:
-
- xsc -unsafe in.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-utf8output.xml b/docs/Help_Spanish/Topics/opt-utf8output.xml
deleted file mode 100644
index d5b5b11bcf..0000000000
--- a/docs/Help_Spanish/Topics/opt-utf8output.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- -utf8output
-
- -utf8output
-
-
-
- -utf8output
-
- The -utf8output option displays compiler output using UTF-8 encoding.
- Syntax
- -utf8output
- Remarks
- In some international configurations, compiler output cannot correctly be displayed in the console. In these configurations, use -utf8output and redirect compiler output to a file.
-
- This compiler option is unavailable in Visual Studio and cannot be changed programmatically.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo1.xml b/docs/Help_Spanish/Topics/opt-vo1.xml
deleted file mode 100644
index 096264a369..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo1.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- -vo1
-
- -vo1
-
-
-
- -vo1Allow Init() and Axit() as aliases for Constructor and Destructor
-
- The -vo1 compiler option directs the compiler to treat Init() methods as constructors and Axit methods as destructors.
- Syntax
- -vo1[+ | -]
- Arguments
- + | - Specifying +, or just -vo1, directs the compiler to convert Init() and Axit() methods to constructors and destructors.
-
-
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo10.xml b/docs/Help_Spanish/Topics/opt-vo10.xml
deleted file mode 100644
index 46e2440801..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo10.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- -vo10
-
- -vo10
-
-
-
- -vo10Compatible IIF Behavior
-
- The -vo10 option enables the IIF operator to behave in a manner compatible with Visual Objects.
- Syntax
- -vo10[+|-]
- Arguments
- + | - Specifying +, or just -vo10, causes the IIF operator to behave as it does in Visual Objects.
- Remarks
- If the true and false expressions in an IIF operator are not the same, or one cannot be implicitly converted to the type of the other, the compiler will raise an error.
-
- Visual Objects allows this, and implicitly converts both expressions to USUAL, causing the IIF expression to also return USUAL. This is neither safe nor efficient, but code originally written in Visual Objects may depend on this behavior, and if -vo10 is not used, errors may occur at runtime.
-
- LOCAL x asLOGIC x := TRUE ? IIF( x, 1, "Sunday")
- When you use the -vo10 compiler option, the compiler will convert this to:
-
- ? IIF( x, (USUAL)1, (USUAL) "Sunday") // for the VO and Vulcan dialect
- or
- ? IIF( x, (OBJECT)1, (OBJECT) "Sunday") // for the Core dialect
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo11.xml b/docs/Help_Spanish/Topics/opt-vo11.xml
deleted file mode 100644
index d4a76056d1..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo11.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- -vo11
-
- -vo11
-
-
-
- -vo11Compatible numeric conversions
-
- The -vo11 option enables Visual Objects compatible arithmetic conversions.
- Syntax
- -vo11[+|-]
- Arguments
- + | - Specifying +, or just -vo11, directs the compiler to emit code that performs arithmetic conversions that are compatible with Visual Objects.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- // using default or /vo11- FUNCTION Start() ASVOID LOCAL f ASFLOAT
f := 1.6 ? (INT)f // 1 (rounding towards zero)
f := 1.5 ? (INT)f // 1 (rounding towards zero)
f := 2.5 // 2 (rounding towards zero) ? (INT)f
f := 3.5 // 3 (rounding towards zero) ? (INT)f
RETURN
// using /vo11 or /vo11+ FUNCTION Start() ASVOID LOCAL f ASFLOAT
f := 1.6 ? (INT)f // 2 (rounding towards closest integer)
f := 1.5 ? (INT)f // 2 (rounding towards closest even integer)
f := 2.5 ? (INT)f // 2 (rounding towards closest even integer)
f := 3.5 ? (INT)f // 4 (rounding towards closest even integer)
RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo12.xml b/docs/Help_Spanish/Topics/opt-vo12.xml
deleted file mode 100644
index cd8d039f4a..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo12.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- -vo12
-
- -vo12
-
-
-
- -vo12Clipper Compatible integer divisions
-
- The -vo12 option enables Clipper compatible integer divisions.
- Syntax
- -vo12[+|-]
- Arguments
- + | - Specifying +, or just -vo12, directs the compiler to emit code that performs Clipper-compatible integer divisions.
- Remarks
- When the -vo12 option is enabled and both operands of the - (division) operator are integral values, both operands are converted to USUAL, and the return type is USUAL. The return value contained in the USUAL is:
-
-
-
INT64 (UsualType() == 22), if one or both operands are greater than Int32.MaxValue and the remainder of the division is zero.
-
INT (UsualType() == 1), if one or both operands are INT or a smaller integral type and the remainder of the division is zero.
-
FLOAT (UsualType() == 3), if one or both operands are INT or a smaller integral type and the remainder of the division is not zero.
-
-
- The -vo12 option is enabled in projects created by the Transporter if the Compiler->Clipper Compatiblity->Integer Divisions option was enabled for the project in Visual Objects.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo13.xml b/docs/Help_Spanish/Topics/opt-vo13.xml
deleted file mode 100644
index e3a8fd4764..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo13.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- -vo13
-
- -vo13
-
-
-
- -vo13Compatible String Comparisons
-
- The -vo13 option enables VO compatible string comparisons.
- Syntax
- -vo13[+|-]
- Arguments
- + | - Specifying +, or just -vo13, tells the compiler that string comparisons are to be performed the same way as they are in VO, and in the RDDs, where the comparison depends on the SetCollation() setting. When - is specified, or -vo13 is not specified, string comparisons in code use String.Compare().
- Remarks
- When this option is enabled, string comparisions are compatible with VO and the RDDs, and depend on SetCollation() as follows:
-
- When collation=#WINDOWS, string comparisons make use of services provided by Windows that automatically handle foreign character sets. These string comparisons are implemented with a call to CompareStringA() function in kernel32.dll.
-
- When collation = #CLIPPER, comparisons are performed byte by byte, using a weight table for each char. As in VO, a different table can be selected with the SetNatDll() function. In .Net we are using the runtime DLL for the weight tables. In the runtime the nation DLLs are not physically implemented as separate files; the weighting tables are embedded as resources inside XSharp.Core.dll.
-
- When collation = #Unicode, the comparisons will be done with the normal String.Compare() routine that uses the current culture.
-
- When collation = #Ordinal, the comparisons will be done with the normal String.Compare() routine using an ordinal comparison (this is the fastest)
-
- When -v013 is not enabled, string comparisons are performed using String.Compare(), where the comparison makes use of culture-sensitive sort rules according to the current culture selected.
-
- The setting for -vo13 is registered with the runtime by the main application at startup. If your library is compiled with -vo13+ but the main app is not, the string comparisons that are called from the library will follow the same rules as the main app, because the main app registers -vo13 setting with the runtime and the stringcomparison routines in the runtime now detect that the main app does not want to do VO compatible string comparisons. Therefore, we recommend that third party products always enable -vo13.
- Compatibility Note:
- When using -vo13, string comparisons involve converting unicode strings to ansi for compatibility and consequently are slower than with String.Compare().
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo14.xml b/docs/Help_Spanish/Topics/opt-vo14.xml
deleted file mode 100644
index 16939888d8..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo14.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- -vo14
-
- -vo14
-
-
-
- -vo14:Use Float Literals
-
- The -vo14 option enables VO compatible handling of floating point literal numbers.
- Syntax
- -vo14[+|-]
- Arguments
- + | - Specifying +, or just -vo14, tells the compiler treat floating point literal numbers (for example: 123.456) as FLOAT data type, instead of as REAL8 (System.Double), which is the default.
- Remarks
- When this option is enabled, floating point literal numbers are treated by the compiler as FLOAT values, for compatibility with existing Visual Objects code. This option is enabled by default in transported projects.
-
- For new code, it is strongly recommended not to enable this compiler option, as it generates less efficient code. For example, for the following code:
-
- LOCAL r := 3.0 ASREAL8 r := r * 4.5 + r + 5.5
-
- if -vo14 is enabled, the compiler treats the "1.0", "1.5" and "2.5" values as numbers of type FLOAT, causing the whole calculation to be made on FLOAT values and the result is at the end converted to REAL8, before it is finally stored to the local variable. FLOAT is a special data type defined in the runtime and is significantly slower than the REAL8 (System.Decimal) data type, which maps directly to a (mathematic) processor registry. Disabling the -vo14 option would cause the above code to execute faster by a large factor.
-
- Note that by using the "d" or "s" suffix, as in 123.456d and 123.456s, the REAL8 or REAL4 data type is being enforced on a literal number, no matter if -vo14 is enabled or disabled. See Literals for more information.
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo15.xml b/docs/Help_Spanish/Topics/opt-vo15.xml
deleted file mode 100644
index e65f145641..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo15.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- -vo15
-
- -vo15
-
-
-
- -vo15: Allow untyped Locals and return types
-
- This compiler option allows you to control what the compiler will do with local variables, parameters and return types without type specification.
- The default is -vo15+ for the VO and Vulcan dialects. For the Core dialect the default is -vo15-.
- Syntax
- -vo15[+|-]
- Arguments
- + | - Specifying +, or just -vo15, tells the compiler to treat untyped locals and return types as USUAL
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- FUNCTION LongSquare(nLong asLONG) -/ Note that the return type is missing
RETURN nLong * nLong
-
- In VO/Vulcan mode, this will, by default, generate a method with a USUAL return type. In Core mode, this will not compile, but produce a "Missing Type" error (XS1031).
-
- When you compile with -vo15-, this will also produce an error.
-
- Similar code that will be influenced by this compiler option:
-
- FUNCTION MultiplyLong(nParam1 asLONG, nParam2) ASLONG -/ Note that the type for nParam2 is missing RETURN nParam1 * nParam2
- And:
- FUNCTION Tomorrow() ASDate LOCAL dToday := Today() -/ Note that the ASDATEis missing RETURN dToday + 1
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo16.xml b/docs/Help_Spanish/Topics/opt-vo16.xml
deleted file mode 100644
index b46df1d0cd..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo16.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- -vo16
-
- -vo16
-
-
-
- -vo16
-
- Automatically generate Clipper calling convention constructors for classes without constructor.
- Syntax
- -vo16[+|-]
- Arguments
- + | - Specifying +, or just -vo16, tells the compiler to automatically generate constructors with the same signature as the constructors of the parent class.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
CLASS ControlEvent INHERITEvent ENDCLASS
-
- In the code above the compiler would generate a constructor for the ControlEvent class. This constructor will pass all the parameters to the constructor of the Event class.
-
- The generated constructor would look as follows:
-
- CONSTRUCTOR(_hWnd, _uMsg, _wParam, _lParam, _oWindow) SUPER(_hWnd, _uMsg, _wParam, _lParam, _oWindow)
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo17.xml b/docs/Help_Spanish/Topics/opt-vo17.xml
deleted file mode 100644
index 9c1ba7087e..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo17.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- -vo17
-
- -vo17
-
-
-
- -vo17
-
- Generate code to fully implement the VO compatible BEGIN SEQUENCE .. END SEQUENCE.
- The compiler generates calls to the runtime functions _SequenceError and _SequenceRecover that you may override in your own code.
- -vo17[+|-]
- Arguments
- + | - Specifying +, or just -vo17, tells the compiler to automatically generate constructors with the same signature as the constructors of the parent class.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
- The generated code by the compiler will call two runtime functions to allow you to adjust the behavior of the BEGIN SEQUENCE .. END SEQUENCE handling.
-
- The default implementation of these functions is in the XSharp Runtime:
- /// <summary> /// This function is automatically inserted by the compiler in a RECOVER USING block and gets called when the /// RECOVER USING block is reached because of an exception. /// </summary> /// <param name="e">The exception that triggered the jump into the RECOVER USING block</param> /// <remarks> /// The default implementation of this function (in the XSharp.RT assembly) called the installed error handler /// that is installed with ErrorBlock() /// The function should then have the following prototype /// <code language="X#"> /// FUNCTION _SequenceError(e as Exception) AS VOID /// </code> /// </remarks> /// <returns>The result of the call to the error handler installed in the ErrorBlock</returns> /// <seelso cref='O:XSharp.RT.Functions._Break'>Break Function</seealso> /// <seelso cref='O:XSharp.RT.Functions.ErrorBlock'>Break Function</seealso> FUNCTION _SequenceError(e as Exception) ASUSUAL LOCAL error as XSharp.Error IF e IS XSharp.Error VAR err error := err ELSE error := Error{e} ENDIF RETURN Eval(ErrorBlock(), error) /// <summary> /// This function is automatically inserted by the compiler in a compiler generated /// RECOVER USING block when you have a BEGIN SEQUENCE .. END SEQUENCE in your code /// without RECOVER USING clause /// </summary> /// <param name="u">The parameter that was passed in the BREAK statement or the call to the _Break function</param> /// <remarks>If a REAL exception occurs then this function is NOT called. The function is only called when /// the (generated) RECOVER USING block is called with a value from a BREAK statement. <br /> /// The default implementation of this function (in the XSharp.RT assembly) does nothing. /// You can override this function in your own code if you want. /// The function should then have the following prototype /// <code language="X#"> /// FUNCTION _SequenceRecover(u as USUAL) AS VOID /// </code> /// </remarks> /// <seelso cref='O:XSharp.RT.Functions._Break'>Break Function</seealso> FUNCTION _SequenceRecover(u asUSUAL) ASVOID RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo2.xml b/docs/Help_Spanish/Topics/opt-vo2.xml
deleted file mode 100644
index cfe617b1a6..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo2.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- -vo2
-
- -vo2
-
-
-
- -vo2Initialize strings
-
- The -vo2 option directs the compiler to initialize all variables and fields of type STRING (System.String) and all elements of DIM ... AS STRING arrays to an empty string (/vo2[+|-]).
- Syntax
- -vo2[+ | -]
- Arguments
- + | - Specifying +, or just -vo2, directs the compiler to initialize all variables and fields of type STRING and all elements of DIM ... AS STRING arrays to an empty string (String.Empty).
- Remarks
- By default, this option is disabled, and all locals, globals, fields and array elements of type STRING have an initial value of NULL, which is the default initial value for any local, global, field or array element that contains a reference type.
-
- Generally, you will initialize a string variable to a specific value before it is used, and initializing it to an empty string would incur unnecessary overhead. In addition, it is inconsistent with the behavior of all other reference types, which have an initial value of NULL. However, this may break existing Visual Objects code that relies on Visual Object's behavior of initializing string variables to a string with zero characters.
-
- When this option is not used, you may test for an empty string variable, field or array element by comparing it against NULL. When this option is enabled, you may test for an empty string variable, field or array element by comparing it against "" or String.Empty, or testing that its length equals zero. System.String.IsNullOrEmpty() may also be used to test whether a string variable contains NULL or a valid string with zero characters.
-
- Also note that the predefined constant NULL_STRING is normally equivalent to NULL, but when -vo2 is used, NULL_STRING is equivalent to "" (a zero-length string).
-
- Compatibility Note:
- -vo2 does not initialize STRING fields in structures. Since structures do not have default constructors, structure fields cannot have initializer expressions. Although this is not a compatibility issue since you cannot create structures (value types) in Visual Objects, it is something to keep in mind if you use structures in an application that uses -vo2.
-
- Note that the use of the term "structure" here refers to STRUCTURE in X#, not STRUCTURE in Visual Objects, which has been renamed VOSTRUCT in X#. -vo2 has no effect on VOSTRUCT since you cannot declare fields that are reference types in a VOSTRUCT.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- // using default or /vo2- FUNCTION Start() ASVOID LOCAL s ASSTRING ? s == NULL// true ? s == "" // false ? s == String.Empty // false ? Len(a) // runtime error - NullReferenceException ? a:Length // runtime error - NullReferenceException ? String.IsNullOrEmpty(a) // true RETURN
- // using /vo2 or /vo2+ FUNCTION Start() ASVOID LOCAL s ASSTRING// this compiles as 'LOCAL s := "" AS STRING' ? s == NULL// false ? s == "" // true ? s == String.Empty // true ? Len(a) // 0 ? a:Length // 0 ? String.IsNullOrEmpty(a) // true RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo3.xml b/docs/Help_Spanish/Topics/opt-vo3.xml
deleted file mode 100644
index b755d86445..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo3.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
- -vo3
-
- -vo3
-
-
-
- -vo3All instance methods virtual
-
- The -vo3 option directs the compiler to treat all methods (including ACCESS and ASSIGN methods) as virtual.
- Syntax
- -vo3[+|-]
- Arguments
- + | - Specifying +, or just -vo3, directs the compiler to treat all methods (including ACCESS and ASSIGN methods) as virtual, regardless of whether the VIRTUAL modifier is used or not. This provides compatibility with the Visual Objects inheritance model.
- Remarks
-
- A class method may always be explicitly declared as a virtual method by using the VIRTUAL keyword, regardless of whether -vo3 is used or not.
-
- For performance reasons, this option is disabled by default. Virtual methods incur a slight performance penalty since the actual method implementation that is called cannot be determined until run-time, and depends on the run-time type of the instance on which the invocation takes place. In contrast, calls to non-virtual members can be fully resolved at compile time, and the call is always made to the compile-time type of the instance.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- CLASS BaseClass METHOD WhoAmI() ASSTRING RETURN "BaseClass" ENDCLASS
CLASS DerivedClass INHERIT BaseClass METHOD WhoAmI() ASSTRING RETURN "DerivedClass" ENDCLASS
FUNCTION Start() ASVOID LOCAL c AS BaseClass c := DerivedClass{} ? c:WhoAmI() RETURN
// Output using default or /vo3-: BaseClass // Output using /vo3 or /vo3+: DerivedClass
-
-
- When the -vo3 switch is not used, the call to 'c:WhoAmI()' always resolves to the implementation in BaseClass, since the variable 'c' is typed as 'BaseClass' and 'BaseClass.WhoAmI' is a non-virtual method.
-
- When the -vo3 switch is used, the call to 'c:WhoAmI()' resolves to the implementation in 'DerivedClass'. Even though the variable 'c' is typed as 'BaseClass', the actual type of the instance stored in 'c' at runtime determines what implementation of 'WhoAmI' to invoke since 'BaseClass.WhoAmI' is a virtual method.
-
- The same behavior without using -vo3 could be obtained by doing:
-
- VIRTUAL METHOD WhoAmI() AS STRING CLASS BaseClass ...
-
- This is preferable over using -vo3 since you have explicit control over which methods are virtual or not, and no unnecessary overhead is incurred where virtual inheritance is not required. However, existing Visual Objects code may not work properly without -vo3, and it may not be practical to modify existing code and add the VIRTUAL keyword to those methods that really need it.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo4.xml b/docs/Help_Spanish/Topics/opt-vo4.xml
deleted file mode 100644
index 25f1ee6057..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo4.xml
+++ /dev/null
@@ -1,131 +0,0 @@
-
-
-
- -vo4
-
- -vo4
-
-
-
- -vo4Implicit numeric conversions
-
- The -vo4 option directs the compiler to implicitly convert numeric types from larger types to smaller types, as well as from fractional types to integral types.
- Syntax
- -vo4[+|-]
- Arguments
- + | - Specifying +, or just -vo4, directs the compiler to implicitly convert signed integer values to/from unsigned values, and larger integer types to smaller integer types. This provides compatibility with Visual Objects, which permits such conversions without an explicit cast or conversion operator.
- Remarks
- For safety reasons, this option is disabled by default. Implicitly converting between signed and unsigned integer types or between larger to smaller integer types can cause numeric overflow errors at runtime or unintended values to be passed depending on whether overflow checking is enabled or disabled. By default, you must explicitly cast a signed integer to its unsigned counterpart, as well as cast larger integer types to smaller ones. By explicitly doing so, it is assumed that the programmer is aware the conversion is safe.
-
- When this option is enabled, the compiler will implicitly convert the data types listed in the table below:
-
-
-
-
- From
-
-
- To
-
-
-
-
- SByte
-
-
- BYTE, WORD, Char, DWORD
-
-
-
-
- SHORT
-
-
- BYTE, SByte, WORD, Char, DWORD
-
-
-
-
- INT
-
-
- BYTE, SByte, WORD, SHORT, Char, DWORD
-
-
-
-
- INT64
-
-
- BYTE, SByte, WORD, SHORT, Char, INT, DWORD, UINT64
-
-
-
-
- BYTE
-
-
- SByte
-
-
-
-
- WORD
-
-
- SByte, BYTE, SHORT, Char, INT
-
-
-
-
- DWORD
-
-
- SByte, BYTE, WORD, SHORT, INT
-
-
-
-
- UINT64
-
-
- SByte, BYTE, WORD, SHORT, Char, INT, DWORD, INT64
-
-
-
-
- REAL8, REAL4, DECIMAL
-
-
- All other numeric types
-
-
-
-
- FLOAT, CURRENCY
-
-
- All other numeric types
-
-
-
-
- For each conversion, the compiler will raise an appropriate warning. You may disable the warning with the -wx switch, or insert an explicit cast in the source code to eliminate the warning.
-
- It is strongly recommended that you do not use this compiler option in new code. All of the conversions listed in the table above have the ability to lose data or return incorrect values, since the range of values in the source data type cannot be represented in the target data type.
-
- For example, an INT containing a negative number cannot be represented in a DWORD. Similarly, an INT greater than 65535 cannot be represented in a SHORT. If you must mix signed and unsigned types or pass a larger type to a smaller type, you should always supply an explicit cast rather than using -vo4. This will document the fact that the conversion is known to be safe, and it will not suppress compile time errors if incompatible integer types are unintentionally used.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- FUNCTION Start() ASVOID LOCAL dw := 4294967296 ASDWORD LOCAL i := -1 ASINT
DWORD_Function( i ) // no error if compiled with /vo4 INT_Function( dw ) // no error if compiled with /vo4 RETURN
FUNCTION DWORD_Function( x ASDWORD ) ASVOID ? x RETURN
FUNCTION INT_Function( x ASINT ) ASVOID ? x RETURN
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo5.xml b/docs/Help_Spanish/Topics/opt-vo5.xml
deleted file mode 100644
index 76c1d16328..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo5.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
- -vo5
-
- -vo5
-
-
-
- -vo5Implicit CLIPPER calling convention
-
- The -vo5 option directs the compiler to implicitly use the CLIPPER calling convention for functions declared with zero-arguments and no explicit calling convention.
- Syntax
- -vo5[+|-]
- Arguments
- + | - Specifying +, or just -vo5, directs the compiler to implicitly use the CLIPPER calling convention for functions, methods and constructors that are declared with zero arguments and no explicit calling convention.
- Remarks
- For compatibility with Clipper, Visual Objects uses the CLIPPER calling convention for all functions and methods that are declared with zero arguments and no explicit calling convention. The STRICT keyword may be used to override the default, and cause the function to use the STRICT calling convention.
-
- However, in the vast majority of cases, parameters are never passed to functions and methods declared with zero arguments, and using the CLIPPER calling convention by default incurs unnecessary overhead not only in the function itself, but at every call site. In addition, the CLIPPER calling convention allows any number and type of arguments to be passed, preventing compile time error checking.
-
- In X#, functions and methods declared with zero arguments are compiled with the STRICT calling convention by default, unless the CLIPPER keyword is explicitly specified. This behavior is the exact opposite of Visual Objects, but results in more efficient code as well as compile time error checking. Passing any arguments to a function declared to accept zero arguments will raise a compile-time error.
-
- However, this can cause compatibility issues in code originally written in Visual Objects. The -vo5 compiler option reverses the default behavior of X# with regard to zero argument functions, so that the behavior is identical to Visual Objects.
-
- Regardless of whether this option is enabled or not, the CLIPPER and STRICT keywords can always be used to explicitly specify the desired calling convention.
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- FUNCTION foo() // CLIPPER ? pcount(), _getFParam( 1 ) RETURN
FUNCTION Start() ASVOID foo( 1 ) RETURN
-
- The above example will compile and run correctly if -vo5 is used, or if the CLIPPER keyword is added at the end of the FUNCTION foo() declaration. Otherwise, a compiler error will be generated on the call to foo(), as well as on the calls to pcount() and _getFParam() (which are illegal in a STRICT calling convention function).
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo6.xml b/docs/Help_Spanish/Topics/opt-vo6.xml
deleted file mode 100644
index 723c989642..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo6.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- -vo6
-
- -vo6
-
-
-
- -vo6Implicit pointer conversions
-
- The -vo6 option directs the compiler to resolve typed function pointers to PTR.
- Syntax
- -vo6[+|-]
- Arguments
- + | - Specifying +, or just -vo6, directs the compiler to resolve pointers that would resolve to typed function pointers in Visual Objects to PTR.
- Remarks
- X# does not support typed function pointers. Existing Visual Objects code that declares typed function pointers will not compile in X#, unless the type is changed to PTR or IntPtr.
-
- If this option is enabled and a pointer type cannot be resolved, the compiler will attempt to locate a function with the same name as the pointer type (without "PTR"). If found, the compiler will resolve the type to PTR. This allows existing Visual Objects code to be compiled without modification, at least as far as the variable declaration is concerned.
-
- The pointer type may be used as an argument to CCallNative(), PCallNative() or CallManaged(), depending on the type of function the pointer points to.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- The following code is valid in Visual Objects, but will not compile in X# unless -vo6 is used.
- FUNCTION foo( x ASINT ) ASVOID RETURN
GLOBAL pFoo AS foo PTR
- Using /vo6 has the same effect as if the GLOBAL declaration were rewritten as:
- GLOBAL pFoo ASPTR
-
-
- Using -vo6 has the same effect as if the GLOBAL declaration were rewritten as:
-
-
- GLOBAL pFoo AS PTR
-
- Note that PTR does not have the same semantics as typed function pointers in Visual Objects. However, typed function pointers are primarily used as arguments to CALL(), CCALL() and PCALL() in Visual Objects, which are not supported in X#. They have been replaced with CCallNative(), PCallNative() and CallManaged(), which accept IntPtr arguments. Therefore, the same end result (invoking a function indirectly through a pointer) is possible in X# without typed function pointers.
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo7.xml b/docs/Help_Spanish/Topics/opt-vo7.xml
deleted file mode 100644
index c5a12e53b9..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo7.xml
+++ /dev/null
@@ -1,126 +0,0 @@
-
-
-
- -vo7
-
- -vo7
-
-
-
- -vo7Implicit casts and conversions
-
- The -vo7 option directs the compiler to allow implicit casts and conversions that are allowed in Visual Objects but which would normally be illegal or require an explicit cast in X#.
- Syntax
- -vo7[+|-]
- Arguments
- + | - Specifying +, or just -vo7, directs the compiler to allow certain implicit casts and conversions that are allowed in Visual Objects.
- Remarks
- Visual Objects allows implicit casts between types with different semantics, whereas X# normally requires explicit casts in such cases.
-
- For example, Visual Objects allows implicit conversions between integer types and pointer types. While pointers are integers, they have different semantics. Integers are numerical values and pointers are addresses representing memory locations. In addition to the difference in semantics, the size of a pointer dependson the underlying platform, while the size of an integer does not change from platform to platform (with the exception of System.IntPtr).
-
- While is it possible (and often necessary) to cast between types with different semantics, this should always be done via an explicit cast. This not only ensures that the correct conversion code is generated (if necessary), it also self-documents the fact that you are casting one type to another type with a different meaning.
-
- X# supports most of the casts that Visual Objects supports, but in cases where the types have different semantics, an explicit cast is usually required. However, this can cause a large number of compiler errors in existing Visual Objects code.
-
- Using -vo7 allows the following conversions to be performed implicitly, allowing existing Visual Objects code to compile:
-
-
-
-
- From
-
-
- To
-
-
- Operation Performed
-
-
-
-
- PTR
-
-
- strongly typed PTR (e.g. INT PTR)
-
-
- None, the types are binary compatible. However, the code may fail at runtime if the data the pointer references is not of the correct type.
-
-
-
-
- INT or DWORD
-
-
- strongly typed PTR (e.g. INT PTR)
-
-
- None, the types are binary compatible. However, the code may fail at runtime if the data the pointer references is not of the correct type. Note that this conversion is only allowed when the target platform is set to x86.
-
-
-
-
- INT64 or UINT64
-
-
- strongly typed PTR (e.g. INT PTR)
-
-
- None, the types are binary compatible. However, the code may fail at runtime if the data the pointer references is not of the correct type. Note that this conversion is only allowed when the target platform is set to x64 or Itanium.
-
-
-
-
- OBJECT
-
-
- any other reference type
-
-
- Compiler inserts an explicit cast to the target type, which may fail at runtime.
-
-
-
-
- type PTR
-
-
- REF type
-
-
- The compiler converts the pointer into a reference. Note that even with -vo7, not all pointers can be converted to references or else it would compromise the integrity of the garbage collector.
-
-
-
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
- Example
- The following code is valid in Visual Objects, but will not compile in X# unless -vo7 is used, because CreateObject() returns OBJECT. There is no implicit conversion from OBJECT to a more derived type, because such a conversion cannot be guaranteed to be safe, while implicit conversions are always safe.
-
- CLASS foo ... ENDCLASS
FUNCTION Start() ASVOID LOCAL f AS foo LOCAL s ASSYMBOL s := #foo f := CreateObject( s ) // no implicit conversion from 'OBJECT' to 'foo' RETURN
-
- Using -vo7 has the same effect as if the assignment into f were rewritten as:
-
- f := (foo) CreateObject( s )
-
- In either case, the resulting code is exactly the same, and the cast to foo may fail at runtime. However, the explicit cast self-documents that you expect the return from CreateObject() to contain an instance of foo.
-
- The following example is also valid in Visual Objects, but will not compile in X# unless -vo7 is used, because the @ operator returns the address of its operand (a typed pointer) and pointers are not the same as references in X#:
-
- LOCAL x ASINT ByRef( @x )
...
FUNCTION ByRef( i REFINT ) ASVOID i := 5 RETURN
-
- The -vo7 option will automatically convert @x, which resolves to type INT PTR, into REF INT which is compatible with the function parameter. However, it is recommended that you remove the @ operator rather than use -vo7 for this purpose.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo8.xml b/docs/Help_Spanish/Topics/opt-vo8.xml
deleted file mode 100644
index 4c56d7b2f4..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo8.xml
+++ /dev/null
@@ -1,78 +0,0 @@
-
-
-
- -vo8
-
- -vo8
-
-
-
- -vo8Compatible preprocessor
-
- The -vo8 option enables Visual-Objects compatible preprocessor behavior.
- Syntax
- -vo8[+|-]
- Arguments
- + | - Specifying +, or just -vo8, changes certain aspects of the preprocessor to behave like Visual Objects.
- Remarks
- Unlike Visual Objects, X# uses a file-based preprocessor which has characteristics of traditional preprocessors in languages such as C, C++ and Clipper. The -vo8 option controls the following behaviors:
-
-
-
Case Sensitivity
-
- In a traditional preprocessor, #define foo 1 and #define FOO 2 declare two separate preprocessor symbols, because preprocessor symbols are case-sensitive.
-
- However, in Visual Objects, DEFINE foo := 1 and DEFINE FOO := 2 declare the same entity (and would cause a compiler error because of the duplicate entity declaration).
-
- In X#, by default, that is when -vo8 is disabled (not used or specified with "-vo8-"), preprocessor symbols are always case sensitive. When -vo8 is enabled, the case sensitivity of symbols is decided by the state of the -cs option:
-
-
when -cs is enabled, which makes the compiler treat all identifiers and type names as case-sensitive, preprocessor symbols are still case-sensitive as well.
-
when -cs is disabled, preprocessor symbols are case-insensitive and behave in the same way as in VO.
-
-
- So, when -vo8 is enabled and -cs is disabled, #define foo 1 and #define FOO 2 declare the same preprocessor symbol (and would cause a compiler warning because of the redefinition).
-
- The following code is valid in Visual Objects:
-
- DEFINE foo := "bar" ? Foo // "bar"
-
- but the following code would raise an unknown variable error on ? Foo because the X# preprocessor is case-sensitive by default:
-
- #define foo "bar" ? Foo
-
-
- Using The -vo8 (but not the -cs) option will allow the above example to compile. An alternative to using -vo8 is to modify the code so that the case of the text you want to replace matches the case used in #define.
-
-
-
#ifdef
-
-
- In a traditional preprocessor, code within a #ifdef ... #endif (or #else) block is compiled if the symbol after #ifdef is defined. It does not matter what the symbol resolves to, if it resolves to anything at all.
-
- In Visual Objects, code within a #ifdef ... #endif (or #else) block is compiled only if the symbol after #ifdef is defined, and it resolves to an expression which resolves to a logical TRUE value. In the example below, the code will print "in #else":
-
- DEFINE foo := FALSE
#ifdef foo ? "in #ifdef #else ? "in #else" // <- this code is compiled in Visual Objects #endif
-
- whereas the equivalent code in X# would print "in #ifdef":
- DEFINE foo := FALSE
#ifdef foo ? "in #ifdef // <- this code is compiled in Vulcan.NET #else ? "in #else" #endif
-
-
- When -vo8 is used, the X# preprocessor examines the value of the preprocessor symbol to determine if the symbol resolves to a logical TRUE or FALSE value. However, the X# preprocessor does not evaluate preprocessor expressions, whereas Visual Objects does. Even with -vo8 enabled, the preprocessor symbol must resolve to a single expression containing TRUE or FALSE (case-insensitive) or a numerical value.
- Numerical values of 0 resolve to FALSE and all non-zero numbers resolve to TRUE. Preprocessor symbols that resolve to expressions are not evaluated and effectively resolve to FALSE.
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- // For the purposes of #ifdef...
// these resolve to FALSE: #define foo FALSE #define foo 0
// these resolve to TRUE: #define foo True #define foo 1 #define foo -567
// these are not processed and effectively resolve to FALSE // and therefore are incompatible with Visual Objects: #define foo TRUE .AND. TRUE #define foo TRUE .OR. TRUE #define foo 1 * 2
-
- Tip: The -ppo option is useful for debugging the output generated by the preprocessor.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-vo9.xml b/docs/Help_Spanish/Topics/opt-vo9.xml
deleted file mode 100644
index 74a82fb5d9..0000000000
--- a/docs/Help_Spanish/Topics/opt-vo9.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- -vo9
-
- -vo9
-
-
-
- -vo9Handle problems with incorrect or missing return statements
-
- The -vo9 option prevents the compiler from raising error XS0161 when a function or method does not have any RETURN statements. It also fixes problems with incorrect return values.
- Syntax
- -vo9[+|-]
- Arguments
- + | - Specifying +, or just -vo9, allows functions and methods that do not have any RETURN statement to compile without raising an error.
- Remarks
- Visual Objects allows functions and methods whose return type is not VOID to omit RETURN statements. The return value from any such functions or methods will always be the default value for the return type.
-
- This is illegal in X#: all functions and methods must explicitly return a value unless the return type is VOID. However, this may prevent code that was originally written in Visual Objects from compiling in X#.
-
- If -vo9 is enabled, any non-void functions or methods that do not have any RETURN statements will raise warning XS9025 instead of error XS0106. The warning may be disabled if desired, but it is strongly recommended that you fix the code in question. If the return value is never used, then type the function or method AS VOID. Otherwise, add a RETURN statement with an appropriate return value.
- This compiler option also checks for methods/functions that have a return statement without value. In that case a warning XS9026 is shown. The final check this compiler option does is for methods that have a return value but are not expected to return anything. If that is found then a warning XS9032 is shown.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
- Example
- FUNCTION x( y ) ? y
METHOD x( y ASINT ) ASINT ? y
- In the first example, the return type is not specified, so it defaults to USUAL. Since there is no RETURN statement, the function will always return NIL (the default value for USUAL) in Visual Objects. In the second example, since there is no RETURN statement, the method will always return zero (the default value for INT) in Visual Objects.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-w.xml b/docs/Help_Spanish/Topics/opt-w.xml
deleted file mode 100644
index e90682bf31..0000000000
--- a/docs/Help_Spanish/Topics/opt-w.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
-
- -w
-
- -w
-
-
-
- -w
-
- The -w compiler option is an alias for the -nowarn command line option for compatibility.
-
-
diff --git a/docs/Help_Spanish/Topics/opt-warn.xml b/docs/Help_Spanish/Topics/opt-warn.xml
deleted file mode 100644
index 23b05ff672..0000000000
--- a/docs/Help_Spanish/Topics/opt-warn.xml
+++ /dev/null
@@ -1,92 +0,0 @@
-
-
-
- -warn
-
- -warn
-
-
-
- -warn
-
- The -warn option specifies the warning level for the compiler to display.
- Syntax
- -warn:option
- Arguments
- optionThe warning level you want displayed for the compilation: lower numbers show only high severity warnings; higher numbers show more warnings. Valid values are 0-4:
-
-
-
-
- Warning level
-
-
- Meaning
-
-
-
-
- 0
-
-
- Turns off emission of all warning messages.
-
-
-
-
- 1
-
-
- Displays severe warning messages
-
-
-
-
- 2
-
-
- Displays level 1 warnings plus certain, less-severe warnings, such as warnings about hiding class members.
-
-
-
-
- 3
-
-
- Displays level 2 warnings plus certain, less-severe warnings, such as warnings about expressions that always evaluate to true or false.
-
-
-
-
- 4 (the default)
-
-
- Displays all level 3 warnings plus informational warnings.
-
-
-
- Remarks
-
- To get information about an error or warning, you can look up the error code in the Help Index. For other ways to get information about an error or warning, see X# Compiler Errors.
-
- Use -warnaserror to treat all warnings as errors. Use -nowarn to disable certain warnings.
-
- -w is the short form of -warn.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Build property page.
-
Modify the Warning Level property.
-
Click here to see the property page.
-
-
- For information on how to set this compiler option programmatically, see WarningLevel.
- Example
- Compile in.prg and have the compiler only display level 1 warnings:
-
-
- xsc -warn:1 in.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-warnaserror.xml b/docs/Help_Spanish/Topics/opt-warnaserror.xml
deleted file mode 100644
index 2027fc5ccc..0000000000
--- a/docs/Help_Spanish/Topics/opt-warnaserror.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- -warnaserror
-
- -warnaserror
-
-
-
- -warnaserror
-
- The -warnaserror+ option treats all warnings as errors.
- Syntax
- -warnaserror[+|-][:warning-list]
- Remarks
- Any messages that would ordinarily be reported as warnings are instead reported as errors, and the build process is halted, meaning no output files are built.
-
- By default, -warnaserror- is in effect, which causes warnings to not prevent the generation of an output file. -warnaserror, which is the same as -warnaserror+, causes warnings to be treated as errors.
-
- Optionally, if you want only a few specific warnings to be treated as errors, you may specify a comma-separated list of warning numbers to treat as errors.
-
- Use -warn to specify the level of warnings that you want the compiler to display. Use -nowarn to disable certain warnings.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties page.
-
Click the Build property page.
-
Modify the "Warnings As Errors" property.
-
Click here to see the property page.
-
- Example
- Compile in.prg and have the compiler display no warnings:
-
- xsc -warnaserror in.prg xsc -warnaserror:642,649,652 in.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-win32icon.xml b/docs/Help_Spanish/Topics/opt-win32icon.xml
deleted file mode 100644
index a6a41b0dcd..0000000000
--- a/docs/Help_Spanish/Topics/opt-win32icon.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- -win32icon
-
- -win32icon
-
-
-
- -win32icon
-
- The -win32icon option inserts an .ico file in the output file, which gives the output file the desired appearance in the File Explorer.
- Syntax
- -win32icon:filename
- Arguments
- filenameThe .ico file that you want to add to your output file.
- Remarks
- An .ico file can be created with the Resource Compiler. The Resource Compiler is invoked when you compile a Visual C++ program; an .ico file is created from the .rc file.
-
- See -linkresource (to reference) or -resource (to attach) a .NET Framework resource file. See -win32res to import a .res file.
-
- To set this compiler option in the Visual Studio development environment:
-
-
Open the project's Properties pages.
-
Click the Application property page.
-
Modify the Application icon property.
-
Click here to see the property page.
-
-
- Example
- Compile in.prg and attach an .ico file rf.ico to produce in.exe:
-
-
- xsc -win32icon:rf.ico in.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-win32manifest.xml b/docs/Help_Spanish/Topics/opt-win32manifest.xml
deleted file mode 100644
index efa1e3055c..0000000000
--- a/docs/Help_Spanish/Topics/opt-win32manifest.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- -win32manifest
-
- -win32manifest
-
-
-
- -win32manifest
-
- Use the -win32manifest option to specify a user-defined Win32 application manifest file to be embedded into a project's portable executable (PE) file.
- Syntax
- -win32manifest: filename
- Arguments
- filenameThe name and location of the custom manifest file.
- Remarks
- By default, the X# compiler embeds an application manifest that specifies a requested execution level of "asInvoker." It creates the manifest in the same folder in which the executable is built, which is typically the bin\Debug or bin\Release folder when you use Visual Studio. If you want to supply a custom manifest, for example to specify a requested execution level of "highestAvailable" or "requireAdministrator," use this option to specify the name of the file.
- Note
- This option and the -win32res option are mutually exclusive. If you try to use both options in the same command line you will get a build error.
- An application that has no application manifest that specifies a requested execution level will be subject to file/registry virtualization under the User Account Control feature in Windows Vista.
- Your application will be subject to virtualization if either of these conditions is true:
-
-
-
You use the -nowin32manifest option and you do not provide a manifest in a later build step or as part of a Windows Resource (.res) file by using the -win32res option.
-
You provide a custom manifest that does not specify a requested execution level.
-
-
- Visual Studio creates a default .manifest file and stores it in the debug and release directories alongside the executable file. You can add a custom manifest by creating one in any text editor and then adding the file to the project. Alternatively, you can right-click the Project icon in Solution Explorer, click Add New Item, and then click Application Manifest File. After you have added your new or existing manifest file, it will appear in the Manifest drop down list.
-
- You can provide the application manifest as a custom post-build step or as part of a Win32 resource file by using the -nowin32manifest option. Use that same option if you want your application to be subject to file or registry virtualization on Windows Vista. This will prevent the compiler from creating and embedding a default manifest in the portable executable (PE) file.
- Example
- The example below shows the default manifest that the X# compiler inserts into a PE.
-
- Note: The compiler inserts a standard application name " MyApplication.app " into the xml. This is a workaround to enable applications to run on Windows Server 2003 Service Pack 3.
-
-
- <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" name="MyApplication.app"/> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2"> <security> <requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3"> <requestedExecutionLevel level="asInvoker"/> </requestedPrivileges> </security> </trustInfo> </assembly>
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-win32res.xml b/docs/Help_Spanish/Topics/opt-win32res.xml
deleted file mode 100644
index 5d1b7eb99b..0000000000
--- a/docs/Help_Spanish/Topics/opt-win32res.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- -win32res
-
- -win32res
-
-
-
- -win32res
-
- The -win32res option inserts a Win32 resource in the output file.
- Syntax
- -win32res:filename
- Arguments
- filenameThe resource file that you want to add to your output file.
- Remarks
- A Win32 resource file can be created with the Resource Compiler. The Resource Compiler is invoked when you include native resources (.RC files) in your X# Visual studio solution.
-
- A Win32 resource can contain version or bitmap (icon) information that would help identify your application in the File Explorer. If you do not specify -win32res, the compiler will generate version information based on the assembly version. You can also include Menu and Dialog definitions in an RC file.
-
- See -linkresource (to reference) or -resource (to attach) a .NET Framework resource file.
-
- To set this compiler option in the Visual Studio development environment:
- You cannot set this compiler option inside Visual Studio. If your application has native resource files, then the build system will automatically convert this to a nativeresources.res file and include this file with the -win32res command line option in your assembly.
- Example
- Compile in.prg and attach a Win32 resource file rf.res to produce in.exe:
-
-
- xsc -win32res:rf.res in.prg
-
-
-
diff --git a/docs/Help_Spanish/Topics/opt-wx.xml b/docs/Help_Spanish/Topics/opt-wx.xml
deleted file mode 100644
index 2154340331..0000000000
--- a/docs/Help_Spanish/Topics/opt-wx.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- -wx
-
- -warnaserror
- -wx
-
-
-
- -wx
-
- The -wx compiler option is an alias for the -warnaserror compiler option for compatibility
-
-
diff --git a/docs/Help_Spanish/Topics/opt-xpp1.xml b/docs/Help_Spanish/Topics/opt-xpp1.xml
deleted file mode 100644
index 06e85cb3f4..0000000000
--- a/docs/Help_Spanish/Topics/opt-xpp1.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- -xpp1
-
- -xpp1
-
-
-
- -xpp1
-
- All XPP classes inherit from the Abstract class (default = OFF).
-
- To set this compiler option in the Visual Studio development environment:
-
-
-
Open the project's Properties page.
-
Click the Dialect tab.
-
Change the value.
-
Click here to see the property page.
-
-
-
diff --git a/docs/Help_Spanish/Topics/optPage-Debugger.xml b/docs/Help_Spanish/Topics/optPage-Debugger.xml
deleted file mode 100644
index 9f04ca355c..0000000000
--- a/docs/Help_Spanish/Topics/optPage-Debugger.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
- Debugger
-
- breakpoint
- breakpoint conditions
- Debugger
- debugger expression evaluator
- Expression evaluator
- intermediate window
- late binding
- watch window
-
-
-
- Debugger
-
- The debugger inside Visual Studio is language-agnostic. We have integrated support for our X# language, allowing you to view variables with X#-specific types in the locals and autos windows, and enter expressions for breakpoint conditions, in the watch window and the intermediate window in X# (e.g., using case-insensitive expressions).
- The debugger expression evaluator (that's how this is called) is powered by the full X# compiler.
- We have added an options page to Visual Studio from where you can control how the X# debugger Expression evaluator parses and compiles expressions.
- Normally, the debugger uses the settings defined in the main application.
- However, if the startup application is not an X# application, then the settings from this dialog are applied.
- The first two options always work.
- When your application uses late binding and you see problems with late binding in the debugger, you can disable it from this dialog.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Command.xml b/docs/Help_Spanish/Topics/pp-Command.xml
deleted file mode 100644
index f7139c02e8..0000000000
--- a/docs/Help_Spanish/Topics/pp-Command.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- #command
-
- #command
- #xcommand
- #ycommand
- Preprocessor
-
-
-
- #command , #xcommand and #ycommand
-
- Purpose
- Specifies a user-defined command or translation directive.
- Syntax
- #command <matchPattern> => <resultPattern>// can be abbreviated to 4 characters #xcommand <matchPattern> => <resultPattern>// cannot be abbreviated to 4 characters #ycommand <matchPattern> => <resultPattern>// cannot be abbreviated to 4 characters and must match case
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Define.xml b/docs/Help_Spanish/Topics/pp-Define.xml
deleted file mode 100644
index fb7557670f..0000000000
--- a/docs/Help_Spanish/Topics/pp-Define.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- #define
-
- #define
- Preprocessor
-
-
-
- #define
-
- Syntax
- #define identifier [token-string]
- or
- #define identifier LPAREN parameters RPAREN
- Description
-
- #define lets you define a symbol, such that, by using the symbol as the expression in a #ifdef directive, the expression will evaluate to true or in a or #ifndef directive the expression will evaluate to false.
- #define also allows you define a symbolic name for a token string, so you can use the symbolic name in your code and the preprocessor will replace all occurences of that name with the token string that you have specified.
- For example:
- #define DEBUG // ... #if DEBUG Console.WriteLine("Debug version"); #endif
-
- or
-
- #define VERSION "1.2.0.0" #define FILEVERSION "1.2.3.4" // ... [assembly: AssemblyVersion(VERSION)] [assembly: AssemblyFileVersion(FILEVERSION)]
- A define with parentheses, such as
- #define MAX(a,b) iif(a>b, a, b)
- will be treated like a #translate.
-
- Notes
- Please note that defines areCASE SENSITIVE, so the following code will work:
-
- #define TEST 123
FUNCTION Test() ASINT RETURN TEST
- but this will NOT compile:
- #define TEST 123
FUNCTION TEST() ASINT RETURN TEST
- because the preprocessor will replace the name TEST in the FUNCTION line with the value 123 which is not a valid identifier. After pre-processing, the code becomes:
- FUNCTION 123() ASINT RETURN 123
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Else.xml b/docs/Help_Spanish/Topics/pp-Else.xml
deleted file mode 100644
index 93fd48a9b7..0000000000
--- a/docs/Help_Spanish/Topics/pp-Else.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- #else
-
- #else
- Preprocessor
-
-
-
- #else
-
- Purpose
- #else lets you create a compound conditional directive, so that, if the expression in the preceding #ifdef directive or #ifndef directive does not evaluate to true, the compiler will evaluate all code between #else and the subsequent #endif.
-
- For example, the following code will show the string "Debug Version" if the symbol DEBUG is defined on the command line, else it will show the text "Release Version":
- // DEBUG may be defined from the command line // ... #if DEBUG Console.WriteLine("Debug version"); #else Console.WriteLine("Release version"); #endif
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Endif.xml b/docs/Help_Spanish/Topics/pp-Endif.xml
deleted file mode 100644
index 8faa40408f..0000000000
--- a/docs/Help_Spanish/Topics/pp-Endif.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- #endif
-
- #endif
- Preprocessor
-
-
-
- #endif
-
- Purpose
- #endif specifies the end of a conditional directive, which began with the #ifdef or #ifndef directive. For example:
- // DEBUG may be defined from the command line // ... #if DEBUG Console.WriteLine("Debug version"); #else Console.WriteLine("Release version"); #endif
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Endtext.xml b/docs/Help_Spanish/Topics/pp-Endtext.xml
deleted file mode 100644
index a55549fed6..0000000000
--- a/docs/Help_Spanish/Topics/pp-Endtext.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- #endtext
-
-
- #endtext
-
- Purpose
- Marks the end of a #text .. #endtext region.
- Syntax
- #text := <varname> First Line Second Line #endtext
- Description
- The language supports the TEXT .. ENDTEXT construct. These commands are converted by the preprocessor into a #text .. #endtext construct.
- #endtext always appears "alone" on a line of code and will be replaced by a call to the (optional) endfunction that is declared with the #text directive and when the block is assigned to a variable then the assignment will be performed on the #endtext line.
-
- Example
- Please note that the 2 UDCs below are already defined in XSharpDefs.xh:
- #xcommand ENDTEXT => #endtext
TEXTTO FILE EXAMPLE.TXT line 1 line 2 line 3 line 4 ENDTEXT
- The TEXT TO FILE command is translated into a call to the function _TextSave(), followed by the #text directive, that specifies that each line must be sent to the QOut() function and that also declares that the #endtext line must be replaced by a call to the _TextRestore() function. The QOut() and _TextRestore function names are specified without parameters. Each line in the block will be sent to the QOut() function as parameter.
-
- So this code is converted to:
- _TextSave("EXAMPLE.TXT"); QOut("line 1") QOut("line 2") QOut("line 3") QOut("line 4") _TextRestore()
- See also
- TEXT command
- #text Directive
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-If.xml b/docs/Help_Spanish/Topics/pp-If.xml
deleted file mode 100644
index e8ad05d925..0000000000
--- a/docs/Help_Spanish/Topics/pp-If.xml
+++ /dev/null
@@ -1,81 +0,0 @@
-
-
-
- #if
-
-
- #if
-
- Purpose
- Marks a region in the source code that will only be included in the compilation when a logical condition evaluates to TRUE.
- Syntax
- #if <logical_expression> <SourceCode included if <logical_expression> evaluates to .T.> [ #else <SourceCode included if <logical_expression> othwerwise> ] #endif
- <logical_expression>: <expression>
<logical_literal> : .T. | TRUE | .F. | FALSE
- Description
- The #if...#else...#endif directive forms a control structure for the preprocessor. When the <logical_expression> evaluates to true (.T.), the preprocessor translates and outputs the source code located between the directives #if and #else to the intermediary file, and the source code between the directives #else and #endif is ignored. If no #else directive is present, the preprocessor translates and outputs the source code located between the directives #if and #endif . If the <logical_expression> evaluates to false (.F.), the source code between the directives #else and #endif is included only.
- The <logical_expression> term can be formed using operands, compare operators and logical operators. A compare operations always requires two operands and will be evaluated prior to logical operations. The operands must be either string literals, numeric literals or logical literals or a valid #define constant that results to one of the mentioned literals. A string will be recognized when it is enclosed within single or double quote characters. If an undefined constant is encountered, the result of that term will be false (.F.).
- A logical expression consists either of two expression and one logical operator, or simply of one literal.
-
- Type conversions
-
- When an expression mixes types, the preprocessor automatically converts types in the following order for comparisons and calculations:
-
- 1.String
- 2.Double
- 3.Integer
- 4.Logic
-
- For example:
- #if 1 > "abc" // the 1 is converted to "1" first before the comparison is done ? "Compare number and string" #endif #if 1.2 > FALSE // the FALSE is converted to 0 first before the comparison is done ? "Compare number and string" #endif
- Conversions For comparisons and calculation operators, the types of the 2 operands are compared. If they are equal, no conversion is needed. If they are not of the same type, the following rules are applied:
-
-
- String: Null or Empty = FALSE, All others = TRUE Integer: 0 = FALSE, All others = TRUE Double: 0.0 = FALSE, All others = TRUE
-
-
-
-
- Comparison operations
- String comparisons are done in case sensitive way using an Ordinal comparison. The '=' operator is NOT supported for string comparisons since the preprocessor does not know what the setting for "SetExact() is that you want to use. All comparisons are done with String.Compare().
-
- Dialects
- In the FoxPro dialect, the operators NOT, AND, OR and XOR are also available.
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Ifdef.xml b/docs/Help_Spanish/Topics/pp-Ifdef.xml
deleted file mode 100644
index bbc6500f67..0000000000
--- a/docs/Help_Spanish/Topics/pp-Ifdef.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- #ifdef
-
- #ifdef
- Preprocessor
-
-
-
- #ifdef
-
- Purpose
- When the X# compiler encounters an #ifdef directive, followed eventually by an #endif directive, it will compile the code between the directives only if the specified symbol is defined.
- The #ifdef statement in X# is Boolean and only tests whether the symbol has been defined or not. For example:
-
- // DEBUG may be defined from the command line // ... #if DEBUG Console.WriteLine("Debug version"); #else Console.WriteLine("Release version"); #endif
- Note
- The /vo8 compiler option will change this behavior:
- when /vo8 is active, any symbol defined with TRUE or a non-0 numeric value will be seen as "defined", symbols defined with FALSE or a 0 numeric value will be seen as "undefined".
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Ifndef.xml b/docs/Help_Spanish/Topics/pp-Ifndef.xml
deleted file mode 100644
index 57efff608c..0000000000
--- a/docs/Help_Spanish/Topics/pp-Ifndef.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- #ifndef
-
- #ifndef
- Preprocessor
-
-
-
- #ifndef
-
- Purpose
- When the X# compiler encounters an #ifndef directive, followed eventually by an #endif directive, it will compile the code between the directives only if the specified symbol is NOT defined.
- The #ifndef statement in X# is Boolean and only tests whether the symbol has been defined or not. For example:
-
- // DEBUG may be defined from the command line // ... #if DEBUG Console.WriteLine("Debug version"); #else Console.WriteLine("Release version"); #endif
- Note
- When /vo8 is active, any symbol defined with FALSE or a 0 numeric value will also be seen as "undefined".
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Include.xml b/docs/Help_Spanish/Topics/pp-Include.xml
deleted file mode 100644
index 268ce9d317..0000000000
--- a/docs/Help_Spanish/Topics/pp-Include.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
- #include
-
- #include
- Preprocessor
-
-
-
- #include
-
- Purpose
- Tells the preprocessor to treat the contents of a specified file as if they appear in the source program at the point where the directive appears.
- #include "path-spec"
-
- You can include preprocessor definitions into files and then use #include directives to add them to any source file.
- The path-spec is a file name that may optionally be preceded by a directory specification. The file name must name an existing file.
- The preprocessor searches for include files in this order:
-
-
In the same directory as the file that contains the #include statement.
-
Along the path that's specified by each /I compiler option.
-
In the Include folder inside the XSharp installation folder.
-
Along the paths that are specified by the INCLUDE environment variable. (Not supported yet)
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Line.xml b/docs/Help_Spanish/Topics/pp-Line.xml
deleted file mode 100644
index 19c0680fbd..0000000000
--- a/docs/Help_Spanish/Topics/pp-Line.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- #line
-
- #line
- Preprocessor
-
-
-
- #line
-
- Purpose
- #line sets the current line number for the compiler. It is usually inserted by the preprocessor after preprocessing an include file to synchronize the line numbers with the original source file.
-
- #line <number> [FileName]
- Argumes
- line number The new line number to use by the compiler.
- FileName An optional new file name to use by the compiler.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Pragma-Options.xml b/docs/Help_Spanish/Topics/pp-Pragma-Options.xml
deleted file mode 100644
index 0e3c6ff73e..0000000000
--- a/docs/Help_Spanish/Topics/pp-Pragma-Options.xml
+++ /dev/null
@@ -1,309 +0,0 @@
-
-
-
- #pragma options
-
- #pragma
- #pragma options
- -az
- -lb
- -memvars
- -options
- -pragma
- -undeclared
- -vo10
- -vo11
- -vo12
- -vo13
- -vo14
- -vo15
- -vo16
- -vo2
- -vo4
- -vo5
- -vo6
- -vo7
- -vo9
-
-
-
- #pragma options
-
- Purpose
- The #pragma options directive allow you to enable or disable certain compiler options for a range of code.
- Syntax
- #pragma options( "option", state )
- Note: #pragma directives must appear before the first entity or between entities and cannot appear in the middle of an entity
-
- "option" can be one of the following (please note that not all compiler options can be used):
-
-
- Clipper/VO Compatible Begin Sequence .. End Sequence
-
-
-
-
- "fox1"
-
-
- This option cannot be set with the #pragma keyword
-
-
-
-
- "fox2"
-
-
- Foxpro array syntax
-
-
-
-
- "xpp1"
-
-
- This option cannot be set with the #pragma keyword
-
-
-
-
- State can be one of the following:
-
-
on
-
off
-
default
-
-
- Please note that you can also enable or disable overflow checking with BEGIN CHECKED .. END / BEGIN UNCHECKED .. END.
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Pragma-Warnings.xml b/docs/Help_Spanish/Topics/pp-Pragma-Warnings.xml
deleted file mode 100644
index 3bf99c0db8..0000000000
--- a/docs/Help_Spanish/Topics/pp-Pragma-Warnings.xml
+++ /dev/null
@@ -1,149 +0,0 @@
-
-
-
- #pragma warning(s)
-
- #pragma warning
- #pragma warnings
- pragma
- warnings
-
-
-
- #pragma warning(s)
-
- Purpose
- The #pragma warning directive allows you to suppress certain compiler warnings for a piece of code. We support both C# style pragma warnings commands (fully) and Vulcan style pragmas (partially).
-
- Syntax
- #pragma warnings( number, state ) #pragma warnings ( pop ) #pragma warning state2 [<errornumbers>]
- Note
- #pragma directives must appear before the first entity or between entities and cannot appear in the middle of an entity.
- Arguments
-
- numberWarning number to disable. Can be both numeric or in the form of XSnnnn
- stateOff | DefaultDisables a warning or switches it back to the situation from the command line
- popSwitches all warnings back to their default value
- state2 Disable | Restore Disables or restores the warning numbers that follow. When no error numbers are specified, then disable disables all warning and restore restores all warning to their default value
- errornumbers(Optional) comma separated list of numbers or names (XSnnnn)
-
- Note:
- The compiler does NOT check if the numbers are valid or if they are indeed warnings. So you can specify non existent numbers and/or numbers that represent errors instead of warnings. The compiler will not warn you when that is the case.
- C# style syntax
-
-
-
-
- Example
-
-
- Description
-
-
-
-
- #pragma warning disable 1234
-
-
- Disable warning 1234
-
-
-
-
- #pragma warning disable 1234, XS2345
-
-
- Disable 2 warnings 1234 and XS2345
-
-
-
-
- #pragma warning restore 1234
-
-
- Reset warning 1234 to the state from the command line
-
-
-
-
- #pragma warning restore 1234, XS2345
-
-
- Reset 2 warnings 1234 and XS2345 to the state from the command line
-
-
-
-
- #pragma warning disable
-
-
- Disables all warnings
-
-
-
-
- #pragma warning restore
-
-
- Restores all warnings to the settings from the command line
-
-
-
- Vulcan style syntax
-
-
-
- Example
-
-
- Description
-
-
-
-
- #pragma warnings (1234, off )
-
-
- Disable warning 1234
-
-
-
-
- #pragma warnings (1234, default)
-
-
- Reset warning 1234 to the state from the command line
-
-
-
-
- #pragma warnings ( pop )
-
-
- Restores all warnings to the settings from the command line
-
-
-
-
- NOT supported:
-
-
-
-
-
-
- #pragma warnings (1234, on )
-
-
-
-
-
-
- #pragma warnings ( push )
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Region.xml b/docs/Help_Spanish/Topics/pp-Region.xml
deleted file mode 100644
index 601ab14458..0000000000
--- a/docs/Help_Spanish/Topics/pp-Region.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- #region - #endregion
-
- #endregion
- #ifdef
- #region
- Preprocessor
-
-
-
- #region - #endregion
-
- Purpose
- #region lets you specify a block of code that you can expand or collapse when using the outlining feature of the Visual Studio Code Editor. In longer code files, it is convenient to be able to collapse or hide one or more regions so that you can focus on the part of the file that you are currently working on. The following example shows how to define a region:
- #region MyClass definition CLASS MyClass EXPORT Name asSTRING ENDCLASS #endregion
- Comments
- A #region block must be terminated with a #endregion directive.
- A #region block cannot overlap with a #ifdef block or an #ifndef block. However, a #region block can be nested in a #ifdef or #ifndef block, and a #ifdef or #ifndef block can be nested in a #region block. For now the compiler does not enforce this, but it will in the not too far future.
- A #region and #endregion block may have optional comments after the #region and #endregion keyword. The compiler will ignore everything after the keyword until the end of the line.
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Stdout.xml b/docs/Help_Spanish/Topics/pp-Stdout.xml
deleted file mode 100644
index 7f5784a867..0000000000
--- a/docs/Help_Spanish/Topics/pp-Stdout.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- #stdout
-
-
- #stdout
-
- Purpose
- Sends data to the output stream during compilation
- Syntax
- #stdout <message>
- Description
- The #stdout directive sends output to the standard output during compilation followed by a CRLF. Whether this output will be shown in the IDE that you are using or not, depends on the settings of this IDE.
-
- Example
- // example of #stdout // The example demonstrates the use of #stdout FUNCTION Start ASVOID #ifndef DEBUG // output at compile time #stdout Compiling a debug version of the program #endif ? "Hello world" RETURN
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Text.xml b/docs/Help_Spanish/Topics/pp-Text.xml
deleted file mode 100644
index 5e612763d4..0000000000
--- a/docs/Help_Spanish/Topics/pp-Text.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-
-
-
- #text
-
- ENDTEXT command
-
-
-
- #text
-
- Purpose
- Marks the start of a #text .. #endtext region.
- The #text directive also defines the nature of the region. This region can either assign a value to a local variable or process the contents of the region.
- There are 2 variations of the #text directive:
- 1.#text [:= | +=] VarName [, LineDelimiter [, LineFunc, [, EndFunc]] ] 2.#text LineFunc [, EndFunc]
-
-
This variation can be recognized by the := or += operator that follows the #text directive. This declares a #text .. #endtext region that stores the value to a local variable for which the name is specified behind the operator. The text declaration may also contain (optional) tokens that will be used as "line delimiters", an optional function that will be used to calculate each line and an optional function name that will be called from the #endtext line.
-
This variation does not have a variable name and declares up to two function names for each line and the #endtext line.
-
- Arguments
- VarNameis the Name of the variable that should be assigned the value of the Text block
-
- LineDelimiteris the delimiter that should be added to the end of every line in the block
-
- LineFuncis the Name of a function that should be called on every line in the block. The function gets passed the line and should return a string
-
- EndFuncis the Name of a function that gets called after all the lines were created. This function receives the string value of the block when the block is assigned to a variable and should return a string. When the block is not assigned to a variable then this function gets called without parameters.
-
- Example 1
- Please note that the 3 UDCs below are already defined in XSharpDefs.xh.
- #xcommand ENDTEXT => #endtext
#xcommand TEXTTO <varname> ADDITIVE ; => #text += <varname>, chr(13)+chr(10)
- LOCAL cResult ASSTRING TEXTTO cResult line 1 line 2 line 3 line 4 TEXT ? cResult
- This code is converted to:
- LOCAL cResult ASSTRING var tempLocal := System.Text.StringBuilder{} tempLocal:Append("Line 1"+chr(13)+chr(10) ) tempLocal:Append("Line 2"+chr(13)+chr(10) ) tempLocal:Append("Line 3"+chr(13)+chr(10) ) cResult := tempLocal:ToString() ? cResult
- Please note that the compiler declares different TEXT commands for different dialects. The TEXT command above works in all dialects. The TEXT command below is for the Non-Core dialects (with the exception of FoxPro):
- #xcommand TEXTINTO <varname> WRAP [<lnbreak>] TRIMMED ; => #text := <varname>, iif(<.lnbreak.>,<!lnbreak!>, CRLF) , LTrim
- This command allows a user-defined end of line character and calls the LTrim() function on each string before assigning it to the variable.
-
- FoxPro declares a special TEXT command that looks like this:
-
- #xcommand TEXTTO <varname> [<tm:TEXTMERGE>] [<noshow:NOSHOW>] [FLAGS <flags>] [PRETEXT <expression> ] ; => __TextInit(<.tm.>, <.noshow.>, iif(<.flags.>, <!flags!>, 0), <!expression!> ) ;; #text := <varname>, ,__TextWriteLine , __TextEnd
- As you can see, the command gets translated into a function call to __TextInit() with the values of the various TEXT command options. Each line is sent to the __TextWriteLine function and the #endtext directive is replaced with a call to __TextEnd(). There are NO delimiters added for each line. This is handled inside __TextWriteLine. This function is also responsible for expanding expressions inside the text when the TEXTMERGE option is chosen, or when the global SET TEXTMERGE is enabled.
- Example 2
- Please note that the 2 UDCs below are already defined in XSharpDefs.xh:
- #xcommand ENDTEXT => #endtext
TEXTTO FILE EXAMPLE.TXT line 1 line 2 line 3 line 4 ENDTEXT
- The TEXT TO FILE command is translated into a call to the function _TextSave(), followed by the #text directive, that specifies that each line must be sent to the QOut() function and that also declares that the #endtext line must be replaced by a call to the _TextRestore() function. The QOut() and _TextRestore function names are specified without parameters. Each line in the block will be sent to the QOut() function as parameter.
-
- So this code is converted to:
- _TextSave("EXAMPLE.TXT"); QOut("line 1") QOut("line 2") QOut("line 3") QOut("line 4") _TextRestore()
- See also
- TEXT command
- Core TEXT Command
- Non-Core TEXT Command
- FoxPro TEXT Command
- #endtext Directive
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Translate.xml b/docs/Help_Spanish/Topics/pp-Translate.xml
deleted file mode 100644
index 81a2452d01..0000000000
--- a/docs/Help_Spanish/Topics/pp-Translate.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- #translate
-
- #translate
- #xtranslate
- #ytranslate
- Preprocessor
-
-
-
- #translate, #xtranslate and #ytranslate
-
- Purpose
- Specify a user-defined translation directive
- Syntax
- #translate <matchPattern> => <resultPattern> // can be abbreviated to 4 characters #xtranslate <matchPattern> => <resultPattern> // cannot be abbreviated to 4 characters #ytranslate <matchPattern> => <resultPattern> // cannot be abbreviated to 4 characters and must match case
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp-Undef.xml b/docs/Help_Spanish/Topics/pp-Undef.xml
deleted file mode 100644
index 63e8dc3d18..0000000000
--- a/docs/Help_Spanish/Topics/pp-Undef.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- #undef
-
- #undef
- Preprocessor
-
-
-
- #undef
-
- Syntax
- #undef identifier
- Description
- #undef lets you undefine a symbol, such that, by using the symbol as the expression in a #ifdef directive, the expression will evaluate to false or, in a #ifndef directive, the expression will evaluate to true.
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp_Match-Markers.xml b/docs/Help_Spanish/Topics/pp_Match-Markers.xml
deleted file mode 100644
index a0fce7030f..0000000000
--- a/docs/Help_Spanish/Topics/pp_Match-Markers.xml
+++ /dev/null
@@ -1,138 +0,0 @@
-
-
-
- Match Markers
-
- <#idMarker>
- <%idMarker%>
- <(idMarker)>
- <*idMarker*>
- <idMarker,...>
- <idMarker:word list>
- <idMarker>
-
-
-
- Match Markers
-
- Match Pattern
- The <matchPattern> portion of a translation directive is the pattern the input text must match. A match pattern is made from one or more of the following components, which the preprocessor tries to match against input text in a specific way:
-
-
-
Literal values are actual characters that appear in the match pattern. These characters must appear in the input text, exactly as specified to activate the translation directive.
-
-
-
-
Words are keywords and valid identifiers that are compared according to the dBASE convention (case-insensitive, first four letters mandatory, etc.). The match pattern must start with a Word.
-
-
-
-
#xcommand and #xtranslate can recognize keywords of more than four significant letters.
-
-
-
-
Match markers are label and optional symbols delimited by angle brackets (<>) that provide a substitute (idMarker) to be used in the <resultPattern> and identify the clause for which it is a substitute. Marker names are identifiers and must, therefore, follow the xBase identifier naming conventions. In short, the name must start with an alphabetic or underscore character, which may be followed by alphanumeric or underscore characters.
-
-
- This table describes all match marker forms:
-
-
-
-
- Match Marker
-
-
- Name
-
-
-
-
- <idMarker>
-
-
- Regular match marker
-
-
-
-
- <idMarker,...>
-
-
- List match marker
-
-
-
-
- <idMarker:word list>
-
-
- Restricted match marker
-
-
-
-
- <*idMarker*>
-
-
- Wild match marker
-
-
-
-
- <(idMarker)>
-
-
- Extended Expression match marker
-
-
-
-
- <#idMarker>
-
-
- Single match marker.
-
-
-
-
- <%idMarker%>
-
-
- Wildcard match marker
-
-
-
-
-
-
Regular match marker: Matches the next legal expression in the input text. The regular match marker, a simple label, is the most general and, therefore, the most likely match marker to use for a command argument. Because of its generality, it is used with the regular result marker, all of the stringify result markers, and the blockify result marker.
-
-
-
-
List match marker: Matches a comma-separated list of legal expressions. If no input text matches the match marker, the specified marker name contains nothing. You must take care in making list specifications because extra commas will cause unpredictable and unexpected results.
The list match marker defines command clauses that have lists as arguments. Typically, these are FIELDS clauses or expression lists used by database commands. When there is a match for a list match marker, the list is usually written to the result text using either the normal or smart stringify result marker. Often, lists are written as literal arrays by enclosing the result marker in curly ({ }) braces.
-
-
-
-
Restricted match marker: Matches input text to one of the words in a comma-separated list. If the input text does not match at least one of the words, the match fails and the marker name contains nothing.
A restricted match marker is generally used with the logify result marker to write a logical value into the result text. If there is a match for the restricted match marker, the corresponding logify result marker writes true (.T.) to the result text; otherwise, it writes false (.F.). This is particularly useful when defining optional clauses that consist of a command keyword with no accompanying argument. Std.ch implements the REST clause of database commands using this form.
-
-
-
-
Wild match marker: Matches any input text from the current position to the end of a statement. Wild match markers generally match input that may not be a legal expression, such as #command NOTE <*x*> in Clippers Std.ch, gather the input text to the end of thestatement, and write it to the result text using one of the stringify result markers.
-
-
-
-
Single match marker. Matches all consecutive tokens until a whitespace token.
-
-
-
-
Wildcard match marker: Matches a list of tokens that are an Id, Comma, ? or *. This can be used in commands such as SAVE ALL LIKE a*,b*.
-
-
-
-
Extended expression match marker: Matches a regular or extended expression, including a file name or path specification. It is used with the smart stringify result marker to ensure that extended expressions will not get stringified, while normal, unquoted string file specifications will.
-
-
-
-
Optional match clauses are portions of the match pattern enclosed in square brackets ([ ]). They specify a portion of the match pattern that may be absent from the input text. An optional clause may contain any of the components allowed within a <matchPattern>, including other optional clauses.
Optional match clauses may appear anywhere and in any order in the match pattern and still match input text. Each match clause may appear only once in the input text. There are two types of optional match clauses: one is a keyword followed by match marker, and the other is a keyword by itself. These two types of optional match clauses can match all of the traditional command clauses typical of the xBase command set.
Optional match clauses are defined with a regular or list match marker to match input text if the clause consists of an argument or a keyword followed by an argument (see the INDEX clause of the USE command in Std.ch). If the optional match clause consists of a keyword by itself, it is matched with a restricted match marker (see the EXCLUSIVE or SHARED clause of the USE command in Std.ch).
In any match pattern, you may not specify adjacent optional match clauses consisting solely of match markers, without generating a compiler error. You may repeat an optional clause any number of times in the input text, as long as it is not adjacent to any other optional clause. To write a repeated match clause to the result text, use repeating result clauses in the <resultPattern> definition.
-
-
-
diff --git a/docs/Help_Spanish/Topics/pp_Result-Markers.xml b/docs/Help_Spanish/Topics/pp_Result-Markers.xml
deleted file mode 100644
index 2f7b4baf4e..0000000000
--- a/docs/Help_Spanish/Topics/pp_Result-Markers.xml
+++ /dev/null
@@ -1,130 +0,0 @@
-
-
-
- Result Markers
-
- #<idMarker>
- <!idmarker!>
- <(idMarker)>
- <.idMarker.>
- <{idMarker}>
- <idMarker>
-
-
-
- Result Markers
-
- Result Pattern
- The <resultPattern> portion of a translation directive is the text the preprocessor will produce if a piece of input text matches the <matchPattern>. <resultPattern> is made from one or more of the following components:
-
-
-
Literal tokens are actual characters that are written directly to the result text.
-
Words are xBase keywords and identifiers that are written directly to the result text.
-
-
-
-
Result markers: refer directly to a match marker name. Input text matched by the match marker is written to the result text via the result marker.
-
-
- This table lists the Result marker forms:
-
-
-
-
- Result Marker
-
-
- Name
-
-
-
-
- <idMarker>
-
-
- Regular result marker
-
-
-
-
- #<idMarker>
-
-
- Dumb stringify result marker
-
-
-
-
- <"idMarker">
-
-
- Normal stringify result marker
-
-
-
-
- <(idMarker)>
-
-
- Smart stringify result marker
-
-
-
-
- <{idMarker}>
-
-
- Blockify result marker
-
-
-
-
- <.idMarker.>
-
-
- Logify result marker
-
-
-
-
- <!idmarker!>
-
-
- Notempty result marker
-
-
-
-
-
-
Regular result marker: Writes the matched input text to the result text, or nothing if no input text is matched. Use this, the most general result marker, unless you have special requirements. You can use it with any of the match markers, but it is almost always used with the regular match marker.
-
-
-
-
Dumb stringify result marker: Stringifies the matched input text and writes it to the result text. If no input text is matched, it writes a null string (""). If the matched input text is a list matched by a list match marker, this result marker stringifies the entire list and writes it to the result text.
This result marker writes output to result text where a string is always required. This is generally the case for commands where a command or clause argument is specified as a literal value, but the result text must always be written as a string, even if the argument is not specified.
-
-
-
-
Normal stringify result marker: Stringifies the matched input text and writes it to the result text. If no input text is matched, it writes nothing to the result text. If the matched input text is a list matched by a list match marker, this result marker stringifies each element in the list and writes it to the result text.
The normal stringify result marker is most often used with the blockify result marker to compile an expression while saving a text image of the expression (See the SET FILTER condition and the INDEX key expression in Std.ch).
-
-
-
-
Smart stringify result marker: Stringifies matched input text only if source text is enclosed in parentheses. If no input text matched, it writes nothing to the result text. If the matched input text is a list matched by a list match marker, this result marker stringifies each element in the list (using the same stringify rule) and writes it to the result text.
The smart stringify result marker is designed specifically to support extended expressions for commands other than SETs with <xlToggle> arguments. Extended expressions are command syntax elements that can be specified as literal text or as an expression if enclosed in parentheses. The <xcDatabase> argument of the USE command is a typical example. For instance, if the matched input for the <xcDatabase> argument is the word Customer, it is written to the result text as the string "Customer," but the expression (cPath + cDatafile) would be written to the result text unchanged (i.e., without quotes).
-
-
-
-
Blockify result marker: Writes matched input text as a code block without any arguments to the result text. For example, the input text x + 3 would be written to the result text as {|| x + 3}. If no input text is matched, it writes nothing to the result text. If the matched input text is a list matched by a list match marker, this result marker blockifies each element in the list.
The blockify result marker used with the regular and list match markers matches various kinds of expressions and writes them as code blocks to the result text. Remember that a code block is a piece of compiled code to execute sometime later. This is important when defining commands that evaluate expressions more than once per invocation. When defining a command, you can use code blocks to pass an expression to a function and procedure as data rather than as the result of an evaluation. This allows the target routine to evaluate the expression whenever necessary.
In Std.ch, the blockify result marker defines database commands where an expression is evaluated for each record. Commonly, these are field or expression lists, FOR and WHILE conditions, or key expressions for commands that perform actions based on key values.
-
-
-
-
Logify result marker: Writes true (.T.) to the result text if any input text is matched; otherwise, it writes false (.F.) to the result text. This result marker does not write the input text itself to the result text.
The logify result marker is generally used with the restricted match marker to write true (.T.) to the result text if an optional clause is specified with no argument; otherwise, it writes false (.F.). In Std.ch, this formulation defines the EXCLUSIVE and SHARED clauses of the USE command.
-
-
-
-
Notempty result marker. Writes the matched input text to the result text, or NIL if no input text is matched. This may be required instead of the regular result marker if you place the marker inside an IIF() expression.
-
-
-
-
Repeating result clauses are portions of the <resultPattern> enclosed by square brackets ([ ]). The text within a repeating clause is written to the result text as many times as it has input text for any or all result markers within the clause. If there is no matching input text, the repeating clause is not written to the result text. Repeating clauses, however, cannot be nested. If you need to nest repeating clauses, you probably need an additional #command rule for the current command.
Repeating clauses are the result pattern part of the #command facility that create optional clauses which have arguments. You can match input text with any match marker other than the restricted match marker and write to the result text with any of the corresponding result markers. Typical examples of this facility are the definitions for the STORE and REPLACE commands in Std.ch.
-
-
-
diff --git a/docs/Help_Spanish/Topics/project_references_Assembly.xml b/docs/Help_Spanish/Topics/project_references_Assembly.xml
deleted file mode 100644
index a5203cf601..0000000000
--- a/docs/Help_Spanish/Topics/project_references_Assembly.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- .Net
-
-
- External .Net Assemblies
-
- The page with assembly references shows the list of assemblies that were found on the developers machine.
- You can select a reference from this list and this reference will be used without extra work.
-
-
-
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/project_references_COM.xml b/docs/Help_Spanish/Topics/project_references_COM.xml
deleted file mode 100644
index ddd11fe3e6..0000000000
--- a/docs/Help_Spanish/Topics/project_references_COM.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- COM
-
-
- External COM Components
-
- The COM page in the Add Reference dialog lists the COM components that were found in the registry on your machine.
- You can select a component from this list.
-
- However, these components cannot be consumed directly by the X# compiler. Therefore, Visual Studio calls a tool (tlbimp.exe) that reads the typelibrary from the COM component and produces a managed wrapper around this COM object. This wrapper usually has a name that starts with "interop". In the Email example, this is the case for the Internet Explorer component for which an Interop.SHDocVw.dll is generated.
- If the COM component is an ActiveX, a second assembly will be generated, with code that declares an object inheriting from System.Windows.Forms.AxHost, for the ActiveX control. For this, Visual Studio calls the tool "aximp.exe". The file names for these wrappers usually start with "axinterop", such as "AxInterop.SHDocVw.dll"
- For the COM components that are used a lot, a so called "Primary Interop Assembly" is installed on your machines. For these components, no "interop" assemblies will be generated, but the primary interop assemblies will be used when compiling. For example, for ADO there is a primary interop assembly in the GAC.
-
-
-
-
-
diff --git a/docs/Help_Spanish/Topics/project_references_Project.xml b/docs/Help_Spanish/Topics/project_references_Project.xml
deleted file mode 100644
index 69c6750b75..0000000000
--- a/docs/Help_Spanish/Topics/project_references_Project.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Project
-
-
- References to other Visual Studio projects
-
- A third type of dependency is between Visual Studio projects. When you add a dependency of this type, Visual Studio (or actually MsBuild) will try to build that project first before building the project that depends on it. Unlike in Visual Objects, you do not have to import a prototype library for the output generated by the project. Visual Studio (and our editor integration) will directly consume the output from the other projects.
-
- If the other project is also a X# Project, our source code editor support code will be able to jump between the declaration of a type and the place where it is used, even if it is in another project. When your X# project depends on a project in different language (such as C#), we will consume the output of that project like we do with "normal" external .Net assemblies.
-
-
-
-
-
-
diff --git a/docs/Help_Spanish/XSHelp.hmxp b/docs/Help_Spanish/XSHelp.hmxp
deleted file mode 100644
index 450f8f8f84..0000000000
--- a/docs/Help_Spanish/XSHelp.hmxp
+++ /dev/null
@@ -1,818 +0,0 @@
-
-
-
-
-
-
-
-
-
- ..\..\Artifacts\Doc\XSharp_ES.chm
- ..\help\XSharp.hmskin
- 1
- CHM
- *
-
-
-
-
- ..\..\artifacts\Doc\XSharp_ES.pdf
- ..\Help\Standard_manual_A4.mnl
- 0
- 0
- 36526
- PDF
- *
- Table of Contents
-
-
-
-
- ..\..\artifacts\Doc\XSharp_ES.mshc
- 0
- HXS
- *
- Table of Contents
-
-
-
-
- ..\..\artifacts\DocSpanish\HTML\index.html
- XSharp_WebHelp.hmskin
- HTML
- OPT_PARENTHOME,OPT_TOPICFOOTER,OPT_WEBFONTS
- *
-
-
-
-
-
-
-
-