A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1710 
====================================================================== 
Reported By:                rillig
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1710
Category:                   Shell and Utilities
Type:                       Omission
Severity:                   Editorial
Priority:                   normal
Status:                     Resolved
Name:                       Roland Illig 
Organization:                
User Reference:              
Section:                    make 
Page Number:                3113 
Line Number:                104930 
Final Accepted Text:        https://austingroupbugs.net/view.php?id=1710#c6357 
Resolution:                 Accepted As Marked
Fixed in Version:           
====================================================================== 
Date Submitted:             2023-05-07 14:00 UTC
Last Modified:              2023-06-27 09:16 UTC
====================================================================== 
Summary:                    Evaluate delayed-expansion macros in '!=' macro
definition
====================================================================== 

---------------------------------------------------------------------- 
 (0006362) geoffclare (manager) - 2023-06-27 09:16
 https://austingroupbugs.net/view.php?id=1710#c6362 
---------------------------------------------------------------------- 
> Did you consider rewording the text

No, we didn't. We just took the existing structure and updated it to fix
the conflicts with other parts of the text.

> Aren't all these details already covered by the sentence starting in line
104914?

Given that what we changed was done in order to resolve conflicts with
other text, I suppose that does mean that the other text in question
already covers it. (That's not just line 104914, but that line in
combination with other parts.) So maybe it would work if we just change the
text to:<blockquote>Delayed-expansion macros after the <equals-sign> in
macro definitions other than the :::=, !=, and += forms, and after the
<equals-sign> in += form macro definitions where the macro named by
<i>string1</i> exists and is a delayed-expansion macro, shall only be
evaluated when the defined macro is expanded.</blockquote> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-05-07 14:00 rillig         New Issue                                    
2023-05-07 14:00 rillig         Name                      => Roland Illig    
2023-05-07 14:00 rillig         Section                   => make            
2023-05-07 14:00 rillig         Page Number               => 3113            
2023-05-07 14:00 rillig         Line Number               => 104930          
2023-05-07 14:03 rillig         Note Added: 0006274                          
2023-06-26 16:22 geoffclare     Note Added: 0006357                          
2023-06-26 16:24 geoffclare     Final Accepted Text       =>
https://austingroupbugs.net/view.php?id=1710#c6357    
2023-06-26 16:24 geoffclare     Status                   New => Resolved     
2023-06-26 16:24 geoffclare     Resolution               Open => Accepted As
Marked
2023-06-26 16:24 geoffclare     Tag Attached: issue8                         
2023-06-26 16:27 geoffclare     Note Added: 0006358                          
2023-06-26 16:59 rillig         Note Added: 0006359                          
2023-06-26 17:01 rillig         Note Edited: 0006359                         
2023-06-27 09:16 geoffclare     Note Added: 0006362                          
======================================================================


  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issue ... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to