you wrote that ACL didn't really change, but:
1. The ACL system didn't change from its "roots"
2. There was no update to the phpGACL-API that affects the system.
3. There is a change to the acl_check-function to make transition in the future easier. Since the check is at the moment dependend on $my->usertype and it will change in future versions to $my->id, Louis created a wrapper. The new call would look like this:
* Make sure the user is authorized to view this page
$user = & $mainframe->getUser();
if (!$user->authorize( 'com_config', 'manage' ))
josRedirect('index2.php?', JText :: _('ALERTNOTAUTH'));
More advanced acl-functions will come in Joomla 1.2.
Well, the ACL changed slightly, but sufficiently to break any direct access to the acl tables (as is needed for BC with mambo 4.5.0 API, yes we are stretching far from 4.5.0 up to 1.1)...as some "group_id" and others "xxx_id" columns changed into "id" naming, for reasons unknown to Johan at BC-tests-time. We supposed during our BC-tests that this was due to update to latest phpGACL by Andrew, but we might be wrong. Maybe you have a better explanation of a good reason why the columns changed name between 1.0 and 1.1.
Yes, we noticed also the changes in acl_check, but Louis made them better backwards-compliant during BC-tests.
Yes, I'm noticing and appreciating highly your work on ACL, and also highly appreciating the fact that it's updating will be concentrated into 1 release (1.2).
My wiki article is a first draft... better a start than nothing.
Thanks also for the pointer to mosGetParam, i will recheck. It didn't bother me as it looked BC-compliant