guile-devel
[Top][All Lists]
Advanced

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

Re: [PATCH] Explain why no native accessors for `s8' and `u8' exist


From: Andy Wingo
Subject: Re: [PATCH] Explain why no native accessors for `s8' and `u8' exist
Date: Sun, 26 Feb 2017 19:04:51 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

Happy to apply; can you fix up the changelog?  Just see any recent
commit to this file for the format.  Thanks :)

Andy

On Thu 23 Feb 2017 20:48, "Diogo F. S. Ramos" <address@hidden> writes:

> Instead of saying it is obvious, explain why no native endianness
> accessors exist for the `s8' and `u8' variants.
> ---
>  doc/ref/api-data.texi | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi
> index 1b3170e..bf46d5c 100644
> --- a/doc/ref/api-data.texi
> +++ b/doc/ref/api-data.texi
> @@ -6942,8 +6942,9 @@ Store @var{value} as an @var{n}-bit (signed) integer 
> (where @var{n} is
>  @end deffn
>  
>  Finally, a variant specialized for the host's endianness is available
> -for each of these functions (with the exception of the @code{u8}
> -accessors, for obvious reasons):
> +for each of these functions (with the exception of the @code{u8} and
> address@hidden accessors, as endianness is about byte order and there is only
> +1 byte):
>  
>  @deffn {Scheme Procedure} bytevector-u16-native-ref bv index
>  @deffnx {Scheme Procedure} bytevector-s16-native-ref bv index



reply via email to

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