Am 16.07.2010 22:33, schrieb Johan Vromans: >> in any other case I would say you right, but here are no parameters >> involved > > Wrong. You pass the caller's @_ to the subroutine so it possibly > *does* get arguments.
i was aware of that. i mean that the sub doesnt fetch any arguments, and because that you get no effects. > Also, once you start calling some subs with & it could become a > habit to use & for other subroutine calls as well. > > You teach Perl, so you know that it is important to use a consistent > approach throughout. Perl trainees will be much confused if you mix > foo() and &foo in your code. of course consistency is good, but it this case i get an advantage with this syntax and i can describe it like it is. there are some cases in Wx when a & is needed like in callback binding of events or if you create shortcuts of extra long routine names. but that are the only cases and I use it, and i do it consciously. the courses I give are mostly about wxperl for people who already know perl quit perl so i still think its allright :) best > -- Johan >
