Context Navigation

Timeline

10:33 PM Ticket #3279 (FileReadToArray() documentation missing important detail) updated by jchd: I disagree: after explicitely opening a file for append, it's plain that the handle's file pointer is set to EOF upon successful return of the function. Reading whatever from there is obviously going to fail and raise an error. This is how low-level fileread/filewrite functions work in all languages I know of. No low-level File* function has the right to change the file pointer before reading/writing! Doing so would make them completely useless in almost all situations. That said I confess that the description in the documentation could have said "reading past EOF" or "EOF unexpectedly reached" like the other FileRead* functions do (with @error set to -1). Yet still, any volontary attempt to read anything from EOF is much more a programming error than a misleading documentation.
9:03 PM Ticket #3279 (FileReadToArray() documentation missing important detail) created by rumbata@…: When using FileReadToArray() with a file handle, the file position may …
7:09 AM Ticket #3274 (Problems with ControlSend) closed by J-Paul Mesnage: Rejected
7:08 AM Ticket #3274 (Problems with ControlSend) updated by J-Paul Mesnage: So I close it

5:23 PM Ticket #3217 (FileInstall() memory leak) updated by BrewManNH: I don't have version 3.3.8.1 to test against, but in 3.3.12.0 it shows the same. It's the file being extracted from the exe, and as soon as that is extracted and saved to disk, the memory usage drops to a normal level. Doesn't look like a memory leak to me, I'd have to agree with TheDcoder that it's normal.
11:22 AM Ticket #3276 (Getting/Setting DllStruct array-element with index stored in varible ...) created by genius257: The code below illustrates the problem […]

9:46 PM Ticket #3275 (free/unset variable) updated by anonymous: So what if it does? The actual memory usage would be tiny, so I don't see why this would be an issue worth implementing.
6:13 PM Ticket #3275 (free/unset variable) created by genius257: It would be nice to be able to free/unset variables. I know setting …

3:59 PM Ticket #3274 (Problems with ControlSend) updated by J-Paul Mesnage: Has I don't have a COM1, I can't reproduce All the pointed tickets do not help to reproduce. If you cannot attached a "working" script I will close it again Sorry
3:47 PM Ticket #3274 (Problems with ControlSend) created by anonymous: ControlSend acts erratically when executed on Minimised window. …

5:56 PM Ticket #3273 (_ArrayExtract: Error return value description) updated by BrewManNH: Is there a reason you quoted what I said, because you forgot to add anything to your post? In case you're wondering the line in your bug report I was responding to is this one: > By the way, where can I get a version of AutoIt with this problem fixed? Thanks! My response was telling you that there's no reason to look for a "fixed" version of AutoIt because your complaint is a minor documentation error that doesn't affect anything in the function itself. Seeing as how you already know what the correct return value is, you shouldn't need an updated help file to know what to do with it. It will get fixed when it gets fixed and now that you know what the correct return value is, write your scripts with that return value in mind.

Note: See TracTimeline for information about the timeline view.