RE: namespacing

new topic     » topic index » view thread      » older message » newer message

Chris Bensler wrote:
> I am writing a library with the function or_all() in it. The file that 
> includes this library, also has a function named or_all(). I would 
> expect to get a collision error or warning, but I don't.
> 
> Shouldn't it be telling me that there is a namespacing conflict?
> 
> Also, if I include x.ew and I include .\x.ew, then a collision DOES 
> occur, even though x.ew is the same file.
> If any library is included twice, and the include statement is relative, 
> 
> a collision occurs.
> 
> Also, shouldn't includes be relative to the directory of the file that 
> called them, instead of the directory of the main source?
> 
> EG:
> <\\dirA\fileX.exw>
> include dirB\fileY.ew
> <end>
> 
> <\\dirA\dirB\fileY.ew>
> include dirC\fileZ.ew
> <end>
> 
> That will not work. You need to do it this way....
> 
> <\\dirA\dirB\fileY.ew>
> include dirB\dirC\fileZ.ew
> <end>
> 
> 
> Chris

  It seems to me when I was complaining about how the
  the namespaces worked about a month a go you said
  that you saw nothing wrong with the way it worked.

Bernie

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu