28 replies to this topic

[i542]

Hi,
When new relase comes? There was no relases 1 year and 4 months. PLEASE, I do not like to have 130 (and more) betas on my PC.
i542

[nfwu]

Real Soon Now ™

#)

edit: btw, I only keep the most recent beta on my PC, and maybe the second most recent beta installation.

Edited by nfwu, 16 July 2006 - 08:43 AM.

[Helge]

I think it will probably come at least a little bit sooner if you stop whining about it..
I don't know about you but I don't have a fetish for numbers, and I can't see any
big problems running the betas now... Come on...give the devs a rest - it's summer !

[Jos]

Hi,
When new relase comes? There was no relases 1 year and 4 months. PLEASE, I do not like to have 130 (and more) betas on my PC.
i542

No reason to keep the old Beta's on you PC... Just keep the last one ....

[beerman]

why cry about the numbers? it just means newer and fixed items. be thankful that there is a beta first, no beta that means they can put out a new version of a program with errors, update once ever so often and i mean a long time. beta good thing hurry the developers bad.... up with the beta down with the hurry...

[Valik]

If it wasn't for stupid posts like this where people are whining for a new arbitrarily labeled "official release", I would have suggested a long time ago that we just classify AutoIt as perpetual beta software since development on it is so frequent.

[i542]

And please insert good old goto command...PLEASE!!!
(Why: I now seen post in v3 support from one guy who need jumping on line 90. And I too want have goto command: it makes scripts easier. Jon, goto commands are not everytime been used instead loops...)
i542

[Valik]

"Good" and "goto" do not go in the same sentence. If you find goto easier, then quite frankly, you are a terrible programmer. In a procedural language like AutoIt, goto is unnecessary. If you can't think of good designs without goto, then you need to find a language that better suits your design style or find a design style that better suits your language of choice.

In short, goto will not be added to AutoIt for any reason.

[Paulie]

"Good" and "goto" do not go in the same sentence.

Unless the sentance also contains "Not".

you can jump to line 90 already, just use functions

EDIT:
I think that there should be a sticky that says:

"THE NEXT OFFICIAL VERSION IS COMMING OUT SOON"

To dicourage and prevent constant "whens the next version" questions

anyone agree?

Edited by Paulie, 16 July 2006 - 08:22 PM.

[beerman]

Goto somewhere

:somewhere
rem the hell else for goto

[Jos]

I think that there should be a sticky that says:

"THE NEXT OFFICIAL VERSION IS COMMING OUT SOON"

To dicourage and prevent constant "whens the next version" questions

anyone agree?

Totally useless... since when are people reading any sticky/forum description when posting to check if their post is correct/needed/mentioned before ?

[Paulie]

Totally useless... since when are people reading any sticky/forum description when posting to check if their post is correct/needed/mentioned before ?

true...

but i know that if i came to this forum wanting to know when the next version was coming, and saw a sticky that said

"Updates on latest Official autoit version"

or something of that nature, i would click it before posting,

maybe i'm just wierd like that

Edit:
also, when questions do arise, we can just link to the sticky instead of actually replying

Edited by Paulie, 16 July 2006 - 09:42 PM.

[Wus]

If it wasn't for stupid posts like this where people are whining for a new arbitrarily labeled "official release", I would have suggested a long time ago that we just classify AutoIt as perpetual beta software since development on it is so frequent.

To some extent an official release is nice to have. I know a friend that uses autoit for admin scripting and logon scripts at his business, but they wont let him use the beta since its labeled "beta". When the "stable" version comes out he can actually use it and it will simplify alt of his scripts.

[beerman]

moot point... slap a label on it and call it omega or alpha.

[Richard Robertson]

We need "AutoIt Now!". Instead of being called beta, we should have AutoIt as a "constantly updated" scripting language.

[i542]

"Good" and "goto" do not go in the same sentence...

Why? You are being sick on that sentence?

If you can't think of good designs without goto, then you need to find a language that better suits your design style or find a design style that better suits your language of choice.

Yes I can think <blah blah> but when I found some good language with goto command it is or trial or it is complicated and if I found very good program language then will I feel sad because I think if you discover I don't using AutoIt as programming language (but I using now) you will close my account on AutoIt Forum. It is complicated sentence but please understand it.

In short, goto will not be added to AutoIt for any reason.

Yes, sir Valik, why?
i542

Edited by i542, 22 July 2006 - 10:29 AM.

[nfwu]

Yes, sir Valik, why?

At least try to respect your elders for the amount of experience they have - you are only 10.

QUOTE from http://www.acm.org/classics/oct95/ :
The unbridled use of the go to statement has an immediate consequence that it becomes terribly hard to find a meaningful set of coordinates in which to describe the process progress. Usually, people take into account as well the values of some well chosen variables, but this is out of the question because it is relative to the progress that the meaning of these values is to be understood! With the go to statement one can, of course, still describe the progress uniquely by a counter counting the number of actions performed since program start (viz. a kind of normalized clock). The difficulty is that such a coordinate, although unique, is utterly unhelpful. In such a coordinate system it becomes an extremely complicated affair to define all those points of progress where, say, n equals the number of persons in the room minus one!

The go to statement as it stands is just too primitive; it is too much an invitation to make a mess of one's program. One can regard and appreciate the clauses considered as bridling its use. I do not claim that the clauses mentioned are exhaustive in the sense that they will satisfy all needs, but whatever clauses are suggested (e.g. abortion clauses) they should satisfy the requirement that a programmer independent coordinate system can be maintained to describe the process in a helpful and manageable way.

QUOTE from Wikipedia:
The GOTO statement in high-level languages has been the target of criticism, because if GOTOs are over-used it becomes very easy to produce unreadable and generally unmaintainable "spaghetti code". As structured programming became more prominent in the 1960s and 1970s, many computer scientists came to the conclusion that programs should always use so-called 'structured' flow-control commands such as loops and if-then-else statements in place of GOTO. However, others believed that even though the use of GOTO is often bad practice, there are some tasks that cannot be straightforwardly accomplished in many programming languages without the use of GOTO statements, such as breaking out of nested loops and exception handling.

#)

[Jos]

At least try to respect your elders for the amount of experience they have - you are only 10.

This assumes that Valik is older .... where did you get this impression from ?

[nfwu]

Hmmm... Let's try thinking over that again...

#)

[/dev/null]

At least try to respect your elders for the amount of experience they have - you are only 10.

Why the f... are children allowed to access the internet without parental control !??! I can't even use swear words now. Dam. Sh..

EDIT: corrected swear word spelling

Cheers
Kurt

Edited by /dev/null, 22 July 2006 - 02:46 PM.