Timeline
May 26, 2015:
- 10:55 PM Ticket #3032 (AutoIt allows nonsense preceding expression) closed by
- No Bug: Absolutely! Since all the code posted so far is correctly flagged as invalid by Au3Check (for a reason) then it is obviously not suitable for interpretation. Closing this as "no bug" until an actual bug is exhibited.
- 9:55 PM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- The code in the first post won't run in any current or beta version of AutoIt even after I declared the variable $expression. Au3Check will flag all the code in this thread as bad.
- 12:00 AM Ticket #3035 (_FileListToArrayRec: new switch for (protected system files)) updated by
-
Version changed
Automatic ticket cleanup.
May 25, 2015:
- 11:04 PM Ticket #3035 (_FileListToArrayRec: new switch for (protected system files)) created by
- add a switch that that will hide files that attributed both hidden + …
- 10:16 PM Ticket #3034 (_Timer_SetTimer() doc example) created by
- A simple example for newbies might be helpful: […] This exmaple …
- 10:08 PM Ticket #1380 (Inform user of required parameters in _Timer_Settimer()) updated by
- Perhaps add a description of what $iTime is
- 9:29 PM Ticket #3027 (_WinAPI_RegEnumKeyEx) updated by
- The date seems to be the only difference, but it's for this reason that I asked it. I think it could be useful…
- 7:41 AM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- Care to explicit where you think Au3Check fails in all you've posted?
- 3:57 AM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- Replying to jchd18: > a valid construct (deemed valid by Au3Check) where the interpretor doesn't produce the correct result That's impossible. How could I know or prove that that's caused by this bug? Replying to jchd18: > a weird construct not caught by Au3Check That's possible? Anyway, let me try. AutoIt bug or Au3Check bug. And maybe related to this bug, through I don't know. Only Jon can know... […]
- 2:58 AM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- Sorry, I misread.
- 2:56 AM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- Easy enough to find errors in Au3Check. […]
May 24, 2015:
- 11:12 PM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- Either you can exhibit a valid construct (deemed valid by Au3Check) where the interpretor doesn't produce the correct result, or you can exhibit a weird construct not caught by Au3Check OR this ticket will have to close.
- 8:38 PM Ticket #3033 (Small mistake in _Excel_PictureAdd() Help File) created by
- _Excel_PictureAdd Second Example "; Insert the picture without …
- 4:45 PM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- Why do you think that this bug only affects "stupid constructs" and doesn't cause wrong results for "reasonable constructs"? Having written interpreters myself, I believe that this bug isn't caused by missing checks but by a logic error.
- 10:19 AM Ticket #3031 (Macro Reference > @MSEC typo) closed by
- Fixed: Fixed by revision [11304] in version: 3.3.13.21
- 5:36 AM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- Why do you believe the interpretor should waste runtime cycles to do the extra work Au3Check is supposed to have done beforehand to catch stupid constructs?
- 1:05 AM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- And the interpreter doesn't stop after the line […]
May 23, 2015:
- 9:33 PM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- The interpreter should complain before executing that line. […] Result: […]
- 7:57 PM Ticket #3032 (AutoIt allows nonsense preceding expression) updated by
- Could you: - explain what is wrong with it? - post a script that will run and show the issue? Jos
- 7:51 PM Ticket #3032 (AutoIt allows nonsense preceding expression) created by
- The AutoIt interpreter can execute the line […]
May 21, 2015:
- 4:39 AM Ticket #3031 (Macro Reference > @MSEC typo) created by
- Range is 00 to 999 should be Range is 000 to 999
- 3:29 AM Ticket #3027 (_WinAPI_RegEnumKeyEx) updated by
- Other than the date the key was last written, how does this differ from RegEnumKey?
- 3:20 AM Ticket #3030 (_Timer_SetTimer: example with $sTimerFunc parameter) closed by
- Rejected: Closing this ticket as instructed.
May 20, 2015:
- 9:01 PM Ticket #3030 (_Timer_SetTimer: example with $sTimerFunc parameter) updated by
- Please ignore this ticket
- 5:56 PM Ticket #3030 (_Timer_SetTimer: example with $sTimerFunc parameter) created by
- It would be desirable to have a second example, one which uses $sTimerFunc
- 3:33 PM Ticket #2634 (Treat keyword Default like an unset optional parameter) updated by
- Please consider if this change do not need some more description in HelpFile
- 3:45 AM Ticket #3029 (_DateDiff() additional help) updated by
- Also: This function can compare a date with a date-time. If $sStartDate is a date-time and $sEndDate is a date (or vice versa), the time is ignored. For example, _DateDiff('D','2015/05/16 14:32','2015/05/17') return 1. But this is not what the function does in this case: _DateDiff('s','2015/05/16 14:32:12','2015/05/17 14:32') returns 86388, being 24*60*60 - 12, so _DateDiff() could be said to append :00 to 14:32 before doing the comparison. I'm not sure what the author intended. I see that the _Date and _Now functions do not follow the standards for UDFs, so I guess that they were written in the early days of UDFs.
May 19, 2015:
- 1:32 PM Ticket #3029 (_DateDiff() additional help) updated by
- Someone brought up a similar problem with _DateAdd recently. I will have a think about how we might add an explanatory note to the Remarks sections of the Help file pages for the 2 functions. M23
- 10:16 AM Ticket #3028 (GUICtrlCreateCombo(0) closed by
- Fixed: Fixed by revision [11303] in version: 3.3.13.21
- 7:52 AM Ticket #2634 (Treat keyword Default like an unset optional parameter) closed by
- Fixed: I agree, I can't remember when …
- 4:50 AM Ticket #3029 (_DateDiff() additional help) updated by
- A better example: I suggest the following be added, perhaps to the Remarks section: This function always returns an integer value. If the precision of $sStartDate and/or $sEndDate exceeds the precision requested in $sType, the user may expect a floating-point result, but in fact the value is floored, thus returning an integer. For example, _DateDiff('D','2015/05/16 14:32','2015/05/16 14:00') returns -1.
- 12:10 AM Ticket #2634 (Treat keyword Default like an unset optional parameter) updated by
- is it completed now ? […]
May 18, 2015:
- 10:56 PM Ticket #3029 (_DateDiff() additional help) created by
- I suggest the following be added, perhaps to the Remarks section: …
- 4:10 PM Ticket #3028 (GUICtrlCreateCombo(0) created by
- Help says: To combine styles with the default style use BitOR/a> ( …
May 16, 2015:
- 1:18 PM Ticket #3023 (GUISetHelp.au3 - HelpFile Example) closed by
- Fixed: Fixed by revision [11298] in version: 3.3.13.21
- 1:14 PM Ticket #3022 (EnvSet(0 help typo) updated by
- Fixed that mistake as well
- 11:10 AM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- Committed the change and move the file into the regular beta directory. Jos
- 11:08 AM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) closed by
- Fixed: Fixed by revision [11296] in version: 3.3.13.21
May 15, 2015:
- 10:54 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- Ha... I only updated the PE header file version but forgot the console message version. That should be fixed now. Jos
- 9:26 PM Ticket #3027 (_WinAPI_RegEnumKeyEx) created by
- It should be useful to have this function in the WinAPIReg.au3 …
- 6:07 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
-
Replying to Jos:
> I've updated the version number to .13.22 and uploaded it to the same place, so we are sure we are looking at the same thing.
>
So, more or less all is good now in .13.21 in my view.> Not sure what that really means. To me it is either working or not working now. :) > > Jos In a short test, actually this ".13.22" looks like works, as expected. Today and tomorrow I have many work to to so I be using this, and report if find any problem with this long names feature. - 4:33 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- When I download https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/au3check-beta/Au3Check.exe and run it, it reports .13.21. Should it now be .13.22? I got confused as to where to take the latest Au3Check beta from. Anyway, I've confirmed .13.21 solves problem bug #3026 for me. As for the "more or less correct" - I think that for the source code posted by mLipok (#comment:7) build .13.21 works fine for long const names, but does not correctly specify what are the exact errors (problem different from #3026). So, when the following code is Au3Check'ed: […] the output is […] whereas I would expect somthing like […] It does report errors when there are some, just does not find the redeclaration problem at once. It's fine with me, because when the first error is fixed (the constant is assigned a value), the other problem shows up, too. So maybe this is another bug (minor), or "working as designed", but totally acceptable. Hope this clarifies things. I've already started to use 3.3.13.21 to track down syntax errors in our autotest framework and will put it into continuous integration system some time soon. I find the tool very useful now that it doesn't report false errors (for me). Thanks again, Tomek
- 3:43 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
-
I've updated the version number to .13.22 and uploaded it to the same place, so we are sure we are looking at the same thing.
So, more or less all is good now in .13.21 in my view.Not sure what that really means. To me it is either working or not working now. :) Jos - 2:40 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
-
@mLipok
OK, so I read once again and now I get what you meant. You were expecting *2* errors reported and you got *4* of them. The thing is, you must be running older Au3Check, becase when I run it with .13.21, I get the following output (which is closer to expectations):
[…]
When I fix the first one and run .13.21 again, I get:
[…]
So, more or less all is good now in .13.21 in my view. Try to run
Au3Check--3.3.13.21.exe -d -w 7 script.au3in the command prompt. Regards Tomek - 2:26 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- @mLipok I think you have two errors in the source code you posted. 1) You're declaring a const without a value, and 2) you're redefining ..._MscKodTeryt2. Try the following code (it gives me no errors): […] (I haven't had a chance to post at the forum yet - I don't have an account there, sorry :) )
- 1:28 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- btw. If this is not a problem, @Tomaszu as I can not find your @member title on the forum, please send me PM in the forum. I like to speak in Polish language with my countryman, about AutoIt.
- 1:07 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- only first line is ok all others line give me an additional errors […] […]
- 11:03 AM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- I've just given it several runs on a number of our test scripts and compared output with 3.3.12.0 and 3.3.13.20. The misleading errors are now gone (good!) and (almost) all the other found errors/warnings are still in place, so no regressions I believe. In fact, I've just found the latest beta to no longer report another not-so-much-of-an-error, which .12.0 did: […] But this improvement is also visible in the previous beta, .13.20. Great job! Many thanks for the quick resolution. Green light from me on making this widely available. Tomek
- 9:53 AM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- The issue isn't about Const but more about just checking the first 64 characters of a variable-name to make them unique. Agree it appears when one is defined a Const and the next as normal as AU3check "thinks" it is checking the same name. I have uploaded this version of AU3CHeck in a separate directory so please give it a good spin and see if all is well now: https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/au3check-beta/Au3Check.exe Jos
- 9:10 AM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- Thanks for a quick response! Actually, there is an easy workaround to this problem - I could replace "Global Const" with just the "Global" (they're not altered anyway), and Au3Check stops complaining. We don't need the long-named definitions to be Const, it just feels right to define them as constants and not variables. Length-wise: the original resource-based constants (with long names) are machine-generated (call them "private" sort of), but we only pick those that are needed in the autotest scripts and redeclare them into more reader-friendly names (2nd layer of resources - "public" definitions). So I agree using *very* long names in a source code is a bad programming practice, but we would still find it useful to define a 90-characters-long constant once in a while. Thanks for considering. I would gladly put the new Au3Check to some heavy testing when you share it. Regards and pozdrowienia, too :) Tomek
May 14, 2015:
- 10:32 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- Well it probably is me being lazy or something but I have done quite some programming in my life but can assure you I've never ever used fieldnames with a length like that as that make the program pretty unreadable for me. I have made a version of au3check that allows a length of 128 characters and will first do some more testing before making that available for other to test with. Jos
- 3:33 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
- Maybe this looks funny but just today I come to the same problem: […] In my project that I'm doing such enumeration more, and their syntax is dependent on the location of the data in an HTML page. If you need to carry out tests, then there's a chance. btw. @Tomasz. Pozdrawiam, rodaku Regards, countryman mLipok
- 1:20 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) updated by
-
Owner, Status changed
There seems to be a limit of 64 characters currently indeed. That it hasn't come up yet till know probably says something about your request and the exceptional length you seem to be using for your variables. It can be enlarged but will require proper testing as I have no idea if there are any consequences to the stacksizes etc with the utilisation of YACC & FLEX. On the fence as to whether we really should do this and to what max length. Jos
May 13, 2015:
- 4:36 PM Ticket #3024 (AutoItTools.lua) closed by
- Rejected: This is not the way to send me a proposal for a modification by reporting a BUG. Please open a thread in the forum so this can be discussed and you can explain what you have done and why this is needed. Thanks Jos
- 4:35 PM Ticket #3025 (AutoItTools.lua) closed by
- No Bug: This is not the way to send me a proposal for a modification by reporting a BUG. Please open a thread in the forum so this can be discussed and you can explain what you have done and why this is needed. Thanks Jos
- 2:43 PM Ticket #3026 (Au3Check unexpectedly trims Const definitions to 63 characters and ...) created by
- In our test automation system we have a number of AutoIt3 script files …
- 12:59 AM Ticket #3025 (AutoItTools.lua) created by
- Not correct work of a debugger, at addition of the debugging lines …
- 12:44 AM Ticket #3024 (AutoItTools.lua) created by
- Bug
May 12, 2015:
- 9:02 PM Ticket #3023 (GUISetHelp.au3 - HelpFile Example) created by
- there is: […] it should be: […]
- 8:08 PM Ticket #3022 (EnvSet(0 help typo) updated by
- Replying to mLipok: > In Au3.3.13.20 it is still avala > > But you must look in Example "EnvSet.au3" > there is: > > {{{ > ; Create an environment variable called %MYVAR% and assign it a value. When you assign or retrieve an envorinment variable you do so minus the percentage signs (%). > > }}} I meant: "In Au3.3.13.20 it is still available"
- 8:06 PM Ticket #3022 (EnvSet(0 help typo) updated by
- In Au3.3.13.20 it is still avala But you must look in Example "EnvSet.au3" there is: […]
- 3:24 PM Ticket #3022 (EnvSet(0 help typo) closed by
- Rejected: Already fixed before. Please check the latest beta version.
- 6:37 AM Ticket #3021 (AutoIt Crash - calling obj method) updated by
- It is even stranger - AutoIt unexpected behavior. Regardless of whether my code is correct, incorrect or foolish, AU3Check should it catch, or finally AutoIt should also catch it, and announce that it is a syntax error in line .... It should not however reach a situation in which any program exits via CRASH.
- 6:04 AM Ticket #3022 (EnvSet(0 help typo) created by
- envorinment should be environment
- 2:39 AM Ticket #3021 (AutoIt Crash - calling obj method) updated by
- Any function reference and dummy method will do: […]
- 1:57 AM Ticket #3021 (AutoIt Crash - calling obj method) created by
- Repro code: […] Result: […]
May 9, 2015:
May 4, 2015:
- 9:30 PM Ticket #3017 (The largest negative integer value we misinterpret) updated by
- > -9223372036854775808 and -9223372036854775807 yield the same result. Only when using a site which limits integral values to Int32 or under the double tab. And no they are not the same value and both are valid int64 values.
- 8:59 PM Ticket #3017 (The largest negative integer value we misinterpret) updated by
- Not Int with Double confused !! http://calc.penjee.com/?s=HJJJJJJJJJJJJJJJ
- 8:32 PM Ticket #3017 (The largest negative integer value we misinterpret) updated by
- That's not an Int64 value, it's too large. When converting it to a 64 bit value, -9223372036854775808 and -9223372036854775807 yield the same result. http://www.binaryconvert.com/result_double.html?decimal=045057050050051051055050048051054056053052055055053056048056
May 3, 2015:
- 9:11 PM Ticket #3019 (#2LOYPRUVG) closed by
- No Bug
- 6:51 PM Ticket #3019 (#2LOYPRUVG) created by
- 1:50 PM Ticket #3018 (_GDIPlus_EffectCreateHueSaturationLightness) closed by
- Fixed: Fixed by revision [11281] in version: 3.3.13.21
May 2, 2015:
- 6:10 PM Ticket #3018 (_GDIPlus_EffectCreateHueSaturationLightness) updated by
- Same for lightnessLevel https://msdn.microsoft.com/en-us/library/windows/desktop/ms534069(v=vs.85).aspx
- 5:33 PM Ticket #3018 (_GDIPlus_EffectCreateHueSaturationLightness) created by
- In the help file (Release&Beta) saturation limits are -180 to 180 but …
May 1, 2015:
- 9:55 PM Ticket #1479 (ListView WM_NOTIFY Message on x64 Returning Wrong Results) updated by
- Forgot to mention that the bug in the current version is still available.
- 9:08 PM Ticket #1479 (ListView WM_NOTIFY Message on x64 Returning Wrong Results) updated by
- If you change the following in the file StructurConstants.au3 then it works with 32bit and 64bit. from […] to […] This probably applies to other structures in this file.
- 2:13 PM Ticket #3017 (The largest negative integer value we misinterpret) updated by
- This is rather the largest negative int64 value, but yes there seems to be an issue with parsing the literal value -9223372036854775808.
- 12:49 PM Ticket #1686 (AU3_PixelSearch crashes with access violation at address 0x00000008) updated by
- Replying to Jpm: > Fixed by revision [5893] in version: 3.3.7.0
- 12:47 PM Ticket #3017 (The largest negative integer value we misinterpret) created by
- The following code illustrates the problem […] at …
Apr 27, 2015:
- 9:44 AM Ticket #3016 (FileSetPos() not used in FileSetPos() example) closed by
- No Bug: No bug there is a FileSetPos() after the 1st MsgBox()
- 6:33 AM Ticket #3016 (FileSetPos() not used in FileSetPos() example) created by
- The example for FileSetPos() does not contain any use of FileSetPos(). …
Note:
See TracTimeline
for information about the timeline view.
