>For example, if you allow the end user to specify a
>specific image to load and end up using something like:
>LoadImage(myfile$) in your code, there is no real way for
>the compiler to know up front if it needs to include the
>PNG loader, the JPG loader, BMP loader, or whatever other
>image formats you may have.
I assume that all 'loaders' would be in the same library.
It just seems so 'ancient' that the compiler is so 'dumb' that it can't figure out which libraries to include.
>Even if it would be impossible for Blitz to give a 100%
>definite answer which modules would be needed, it would be
>extremely helpful if it were possible for it to generate
>a 'best guess' that can be finetuned by the programmer...
>Sure beats making it up from scratch each time.
If we assume that all commands dealing with loading different kinds of images is in the same library, then it doesn't seem that farfetched.
Andy
>specific image to load and end up using something like:
>LoadImage(myfile$) in your code, there is no real way for
>the compiler to know up front if it needs to include the
>PNG loader, the JPG loader, BMP loader, or whatever other
>image formats you may have.
I assume that all 'loaders' would be in the same library.
It just seems so 'ancient' that the compiler is so 'dumb' that it can't figure out which libraries to include.
>Even if it would be impossible for Blitz to give a 100%
>definite answer which modules would be needed, it would be
>extremely helpful if it were possible for it to generate
>a 'best guess' that can be finetuned by the programmer...
>Sure beats making it up from scratch each time.
If we assume that all commands dealing with loading different kinds of images is in the same library, then it doesn't seem that farfetched.
Andy