Precompiler and Code Contents

[wb]

Hi,
we use the C-Precompiler and have the Problem, that the PL/SQL-Analyser cannot analyse our code.

If we use an #ifdef the Content Pane shows not all functions and procedures.

We had no problems, if we coult define the # as a Symbol for a line-comment like the --.

Is that possible?

Thanks,
wb

 

[Joachim Rupik]

Please edit your plsql.kwf file in PLSD root directory and add the following line in %%words section:

'#'               _dont_care_       st_COMMENT_LINE

In this section you can see a line for -- comments:

'--'              _dont_care_       st_COMMENT_LINE

Joachim Rupik

 

[wb]

Ok, now in the code window it is shown like a comment, but it dosen't change anything in the content pane

When I put an -- infront of the # then everything in the content pane ok, but then our code is not working anymore

 

[Marco Kalter]

Pro*C code is not supported by the Code Contents feature.

 

[wb]

We do not use Pro*C we use the C-preprocessor for our PL/SQL-Code.

Example:

begin
         TRC_SEL ('ps_bestell');
         select *
           into v_ps_bestell
           from ps_bestell
          where mdt_nr     = v_mdt_nr
            and bestell_nr = v_bestell_nr;
       exception
       when no_data_found then
         PUSH_PRO_NR ('04620');
         raise e_error_return;
       end;

In this code are 2 defined macros: TRC_SEL and PUSH_PRO_NR

These macros are no problem for the Code Contents feature, but if we use #ifdef, #endif then we get in trouble.

If we could tell the code contents feature that the # is a line comment symbol, then we had no trouble (I think).

Wolf Beckmann
TEAM GmbH

 

[Joachim Rupik]

Marco,

Is it a bug in Code Contents feature?
Code Contents is not synchronized with editor syntax highligher definitions.

Joachim Rupik

 

[Marco Kalter]

These macros are no problem for the Code Contents feature, but if we use #ifdef, #endif then we get in trouble.

#ifdef and #endif are indeed not supported.

Code Contents is not synchronized with editor syntax highligher definitions.

I'm not sure what you mean. Can you explain?

 

[Joachim Rupik]

Marco:
I thought that when I define additional or redefine an old line comment character (in plsql.kwf file), it should be taken into account in any other places, so also a "Code Contents feature" should treat # as a bigining of line comment and ignore such line. That would be logical!

Joachim Rupik

 

[Joachim Rupik]

Marco,

Already explained.

Joachim Rupik

 

[Marco Kalter]

No, the Code Contents only uses the standard PL/SQL syntax, and does not look at keyword files.

 

[wb]

Hi Marco,
is this something for the new feature list?

Wolf Beckmann
TEAM GmbH

 

[Marco Kalter]

For comments this should be possible. I have added it to the list of enhancement requests.

 

[wb]

Hi Marco,
can you tell me about the Status of this enhancement request?

Wolf Beckmann
TEAM GmbH

 

[Marco Kalter]

It has not yet been implemented in 7.0.0.

 

[wb]

Hi Marco,
we have still the Problem that our functions in a Package are not displayed in the Code Contents.
So again the Question for the Status of this enhancement request?

Thanks,
Wolf Beckmann
TEAM GmbH

 

[Marco Kalter]

We hope to support this for 7.0.3.

 

[wb]

That would be great!

Thanks,
Wolf Beckmann
TEAM GmbH