Przemyslaw Czerpak wrote:
It looks very nice. Can youy add it to compiler?
In such case we can make two things:
1. we can extract local file name (hb_compLocalVariableName())
2. we can activate this analyse phase before HB_P_NOOP optimization
and strip unnecessary code by filing it with NOOP p
Hi Mindaugas,
> > It looks very nice. Can youy add it to compiler?
> I thought that you'll find an easier way to generate these warnings
> using pExpr tree :) Like there was with push/pop optimisation with jump
> in between some time ago.
Unfortunately it's not possible without serious compiler
Hi,
It looks very nice. Can youy add it to compiler?
I thought that you'll find an easier way to generate these warnings
using pExpr tree :) Like there was with push/pop optimisation with jump
in between some time ago.
This is not real deadcode. In dead code eliminator inside compiler
I
Hi Mindaugas,
Sorry for late response but I still haven't received any messages
from Harbour-devel list so I'm coping them from Harbour mail list
archive.
Phil - I really need your help.
> I've just finished to implement a "test" program for PCode analysis. It
> is capable to test PCode for corr
