> The lexical feature would only affect code that enables it specifically, > though. > > Itâs the same situation as signatures: the only things that would see $@ > as an object are code paths that specifically ask for that behaviour. > > -FG > when populating $@ you have to consider context of the code which consumes it (ie handles it) Imagine situation: - your code can generate two exceptions - one will be handled by code expecting $@ to be object - second will be handled by code expecting $@ to be string Best regards, BranoThread Previous | Thread Next