FILE HANDLE bug?

[Albert-Jan Roskam-2]

Hi,
 
Yesterday I ran it to the following weird thing. It happened in the context of a parametrized Production Facility (which uses macros with a '@' prefix), but this does not really matter. But The inline comment prevents the FILE HANDLE from working. Any idea why?
 
DEFINE @input () "c:/will_expand.sav" !ENDDEFINE.
DEFINE @output () "c:/will_not_expand.sav" !ENDDEFINE.
FILE HANDLE input /NAME  = @input.
FILE HANDLE output /NAME = @output.  /* I can haz no expanzzzion?.
SHOW HANDLES.

Regards,

Albert-Jan




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

All right, but apart from the sanitation, the medicine, education, wine, public order, irrigation, roads, a

fresh water system, and public health, what have the Romans ever done for us?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[Kirill Orlov]

The bug seems to be associated with a comment after FILE HANDLE.
Erase the comment and rerun.

05.08.2014 13:09, Albert-Jan Roskam пишет:

Hi,
 
Yesterday I ran it to the following weird thing. It happened in the context of a parametrized Production Facility (which uses macros with a '@' prefix), but this does not really matter. But The inline comment prevents the FILE HANDLE from working. Any idea why?
 
DEFINE @input () "c:/will_expand.sav" !ENDDEFINE. 
DEFINE @output () "c:/will_not_expand.sav" !ENDDEFINE. 
FILE HANDLE input /NAME  = @input. 
FILE HANDLE output /NAME = @output.  /* I can haz no expanzzzion?. 
SHOW HANDLES.

Regards,

Albert-Jan




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

All right, but apart from the sanitation, the medicine, education, wine, public order, irrigation, roads, a 

fresh water system, and public health, what have the Romans ever done for us?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD

[Andy W]

It isn't just a "bug" with FILE HANDLE, it appears that inline comments prevent expansion for other commands as well. For example:

DEFINE @input () "c:/will_expand.sav" !ENDDEFINE.
DEFINE @output () "c:/will_not_expand.sav" !ENDDEFINE.
ECHO @input.
ECHO @output. /*cheese*/.

[Jon K Peck]

It appears that this problem is tied up with macro expansion - @ symbols in production mode are actually mini macros.   This behavior may have always been that way, but I have filed a bug on it.


Jon Peck (no "h") aka Kim
Senior Software Engineer, IBM
[hidden email]
phone: [phone]




From:        Albert-Jan Roskam <[hidden email]>
To:        [hidden email]
Date:        08/05/2014 03:10 AM
Subject:        [SPSSX-L] FILE HANDLE bug?
Sent by:        "SPSSX(r) Discussion" <[hidden email]>

---

Hi,
 
Yesterday I ran it to the following weird thing. It happened in the context of a parametrized Production Facility (which uses macros with a '@' prefix), but this does not really matter. But The inline comment prevents the FILE HANDLE from working. Any idea why?
 
DEFINE @input () "c:/will_expand.sav" !ENDDEFINE.
DEFINE @output () "c:/will_not_expand.sav" !ENDDEFINE.
FILE HANDLE input /NAME  = @input.
FILE HANDLE output /NAME = @output.  /* I can haz no expanzzzion?.
SHOW HANDLES.

Regards,

Albert-Jan




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

All right, but apart from the sanitation, the medicine, education, wine, public order, irrigation, roads, a

fresh water system, and public health, what have the Romans ever done for us?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD


===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD

[David Marso]

Actually it has to do with the period '.' before the /* comment! ;-)

@Albert-Jan
/**/.
DEFINE @input () "c:/will_expand.sav" !ENDDEFINE.
DEFINE @output () "c:/will_not_expand.sav" !ENDDEFINE.
FILE HANDLE input /NAME  = @input.
FILE HANDLE output /NAME = @output /* I can haz no expanzzzion?.
SHOW HANDLES.


@Andy
/**/.
DEFINE @input () "c:/will_expand.sav" !ENDDEFINE.
DEFINE @output () "c:/will_not_expand.sav" !ENDDEFINE.
ECHO @input.
ECHO @output /*cheese*/.

Kirill Orlov wrote

The bug seems to be associated with a comment after FILE HANDLE.
Erase the comment and rerun.

05.08.2014 13:09, Albert-Jan Roskam ?????:
> Hi,
>  
> Yesterday I ran it to the following weird thing. It happened in the context of a parametrized Production Facility (which uses macros with a '@' prefix), but this does not really matter. But The inline comment prevents the FILE HANDLE from working. Any idea why?
>  
> DEFINE @input () "c:/will_expand.sav" !ENDDEFINE.
> DEFINE @output () "c:/will_not_expand.sav" !ENDDEFINE.
> FILE HANDLE input /NAME  = @input.
> FILE HANDLE output /NAME = @output.  /* I can haz no expanzzzion?.
> SHOW HANDLES.
>
> Regards,
>
> Albert-Jan
>
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> All right, but apart from the sanitation, the medicine, education, wine, public order, irrigation, roads, a
>
> fresh water system, and public health, what have the Romans ever done for us?
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> =====================
> To manage your subscription to SPSSX-L, send a message to
> [hidden email] (not to SPSSX-L), with no body text except the
> command. To leave the list, send the command
> SIGNOFF SPSSX-L
> For a list of commands to manage subscriptions, send the command
> INFO REFCARD
>
>



=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD

[Kirill Orlov]

If you remove the period after @output, it then works OK.
But it is nasty, Andy. I'm upset. Don't know what to say.

05.08.2014 15:46, Andy W пишет:

DEFINE @input () "c:/will_expand.sav" !ENDDEFINE. 
DEFINE @output () "c:/will_not_expand.sav" !ENDDEFINE. 
ECHO @input. 
ECHO @output. /*cheese*/.

===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD