Size Of Autoitsc.bin In Beta 123 Grow Very Much

[Zedna]

Versions/Sizes:

123: 418 816

122: 396 800

...

110: 391 168

So in version 123 was made big jump in size, but there are no new functions, only few fixes (from 122).

So question is: Is it right or some problem?

If it's OK and it was only my misunderstanding of something then sorry...

Edited May 8, 2006 by Zedna

[w0uter]

Jon put spyware in it to cover the hosting.

maby there just big bugfixes ?

[jpm]

I correct 2 missing dot in message string and I get and update that lead to this increment.

Will be back in .124

Thanks Zedna

[Zedna]

Same problem (as with version 123) is now with version 125.

Only some fixes and size grow very much.

Versions/Sizes:

125: 419 328

124: 397 824

123: 418 816

[Zedna]

Same problem (as with version 125) is now with version 132.

Only some fixes and size grow very much.

But maybe Compilation done with VC8 instead of VC6. (by Jon) could be source of this ...

Versions/Sizes:

132: 444 416

131: 399 360

130: 399 360

[jpm]

Same problem (as with version 125) is now with version 132.

Only some fixes and size grow very much.

But maybe Compilation done with VC8 instead of VC6. (by Jon) could be source of this ...

Versions/Sizes:

132: 444 416

131: 399 360

130: 399 360

It look like the VC8 is bringing some more stuff. Compiling with VC6 will have done the same size as before.

But it is a Dev Team decision to go with VC8

[Zedna]

It look like the VC8 is bringing some more stuff. Compiling with VC6 will have done the same size as before.

But it is a Dev Team decision to go with VC8

OK. I have no problem with this - if bigger size is not due to some "error".

[Jon]

The compiler we've used for releases to date is Visual C++ 6 but that's like 8+ years old now and is very "loose" with the C++ standard it's years since it was updated. Quite often we've had to write code in a bizarre way so that it will even compile in VC6. Most of the devs have been using Visual C++ 2003 and recently 2005 for dev work as it's a much more compliant compiler and nicer environment.

It's annoying about the size difference though. :grr:

[JSThePatriot]

@Zedna

I am glad this community has people like you. I would never have known the size difference, or thought to check it.

Thanks for your dedication to the community.

JS

[rbhkamal]

The compiler we've used for releases to date is Visual C++ 6 but that's like 8+ years old now and is very "loose" with the C++ standard it's years since it was updated. Quite often we've had to write code in a bizarre way so that it will even compile in VC6. Most of the devs have been using Visual C++ 2003 and recently 2005 for dev work as it's a much more compliant compiler and nicer environment.

It's annoying about the size difference though. :grr:

Just one question,

If you compile the same code twice (make no changes) do you get the same size?

If not maybe there is a problem with the compiler, right?

RK

[Jon]

Just one question,

If you compile the same code twice (make no changes) do you get the same size?

If not maybe there is a problem with the compiler, right?

RK

The compiler's fine. It justs adds in lots more features (for example, inbuilt buffer overrun checking).

[Richard Robertson]

The size of the AutoIt bin file isn't too big. I think the script files ending up at about 40 kb compiled isn't too bad. It would be nice smaller, but this isn't bad yet.

[jftuga]

Is there a way to tell VC8 to compile for a smaller size exe / dll? I imagine that if there were such an option, it would probably come at a cost of running slower.

Just a thought - one of those size vs. speed tradoffs.

-John

[Valik]

AutoIt has always been compiled with the "favor small size" optimization on.

[Zedna]

Same problem (as with version 3.1.1 beta 123,125,132) is now with version 3.2.1 beta 1,2.

Only some fixes and size grow very much.

Versions/Sizes:

3.2.1.12: 416 256

...

3.2.1.2: 433 664

3.2.1.1: 381 440

3.2.0.1: 382 464

So in version 3.2.1.2 is much bigger size

Jon said that new VC8 compiler was ued instead of old VC6 in version 3.1.1.132.

So if all 3.2.x versions would have bigger size I would say nothing here.

But why is bigger size in version 3.2.1.2?

[Richard Robertson]

More native support?

[Jos]

The change of the regex libary has added some size...

[Zedna]

The change of the regex libary has added some size...

This was added in version 3.2.1.7 (and not in 3.2.1.2):

- Added: StringRegExp() and StringRegExpReplace() regular expression support (Perl compatible)

Edited November 17, 2006 by Zedna

[Valik]

The size of 3.2.1.12 looks about right to me. It has the new regular expression engine which added some size. There's also some new code I added which increased AutoIt by around 5KB. So I think the size of 3.2.1.12 is about right when compared to 3.2.0.1 since we've knowing added some stuff to increase the size 25KB - 30KB. I see no significance in the size of 3.2.1.2 because that is 10 builds ago.

[Zedna]

The size of 3.2.1.12 looks about right to me. It has the new regular expression engine which added some size. There's also some new code I added which increased AutoIt by around 5KB. So I think the size of 3.2.1.12 is about right when compared to 3.2.0.1 since we've knowing added some stuff to increase the size 25KB - 30KB. I see no significance in the size of 3.2.1.2 because that is 10 builds ago.

3.2.1.2: 433 664

3.2.1.1: 381 440

RegExp wasn't added in this version (3.2.1.2), so why more than 52KB in this version?

EDIT: OK I don't want to "tease" developers with such minor problem if they don't want to observe more details about that. So no problem.

Edited November 17, 2006 by Zedna