A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1771 
====================================================================== 
Reported By:                calestyo
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1771
Category:                   Shell and Utilities
Type:                       Enhancement Request
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Christoph Anton Mitterer 
Organization:                
User Reference:              
Section:                    Utilities / printf 
Page Number:                3269 
Line Number:                111019 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2023-08-07 19:22 UTC
Last Modified:              2023-08-31 16:10 UTC
====================================================================== 
Summary:                    support or reserve %q as printf-utility format
specifier
====================================================================== 

---------------------------------------------------------------------- 
 (0006439) Don Cragun (manager) - 2023-08-31 16:10
 https://www.austingroupbugs.net/view.php?id=1771#c6439 
---------------------------------------------------------------------- 
On page 2793 line 92597-92599 section echo, add a sentence after the
example:<blockquote>However, this usage of %b with the <i>printf</i>
utility is now obsolescent, and applications desiring escape sequence
processing on non-XSI implementations should instead place escape sequences
(other than \c) to be processed in the format string of the <i>printf</i>
utility.</blockquote>

On page 3269 line 111000-111019 section printf, add OB shading to list item
7 (b conversion)

On page 3271 line 111104 section printf, change:<blockquote>The %b
conversion specification is not part of the ISO C standard; it has been
added here as a portable way to process <backslash>-escapes expanded in
string operands as provided by the <i>echo</i> utility. See also the
APPLICATION USAGE section of [xref to echo] for ways to use <i>printf</i>
as a replacement for all of the traditional versions of the <i>echo</i>
utility.</blockquote>to:<blockquote>The %b conversion was originally added
as a portable way to process <backslash>-escapes expanded in string
operands as provided by the <i>echo</i> utility on XSI implementations.
However, it will conflict with the next version of the ISO C standard,
which is adding it for binary output of integers, and has consequently been
marked obsolescent.</blockquote>

After page 3275 line 111227 section printf, add two paragraphs to FUTURE
DIRECTIONS:<blockquote>A future version of this standard may change the %b
conversion to a binary conversion in alignment with the next version of the
ISO C standard. It is recommended that implementations treat the "%#s"
conversion specification, which is undefined by this standard, as a synonym
for the current "%b" behavior; this can then be added in a future version
of this standard once there is existing practice.


A future version of this standard may add a %q or %Q conversion (or both)
to convert a string argument to a quoted output format that can be reused
as shell input.</blockquote> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-08-07 19:22 calestyo       New Issue                                    
2023-08-07 19:22 calestyo       Name                      => Christoph Anton
Mitterer
2023-08-07 19:22 calestyo       Section                   => Utilities / printf
2023-08-07 19:22 calestyo       Page Number               => 3269            
2023-08-07 19:22 calestyo       Line Number               => 111019          
2023-08-07 19:36 chet_ramey     Note Added: 0006416                          
2023-08-07 19:46 calestyo       Note Added: 0006417                          
2023-08-07 23:39 salewski       Issue Monitored: salewski                    
2023-08-08 08:46 geoffclare     Note Added: 0006418                          
2023-08-08 14:28 calestyo       Note Added: 0006420                          
2023-08-08 15:04 geoffclare     Note Added: 0006421                          
2023-08-08 17:10 calestyo       Note Added: 0006422                          
2023-08-08 18:45 eblake         Note Added: 0006423                          
2023-08-08 20:40 jsm28          Note Added: 0006424                          
2023-08-08 20:53 calestyo       Note Added: 0006425                          
2023-08-31 16:10 Don Cragun     Note Added: 0006439                          
======================================================================


  • [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
    • [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