bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/518] Documentation error for MEMORY command


From: dk at artimi dot com
Subject: [Bug ld/518] Documentation error for MEMORY command
Date: 18 Nov 2004 17:53:59 -0000

------- Additional Comments From dk at artimi dot com  2004-11-18 17:53 -------
Subject: RE:  Documentation error for MEMORY command

> -----Original Message-----
> From: nickc at redhat dot com 

> ------- Additional Comments From nickc at redhat dot com  
> 2004-11-18 17:41 -------
> Subject: Re:  New: Documentation error for MEMORY command
> 
> Hi Dave,

  Hiya!

> How about this patch for rewording this part of the manual ?  I was not 
> sure whether I ought to remove the part about "must evaluate to a 
> constant" since this is now redundant.  (Numerical only expressions have 
> to evaluate to a constant).  But there did not seem to be any harm in 
> leaving it in.

  If there are no symbols involved, is there any distinction left between
before and after memory allocation?  If not, we could perhaps simplify the
description slightly further, leaving that bit out altogether.  Otherwise,
looks good to me, with just one slight nit:

--- 3843,3862 ----
  @kindex ORIGIN =
  @kindex o =
  @kindex org =
! The @var{origin} is an nurmical expression for the start address of
                         ^^^^^^^^

  You mis-speeled "numrical"!  ;)
  

> I do not think that we need to say "support for expressions might be 
> implemented in the future" in order to encourage someone to do that.  If 
> someone wants it badly enough they will write the code and submit it.

  Absolutely agree.  There are a potentially infinite number of possible
future enhancements, we can't start documenting all the features that don't
exist as well as the ones that do!

    cheers, 
      DaveK


-- 


http://sources.redhat.com/bugzilla/show_bug.cgi?id=518

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]