SOME COMMAND FIX LIKE APPEND BLANK, DELETE

If you are converting a text-based Clipper application, a FoxPro application or just writing an application from scratch, use this forum for your eXpress++ questions.
Post Reply
Message
Author
User avatar
alepap
Posts: 94
Joined: Tue Jul 28, 2015 5:15 am

SOME COMMAND FIX LIKE APPEND BLANK, DELETE

#1 Post by alepap »

Some commands in Alaska requires rlock() when used in a shared mode file.

It looks like eXpress provides the same commands with the rlock() built in. (you don't need to use the rlock().
This is provided by using DCSTD.CH

In the eXpress documentation, it says APPENDBLANK in one word. But inside, it´s APPEND BLANK in 2 words exactly the same as Alaska xBase++.

To use the eXpress version of APPEND BLANK, you need to add #include DCSTD.CH at the beginning of each PRG file.
Could this be added in the XPJ file?

User avatar
alepap
Posts: 94
Joined: Tue Jul 28, 2015 5:15 am

Re: SOME COMMAND FIX LIKE APPEND BLANK, DELETE

#2 Post by alepap »

Question below.

--- from Alaska Help file.

The #include directive causes the preprocessor to insert the contents of the indicated file into the source code file. Files which are inserted from the preprocessor into the source code are called Include files and should contain only Directives or REQUEST declarations. The contents of an Include file is inserted at the location of the #include directive. The default file extension for include files is ".CH". All Xbase++ Include files are located in the ..\INCLUDE directory.

#include directives are generally placed at the beginning of a source code file. Include files solve a fundamental problem with directives. Directives are scoped to the source file in which they are defined. This means that if the same directive is used in several source files, it must be defined in each file. The Include file provides a method to define directives in one file, and then just #include that file in each source file requiring one more directives contained in that file. By their nature, Include files also promote better modularity, since maintenance of the various directives can be performed in one location.

The Include file STD.CH is automatically inserted by the preprocessor into each PRG file, without requiring a corresponding #include directive. The file STD.CH contains the directives for the translation of all Xbase++ commands. Instead of STD.CH, another file can be used as the automatic include file by using the /U compiler switch. STD.CH should not be changed. If changes are desired then a copy of STD.CH should be made and that new copy should be incorporated into the compile using /U.

---

So the question is more like: How should the DCSTD.CH be used, since, STD.CH from Alaska is automatically used and they could have the same command, like APPEND BLANK?

User avatar
rdonnay
Site Admin
Posts: 4722
Joined: Wed Jan 27, 2010 6:58 pm
Location: Boise, Idaho USA
Contact:

Re: SOME COMMAND FIX LIKE APPEND BLANK, DELETE

#3 Post by rdonnay »

I do not recommend using DCSTD.CH in your applications.

This command set was designed only for using within DC_Dot() and XDOT.EXE.

You will run into many more problems if you do this.

You can easily create your own .CH file with the commands you want.
This will override the same commands that are in STD.CH.
The eXpress train is coming - and it has more cars.

Post Reply