rust/src/test/run-pass/invoke-external-native.rs

// xfail-fast
// aux-build:native_lib.rs

// The purpose of this test is to check that we can
// successfully (and safely) invoke external, cdecl
// functions from outside the crate.

use native_lib;

fn main() {
    let foo = native_lib::rustrt::last_os_error();
}
core: Clean up comments and exports 2012-03-10 00:04:09 -08:00			`// xfail-fast`
			`// aux-build:native_lib.rs`
work around bug when calling c-stack-cdecl fns from outside crate In the main test, I call the wrapper instead of the native fn, as intended. I also added an xfail-test that exercises the broken code path. Will file a bug. Description of the broken code path: The code path is that when we look up the external identifier we go through trans_external_path() -> type_of_ty_param_kinds_and_ty() -> type_of_fn_from_ty() -> type_of_fn(), and type_of_fn() adds a lot of external parameters. Problem is, I guess, that we don't pass the native ABI (or even the fact that it's a native function!), just the types and kinds of the parameters. 2011-10-21 12:14:01 -07:00
			`// The purpose of this test is to check that we can`
Add "cdecl" as synonym for "c-stack-cdecl" 2011-11-09 16:04:07 -08:00			`// successfully (and safely) invoke external, cdecl`
work around bug when calling c-stack-cdecl fns from outside crate In the main test, I call the wrapper instead of the native fn, as intended. I also added an xfail-test that exercises the broken code path. Will file a bug. Description of the broken code path: The code path is that when we look up the external identifier we go through trans_external_path() -> type_of_ty_param_kinds_and_ty() -> type_of_fn_from_ty() -> type_of_fn(), and type_of_fn() adds a lot of external parameters. Problem is, I guess, that we don't pass the native ABI (or even the fact that it's a native function!), just the types and kinds of the parameters. 2011-10-21 12:14:01 -07:00			`// functions from outside the crate.`

core: Clean up comments and exports 2012-03-10 00:04:09 -08:00			`use native_lib;`

work around bug when calling c-stack-cdecl fns from outside crate In the main test, I call the wrapper instead of the native fn, as intended. I also added an xfail-test that exercises the broken code path. Will file a bug. Description of the broken code path: The code path is that when we look up the external identifier we go through trans_external_path() -> type_of_ty_param_kinds_and_ty() -> type_of_fn_from_ty() -> type_of_fn(), and type_of_fn() adds a lot of external parameters. Problem is, I guess, that we don't pass the native ABI (or even the fact that it's a native function!), just the types and kinds of the parameters. 2011-10-21 12:14:01 -07:00			`fn main() {`
core: Clean up comments and exports 2012-03-10 00:04:09 -08:00			`let foo = native_lib::rustrt::last_os_error();`
re-enable tests for #1058 and #1059 2011-11-18 16:29:01 -08:00			`}`