Book a Demo
« previous next »
Pages: [1]

Author Topic: Import C# - Operations vs Attributes  (Read 3487 times)

buckbuchanan

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Import C# - Operations vs Attributes
« on: December 06, 2010, 03:48:00 pm »
Hi

Why is it that when I import from C# files, all my properties are imported as Operations, rather than Attributes?

Thanks.
Logged

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Import C# - Operations vs Attributes
« Reply #1 on: December 06, 2010, 05:00:17 pm »
Because that's the way EA sees Proerties.

I have some issues with the way EA handles Properties in general (See: Property Redux).

You might also be interested in : UML Properties - quo vadis Attributes?

If you agree with the proposal, formally submit a feature request - the original (over 5 years old) must have been lost in the recent floods near Sparx HQ.

HTH,
Paolo
« Last Edit: December 06, 2010, 05:08:57 pm by PaoloFCantoni »
Logged
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

buckbuchanan

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Import C# - Operations vs Attributes
« Reply #2 on: December 06, 2010, 05:08:07 pm »
Thanks for that info. I hoped there would be an option I could set  :'(
Logged

buckbuchanan

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Import C# - Operations vs Attributes
« Reply #3 on: December 07, 2010, 09:00:47 am »
... and I have also submitted a feature request. I think the way EA handles properties, both reverse engineering and generating code, is very poor.

Thanks for your advice!
Logged

Kevin G. Watson

  • EA User
  • **
  • Posts: 217
  • Karma: +0/-0
  • I love EVERYTHING including Microsoft
    • View Profile
Re: Import C# - Operations vs Attributes
« Reply #4 on: December 08, 2010, 07:21:36 pm »
Hi'ya....

In fairness UML doesn't have the concept of 'Properties'...  I know at some point the OMG kinda thought it'd be cute to stop using 'Attributes' (fields to sharpe heads) and started using property...

Strictly C# Property accessors are operations are they not, what handling would sir like?

Kevin [smiley=2vrolijk_08.gif]
Logged

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Import C# - Operations vs Attributes
« Reply #5 on: December 08, 2010, 07:44:36 pm »
Quote
Hi'ya....

In fairness UML doesn't have the concept of 'Properties'...  I know at some point the OMG kinda thought it'd be cute to stop using 'Attributes' (fields to sharpe heads) and started using property...

Strictly C# Property accessors are operations are they not, what handling would sir like?

Kevin [smiley=2vrolijk_08.gif]
Yes Kevin, that's true about UML, but there are lots of things that EA handles that aren't UML...

Also, true the Accessors are operations but the C# Property itself behaves more like a structural feature.  Since they are all elements of the C# language it would help if EA linked the two bits better.

Paolo
Logged
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

buckbuchanan

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Import C# - Operations vs Attributes
« Reply #6 on: December 09, 2010, 08:02:08 am »
Quote
Strictly C# Property accessors are operations are they not, what handling would sir like?[smiley=2vrolijk_08.gif]
Sir would like the choice if it isn't too much trouble  :)
Logged
Pages: [1]
« previous next »