Re: Source of EXE Size OT
- From: "Dan Johnson" <johnson@xxxxxxxxxx>
- Date: Tue, 13 Sep 2005 10:34:50 -0600
> I had forgotten this tidbit when responding to Dan. If it is true in
> general, then one would expect that the code size would jump in
> increments. I guess another question I didn't ask was whether he is
> generating p-code or native and whether he has changed any of the
> default compiler options (empahsize speed over size comes to mind).
I'm compiling to native code, and optimizing for speed. Haven't changed any
of these options in a long time.
While I understand exe size for a VB app may not carry much significance,
I'm still somewhat surprised that there don't seem to be many tools that can
be used to identify "bloat". I can remember leaving an unneeded huge image
file in a picture frame once, where the image was positioned in such a way
that there was no way I would ever see it during normal VB use...a situation
where it would be nice to have something pointing you to the potential
problem.
Dan
.
- Follow-Ups:
- Re: Source of EXE Size OT
- From: Jonathan Wood
- Re: Source of EXE Size OT
- References:
- Source of EXE Size
- From: Dan Johnson
- Re: Source of EXE Size
- From: Duane Bozarth
- Re: Source of EXE Size
- From: Dan Johnson
- Re: Source of EXE Size
- From: Duane Bozarth
- Re: Source of EXE Size OT
- From: Ralph
- Re: Source of EXE Size OT
- From: Duane Bozarth
- Source of EXE Size
- Prev by Date: Re: short cut keys + VB
- Next by Date: Re: Source of EXE Size
- Previous by thread: Re: Source of EXE Size OT
- Next by thread: Re: Source of EXE Size OT
- Index(es):
Relevant Pages
|
Loading