Book a Demo

Author Topic: VB.NET Parser Bugs?  (Read 3731 times)

YoPapa

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
VB.NET Parser Bugs?
« on: June 05, 2002, 02:37:13 pm »
Hi everyone,

I just tried out EA and it looks like a really nice program. However, I have come across what I think might be bugs in the VB.NET parser. Maybe I am just doing something wrong, but before I buy the program, I would like to make sure that it works  :)

So here goes - I came across the problem by doing the following:

1.) create a class diagram, say, for class "Class1" (as VBNet).

2.) add a function, say, "Function1", with 2 "in"-parameters x1 and x2, maybe of type String; the return value of type Integer.

3.) now forward-engineer to vb.net. the vb.net code is ok up to this point.

4.) modify the vb.net code to read "ByRef" instead of "ByVal" for one of the parameters, and save it.

5.) go back to EA and synchronize - the class diagram will *not* reflect the change just made. (bug #1?)

6.) forward-engineer again, without overwriting the vb.net file (i.e., let EA update it instead, as it does by default) - the parameter will again by ByVal, and the return value will now be of type "IntegerInteger" (bug #2?)

7.) repeating step 6 will yield return type "IntegerIntegerInteger", and so on.

What am I doing wrong?  ???

gsparks

  • EA User
  • **
  • Posts: 325
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Re: VB.NET Parser Bugs?
« Reply #1 on: June 05, 2002, 10:57:53 pm »
Hi,

I checked this out and found the problems. We will be releasing an update to EA in the next couple of days that will correct these problems. Specifically:

Repeated return type in synchronized VB.Net code
Support for synchronizing (reversing) parameter information (name kind etc)

Plus:
Support for default parameter values in VB.Net (force use of Optional keyword)

These will be in build 494 ... I will try and organise for this to be released in the next couple of days.

Geoff Sparks