Re: WxPerl best practices

2010-07-16 Thread herbert breunung
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 bec

Re: WxPerl best practices

2010-07-16 Thread Dodger
On 16 July 2010 13:33, Johan Vromans wrote: > herbert breunung writes: > >> 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. > Also, once you start calling some subs with &

Re: WxPerl best practices

2010-07-16 Thread Johan Vromans
herbert breunung writes: > Am 15.07.2010 11:15, schrieb Johan Vromans: > > Calling subroutines with & is explictly advised > > against, and with reason. > > which reason? You already hint at parameters... Calling a subroutine with & bypasses context coercion and also passes the caller's @_ whic

Re: WxPerl best practices

2010-07-16 Thread Eric J. Roode
On the topic of "Best Practices": Here is a tutorial I came across: http://www.pnelsoncomposer.com/FAQs/wxWidgetsFAQ.html#Q4A It's C++, but that is irrelevant to the concepts involved. The author suggests that all panels should be both children of and parents of sizers. But he doesn't say w