factor/basis/libc/libc-tests.factor

USING: destructors kernel libc libc.private namespaces
tools.test ;

100 malloc "block" set

{ t } [ "block" get malloc-exists? ] unit-test

{ } [ [ "block" get &free drop ] with-destructors ] unit-test

{ f } [ "block" get malloc-exists? ] unit-test

{ "Operation not permitted" } [ 1 strerror ] unit-test
libc: fix tests using. 2014-04-04 12:29:42 -04:00			`USING: destructors kernel libc libc.private namespaces`
			`tools.test ;`
libc: test "1 strerror" since zero gives different output on different platforms. 2014-04-04 12:28:39 -04:00
			`100 malloc "block" set`

factor: Retrying on the unit tests. Also normalize some syntax with FUNCTION:. 2015-07-02 20:28:17 -04:00			`{ t } [ "block" get malloc-exists? ] unit-test`
libc: test "1 strerror" since zero gives different output on different platforms. 2014-04-04 12:28:39 -04:00
factor: Retrying on the unit tests. Also normalize some syntax with FUNCTION:. 2015-07-02 20:28:17 -04:00			`{ } [ [ "block" get &free drop ] with-destructors ] unit-test`
libc: test "1 strerror" since zero gives different output on different platforms. 2014-04-04 12:28:39 -04:00
factor: Retrying on the unit tests. Also normalize some syntax with FUNCTION:. 2015-07-02 20:28:17 -04:00			`{ f } [ "block" get malloc-exists? ] unit-test`
libc: test "1 strerror" since zero gives different output on different platforms. 2014-04-04 12:28:39 -04:00
factor: Retrying on the unit tests. Also normalize some syntax with FUNCTION:. 2015-07-02 20:28:17 -04:00			`{ "Operation not permitted" } [ 1 strerror ] unit-test`