| View previous topic :: View next topic |
| Author |
Message |
Sebastian
Joined: 20 Feb 2008
Posts: 177
|
 Posted: Tue Apr 12, 2011 6:38 pm Post subject: |
 |
|
Thanks for reporting back on this.
How is this related to 32K character writing? The source and destination strings in my example were all below 256 bytes. I'm asking because I've gotten the problem again in a bigger application but could not extract it into a small test case this time. |
|
| Back to top |
|
 |
Sebastian
Joined: 20 Feb 2008
Posts: 177
|
| Posted: Thu Jul 14, 2011 7:49 am Post subject: |
|
|
| So is this going to be fixed or at least checked? It again turned up in an apmost impossible to debug scenario where changing fully-correct code into still-fully-correct-but-differently-looking code made it work, the only change being a change of name to name(1:transfer_end) where name was a parameter of the WRITE function. |
|
| Back to top |
|
|
PaulLaidler
Site Admin
Joined: 21 Feb 2005
Posts: 7928
Location: Salford, UK
|
| Posted: Thu Jul 14, 2011 12:02 pm Post subject: |
|
|
| Martin has reported that this has been fixed at FTN95 6.10. Which version are you using? |
|
| Back to top |
|
|
Sebastian
Joined: 20 Feb 2008
Posts: 177
|
| Posted: Thu Jul 14, 2011 3:50 pm Post subject: |
|
|
See my later replies, the small test example is indeed fixed in 6.10, larger programs still exhibit the bug.
That's why I guess that
| Quote: | | Writing more than 32K characters using the 'A' format gave an "invalid record length" run time error. |
may have fixed the small example by accident but didn't touch the real problem. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
