From: Xavier V. <xav...@fr...> - 2004-02-18 10:29:00
|
Hello list ! > - there is no real 'object/method' system behind, so why try to mimic one? But there's a king of 'namespace/function' like in Perl, so I keep :: (I like being flamed ;) ). Another argument is below. > - the only reason for this delimiter is that the evaluator needs a hint > how to find the plugin that offers a specific function. So the function > name has to start with the plugin name. If a plugin offers just one > function, it may take only the plugin name (without any extension) > > function call to foo(): > [...] > function call to foo_bar(): > [...] And what about i2c_sensors() and proc_stat() ?? The eval will try to load plugin_i2c.so or plugin_proc.so !! We'll have to find another replacement for spaces or write i2csensors() or I2cSensors() which is quite uggly :/ So I don't think '_' is the best choice as it's already used. > from the plugin's point of view, it's absolutely free to you (the > author) wether to implement a "generic parsing function" with the > requested item as a parameter, or to implement a seperate function for > each item, or both. That's what we were talking about. But instead of calling xmms::parse() you call it xmms(). Bye ! -- Xavier VELLO <xav...@fr...> |