στις 24/03/2010 12:01, O/H Viktor Szakáts έγραψε:
WORKING -------------------------------------
C:\DEV\Harbour\Mytests>hbrun tst.prg

aa->DACC : hello
aa->&("DACC") : hello
Press any key to continue...
C:\DEV\Harbour\Mytests>

NOT WORKING -------------------------------------
C:\DEV\Harbour\Mytests>hbmk2 tst.prg
hbmk2: Processing configuration: C:\Harbour\bin\hbmk.cfg
Harbour 2.1.0dev (Rev. 14220)
Copyright (c) 1999-2010, http://www.harbour-project.org/
Compiling 'tst.prg'...
Lines 13, Functions/Procedures 1
Generating C source output to 'E:\WIN_TEMP\tst.c'... Done.

C:\DEV\Harbour\Mytests>tst

aa->DACC : hello
Error BASE/1449  Syntax error:&
Called from MAIN(9)
C:\DEV\Harbour\Mytests>
----------------------------------------------------------------------

Exactly the same error generates the line:

Public&mVar. := Len(_HMG_SYSDATA [  66 ]) + 1

Very interesting. Here they both compile cleanly
(and first one also works) alright even with latest SVN.

Here is tested code (unaltered):
---
DBCREATE( "aa.dbf", { { "DACC", "C", 10, 0 } } )

use aa.dbf alias aa new
DBAPPEND()
aa->DACC := "hello"
? "aa->DACC :", aa->DACC
? 'aa->&("DACC") :', aa->&("DACC")
---

---
LOCAL _HMG_SYSDATA
Public&mVar. := Len(_HMG_SYSDATA [  66 ]) + 1
---

Double check your environment and test .prg,
because it's almost sure there is something
wrong with it.

Brgds,
Viktor


Ok, I will try to check my env. (although i'm not sure what exactly should I look for, since everything looks simple & clean. -I am just setting paths and let the hbmk2 do the rest.)
BTW, is there any possibility to be the problem O/S related?
I 'm getting the error(s) on my every-day-use WIN2K box. On a WinXPPRO machine (where I make clean harbour's builds) everything works w/o prob. However binaries (exes and libs) on WIN2K box are copy/pasted from WinXPPRO.


regards,

---
Pete











_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to