Hi Alex,
thank you. helps a lot.
cheers
/e
On Sun, Aug 28, 2011 at 2:53 AM, Alexander Burger wrote:
> Hi Edwin,
>
>> came across these macros in pico.h:
>>
>> #define isSym(x) (num(x)&WORD)
>> #define isSymb(x) ((num(x)&(WORD+2))==WORD)
>>
>> what is the intent of isSymb()? as comp
> On Fri, Aug 26, 2011 at 07:10:06PM +0200, Alexander Burger wrote:
>> Great, thanks! Got "code.s" ... will analyze it on Sunday.
>
> Good, just now I found the time! :)
>
>
> So I constructed a new "src64/sys/x86-64.openBsd.code.l" from what I
> found in your "code.s". I can't test it, but I hope
Hello Kim Max :-)
You are now subscribed
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Thanks Jakob,
On Sat, Aug 27, 2011 at 08:34:44PM +0200, Jakob Eriksson wrote:
> On Sat, Aug 27, 2011 at 08:25:05PM +0200, Alexander Burger wrote:
> > Ah, one important point: Can we be sure that OpenBSD uses the ELF linker
> > format? If not (e.g. the old "a.out" format), we might have problems
>
Hi Edwin,
> came across these macros in pico.h:
>
> #define isSym(x)(num(x)&WORD)
> #define isSymb(x) ((num(x)&(WORD+2))==WORD)
>
> what is the intent of isSymb()? as compared to isSym()?
as ever, the files "doc64/structures", "doc/structures" and
"mini/doc/structures" are the abs
On Sat, Aug 27, 2011 at 08:25:05PM +0200, Alexander Burger wrote:
> Ah, one important point: Can we be sure that OpenBSD uses the ELF linker
> format? If not (e.g. the old "a.out" format), we might have problems
> similar to those on Mac OS.
Yes:
http://www.phiral.net/openbsdasm.htm
I don't und
On Fri, Aug 26, 2011 at 07:10:06PM +0200, Alexander Burger wrote:
> Great, thanks! Got "code.s" ... will analyze it on Sunday.
Good, just now I found the time! :)
So I constructed a new "src64/sys/x86-64.openBsd.code.l" from what I
found in your "code.s". I can't test it, but I hope it is correc
Hi List,
came across these macros in pico.h:
#define isSym(x)(num(x)&WORD)
#define isSymb(x) ((num(x)&(WORD+2))==WORD)
what is the intent of isSymb()? as compared to isSym()?
yes, still on that long path of understanding the C implementation.
:). this is still minipicolisp by the