Page 6 of 6
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 2:13 pm
by Antonio Linares
Enrico,
If I properly understand you, what you want should get solved this way:
[\{|
[<oMenuItem>
] | <uAction>\}],;
If with this change is working right, then we modify FiveWin.ch and problem solved
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 2:17 pm
by Antonio Linares
But it is not a proper solution, because that oMenuItem is not this one:
#xcommand MENUITEM [ <oMenuItem> PROMPT ] [<cPrompt>]
because it could be used from the codeblock, but not defined there.
In other words, the codeblock parameter oMenuItem should only exist if it is used from the codeblock inside code. As far as I know the Harbour preprocessor (neither Clipper's one) provides support for that.
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 2:25 pm
by Enrico Maria Giordano
Antonio,
Antonio Linares wrote:Enrico,
If I properly understand you, what you want should get solved this way:
[\{|
[<oMenuItem>
] | <uAction>\}],;
If with this change is working right, then we modify FiveWin.ch and problem solved
Please note that this is only one of many warnings we can receive.
EMG
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 2:27 pm
by Enrico Maria Giordano
Antonio,
Antonio Linares wrote:But it is not a proper solution, because that oMenuItem is not this one:
#xcommand MENUITEM [ <oMenuItem> PROMPT ] [<cPrompt>]
because it could be used from the codeblock, but not defined there.
In other words, the codeblock parameter oMenuItem should only exist if it is used from the codeblock inside code. As far as I know the Harbour preprocessor (neither Clipper's one) provides support for that.
So? Ok, I will lower warning level to try Harbour but we need of a proper solution.
EMG
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 2:30 pm
by Antonio Linares
Enrico,
Clipper did not support that, as far as I know, neither Harbour (or xharbour). If the warning that you get comes from the codeblock (have you checked this ?) then I don't see a solution.
BTW, I am sure that you will love this:
viewtopic.php?p=161905#p161905OMG, just to report a bug...
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 2:31 pm
by Enrico Maria Giordano
I just lowered warnings level from /w3 to /w.
EMG
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 2:36 pm
by Enrico Maria Giordano
Antonio,
Antonio Linares wrote:Enrico,
Clipper did not support that, as far as I know, neither Harbour (or xharbour). If the warning that you get comes from the codeblock (have you checked this ?) then I don't see a solution.
So /w3 and /w2 are not useable with Harbour/FWH.
"How to Donate"? Is it a joke?
Antonio Linares wrote:OMG, just to report a bug...
I don't understand. What bug?
EMG
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 2:49 pm
by cnavarro
Enrico Maria Giordano wrote:Cristobal,
cnavarro wrote:Enrico, look the .ppo
Code: Select all | Expand
oMen := MenuBegin( .F.,,, .F., .F. )
MenuAddItem( "Test",, .F.,, {|oMenuItem|MSGINFO( "OK" )},,,,,,, .F.,,, .F. )
MenuEnd()
If you are suggesting to change tons of lines of code, well, it's not an option.
EMG
Enrico,
Not what I meant
Was only to document where the warning comes from varying oMenuitem
No es lo que queria decir
Solo era para documentar de dónde viene el warning de la variable oMenuitem
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 3:05 pm
by Enrico Maria Giordano
Cristobal,
Understood, thank you.
EMG
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 6:55 pm
by Antonio Linares
Enrico,
In
https://raw.githubusercontent.com/vszakats/harbour-core/master/CONTRIBUTING.md please read from:
# Troubleshooting
Evaluate these points before reporting an issue:
Now read the list of tasks to be done before asking for a question
You will understand what I mean
Re: Migrate to Harbour
Posted: Sat Jul 05, 2014 7:36 pm
by Enrico Maria Giordano
Antonio,
GOSH! It's just like to say "Please do not disturb. We are playing with our toy.".
EMG