Mikhael Goikhman <[EMAIL PROTECTED]> writes: > On 04 Feb 2006 16:56:47 +0000, seventh guardian wrote: > > > > > > existing structure only stores the name, and not the asterisk. Of > > > > course we could use the existing char* MyName, but that would defeat > > > > the whole purpose of using the ModuleArgs struct. > > > > > > > > I wonder if we need the asterisk in the first place. Wouldn't it be > > > > easyer "new-code-wise" to use only the name for pattern matching? It > > > > could be stripped off by fvwm or simply not used in the config files. > > > > > > > > (since this is only experimental code we are allowed to forget > > > > backward compatibility issues) > > > > > > Eventually you have to deal with compatibility. > > > > Yes, but unless there's a reason for the use of the asterisk, it is > > cleaner not to have it. Configuration keywords are changing all the > > time, it won't be that difficult to strip the * from the config files. > > Here you speak about the fvwm configuration. You can't omit the asterisk > without inventing a new syntax that does not conflict with the syntax of > fvwm commands and functions. I see no problem in the asterisks syntax, it > seems to be more optimal than other possible syntaxes for module configs.
The asterisk tells Fvwm to save up the module config commands, not parse them. It then sends out the commands to a module when the module asks for them. There's more to it than what I just described. Check the module documentation. -- Dan Espen E-mail: [EMAIL PROTECTED]
