Re: Error in opening the Library module file

Richard Maine wrote:
| Jugoslav Dujic <jdujic@xxxxxxxxx> wrote:
|
|| Right, "cyclic" or "circular". What you had is (as far as I can tell)
|| allowed by the standard but it will confuse most compilers -- they
|| expect the dependency hierarchy to be "tree-like" and cannot tell which
|| module should be compiled first (esp. when they're in the same source
|| file).
|
| No. Cyclic module dependency is not allowed by the standard. Not only is
| it a matter of which should be compiled first, but also it is possible
| (easy, in fact) for a cyclic dependency to have contradictions. A
| trivial example would be a two parameters m and n, with mdefined to
| equal n+1 and n defined to equal m+1.

Please see Mike's example in post #2 in this thread -- circular USEs
are in contained routines rather than in module declaration sections;
I am aware that cyclic dependency is prohibited in the latter form,
but I'm not sure about the example at hand.

--
Jugoslav
___________
www.xeffort.com

Please reply to the newsgroup.
You can find my real e-mail on my home page above.
.

Relevant Pages

  • Re: Larrabee details: Yes, it is based on the Pentium. :-)
    ... The Holy Grail of compilers is to take an arbitrary serial program and ... extract an almost infinite amount of parallelism from it - that was ...
    (comp.arch)
  • Re: Error in opening the Library module file
    ... allowed by the standard but it will confuse most compilers -- they ... No. Cyclic module dependency is not allowed by the standard. ...
    (comp.lang.fortran)
  • Re: Error in opening the Library module file
    ... allowed by the standard but it will confuse most compilers -- they ... module should be compiled first (esp. ... try to avoid the situation -- the solution is often ... How to avoid cyclic dependency at first? ...
    (comp.lang.fortran)
  • Re: Incremental linking and multiple projects
    ... I installed this plugin a while ago and ... fraction of the time VS needs for this. ... Dependency ... "Sometimes compilers are so much more reasonable than people." ...
    (microsoft.public.dotnet.languages.vc)
  • Re: ACPI, Standard PC collision
    ... Looking at the manufacturer manual should help you understanding whether particular feature is supported by hardware. ... turning off auto-resolve dependency option in TD and just manually resolve the dependency stack. ... After I removed all other ACPI and standard PC objects, the above object gave me an error requiring the need for the Standard PC ... If you target is ACPI one processor PC the ACPI Uniprocessor PC is the AAHL you'd want to use if you were to leverage the HAL ...
    (microsoft.public.windowsxp.embedded)