compiler construction - Staticlink vs standalone quirk with F# -


in vs2010 ultimate edition if hand --standalone flag f# compiler in projects pane not link empty c# project configuration files/resource files

it will, however, link assembly if explicitly declare --staticlink:config

this feels bug...if intentional, may ask why be?

this expected behavior:

  • the standalone flag statically links fsharp.core.dll (f# runtime) , reference assemblies depend on (i.e. other f# assemblies). need linked because may share types primary assembly (e.g. f# list type etc.)

  • the staticlink flag links assembly explicitly specify (and assemblies depend on it). means can use option link, example, c# library main f# assembly references.

i think 2 cases handled separately, because inlining f# runtime requires special handling (almost f# code uses in way, , compiler treats differently)


Comments

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

fortran - Function return type mismatch -

queue - mq_receive: message too long -