Talk:Executable library: Difference between revisions
Content added Content deleted
| Line 75: | Line 75: | ||
==ADA and use of library== |
==ADA and use of library== |
||
It is not clear if the executable ./hailstone_test calls the compiled library ./hailstone or if it just compiles in the source to ./hailstone (which would not satisfy the task). --[[User:Paddy3118|Paddy3118]] 18:10, 29 May 2012 (UTC) |
It is not clear if the executable ./hailstone_test calls the compiled library ./hailstone or if it just compiles in the source to ./hailstone (which would not satisfy the task). --[[User:Paddy3118|Paddy3118]] 18:10, 29 May 2012 (UTC) |
||
: With the proper set of compiler options, you can compile and link ''hailstone_test.adb'' and generate the executable hailstone_test '''without''' the source ''hailstone.adb'', but with the specification ''hailstone.ads''. Which seems to satisfy the task. On the other hand, as for most compiled languages, there is something in between source code and executable. To generate either of the the executables ''hailstone'' and ''hailstone_test'' the linker must access the object code in ''hailstone.o''. |
|||