I keep finding these little cleanup features to add. Currently, if you
create a package object, you can get access to everything about the package
EXCEPT that main section of code before the first directive. This is
pretty easy to add, but what should we call the method? Do we want to call
it "MAIN"? The ::OPTIONS directive has had PROLOG/NOPROLOG options added
to control whether that gets called at load time. Should we call it
PROLOG? Something else? I'm leaning toward MAIN right now, but I'm not
terribly tied to that if someone has a better suggestion.
Rick
---------- Forwarded message ----------
From: Rick McGuire <[email protected]>
Date: Mon, Oct 13, 2014 at 1:09 PM
Subject: [oorexx:feature-requests] #638 Allow access to the "main" part of
a package object.
To: Ticket 638 <[email protected]>
---
** [feature-requests:#638] Allow access to the "main" part of a package
object. **
**Status:** unread
**Milestone:** None
**Created:** Mon Oct 13, 2014 05:09 PM UTC by Rick McGuire
**Last Updated:** Mon Oct 13, 2014 05:09 PM UTC
**Owner:** nobody
When you create or load a package object, it would sometimes be desirable
to access the "main" section of code as a routine object. Every other
element of the package can be accessed.
---
Sent from sourceforge.net because you indicated interest in <
https://sourceforge.net/p/oorexx/feature-requests/638/>
To unsubscribe from further messages, please visit <
https://sourceforge.net/auth/subscriptions/>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
