There are some differences between Harbour and xHarbour.
Harbour hb_compileBuf() is very powerfull as no external Harbour.exe is required. xHarbour should provide it.
Also, as you have seen, __HrbRun() is a little different too. But using it with HRB files from disk, they will behave the same.
__HrbRun( <file.hrb> )
// or
cHrb := memoread( "file.hrb" )
pBody := __hrbload( cHrb ) // __hrbload( "file.hrb" ) also works
// pBody is pointer variable
__hrbdo ( pBody )
// or we can make a small function
FUNCTION XHRBRUN ( cSource ) // can be file on disk or buffer in memory
RETURN __HrbDo( __HrbLoad( cSource ) )
// note: this is from the sourc of ver 99.70
// works with ver 99.71NageswaraRao,
Better rename cSource as cHRBFileName to avoid confusions, thanks
FUNCTION xHrbRun( cHRBfileNameOrcHRBCode )
LOCAL pHrb
__HrbRun( pHrb := __HrbLoad( cHRBfileNameOrcHRBCode ) )
__HrbUnload( pHrb )
RETURN NIL
// Note: arguments support still to be addedAntonio Linares wrote:My mistake, you can directly execute it from memory too
__HrbRun( MemoRead( "another.hrb" ) )
nageswaragunupudi wrote:Yes thanks. I forgot to unload the pointer.
FUNCTION xHrbRun( cHRBfileNameOrcHRBCode ) LOCAL pHrb __HrbRun( pHrb := __HrbLoad( cHRBfileNameOrcHRBCode ) ) __HrbUnload( pHrb ) RETURN NIL // Note: arguments support still to be added
The above function can be used for .hrb file on disk or hrb compiled code in memory ( ideal for storing in database and execute retrieved code )
Application
===========
Path and name: C:\A\AMDI\eng32.exe (32 bits)
Size: 2,767,360 bytes
Time from start: 0 hours 0 mins 7 secs
Error occurred at: 2007.11.02, 18:43:23
Error description: Error BASE/9999 Corruption detected: __HRBLOAD
Args:
Stack Calls
===========
Called from: => __HRBRUN(0)
Called from: ENG32.PRG => XHRBRUN(2190)
Called from: ENG32.PRG => TAPPLIC:SCRPT(1819)
Called from: ENG32.PRG => (b)TAPPLIC:BUILDBAR(691)
Called from: btnbmp.prg => TBTNBMP:CLICK(0)
Called from: btnbmp.prg => TBTNBMP:LBUTTONUP(0)
Called from: window.prg => TWINDOW:HANDLEEVENT(0)
Called from: control.prg => TBTNBMP:HANDLEEVENT(0)
Called from: window.prg => _FWH(0)
Called from: => WINRUN(0)
Called from: window.prg => TMDIFRAME:ACTIVATE(0)
Called from: ENG32.PRG => TAPPLIC:ACTIVATE(344)
Called from: ENG32.PRG => MAIN(109)Rimantas,
>
Only one question - can we use FWH syntax in this externals prgs ? That's the "another.prg" can contain DIALOG , BUTTONS , GET in FWH syntax ? Also it's one important - will that suport native class ? I'm using xHarbour Bcc ...
>
Yes 
Rimantas,
Please try the test I posted
Antonio Linares wrote:Rimantas,
Please try the test I posted
__HrbRun( MemoRead( "another.hrb" ) )
I'm confused. What is in an .HRB file? Is it simply FW code? If so, then could we just read a PRG? Any PRG?
__HrbRun( MemoRead( "another.prg" ) )
James
James,
> What is in an .HRB file?
HRB is a binary file (not ascii) that contains some specific Harbour information (pcode, symbols table).
Its called "Harbour portable file" as theoretically could be executed on any operating system, as it does not include any operating system related info.
Does any one know the equivalent of Harbour's hb_compileBuf() in xHarbour please?
afaik, it is not implemented in xharbour 
Sad. Missing a really powerful and very useful function.
cFilePrg := "myprg.prg"
__Run( "harbour "+cFilePrg+" -i -gh -m -n -b " )
Estoy probando generar la compilación hrb para poder compilar un archivo hrb ahora para ejecutar este archivo como si fuera un archivo ejecutable de otro archivo ejecutable. ¿Alguien sabe o tiene alguna idea?
