in reply to Re: Micro optimisations can pay off, and needn't be a maintenance problem
in thread Micro optimisations can pay off, and needn't be a maintenance problem
Indeed, positioning the use constant... calls inside the function body in the short example is misleading. Sorry.
As constants constructed this way become constant subs, they end up having package scope just as any sub would. It probably makes sense to have them grouped at the top of the package as shown in the benchmark code, or grouped above the sub which they are related to if the package is bigger, but in anycase, in a position where their scope is (more) obvious from their position. I'll change that. Thanks.
Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.
|
|---|