Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

uint32 arrays show hexadecimal #1210

Closed
ViralBShah opened this issue Aug 25, 2012 · 6 comments
Closed

uint32 arrays show hexadecimal #1210

ViralBShah opened this issue Aug 25, 2012 · 6 comments

Comments

@ViralBShah
Copy link
Member 

julia> b = uint32([1 2 60])

1x3 Uint32 Array:
 0x00000001  0x00000002  0x0000003c
@ViralBShah
Copy link
Member Author

Also:

julia> uint32(5)
0x00000005

@JeffBezanson
Copy link
Member

Uh, that was done on purpose.

@StefanKarpinski
Copy link
Member

It's been like that for quite some time. Hex is has been the literal input and output format for unsigned ints for a while.

@ViralBShah
Copy link
Member Author

Ok - I filed because I thought it had slipped by. I can see why we do this. I can't decide if as a user, I would just like to see the integer value printed. I'll close this for now.

@pao
Copy link
Member

pao commented Aug 25, 2012

Would it be possible to build in REPL functionality so that we (as users) can control these sorts of things? I'm thinking of options along the lines of MATLAB's format commands. I suppose a reification of the REPL session might be needed to maintain those options if we wanted to be able to change them on the fly; show would need to know where to look.

I'm not sure the REPL-command escape character approach (such as GHCi's :-prefixed commands) make as much sense for Julia, especially considering how few characters there are to play with.

@ViralBShah
Copy link
Member Author

Yes, I have often used matlab's format, and it is certainly useful. Perhaps we should have a separate issue opened for this - or rename and reopen this issue.

KristofferC added a commit that referenced this issue Feb 25, 2025
@DilumAluthgeBot @KristofferC
🤖 [master] Bump the LinearAlgebra stdlib from e7da19f to f781708 (#57522
9f7cdfd 
)

Stdlib: LinearAlgebra
URL: https://github.com/JuliaLang/LinearAlgebra.jl.git
Stdlib branch: master
Julia branch: master
Old commit: e7da19f
New commit: f781708
Julia version: 1.13.0-DEV
LinearAlgebra version: 1.12.0(Does not match)
Bump invoked by: @KristofferC
Powered by:
[BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl)

Diff:
JuliaLang/LinearAlgebra.jl@e7da19f...f781708

```
$ git log --oneline e7da19f..f781708
f781708 use the custom sysimage when running documentation (and doctests) as well (#1226)
8fdbfd5 Add `getindex` for `SymTridiagonal` using a `BandIndex` (#1223)
91b8845 Use `BandIndex` directly in `diagzero` call in `getindex` (#1222)
ef7ef3a Restrict triangular type aliases to `AbstractMatrix`es (#1220)
af7a9ac Use `BandIndex` directly in `diagzero` call in `getindex` for banded matrices
579b5f7 Specialize Diagonal * Adjoint (#1207)
5cf41c4 Indirection in matrix multiplication to avoid ambiguities (#1210)
0a9c164 Remove specialized `issymmetric`/`ishermitian` for `Diagonal{<:Number}` (#1213)
ff5648a Make unitary matrices in `svd`/`eigen` of `Diagonal` be unitless (#1155)
e096a03 Don't mutate arrays in symmetric trig functions (#1206)
c234bed Loop over `diagind` in `diag` for banded matrices (#1211)
57785c7 More resizing for truncating return values from LAPACK (#1190)
b464203 Materialize adjoint in mul with `HermOrSym` (#1191)
16d9d61 Restrict Diagonal sqrt branch to positive diag (#1203)
baa48b7 Verbose `showerror` for `SingularException` (#1204)
e0b59a7 Remove `LinearAlgebra` qualifications in `cholesky.jl` (#1209)
95d009b Remove `LinearAlgebra` qualifications in `cholesky.jl`
c550974 change to pivot
ed35a37 Add fast path in generic matmul (#1202)
8c7fe68 Detailed `showerror` for `SingularException`
2a1696a Explicitly declare type constructor imports (#1196)
101f766 Added note to BLAS.[g|s]et_num_threads about Apple Accelerate not supporting it  (#1195)
5aca26f Simplify `getproperty` for `Cholesky*` (#1197)
924dda4 remove copy-allocation on accessing `cholesky` factors (`.L`, `.U`) (#1186)
6f02532 Use `BLAS.trsm!` instead of `LAPACK.trtrs!` in left-triangular solves (#1194)
```

Co-authored-by: KristofferC <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pao @StefanKarpinski @ViralBShah @JeffBezanson