On 2020-01-24 16:26, Peter Pentchev wrote:
PS. Don't get me wrong, I've done a lot of assembly language
programming, and it is undoubtedly the correct tool for some tasks.
Just... not all of them.
Back in "the day", I did a bunch of "in line" machine coding.
I was writing directly to video memo
gt; > > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > > This is just a trivia question.
> > > > > > >
> > > > > > > Does anyone know if the actual data stored in
> > &g
mailto:perl6-us...@perl.org>> wrote:
Hi All,
This is just a trivia question.
Does anyone know if the actual data stored in
Raku variables is little endian or big endian?
-T
On 2020-01-23 09:07, Paul Procacci wrote:
endianess is dictate by the cpu.
If I store the value
; perl6-users > > > > <mailto:perl6-us...@perl.org>> wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > This is just a trivia question.
> > > > >
> > > > > Does anyone know
l data stored in
Raku variables is little endian or big endian?
-T
On 2020-01-23 09:07, Paul Procacci wrote:
endianess is dictate by the cpu.
If I store the value 4 into some memory address, the storage of and
retrieval thereof is controlled by the cpu.
Then I presume Raku rug on a
On 1/23/20 6:28 PM, ToddAndMargo via perl6-users wrote:
On Thu, Jan 23, 2020 at 11:51 AM ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
Hi All,
This is just a trivia question.
Does anyone know if the actual data stored in
Raku variables is little end
On Thu, Jan 23, 2020 at 11:51 AM ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
Hi All,
This is just a trivia question.
Does anyone know if the actual data stored in
Raku variables is little endian or big endian?
-T
On 2020-01-23 09:07, Paul Pr
stion.
>
> Does anyone know if the actual data stored in
> Raku variables is little endian or big endian?
>
> -T
>
--
__
:(){ :|:& };:
Hi All,
This is just a trivia question.
Does anyone know if the actual data stored in
Raku variables is little endian or big endian?
-T
# New Ticket Created by Rob Hoelz
# Please include the string: [perl #126705]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=126705 >
MVM_string_utf16_encode_substr works using native endianness; we should have
operations for
On Mie. Mar. 14 11:46:38 2007, [EMAIL PROTECTED] wrote:
> I keep getting a test failure on t/op/stringu.t with test 25 on
> ppc-darwin(and likely all big endian systems with icu installed).
> Parrot outputs "\x00A\x00B" when the test expects "A\x00B\x00" to be
ely all big endian systems with icu installed).
Parrot outputs "\x00A\x00B" when the test expects "A\x00B\x00" to be
printed. I got a hint to the problem at the icu
faq(http://icu.sourceforge.net/userguide/icufaq.html). "A Unicode
string is currently represented as UTF
On Mon, Oct 17, 2005 at 12:48:32PM -0700, Leopold Toetsch wrote:
> 0 ... 8 byte IEEE double
> 1 ... 12 byte IEEE double (both according to endianess)
>
> We need additionally (at least and AFAIK):
>
> 2 ... 8 byte (ARM) mixed-endian
>
> which is according to Nichol
double (both according to endianess)
We need additionally (at least and AFAIK):
2 ... 8 byte (ARM) mixed-endian
which is according to Nicholas a LE double with 2 BE arranged words.
See also: src/packf*.c, pf/pf_items.c, t/native_pbc/number.t ...
Takers welcome,
leo
On Mon, Aug 09, 2004 at 05:20:41PM -0400, Dan Sugalski wrote:
> Applied, thanks. (With some chagrin, as I'm responsible for that
> particular monstrisity)
Parrot now passes all tests on Solaris built with LP64.
Nicholas Clark
At 1:52 PM -0700 8/9/04, Jarkko Hietaniemi (via RT) wrote:
Things like this
(int*)&something_not_int
just aren't cool. The attached patch does a horrible hack for
build_nativecall.pl to introduce the necessary temp variables.
With this patch IRIX64 is now passing all but one of the nci.t.
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #31029]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31029 >
Things like this
(int*)&something_not_int
just aren't cool. The attac
17 matches
Mail list logo