Was this feature ever enabled in the commercial version ?
// example
LOCAL Var1 AS CHARACTER
Var1 := 3
seems to compile and run without issue
Any documentation ?
Was this feature ever enabled in the commercial version ?Hi Gary,
// example
LOCAL Var1 AS CHARACTER
Var1 := 3
seems to compile and run without issue
Any documentation ?
In terms of tying, I wrote this so long ago I don't recall the status exactly but IIRC you have to enable HIGHER WARNING level to enable Compile Time warning for static type conflicts.
Il 09/09/2023 01:16, Ron Pinkas ha scritto:
In terms of tying, I wrote this so long ago I don't recall the status exactly but IIRC you have to enable HIGHER WARNING level to enable Compile Time warning for static type conflicts.I tried with -w3 and got no warning. I suppose type checking is disabled.
I had forgotten the W3 level, it always threw warnings a variable was not in use, when it clearly was,
I tried with -w3 and got no warning. I suppose type checking is disabled.
Il 09/09/2023 01:16, Ron Pinkas ha scritto:
In terms of tying, I wrote this so long ago I don't recall the status exactly but IIRC you have to enable HIGHER WARNING level to enable Compile Time warning for static type conflicts.I tried with -w3 and got no warning. I suppose type checking is disabled.
--
Enrico Maria Giordano
http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg
I just checked the sources, and apparently xHarbour has to be compiled with HB_COMP_STRONG_TYPES defined to enable and then W3 or greater.Thanks for checking Ron,
Ron
I just checked the sources, and apparently xHarbour has to be compiled with HB_COMP_STRONG_TYPES defined to enable
and then W3 or greater.
Il 10/09/2023 03:24, Ron Pinkas ha scritto:
I just checked the sources, and apparently xHarbour has to be compiled with HB_COMP_STRONG_TYPES defined to enableOk, thank you. I prefer not to enable it in the official distribution.
Sadly I no longer remember, but if exists it is likely related to the AdaptiveType/StrongType.
Il 10/09/2023 03:24, Ron Pinkas ha scritto:
I just checked the sources, and apparently xHarbour has to be compiled with HB_COMP_STRONG_TYPES defined to enableOk, thank you. I prefer not to enable it in the official distribution.
and then W3 or greater.Greater? I was not aware there are greater warning levels! I tried -w4
with my programs and found no new warnings. The level -w5 is not
accepted, -w4 seems to be the higher warning level. What is the
difference between -w3 and -w4?
--
Enrico Maria Giordano
http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg
Il 10/09/2023 16:43, Ron Pinkas ha scritto:
Sadly I no longer remember, but if exists it is likely related to the AdaptiveType/StrongType.
Ok, thank you. Ron, can you give me write access to the GitHub
repository, please?
Ron, can you give me write access to the GitHub
repository, please?
Il 10/09/2023 16:47, Enrico Maria Giordano ha scritto:I just created an xharbour-org (xHarbour.org) organization on GitHub, transferred the xHarbour repo to xHarbour.org, and gave your ownership role so you can continue as Admin.
Ron, can you give me write access to the GitHubThank you! :-)
repository, please?
--
Enrico Maria Giordano
http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg
FWIW, Here is the current list of ALL Warnings, and their respective level from hbgenerr.c:
const char * hb_comp_szWarnings[] =
I just created an xharbour-org (xHarbour.org) organization on GitHub, transferred the xHarbour repo to xHarbour.org, and gave your ownership role so you can continue as Admin.
Il 10/09/2023 17:57, Ron Pinkas ha scritto:
I just created an xharbour-org (xHarbour.org) organization on GitHub, transferred the xHarbour repo to xHarbour.org, and gave your ownership role so you can continue as Admin.Ok, I don't know what it exactly means but thank you! :-)
Means you now can give write access yourself. Since you have been the person that maintained the project for last years it seems natural that you continue.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 10:17:47 |
Calls: | 10,389 |
Calls today: | 4 |
Files: | 14,061 |
Messages: | 6,416,853 |
Posted today: | 1 |