Hi Przemek,
to keep -w hbppgen option semantic as is. Does anyone find it as
a problem?
I've checked and I don't get the way it works now, maybe
it's just me. I might be wrong, but simply running
'hbppgen test.prg' does nothing, I have to use
'hbppgen test.prg -w', to get the .ppo. It's a little
strange to me :/
I can make -w default when -o and -v is missing or I will have to
Good idea.
create new switch to disable .ppo output for build time when this
tool is used to generate .c file with std.ch rules.
It's fine as it is.
Also, the help text says: '-w write .ppo
input file', shouldn't it rather say 'output file'?
It's probably result of my fatal English but full option name is:
"write preprocessed (.ppo) input file"
and I though about "preprocessed (.ppo) input (.prg) file."
If it confuse user then I will have to change it. Maybe simple:
"write preprocessed (.ppo) file"
will be enough.
Yes, that's perfect.
In any case, instead of not doing anything ('hbpp test.prg')
I think it would be helpful to show some message about
what's going on.
And one thing else I forgot. This version of hbpp by default
does not have any rules hardcoded inside. We can add them
by recompiling hbpp after generating the pptable.c but personally
That seems too complicated.
I like such behavior and I'd prefer to only add support for
-u<file> use command def set in <file>
I agree. We may also consider looking for a default
std.ch in std INCLUDE dirs. If not found, show a warning.
Simple -u disables this, and -u<file> overrides it with
another file.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
