On 8/9/05, Frank Condello <developer at chaoticbox dot com> wrote:
>
> On 9-Aug-05, at 4:50 PM, Ken Mankoff wrote:
>
> > We'd have to redesign the entire Declare system and much of the
> > compiler
> > frontend to fix this problem; it is an error not of implementation
> > but of
> > design.
>
> Everyone seems to be missing the real issue - if two declares confuse
> the compiler, the obvious solution is to use one declare. So, if RB
> let you define constants for build environments, i.e. "Mach-O Debug"
> vs. "Mach-O Release" everything would be fine.
Agreed. In fact, I filled out a feature request for this about 6 months ago:
http://www.realsoftware.com/feedback/viewreport.php?reportid=bfrmpvcl
An alternate (better) solution would be to provide a post-linker
> "copy files" phase so we can stuff dylibs into the app bundle where
> they belong.
>
> @Ken; If you've only got a few declares to this library, try defining
> constants locally in each method:
#If TargetMacOS
> #If DebugBuild
> Const libname = "aoeu"
> #else
> Const libname = "aoeuX"
> #endif
> #elseif TargetWin32
> Const libname = "aoeuW"
> #endif
>
> soft declare function foo lib libname ( baz as integer ) as integer
I wish. I have 36 declares. Actually, 36 x 2 because I've done each 2x, once
for DebugBuild and once for release build. I was about to make it 36 x 3 by
adding in the #TargetWin32, but I guess I'll have to find another solution.
-k.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|