cons-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

cons 2.1.2 issues


From: Zachary Deretsky
Subject: cons 2.1.2 issues
Date: Thu, 2 Nov 2000 12:27:39 -0800

1. Path for QuickScan does not work, Tony's last resort suggestion
to use froward slashes only did not help either.
I believe this is a critical bug.

2. Depends with anonimous array reference does not work:

Depends $CONS [qw(rings.cpy ringspyapi.py)], qw( rings.i rings.ii);

is not executed, but if I put:

Depends $CONS qw(rings.cpy), qw( rings.i rings.ii);
Depends $CONS qw(ringspyapi.py), qw( rings.i rings.ii);

both of them get called.

So this has a workaround which, maybe, should be mentioned in the release
notes.

3. Variables in the Depends and Command methods do not work or
I do not understand how to use them. Only %>:? style works,
something like

Depends $CONS qw(rings.cpy ), qw(
                                        $INCLUDE/rngCommon.hpp
                                        $SWIG/gandalf.i
                              );

does not work, neither does this:

Command $CONS [qw(ringspyapi.pyc ctmpyapi.pyc rtcpyapi.pyc)],
   qw(ringspyapi.py ctmpyapi.py rtcpyapi.py), qq(
    python $CONS->{ENV}{TPCROOT}/lib/pyc/compileall.py %>:d
);

So, how can I refer to the absolute path
$CONS->{ENV}{TPCROOT}/lib/pyc/compileall.py
which is passed through the environment from Construct?

4. It would be nice if QuickScan interface could be changed to just filename
as a parameter. There are at least 2 problems now: the scanner is called too
many times and the filename of the scanned file is not available
for debugging.

Please manifest your wisdom on the above issues!

Thanks, Zach.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]