Sorry, didn't see this message untill now (PM me if you need a quick reply to a new *thread*).

I removed EXPORT from PortablE, and replaced it with PUBLIC and PRIVATE. By default all PROCs/etc declarations are public. PUBLIC & PRIVATE must be on their own line, and affects all declarations after it.

PortablE's backwards compatibility mode (OPT AMIGAE) stops it from reporting errors about EXPORT (but it merely ignores it).


There is currently no "ShowModule" utility, mainly because all PortablE modules are source code (rather than .m object code) and so are human-readable in the first place.

Quote:
You can declare methods as PRIVATE in the same way that procedures/etc can be. Of course such methods are not accessible outside of the module, not even for parent classes.

PortablE also supports PROTECTED object *members*, but currently not *methods*. If that is a problem, then one possible work-around is have 'protected' members declared in a child class, but to cast that class to the parent class when returning it.

Hello,

I'm working on porting my hashtable routine to PortablE in the hopes that type-safety will make it easier to find the bugs. The first thing that the compiler told me when compiling my port is that the hash function and the umod (unsigned modulo replacement) do not recognize the EXPORT directive for module visibility. Is this a change in PortablE over AmigaE? Note that those two procedures are not methods.

The reason I'm asking is that if a show-module utility for PortablE exists, I'd like it to only list the EXPORTed procedures. Also, is it possible to make a private constructor so that I can use a factory method to create an iterator?

Thanks,

--Sam