Ticket #2 (closed defect: fixed)
Let/set properties problem
| Reported by: | xyon75 | Owned by: | sevo |
|---|---|---|---|
| Priority: | major | Component: | doxyvb |
| Version: | 2.3 | Keywords: | property let set |
| Cc: |
Description
Hi, first of all i really want to thank you for your great work!
Now the problem.. VB6 Properties recognition doesn't work really well: the c# parsing of the vb6 document loses the definition of the LET and SET properties, so if i define a property with only the LET/SET method, there's no trace of it in the generated doc.
It seems that the c# parser only keeps the GET properties saying they are defined as both get and set.
Can this be fixed?
Thanks again!
Change History
comment:2 Changed 5 months ago by sevo
- Status changed from accepted to closed
- Resolution set to fixed
Ok,
I've managed to fix that partially. The problem is that Get/Let/Set are completely independent blocks in classic VB (in VB.NET properties have always only one block). So it is really hard to recognize a Set/Let while Get gets parsed.
The partially fix in r38 requires Get to preceed Set/Let to get the property recognized as RW. If there is no Set/Let in the code before the Get block, the property will stay ReadOnly.
