* Edwin Eyan Moragas [110610 15:23]:
> downloaded and ran the unit tests
>
> now runs fine on osx snow leopard and obsd 4.8 32 bit.
Cool, thanks for testing!
Cheers,
Christian
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
downloaded and ran the unit tests
now runs fine on osx snow leopard and obsd 4.8 32 bit.
thanks a bunch again guys!
On Fri, Jun 10, 2011 at 9:01 PM, Edwin Eyan Moragas wrote:
> whopee!
>
> thanks Alex and ckeen!
>
> On Fri, Jun 10, 2011 at 8:24 PM, Alexander Burger
> wrote:
>> Hi Edwin,
>>
>>
whopee!
thanks Alex and ckeen!
On Fri, Jun 10, 2011 at 8:24 PM, Alexander Burger wrote:
> Hi Edwin,
>
>> We are at it ... :)
>
> We've got it!! Thanks to ckeen! :)
>
> There were actually two problems with the OpenBSD version:
>
> 1. Signal handling was wrong. There was the possibility of an arr
Hi Edwin,
> We are at it ... :)
We've got it!! Thanks to ckeen! :)
There were actually two problems with the OpenBSD version:
1. Signal handling was wrong. There was the possibility of an array
out-of-bound access because of a non-portable max signal number.
2. UDP handling was indeed wrong
Hi Edwin,
> ctrl-c when repl is running is not working on obsd. not sure if this
> is related to the signal() call. it's in my todo list.
Yes, that's the same case. The whole complex of catching signals.
We are at it ... :)
Cheers,
- Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=
On Fri, Jun 10, 2011 at 5:43 PM, Alexander Burger wrote:
> Hi Edwin,
>
>> i'll be on it. not sure about time frame tho since i'm diddling with
>
> Great!
>
>> an app at the moment. looks like i'm the only one running it on obsd
>> so i guess it's not an urgent issue. :)
>
> We are now discussing i
Hi Edwin,
> i'll be on it. not sure about time frame tho since i'm diddling with
Great!
> an app at the moment. looks like i'm the only one running it on obsd
> so i guess it's not an urgent issue. :)
We are now discussing it also in IRC. ckeen checked on his BSD system,
and the UDP binding wor
Hi Alex,
On Fri, Jun 10, 2011 at 4:05 PM, Alexander Burger wrote:
> Hi Edwin,
>
>> eyan@faya $ $(/bin/pwd)/p lib/test.l -bye +
>> [test/lib.l:5] !? (port T )
>> IP bind error: Address already in use
>
> Oh, I see. This are the unit tests, and it is the place where it tries
> to bind to a UDP
Hi Edwin,
> eyan@faya $ $(/bin/pwd)/p lib/test.l -bye +
> [test/lib.l:5] !? (port T )
> IP bind error: Address already in use
Oh, I see. This are the unit tests, and it is the place where it tries
to bind to a UDP port.
So it seems the UDP handling of PicoLisp doesn't work under Mac OS (and
Hi Alex,
On Fri, Jun 10, 2011 at 1:16 PM, Alexander Burger wrote:
> Hi Edwin,
>
>> any chance ideas on how to fix this on osx?
>
> In which situation does this error appear?
not sure which specific one. but the ouput's here:
eyan@faya $ $(/bin/pwd)/p lib/test.l -bye +
[test/lib.l:5] !? (port T
Hi Edwin,
> any chance ideas on how to fix this on osx?
In which situation does this error appear?
An IP bind error occurs if a port is already used by (bound to) some
other process. This either happens if another, already running,
application uses the same port, or if you start your app a secon
On Fri, Jun 10, 2011 at 5:01 AM, Edwin Eyan Moragas wrote:
> Hi guys,
>
> any chance ideas on how to fix this on osx?
by the way, i changed the port numbers too and still get the same error.
>
> /e
>
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
12 matches
Mail list logo
