OpenEuphoria

1. warning from Euphoria

• Posted by judith evans Jul 03, 2008
• 713 views

Warning ( resolution_warning ): Irregular.ew:24 - identifier 'allocate' in 'machine.e' is not included

What is this trying to tell me?

3. Re: warning from Euphoria

• Posted by Jeremy Cowgar Jul 03, 2008
• 702 views

That is a bit of a confusing message. I wonder if we can come up with a better message... I was thinking:

Warning ( resolution_warning ): 
        Irregular.ew:24 - identifier 'allocate' in 'machine.e' is not directly included 

but that's not totally true. For instance, you could have:

-- lib.e 
global function abc() ... 
 
-- mycommon.e 
include lib.e 
 
-- myprog.ex 
include mycommon.e 

and abc() will resolve correctly. What you cannot have is brother/sister includes...

-- mylib.e 
global function abc() ... 
 
-- mycommon.e 
include mylib.e 
 
-- other.e 
abc() 
 
-- myprog.ex 
include mycommon.e 
include other.e 

In the above situation, other.e use to see abc() because include mycommon.e included it, but this is pretty bad practice. Rearrange your include files and all sorts of things begin to break, not to mention, you look at other.e and say, now, where does abc() come from? So, this very problem is what that warning is talking about.

Jeremy

5. Re: warning from Euphoria

• Posted by Jeremy Cowgar Jul 03, 2008
• 681 views

I am not totally sure how this would solve the above problem? Basically you do not want a brother/sister file affecting each other. So, let's say you have a brother file that defines say_hello(). You do not want the ability in the sister file to define a forward reference to say_hello() and access it from the brother file? That solves nothing, as it's still obscure, where is say_hello() actually defined at? The correct solution is to include the files you need in your own file.

I know there are sometimes circular dependencies, but to borrow the classic phrase that is tossed around all the time, refactor. Now, a forward declaration will fix problems in the same file, for instance you want to use function abc() in def() but abc() is not defined yet because it uses def() as well. Thus, a forward reference would fix that, and that is nice at times. I do not see, however, how this would fix brother/sister file includes.

Jeremy

7. Re: warning from Euphoria

• Posted by ChrisB. Jul 03, 2008
• 707 views

I meant, of course forward referincing.

Chris

9. Re: warning from Euphoria

• Posted by ChrisB (moderator) Jul 03, 2008
• 715 views

Hi

In the olden days, when I programmed (dabbled more correctly), I had a heck of a job including files because each of the files that I had incleded had to say what else was included and define each of the functions to be included (or something, I basically gave up in the end, mot=re hassle than it was worth, and stuffed as much as I could in one file as possible)

Euphorias include system is much nicer, and the forward ref issue is easy to work round, with routine_ids, and function shuffling, but wouldn't it be nice not to worry about that?

Brother sister circular includes, when they did occur, could be resolved by the programmer using namespaces where the program required it, with the interpreter stopping with a warning when the situation arose.

As I say no biggy, but I'll just keep chucking it in every now and again. I kept on about a decent forum, and look what we've got now! (cheers btw)

Chris