1. LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
Lame title, I know.. Spent quite some time, and came up with that..! Doh!
When we declare procedures and functions, the last procedures/functions
aren't visible to the early procedures/functions.
ie;
procedure firstproc()
lastproc()
end procedure
procedure lastproc()
end procedure
If I want to execute lastproc() within firstproc(), I have to make lastproc()
visible/known to firstproc() - and I've been twisting my brains for hours!
Could someone please remind me what to do..?
(And yes - I know I could just move firstproc() declaration below lastproc(),
but in my case it isn't that easy, since both procedures must know of each-
other!)
Kenneth/ZNorQ
2. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
ZNorQ wrote:
> Lame title, I know.. Spent quite some time, and came up with that..! Doh!
>
> When we declare procedures and functions, the last procedures/functions
> aren't visible to the early procedures/functions.
> ie;
>
> procedure firstproc()
> lastproc()
> end procedure
>
> procedure lastproc()
> end procedure
You need routine_id():
integer lastproc_id
procedure firstproc()
call_proc(lastproc_id, {})
end procedure
procedure lastproc()
end procedure
lastproc_id = routine_id("lastproc")
Also see one of my old posts here: http://tinyurl.com/5y7y9
Carl
--
[ Carl R White == aka () = The Domain of Cyrek = ]
[ Cyrek the Illogical /\ www.cyreksoft.yorks.com ]
3. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
Again, please do not type the subject all in caps. It makes spam filters go
nuts.
Regards, Alexander Toresson
4. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
go nuts? What did it do? I would have thought that it would have just
deposited the message in the spam folder, if anything. But it made it go
crazy?
Michelle Rogers
----- Original Message -----
From: "Alexander Toresson" <guest at RapidEuphoria.com>
To: <EUforum at topica.com>
Sent: Tuesday, March 29, 2005 5:15 AM
Subject: Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
>
>
> posted by: Alexander Toresson <alexander.toresson at gmail.com>
>
> Again, please do not type the subject all in caps. It makes spam filters
> go
> nuts.
>
> Regards, Alexander Toresson
>
>
>
>
5. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
> go nuts? What did it do? I would have thought that it would have just
> deposited the message in the spam folder, if anything. But it made it go
> crazy?
I know if I get to many spam messages at once, my spam filter start
swearing at me and proceeds to throw a fit and go on strike. :)
~Greg
6. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
Michelle Rogers wrote:
>
> go nuts? What did it do? I would have thought that it would have just
> deposited the message in the spam folder, if anything. But it made it go
> crazy?
> Michelle Rogers
Yeah, it just jumped out the window, poor thing :(
It just can't stand not being correct.
;)
Regards, Alexander Toresson
7. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
*smirks*
Michelle Rogers
----- Original Message -----
From: "Greg Haberek" <ghaberek at gmail.com>
To: <EUforum at topica.com>
Sent: Tuesday, March 29, 2005 12:53 PM
Subject: Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
>
>> go nuts? What did it do? I would have thought that it would have just
>> deposited the message in the spam folder, if anything. But it made it go
>> crazy?
>
> I know if I get to many spam messages at once, my spam filter start
> swearing at me and proceeds to throw a fit and go on strike. :)
>
> ~Greg
>
8. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
*smirks* sounds like that's a problem with the Spam Filter's pride more
than it is a problem with capital letters
Michelle Rogers
----- Original Message -----
From: "Alexander Toresson" <guest at RapidEuphoria.com>
To: <EUforum at topica.com>
Sent: Tuesday, March 29, 2005 1:22 PM
Subject: Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
>
>
> posted by: Alexander Toresson <alexander.toresson at gmail.com>
>
> Michelle Rogers wrote:
>>
>> go nuts? What did it do? I would have thought that it would have just
>> deposited the message in the spam folder, if anything. But it made it go
>> crazy?
>> Michelle Rogers
>
> Yeah, it just jumped out the window, poor thing :(
> It just can't stand not being correct.
>
> ;)
>
> Regards, Alexander Toresson
>
>
>
>
9. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
Alexander Toresson wrote:
>
> Again, please do not type the subject all in caps. It makes spam filters go
> nuts.
>
> Regards, Alexander Toresson
>
*Note to self; NO CAPS IN HEADINGS.
Done, wont see me do that again! :D
Kenneth/ZNorQ
10. Re: LAST DECLARED PROCS VISIBLE TO EARLY DECLARD PROCS
Carl R. White wrote:
>
> ZNorQ wrote:
>
> > Lame title, I know.. Spent quite some time, and came up with that..! Doh!
> >
> > When we declare procedures and functions, the last procedures/functions
> > aren't visible to the early procedures/functions.
> > ie;
> >
> > procedure firstproc()
> > lastproc()
> > end procedure
> >
> > procedure lastproc()
> > end procedure
>
> You need routine_id():
>
> integer lastproc_id
>
> procedure firstproc()
> call_proc(lastproc_id, {})
> end procedure
>
> procedure lastproc()
> end procedure
>
> lastproc_id = routine_id("lastproc")
>
> Also see one of my old posts here: <a
> href="http://tinyurl.com/5y7y9">http://tinyurl.com/5y7y9</a>
>
> Carl
>
> --
> [ Carl R White == aka () = The Domain of Cyrek = ]
> [ Cyrek the Illogical /\ www.cyreksoft.yorks.com ]
>
>
Yeah, I found out just after I pressed the "send now" button on the
forum.. Typical me. Thanks anyway.
Kenneth / ZNorQ
