Welcome to the Lounge

Jim_Snyder wrote:

For some Markdown Formatting reason, I cannot get Processing.Fire to display in the block.

Bizarre. Works for me!

GuyThiebaut wrote:

insert a field in the middle of the others and the thing will go kaboom

Richard Deeming wrote:

Does it make sense for the properties to be writeable?

public class ProcessEventArgs : EventArgs
{
  public IMembrane FromMembrane { get; protected set; }
  public IReceptor FromReceptor { get; protected set; }
  public IMembrane ToMembrane { get; protected set; }
  public IReceptor ToReceptor { get; protected set; }
  public ISemanticType SemanticType { get; protected set; }

  public ProcessEventArgs(IMembrane fromMembrane, IReceptor fromReceptor, IMembrane toMembrane, IReceptor toReceptor, ISemanticType st)
  {
    FromMembrane = fromMembrane;
    FromReceptor = fromReceptor;
    ToMembrane = toMembrane;
    ToReceptor = toReceptor;
    SemanticType = st;
  }
}

public class ProcessEventArgs : EventArgs
{
  public IMembrane FromMembrane { get; }
  public IReceptor FromReceptor { get; }
  public IMembrane ToMembrane { get; }
  public IReceptor ToReceptor { get; }
  public ISemanticType SemanticType { get; }
 
  public ProcessEventArgs(IMembrane fromMembrane, IReceptor fromReceptor, IMembrane toMembrane, IReceptor toReceptor, ISemanticType semanticType)
  {
    FromMembrane = fromMembrane;
    FromReceptor = fromReceptor;
    ToMembrane = toMembrane;
    ToReceptor = toReceptor;
    SemanticType = semanticType;
  }
}

Processing.Fire(this, new ProcessEventArgs(
  fromMembrane: fromMembrane,
  fromReceptor: fromReceptor,
  toMembrane: membrane,
  toReceptor: target,
  semanticType: obj
));

Richard Deeming wrote:

Also, named parameters can make the constructor look more like the object initializer:

Richard Deeming wrote:

Also, named parameters can make the constructor look more like the object initializer:

Pete O'Hanlon wrote:

More importantly, the second example implies that you have opened up the scope of the properties to be read/write as opposed to read only

Johnny J. wrote:

I'm old school, so the second one any day!

Tim Carmichael wrote:

I prefer the first; I can see what the arguments are on each line without having to scan a list looking for something.

Jeremy Falcon wrote:

For me, code is like art. You make it look pretty and readable on a case-by-case basis. If it makes sense to do something then you do it, but it doesn't always mean you do the same thing every time for the rest of your life.

Marc Clifton wrote:

Which form do you prefer? Why?

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]

auto pea = new ProcessEventArgs(fromMembrane, fromReceptor, membrane, target, obj);
Processing.Fire(this, pea);