Re: Strange Porting Problem CVF to IVF, requesting help and ideas.

David Flower wrote:

(snip)

Another couple of tricks that might help:

1) When you print out LDIF2, also print out LOC(LDIF2). (Surprisingly,
LOC, despite having its origins early in the history of the language,
is not standard, but most compilers support it). This will check that
the program is always looking in the same place for LDIF2

I thought LOC came with VAX/VMS, along with %VAL, %REF, and %DESCR
for specifying different argument passing methods.

-- glen

.

Relevant Pages

  • Re: How Common Lisp sucks
    ... language is to newcomers. ... If the language is full of random crap then ... on history and religious and science, ... Lisp can't settle on a standard? ...
    (comp.lang.lisp)
  • Re: Compiling a C program through another C program
    ... in the C standard is part of the C language, and anything not in the C ... I think we are moving away from the ANSI standard phase of C's history and into something new. ...
    (comp.lang.c)
  • Re: Is C99 the final C? (some suggestions)
    ... > that someone will try compile their stuff on an old compiler. ... > because the ANSI standard obsoleted them, and everyone picked up the ANSI ... fixed by using another language. ... >>are multiplying two expressions of the widest type supported by your ...
    (comp.lang.c)
  • Re: Forth Frustrations
    ... How would they even know what they are without being language lawyers? ... standard systems and a large number of nonstandard ones. ... interpreter, ... They set up four states -- HOST INTERPRETER COMPILER ...
    (comp.lang.forth)
  • Re: Two Questions about "strlen", "strcat" and "strcpy"
    ... >> No. zero terminated strings is the whole problem in the first place. ... > OR length prefixed strings the language would retain compatibility ... is not easily duplicated with the old standard then it will foster interest. ... The C standards committee is dead. ...
    (comp.lang.c)