【问题标题】:Delphi SysUtils.Supports unexpectedly returns trueDelphi SysUtils.Supports 意外返回 true
【发布时间】:2018-08-08 21:21:02
【问题描述】:

我正在根据 Spring4d 的文档示例制作 eventPublisher

不同之处在于订阅者必须明确订阅事件。

我想根据他们是否触发他们的 Handle 程序 实现IEventHandler<TEventType>接口。

发布传入事件时,我使用事件的类名和 Spring4d 的 TType.FindType('IEventHandler<TEvent1>') 找到 IEventHandler<TEventType> 类型引用

然后我遍历我的订阅者(实现 IEventHandler 接口的对象)并检查它是否支持 IEventHandler 类型。

问题是 Supports 方法返回 true 即使订阅者没有实现接口。

另外,我尝试列出TMyEventHandler2 类型的接口。 它包含IEventHandler<TEvent2>??

我相信这是由于 IEventHandler<TEvent2> 的限制 和 IEventHandler<TEvent1> 共享相同的 GUID

有解决办法吗?

使用这些类和接口:

TEvent1 = class(TObject)
end;

TEvent2 = class(TObject)
end;

IEventHandler = interface(IInvokable)
[guid]
procedure Handle(aEvent : TObject);
end;

IEventHandler<T : class> = interface(IEventHandler)
[guid]
procedure Handle(aEvent : T);
end;

TMyEventHandler1 = class(TObject, IEventHandler, IEventHandler<TEvent1>)
public 
procedure Handle(AEvent : TObject); overload;
procedure Handle(AEvent : TEvent1); overload;
end;

TMyEventHandler2 = class(TObject, IEventHandler, IEventHandler<TEvent2>)
public 
procedure Handle(AEvent : TObject); overload;
procedure Handle(AEvent : TEvent2); overload;
end;

TEventPublisher = class(TObject)
public
  fSubscribers : IList<TValue>;
  procedure Subscribe(aSubscriber : TValue);  // Simply adds the subscriber to the list of subscribers
  procedure Publish(aEvent : TObject); // Publishes an event to the subscribers
end;

procedure TEventPublisher.Publish(const event: TObject; ownsObject: Boolean = True);
const
  IEventSubscriberName = 'IEventSubscriber<*>';
var
  consumerTypeName: string;
  consumerType    : TRttiType;
  intfType        : TRttiInterfaceType;
  subscriber      : TValue;
  subscribed      : IInterface;
  lEventSubscriber: IEventSubscriber;
  lIntfs          : IReadOnlyList<TRttiInterfaceType>;
begin

  consumerTypeName := StringReplace(IEventSubscriberName, '*', GetQualifiedClassName(event), []);
  consumerType     := TType.FindType(consumerTypeName);
  intfType         := consumerType as TRttiInterfaceType;

  for subscriber in fSubscribers do
  begin

    lIntfs := TType.GetType(subscriber.AsObject.ClassInfo).GetInterfaces();

    // lIntfs for TMyEventHandler2 containts IEventHandler<TEvent1> ???

    if Supports(subscriber.AsObject, intfType.GUID, subscribed) then
      if Supports(subscriber.AsObject, IEventSubscriber, lEventSubscriber) then
      begin
        intfType.GetMethod('Handle').Invoke(TValue.From(@subscribed, intfType.Handle), [event])
      end;
  end;

  if ownsObject then
    event.Free;
end;


lEventPublisher := TEventPublisher.Create;
lEventPublisher.Subscribe(TMyEventHandler1.Create);
lEventPublisher.Subscribe(TMyEventHandler2.Create);
lEventPublisher.Publish(TEvent1.Create); // Will both trigger TMyEventHandler1.Handle and TMyEventHandler2.Handle. Why ??

【问题讨论】:

  • 是的,这是意料之中的,也是单一 guid 的结果
  • 是的,这是意料之中的,正如@David 所说,不,没有解决方法,除了在这种情况下不使用 generic 接口。

标签: delphi reflection interface rtti spring4d


【解决方案1】:

发生这种情况是因为如果您将 guid 放在泛型接口上,则该接口的每个特化都将具有相同的 guid,而不管其泛型类型参数。

我通常通过在接口中提供有关该信息的方法来解决此问题(例如 Spring.Collections.IEnumerable 有一个 ElementType 属性来获取 IEnumerable&lt;T&gt; 的实际类型)。

所以实现看起来像这样:

program GenericEventPublisher;

{$APPTYPE CONSOLE}

uses
  Spring,
  Spring.Collections,
  System.SysUtils;

type
  IEventHandler = interface
    ['{2E4BD8F4-4EB8-4B33-84F4-B70F42EF9208}']
    procedure Handle(const event: TObject);
  end;

  IEventHandler<T: class> = interface
    ['{82B7521E-D719-4051-BE2C-2EC449A92B22}']
    procedure Handle(const event: T);
    function GetHandledClass: TClass;
  end;

  IEventPublisher = interface
    ['{2A460EF0-AE27-480F-ACEA-1B897F2DE056}']
    procedure Subscribe(const subscriber: IEventHandler);
    procedure Publish(const event: TObject; ownsObject: Boolean = True);
  end;

  TEventHandlerBase<T: class> = class(TInterfacedObject, IEventHandler, IEventHandler<T>)
  private
    function GetHandledClass: TClass;
    procedure Handle(const event: TObject); overload;
  public
    procedure Handle(const event: T); overload; virtual; abstract;
  end;

  TEvent1 = class
  end;

  TEvent2 = class
  end;

  TMyEventHandler1 = class(TEventHandlerBase<TEvent1>)
  public
    procedure Handle(const event: TEvent1); override;
  end;

  TMyEventHandler2 = class(TEventHandlerBase<TEvent2>)
  public
    procedure Handle(const event: TEvent2); override;
  end;

  TEventPublisher = class(TInterfacedObject, IEventPublisher)
  private
    fSubscribers: IList<IEventHandler>;
  public
    constructor Create;
    procedure Subscribe(const subscriber: IEventHandler);
    procedure Publish(const event: TObject; ownsObject: Boolean = True);
  end;

{ TEventPublisher }

constructor TEventPublisher.Create;
begin
  fSubscribers := TCollections.CreateList<IEventHandler>;
end;

procedure TEventPublisher.Publish(const event: TObject; ownsObject: Boolean);
var
  subscriber: IEventHandler;
  eventSubscriber: IEventHandler<TObject>;
begin
  for subscriber in fSubscribers do
    if Supports(subscriber, IEventHandler<TObject>, eventSubscriber)
      and (eventSubscriber.GetHandledClass = event.ClassType) then
        eventSubscriber.Handle(event);

  if ownsObject then
    event.Free;
end;

procedure TEventPublisher.Subscribe(const subscriber: IEventHandler);
begin
  fSubscribers.Add(subscriber)
end;

{ TEventHandlerBase<T> }

function TEventHandlerBase<T>.GetHandledClass: TClass;
begin
  Result := T;
end;

procedure TEventHandlerBase<T>.Handle(const event: TObject);
begin
  Assert(event is T);
  Handle(T(event));
end;

{ TMyEventHandler1 }

procedure TMyEventHandler1.Handle(const event: TEvent1);
begin
  Writeln(event.ClassName, ' handled by ', ClassName);
end;

{ TMyEventHandler2 }

procedure TMyEventHandler2.Handle(const event: TEvent2);
begin
  Writeln(event.ClassName, ' handled by ', ClassName);
end;

var
  eventPublisher: IEventPublisher;
begin
  eventPublisher := TEventPublisher.Create;
  eventPublisher.Subscribe(TMyEventHandler1.Create);
  eventPublisher.Subscribe(TMyEventHandler2.Create);
  eventPublisher.Publish(TEvent1.Create);
  eventPublisher.Publish(TEvent2.Create);
end.

由于接口上存在类约束,我们可以确保无论 T 的类型如何,接口都是二进制兼容的(因为它们只能是对象)。此外,使用通用事件处理程序的基本类型可以减少要编写的额外代码。它只是将非泛型Handle 方法重定向到必须在具体实现中实现的泛型方法。

此外,由于基类实现了这两个接口,我们不需要将处理程序存储在TValue 列表中,而是可以使用非通用接口类型并轻松访问它们而无需 RTTI。

现在Publish 方法使用了一个小技巧,用IEventHandler&lt;TObject&gt; 调用Support - 因为eventSubscriber 属于那种类型,我们可以将event 参数传递给它的Handle 方法,它恰好是正确的 - 这是因为我之前解释过的二进制兼容性,因为我们只是将不同的类作为 T 类型处理 - 如果我们没有该类约束,故事将完全不同。

【讨论】:

    猜你喜欢
    • 2022-07-12
    • 2017-10-06
    • 2015-05-10
    • 1970-01-01
    • 2021-02-14
    • 2015-08-18
    • 1970-01-01
    • 2020-04-21
    • 2020-12-08
    相关资源
    最近更新 更多