Beware changed signatures

General
1

I just ran into this:

<https://xojo.com/issue/58935>

I have a FolderItem subclass that overrides various methods, including Child. But the signature of Child has changed to add an optional followAlias parameter, so my override was being silently ignored and breaking code.

Check your subclasses for any functions that override native ones where the signature has changed. I don’t know if this has happened anywhere else, but be aware.

2

This was introduced in r2
Public Function Child(name As String, followAlias As Boolean = True) As FolderItem
Public Function ChildAt(index As Integer, followAlias As Boolean = True) As FolderItem
Public Function Children(followAlias As Boolean = True) As Iterable

3

The new methods aren’t an issue, of course.