NetTalk Central

Author Topic: Global, really? yikes  (Read 3376 times)

Poul

  • Full Member
  • ***
  • Posts: 160
    • View Profile
Global, really? yikes
« on: November 28, 2008, 05:13:50 PM »
I just noticed that some of my procedures do not obey this rule.

Quote
The procedure must have the Declare Globally option ticked on.

As far as i can tell this has not had any adverse affects, but as i reviewed Bruces new NetBrowse Template documentation - the word must aroused my concern. i rember in the past this was certainly true, but in recent times I have paid it no mind, when i check sure enough many of my browses are unticked.

Whats the implication of not being Declared Global?

ps  See bruce, your documentation does get read <g>

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: Global, really? yikes
« Reply #1 on: November 28, 2008, 09:46:54 PM »
Hi Poul,

>> See bruce, your documentation does get read <g>

miracles...

Seriously though - there's no implication if you leave it off, and the app compiles ok. (Which it quite probably does.) If you get a compile error in the WebHandler about unknown functions then turn Generate Globally on.

so as long as it compiles you're ok.

Cheers
Bruce