OpenEuphoria

1. Euphoria 3.2

• Posted by ArthurCrump Sep 15, 2012
• 1331 views

There appear to be a few people stll using pre-V4 Euphoria and some using both 3.1 and 4.0. How about a Euphoria version 3.2 whose only enhancement is an ifdef structure?

That would allow for libraries that work on both 3.2 and 4.0 or that use global on 3.2 and public on 4.0.

I am joking really because I gave up using v3.1 ages ago.

Arthur

3. Re: Euphoria 3.2

• Posted by BRyan Sep 15, 2012
• 1293 views

I have been working on ver 3 trying to add features. 
But I can not get anyone to tell me how to use call_func() from "C" code . 
I can not use callback because of DOS . 

5. Re: Euphoria 3.2

• Posted by mattlewis (admin) Sep 15, 2012
• 1302 views

Assuming that you want the backend of your interpreter to call some code in your translated front end, I think the best way (as Jim mentioned) is to use the same technique that 4.1 uses.

Basically, when backend.e calls the machine_func that hands control over to the back end, you pass a routine id. Note that this will be a valid routine id for your translated front end, NOT the user's program. Then, using the routine list that the translator creates, you can get a pointer to the correct translated function and call that from you backend C code.

Here's what the call looks like currently:

	machine_proc(65,  
		{ 
			st,  
			sl,  
			ms,  
			lit,  
			include_info,  
			get_switches(),  
			Argv, 
			routine_id( "cover_line" ), 
			routine_id( "cover_routine" ), 
			routine_id( "write_coverage_db" ), 
			routine_id( "DisplayColorLine" ), 
			external_debugger_ptr, 
			routine_id( "map:new" ), 
			routine_id( "map:put" ), 
			routine_id( "map:get" ), 
			trace_lines, 
			$ 
		}) 

In start_backend(), we then do:

 
	map_new = get_pos_int(w, *(x_ptr->base+13)); 
	map_put = get_pos_int(w, *(x_ptr->base+14)); 
	map_get = get_pos_int(w, *(x_ptr->base+15)); 

In be_execute.c:

 
// routine ids to euphoria std/map routines: 
int map_new; 
int map_put; 
int map_get; 
 
/** 

 * Call's the front end's map:new() function 
 */ 
object call_map_new(){ 
	return internal_general_call_back( map_new, 690, 0, 0, 0, 0, 0, 0, 0, 0 ); 
} 
 
/** 

 * Calls the front end's map:put procedure 
 */ 
void call_map_put( object map, object key, object value, object operation ){ 
	RefDS( map ); 
	Ref( key ); 
	Ref( value ); 
	internal_general_call_back( map_put, map, key, value, operation, 23 /* default threshold */, 0, 0, 0, 0 ); 
} 
 
/** 

 * Calls the front end's map:get function 
 */ 
object call_map_get( object map, object key, object default_value ){ 
	RefDS( map ); 
	Ref( key ); 
	Ref( default_value ); 
	return internal_general_call_back( map_get, map, key, default_value, 0, 0, 0, 0, 0, 0 ); 
} 

These are the functions that wrap the actual call to the translated front end routines. I'm not sure if the syntax, names, etc, is exactly the same as for 3.1 code, but you can look at some translated code that uses call_func() to see an example.

Matt