FiveTech Software tech support forums

Just as idea maybe TSTRUCT:NSIZE is readonly class variable and cannot be used at left side of assignment statement. Or instead of class referencing TSTRUCT you should use an object name?

You can use LIB utility for extracting object files from a library. As a rule such utility is included in every C compiler.

For example

LIB CLIPPER *OM, Clipper

By the way I think (though I might be wrong) the expression "@!@k" is not valid for PICTURE clause though it may have no any serious consequence. IMO it is better to use @!K before either right quatation mark or a space.

The maximum number of characters in a full path, including the drive letter, colon, leading backslash, file name, and terminating null character, is 260.

Maybe you should use ComboBox (or other control) to let a user select approciated picture format himself?

Vladimir Grigoriev

I have pointed out incompatibility of MEMOWRITE() functions between Harbour and xHarbour on xHarbour forum.

Ops! You are writing about xHarbour but the code for MEMOWRITE() discussed is from Harbour !
I have looked through xHarbour source code for MEMOWRITE() and indeed it has not the third parameter. So xHarbour MEMOWRITE() always writes EOF character! The code from xHarbour is below

HB_FUNC( MEMOWRIT ...

Unfortunately I can not test your code as I have not Harbour. From the source code of memofile.c one should conclude that MEMOWRITE() will work correctly i.e. it will write into file without EOF character if the third parameter will be set to .F..
By the way how do you determine that EOF character ...

I think you mean this code :
if( hb_parinfo(0) == 3 && ISLOG( 3 ) )
bWriteEof = hb_parl( 3 );
Yes I have meant this code above. So maybe there is a bug in your Harbour build or there is another idea. What about your string data <text> contains EOF character itself? Can you test last character of ...

As I have understood the new function MEMOWRITE() has three parameters. The third parameter of type Logical specifies either to write EOF character ( .T. by default) or not (.F.).
So you should specify MEMOWRITE() function with three parameters and the third parameter should be specified as .F..

In Clipper MEMOWRITE() is nothing more than sequence of the functions fopen(), fwrite(), fclose(). The only thing MEMOWRITE() does itself is appending EOF character. Though I don't use Harbour but I think the same is justly for Harbour. So you can use fopen(), fwrite(), fclose() functions by youself ...

This is an idea! It need to be tested.

In fact can be bought! For example what about xHarbour "professional" or some releases of Linux published, for example, by Red Hat? If you have enough capital you can buy a project and turn buissness such away that you program will reduce to zero all efforts of open source project!

I did not test but can be a such situation that BEGIN SEQUENCE will intercept an error which occured inside MyFunc() and wil be difficult to distinguish if the error is generated by the absence of the function or by the function itself?

And where is this company? By the way is this company CA? Or Borland is searching another killer?