bugmake - Bugs: bug #66324, Typo in documentation?

 
 

bug #66324: Typo in documentation?

Submitter:  None
Submitted:  Fri 11 Oct 2024 04:05:25 PM UTC
   
 
Severity:  3 - Normal Item Group:  Documentation
Status:  Fixed Privacy:  Public
Assigned to:  psmith Open/Closed:  Closed
Component Version:  SCM Operating System:  Any
Fixed Release:  SCM Triage Status:  Small Effort
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 09 Dec 2024 04:36:49 AM UTC, comment #1: 

I applied the change.  Thanks for the pointer!

Paul D. Smith <psmith>
Group administrator
Fri 11 Oct 2024 04:05:25 PM UTC, original submission:  

Hi, I think section 6.11 Target-specific Variable Values has a typo. It says:

> The variable-assignment can be any valid form of assignment; recursive (‘=’), simple (‘:=’ or ‘::=’), immediate (‘::=’), ...


and the last operator should be `:::=` instead? The typo is there in the current master. I'd submit a patch/PR but couldn't easily find how to do so, here's the diff (untested

diff --git a/doc/make.texi b/doc/make.texi
index 4b9bf985..34a257f2 100644
--- a/doc/make.texi
+++ b/doc/make.texi
@@ -6773,7 +6773,7 @@ Multiple @var{target} values create a target-specific variable value for
 each member of the target list individually.
 
 The @var{variable-assignment} can be any valid form of assignment; recursive
-(@samp{=}), simple (@samp{:=} or @samp{::=}), immediate (@samp{::=}), shell
+(@samp{=}), simple (@samp{:=} or @samp{::=}), immediate (@samp{:::=}), shell
 (@samp{!=}), or appending (@samp{+=}), and may be preceded by a conditional
 modifier (@samp{?}).  The variable that appears within the
 @var{variable-assignment} is evaluated within the context of the target: thus,

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by psmith (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-12-09 psmith StatusNone Fixed
        Assigned toNone psmith
        Open/ClosedOpen Closed
        Operating SystemNone Any
        Fixed ReleaseNone SCM
        Triage StatusNone Small Effort

    Back to the top

    Powered by Savane 3.15-e6e5.
    Corresponding source code