Dear Aparajita
You write in Release Notes v4.pdf
• [690] include within a library method now correctly searches
relative to the library file.
I don't find this to be a logical change.
Paths referenced in functions shouldn't have their "own path"; the
path should be relative to the calling include file (as it was in
Active 4d v3).
Example:
-----------------------------
library "test"
method "foo"($path)
include($path)
end method
end library
----------------------------
script /test/bla.inc
----------------------------
method foo2
include($path)
method foo2
test.foo("abc.inc") // should include "/test/abc.inc", in version 4
it will open /mylibraryfolder/abc.inc
global.foo("abc.inc") // should include "/test/abc.inc"
----------------------------
I hope we can both come to the same conclusion!
Regards
Oliver Brodwolf_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
