It is true you would be able to get a bit extra mileage doing this in
the info function, but I don't really want to detach the info function
[(info...)] from the info var syntax {::var}, at least in the core.
That is, I don't want separate patterns. And changing the way vars
work just looks a bit too dramatic to change at this point.I'd be more inclined to support a change to the info function that might be able to take a special info extension for this kind of stuff. Or a completely separate function is possible. I prefer the idea of having all (core) vars act like a field_name not a "string of text". But I suppose you could try resetting the $BOLTinfoVarPat in a config file and see if it doesn't at least partially work for you. I'm not sure what other implications there might be. But there's a good chance it might just work fine. Let me know... Cheers, Dan On Tue, Jul 28, 2009 at 11:11 AM, Martin<[email protected]> wrote: > > Thank you for taking care of this. > >> DM's point that changing the default pattern might also adversely >> affect performance is also noted. And I suspect he's right, though I >> haven't tested. I'm willing to explore or help with other options if >> this capability is needed, but think it's best for BoltWire if we >> think of info var field names as a variable, not a string. IE, not >> spaces or weird punctuation, etc. > > Changing > if ($BOLTinfoVarPat == '') $pattern = '/^(\S+)\: (.+)?/m'; > aka "no white space" > to > if ($BOLTinfoVarPat == '') $pattern = '/^([A-Za-z0-9]+)\: (.+)?/m'; > wouldn't hurt? > > Greetings, Martin > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
