Comparison with procedure-based programming PUBLIC and PRIVATE events
- Last Updated: March 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
Comparison with procedure-based programming PUBLIC and PRIVATE events
By comparison, named events are always PUBLIC by
default, which means that handlers can be subscribed (through the SUBSCRIBE statement)
to named events from within an owning super procedure stack or from
any code that has a handle to the procedure object that owns the
event and its handler procedures. You can also define internal procedures
as PRIVATE to restrict handler subscriptions for
named events to the defining procedure.