that's an interesting comment. Yes, it shouldn't be a problem. It is quite definitely a feature of SVG, an essential key to its flexibility. So even more than expecting it, I should have been looking forward to it.

I'm just looking for the right programming manner in which to express that flexibility. Many features become problems due to a context or situation with unaligned constraints. Choosing Image::LibRSVG and its comparatively small number of methods is just such a situation. And I mean my choice of the module, not the module itself ... I'm taking about the design decision.

I'm not sure I should apologise though. It's just far too common a perspective to take. At best I was cavalier in calling it a problem. At worst, careless. I could have made two spelling mistakes instead, I don't think it would be graver.