How to avoid automatic renaming of signature parameters in visual base 6

In Visual Basic 6, I declare sub as follows:

Private Sub test1(ByRef XmlFooOutput As String)
  ...
End Sub

After that, I declare another subtype similar to the following:

Private Sub test2(ByRef xmlFooOutput As String)
  ...
End Sub

Automatically the first method is converted to:

Private Sub test1(ByVal xmlFooOutput As String)
   ...
End Sub

Thus, the XmlFooOutput parameter is converted to xmlFooOutput.

This is a pretty dangerous function because such methods can be mapped to various XSL presentation files that read XML values ​​through Xpath. Therefore, when test1 is renamed, the XSL method associated with test1 is aborted because Xpath points to XmlFooOuput, but the correct value is now in xmlFooOutput.

Is it possible to remove this strange function? I am using Microsoft Visual Basic 6.0 (SP6).

This question has several duplicates:

, , , Intellisense.

+3
2

- VB6 .

, , IDE . .

+3

Visual Basic, , , QuickBasic, , .

OP VB6 test1(), .

- .

0

Source: https://habr.com/ru/post/1737020/


All Articles