Re: Reference Notice

It's a notice. Your soul won't curdle and fall out of your ears just because your code produces a notice which you can easily prevent from being output. Robert Cummings wrote: >I think the reference notice stuff is a bit ridiculous. I mean I can >understand the concern behind: > > function &foo() > { > return $fee.$fii; > } > >But I mean the following gives errors too which is a bit too anal >retentive even for my liking: > > function &foo() > { > $fee = 'bullshitBullshitBullshit'; > > return $fee; > } > > function &fee() > { > return foo(); > } > > fee(); > >Anyways my two cents. Seems moronic that I now need to worry about >stupid reference notices X levels deep in the code for functions that >I'm consuming. I gueeeeeeeeeeeeess I can assign return values EVERYWHERE >to temporary variables just to get rid of the notices, but really, >shouldn't the engine be happy enough returning references to it's own >intermediate variable? I mean, heck, the engine knows enough to print a >warning, it can do the work-- and a hell of a lot faster than developers >having to temporarily assign everything. > >Cheers, >Rob. > >