Hi there guys,

    I'm not sure that is a bug, but for sure is a very strange case.
    Early this week I have open a thread on this newsgroup about
xBase skipping some lines of code. But after some more elaborated tests
seems like xBase skips lines only (so far) in 1 specific case: If the line
of code STARTS with "note_" xbase will just SKIP the line..
   Did anyone had the same problem?
   Well anyways to save you guys some time in case you want to test this
issue,
I've wrote a small program to reproduce the problem, just PBUILD it..

    If anyone has a solution for that (other then changing note_ to
something else :D) ..

Thanks a lot!
[]s
Marcelo

On Fri, 29 Oct 2004 09:41:17 -0400, Marcelo Ramos wrote:
Marcelo
These is from clipper Manual
 NOTE*
 Place a single-line comment in a program file
------------------------------------------------------------------------------
 Syntax

     NOTE [<commentText>]

 Arguments

     <commentText> is a string of characters placed after the comment
     indicator.

 Description

     NOTE is command synonym for the single-line comment indicator (*).
All
     characters after NOTE are ignored until the CA-Clipper compiler
     encounters an end of line (carriage return/line feed).  This means a
     single-line comment cannot be continued with the semicolon ( onto a
     new line.

     If you need a multi-line or inline comment, begin the comment block
with
     a slash-asterisk (/*) symbol and end the comment block with an
     asterisk-slash (*/) symbol.  If you need to comment out a block of
code,
     use the conditional compilation directives #ifdef...#endif instead of
     multiline comments.  This is important since nested comments are
     illegal.

     NOTE is a compatibility command and therefore not recommended.  It is
     superseded by the C-style comment symbols slash-asterisk (/*) and
     asterisk-slash (*/), as well as the double-slash (//).  It is also
     superseded by the dBASE-style comment symbols, asterisk (*) and the
     double-ampersand (&&).

     For a complete discussion on comment indicators, refer to the "Basic
     Concepts" chapter in the Programming and Utilities Guide.

 Examples

     ¦  These examples show the various comment symbols supported by
        CA-Clipper:

         This is a comment
        /* This is a comment */
        * This is a comment
        && This is a comment
        NOTE This is a comment

Regards
Mike Evans
> Hi there guys,
> 
>     I'm not sure that is a bug, but for sure is a very strange case.
>     Early this week I have open a thread on this newsgroup about
> xBase skipping some lines of code. But after some more elaborated tests
> seems like xBase skips lines only (so far) in 1 specific case: If the line
> of code STARTS with "note_" xbase will just SKIP the line..
>    Did anyone had the same problem?
>    Well anyways to save you guys some time in case you want to test this
> issue,
> I've wrote a small program to reproduce the problem, just PBUILD it..
> 
>     If anyone has a solution for that (other then changing note_ to
> something else :D) ..
> 
> Thanks a lot!
> []s
> Marcelo

Hi Mike,

    I saw that one, but I'm using "note_" ... Shouldn't _ be recognized as a
character instead a space?

Thanks,
Marcelo
"Mike Evans" <makis1970@hotmail.com> wrote in message
news:1pw1yp2gs5ka5$.kgqksmet2iyf.dlg@40tude.net...
> On Fri, 29 Oct 2004 09:41:17 -0400, Marcelo Ramos wrote:
> Marcelo
> These is from clipper Manual
>  NOTE*
>  Place a single-line comment in a program file
> --------------------------------------------------------------------------
----
>  Syntax
>
>      NOTE [<commentText>]
>
>  Arguments
>
>      <commentText> is a string of characters placed after the comment
>      indicator.
>
>  Description
>
>      NOTE is command synonym for the single-line comment indicator (*).
> All
>      characters after NOTE are ignored until the CA-Clipper compiler
>      encounters an end of line (carriage return/line feed).  This means a
>      single-line comment cannot be continued with the semicolon ( onto a
>      new line.
>
>      If you need a multi-line or inline comment, begin the comment block
> with
>      a slash-asterisk (/*) symbol and end the comment block with an
>      asterisk-slash (*/) symbol.  If you need to comment out a block of
> code,
>      use the conditional compilation directives #ifdef...#endif instead of
>      multiline comments.  This is important since nested comments are
>      illegal.
>
>      NOTE is a compatibility command and therefore not recommended.  It is
>      superseded by the C-style comment symbols slash-asterisk (/*) and
>      asterisk-slash (*/), as well as the double-slash (//).  It is also
>      superseded by the dBASE-style comment symbols, asterisk (*) and the
>      double-ampersand (&&).
>
>      For a complete discussion on comment indicators, refer to the "Basic
>      Concepts" chapter in the Programming and Utilities Guide.
>
>  Examples
>
>        These examples show the various comment symbols supported by
>         CA-Clipper:
>
>          This is a comment
>         /* This is a comment */
>         * This is a comment
>         && This is a comment
>         NOTE This is a comment
>
> Regards
> Mike Evans
> > Hi there guys,
> >
> >     I'm not sure that is a bug, but for sure is a very strange case.
> >     Early this week I have open a thread on this newsgroup about
> > xBase skipping some lines of code. But after some more elaborated tests
> > seems like xBase skips lines only (so far) in 1 specific case: If the
line
> > of code STARTS with "note_" xbase will just SKIP the line..
> >    Did anyone had the same problem?
> >    Well anyways to save you guys some time in case you want to test this
> > issue,
> > I've wrote a small program to reproduce the problem, just PBUILD it..
> >
> >     If anyone has a solution for that (other then changing note_ to
> > something else :D) ..
> >
> > Thanks a lot!
> > []s
> > Marcelo

On Fri, 29 Oct 2004 11:03:18 -0400, Marcelo Ramos wrote:

> Hi Mike,
> 
>     I saw that one, but I'm using "note_" ... Shouldn't _ be recognized as a
> character instead a space?
> 
> Thanks,
> Marcelo
> "Mike Evans" <makis1970@hotmail.com> wrote in message
> news:1pw1yp2gs5ka5$.kgqksmet2iyf.dlg@40tude.net...
>> On Fri, 29 Oct 2004 09:41:17 -0400, Marcelo Ramos wrote:
>> Marcelo
>> These is from clipper Manual
>>  NOTE*
>>  Place a single-line comment in a program file
>> --------------------------------------------------------------------------
> ----
>>  Syntax
>>
>>      NOTE [<commentText>]
>>
>>  Arguments
>>
>>      <commentText> is a string of characters placed after the comment
>>      indicator.
>>
>>  Description
>>
>>      NOTE is command synonym for the single-line comment indicator (*).
>> All
>>      characters after NOTE are ignored until the CA-Clipper compiler
>>      encounters an end of line (carriage return/line feed).  This means a
>>      single-line comment cannot be continued with the semicolon ( onto a
>>      new line.
>>
>>      If you need a multi-line or inline comment, begin the comment block
>> with
>>      a slash-asterisk (/*) symbol and end the comment block with an
>>      asterisk-slash (*/) symbol.  If you need to comment out a block of
>> code,
>>      use the conditional compilation directives #ifdef...#endif instead of
>>      multiline comments.  This is important since nested comments are
>>      illegal.
>>
>>      NOTE is a compatibility command and therefore not recommended.  It is
>>      superseded by the C-style comment symbols slash-asterisk (/*) and
>>      asterisk-slash (*/), as well as the double-slash (//).  It is also
>>      superseded by the dBASE-style comment symbols, asterisk (*) and the
>>      double-ampersand (&&).
>>
>>      For a complete discussion on comment indicators, refer to the "Basic
>>      Concepts" chapter in the Programming and Utilities Guide.
>>
>>  Examples
>>
>>      ¦  These examples show the various comment symbols supported by
>>         CA-Clipper:
>>
>>          This is a comment
>>         /* This is a comment */
>>         * This is a comment
>>         && This is a comment
>>         NOTE This is a comment
>>
>> Regards
>> Mike Evans
>>> Hi there guys,
>>>
>>>     I'm not sure that is a bug, but for sure is a very strange case.
>>>     Early this week I have open a thread on this newsgroup about
>>> xBase skipping some lines of code. But after some more elaborated tests
>>> seems like xBase skips lines only (so far) in 1 specific case: If the
> line
>>> of code STARTS with "note_" xbase will just SKIP the line..
>>>    Did anyone had the same problem?
>>>    Well anyways to save you guys some time in case you want to test this
>>> issue,
>>> I've wrote a small program to reproduce the problem, just PBUILD it..
>>>
>>>     If anyone has a solution for that (other then changing note_ to
>>> something else :D) ..
>>>
>>> Thanks a lot!
>>> []s
>>> Marcelo

Marcelo 
I'm not sure but the NOTE is exactly like * in the start of line. So after
the word NOTE everythink is considered as a comment. So yes you have an
underscore after the NOTE but even these character is considered as a
comment.
Regards
Mike Evans

Marcelo

From the docs
-------------------------
Syntax 

NOTE [<Comment>] 

Parameters 

NOTE <Comment>

<Comment> is any one line of text in the source code. It will be ignored by
the compiler. 

Description 

NOTE identifies a line in the program source code as a comment and
indicates that it should not be compiled. This command exists only for
compatibility reasons. A comment line should be identified with an asterisk
(*) at the beginning of the line instead of using NOTE. 
Comments that are longer than one line are excluded from compilation using
the character pairs /* (begin comment) and */ (end comment). Inline
comments can be identified by the characters  or &&. 
----------------

It seems the debugger is recognizing these lines as comments ...

>     If anyone has a solution for that (other then changing note_ to
> something else :D) ..

Yeap, ask Alaska <VBG>

Very Best Regards

João Pedro Machado de Sousa

Hi Joao,

    I saw that one, but I'm using "note_" ... Shouldn't _ be recognized as a
character instead a space?

Thanks,
Marcelo

"Joo Pedro Machado de Sousa" <macsousa@maso.co pt> wrote in message
news:1jpmclp70jo6c.tv5cn0vnx5lr$.dlg@40tude.net...
> Marcelo
>
> From the docs
> -------------------------
> Syntax
>
> NOTE [<Comment>]
>
> Parameters
>
> NOTE <Comment>
>
> <Comment> is any one line of text in the source code. It will be ignored
by
> the compiler.
>
> Description
>
> NOTE identifies a line in the program source code as a comment and
> indicates that it should not be compiled. This command exists only for
> compatibility reasons. A comment line should be identified with an
asterisk
> (*) at the beginning of the line instead of using NOTE.
> Comments that are longer than one line are excluded from compilation using
> the character pairs /* (begin comment) and */ (end comment). Inline
> comments can be identified by the characters  or &&.
> ----------------
>
> It seems the debugger is recognizing these lines as comments ...
>
> >     If anyone has a solution for that (other then changing note_ to
> > something else :D) ..
>
> Yeap, ask Alaska <VBG>
>
> Very Best Regards
>
> Joo Pedro Machado de Sousa

Hi Marcelo

>     I saw that one, but I'm using "note_" ... Shouldn't _ be recognized as a
> character instead a space?

You're right, it _should_, which does not mean it does . You should
mail this one to support@alaska-software.com. It may be some bug

Very Best Regards

João Pedro Machado de Sousa

Hi Marcelo

There is definately a difference beetween Clipper and Xbase++ which is not,
at least, documented:

if you

clipper temp /p -> the line Note_Pad:=100 is included

but with

xpp temp /p -> the line is skipped

So, once again, you should address the only ones who can do anything about
it: Alaska support.

Very Best Regards

João Pedro Machado de Sousa

On Fri, 29 Oct 2004 09:41:17 -0400, Marcelo Ramos wrote:
Marcelo
http://www.alaska-software.com/scripts/waa001.dll?WAA_PACKAGE=PUBLICDTS&WAA_FORM=DISPLAYPDR&PDRID=5245
They have allready fixed it

Regards
Mike Evans
> Hi there guys,
> 
>     I'm not sure that is a bug, but for sure is a very strange case.
>     Early this week I have open a thread on this newsgroup about
> xBase skipping some lines of code. But after some more elaborated tests
> seems like xBase skips lines only (so far) in 1 specific case: If the line
> of code STARTS with "note_" xbase will just SKIP the line..
>    Did anyone had the same problem?
>    Well anyways to save you guys some time in case you want to test this
> issue,
> I've wrote a small program to reproduce the problem, just PBUILD it..
> 
>     If anyone has a solution for that (other then changing note_ to
> something else :D) ..
> 
> Thanks a lot!
> []s
> Marcelo

I read in a thread somewhere where note_ are preprocessed as the old dbnase
style note command ( like  or /* */)
Theres a PDR that fixes this problem with the compiler.

See the thread called "The compiler skip code lines started with note_" in
the new.xbase convo. I think the PDR is

 this problem is know under PDR 5245, you can get a hotfix from
 Technical Support upon request. Please send email to
support@alaska-software.com
 requesting hotfix for PDR 5245.


Regards,
Mark Bloomfield


"Marcelo Ramos" <mramos@caisoftdesign.ca> wrote in message
news:WAsr1xbvEHA.8060@S15147418...
> Hi there guys,
>
>     I'm not sure that is a bug, but for sure is a very strange case.
>     Early this week I have open a thread on this newsgroup about
> xBase skipping some lines of code. But after some more elaborated tests
> seems like xBase skips lines only (so far) in 1 specific case: If the line
> of code STARTS with "note_" xbase will just SKIP the line..
>    Did anyone had the same problem?
>    Well anyways to save you guys some time in case you want to test this
> issue,
> I've wrote a small program to reproduce the problem, just PBUILD it..
>
>     If anyone has a solution for that (other then changing note_ to
> something else :D) ..
>
> Thanks a lot!
> []s
> Marcelo
>
>
>