AutoHotkey Community

In what way do you use the Log and Error Class? For the Class library, an interface will mimic an abstract class (for the most part). For example, you can implement functions in the base class (if you wish), or leave it up to the implementing class. As an abstract class, you won't be able to create objects of that class. Instead, you define a class (e.g. a MyLog class) which would implement the interface, and you could then create MyLog objects.

You ARE allowed getters and setters in an interface - they are only functions. However, you can't define their type or index - this is because an interface CANNOT have data. Instead, the implementing class would be responsible for the details.

Under this setup. You could define a "writeLine" function like this.



In this case, Log_getData would be a getter function which an implementing class would implement - it would return the data for the log file (e.g. a Vector of Strings or a Vector of LogLines - a Class you create). Likewise, Log_addLine would be a static function which would be implemented - this would add the line of text to the specified log file. Note: the above function works regardless how these two functions are implemented. It is up to the implementing class to implement HOW to add the line of text.

Also, notice how static functions can be part of an interface. Since AHK isn't OOP, EVERY function is technically static. This differs from traditional interfaces (e.g. in Java) where static functions cannot be defined.

_________________
As always, if you have any further questions, don't hesitate to ask.

Add OOP to your scripts via the Class Library. Check out my scripts.

OK. The design for interfaces is done, but there's one final question. As posted in my wish list thread, A_ParamCount - to retrieve the number of PASSED parameters, there is no way to detect how many parameters were ACTUALLY passed to a function. Therefore, in the meanwhile, I'm going to use a "reserved" value to detect when an optional parameter wasn't passed.

The problem is that this reserved value couldn't be used as an actual parameter, so the empty string, the obvious choice, isn't an option. For if the empty string was the "reserved string", it couldn't be used as a parameter. I was thinking "C1@s5" (L33T Class). This value should be never been needed (which is a requirement of the "reserved value"), and it's short, so functions with several optional parameters won't have "long" function signatures. Note: this value would be case-sensitive (for performance).


As a reserved value, if passed, the code would think that the parameter (and thus the ones after), were not passed. So, before uploading the latest version of the Class library (with interfaces), I wanted to verify that no one had objections to "C1@s5" being used as the "reserved value".

An example of it's use:



Note: the above function is all that is required to add a "getPurchaseDate" function to the Car interface. The Class_call function handles the details. Because the "reserved value" is used for the default value, the default value in the implementing class would be used when calling the Interface function.

_________________
As always, if you have any further questions, don't hesitate to ask.

Add OOP to your scripts via the Class Library. Check out my scripts.

That sounds fine; I've never have, and never plan to, use that term in my code. Sounds like interfaces are almost ready. Exciting

_________________
Ben

My Trac projects
My Wiki
[Broken] - My music

does this require AHK_L? how does it compare/contrast against AHK_L objects?