[jawsscripts] Re: Jaws 13 compile issue
- From: Christopher Chaltain <chaltain@xxxxxxxxx>
- To: jawsscripts@xxxxxxxxxxxxx
- Date: Fri, 13 Jan 2012 11:02:47 -0600
Different compilers are implemented differently. Some compilers will
simply ignore any line that starts off with a comment character. Other
compilers will still go ahead and parse lines starting with the comment
character.
I remember you couldn't use unpaired quotes in ksh scripts since ksh
still went ahead and parsed lines starting with a hash or pound
character. This gave a whole new meaning to the phrase "I just changed a
few comments!"
Python will use a statement starting with a pound or hash sign to
indicate the encoding being used for that file. Apparently the JAWS
compiler does something similar to indicate, as a compiler directive, to
make the resulting compiled code backward compatible. Apparently this
string is unrecognized and treated as a comment by earlier version of
JAWS but not ignored in JAWS 13.
On 13/01/12 09:34, Mario Brusco wrote:
> But, umm... I don't understand, because doesn't the semicolon denote that
> the text following it is a comment, in which it is ignored by the compiler?
> Please explain the answer so I can understand better.
>
> ----- Original Message -----
> From: "Doug Lee" <doug.lee@xxxxxxxxxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: January 13, 2012 3:29 AM
> Subject: [jawsscripts] Re: Jaws 13 compile issue
>
>
> For this particular line, the leading semicolon is part of the line,
> and it was designed that way so older JAWS versions won't trip over
> the line while newer ones can still obey it.
>
> On Fri, Jan 13, 2012 at 03:25:57AM -0500, Bob Kennedy wrote:
> Do you leave in the ; at the beginning of the line? Doesn't that tell Jaws
> to ignore that whole line?
>
> Keep in mind FS support is not made up of scripters. They are in a
> completely different part of the building.
>
>
> ----- Original Message -----
> From: "John Martyn" <johnrobertmartyn@xxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Friday, January 13, 2012 12:46 AM
> Subject: [jawsscripts] Re: Jaws 13 compile issue
>
>
> Excellent, this worked like a charm.
> Thank you very much. FS tech support didn't fill me in on that little trick.
> John
>
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Doug Lee
> Sent: Thursday, January 12, 2012 12:27 PM
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Jaws 13 compile issue
>
> Add the following line to the top of your scripts to make them work properly
> in JAWS 13 and JAWS 12 and below:
>
> ;#pragma StringComparison partial
>
> This is how they fixed this issue. JAWS 13 natively makes == and other
> comparison operators, when comparing strings, compare the whole string, not
> just through the end of the shortest one. This is like most other languages
> out there, but it breaks things like checking for a RichEdit control by
> comparing getWindowClass(hwnd) to "RichEdit,"
> since RichEdit window classes tend to be longer (e.g., "RichEdit20W").
>
> On Thu, Jan 12, 2012 at 03:18:04PM -0500, Alex H. wrote:
> Man, I hope they fix that, it's kind of a big show stopper.
>
> On 1/12/12, John Martyn <johnrobertmartyn@xxxxxxxxx> wrote:
>> For those interested, if you compile a script in jaws 13, it won't
>> work with jaws 12 and below, so in a universal sense, compile your
>> scripts in JAWS 12 and it will work with all recent versions.
>> John Martyn
>>
>>
>>
>> __________???
>>
>> View the list's information and change your settings at
>> //www.freelists.org/list/jawsscripts
>>
>>
> __________???
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
> --
> Doug Lee, Senior Accessibility Programmer SSB BART Group -
> Accessibility-on-Demand mailto:doug.lee@xxxxxxxxxxxxxxxx
> http://www.ssbbartgroup.com "While they were saying among themselves it
> cannot be done, it was done." --Helen Keller __________o?=
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
> __________???
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
> __________???
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
--
Christopher (CJ)
chaltain@xxxxxxxxx
__________�
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
Other related posts:
