[wx-dev] Re: execve like wxExecute?

[Armel Asselin]

>>> > then I think adding a "const wxArrayString *env = NULL" parameter to 
>>> > (some)
>>> > wxExecute overloads would be a Good Thing.
>>> > I'd not use wxChar* or wxChar** pointers as IMO we should abstract
>>> from > the
>>> > OS-specific way of representing the environment.
>>>
>>> Then an even better choice might be something like a "const
>>> wxStringStringHashMap *env = NULL" parameter. This would remove
>>> the need for a specific format for the environment settings
>>> (even if it would just be "x=y").
>> it's maybe over-the-top, all the OSes seem OK with the VARIABLE=VALUE 
>> approach.
> however if you're using wxStringStringHashMap (I declare them in almost 
> all my wxprojects) it would be really handy to use it for such 
> environment-handling functions; so also having an overload which takes a 
> wxStringStringHashMap wouldn't be a bad idea IMHO.
finally, it seems the better idea to me (how to manipulate the values in 
fact, if they are not in such a collection)...
now the question is: is want to declare wxStringStringHashMap
(probably as DECLARE_STRING_HASH_MAP(wxString, wxStringStringHashMap) or 
similar)
won't you get into trouble??? where should I put it? directly at the end of 
hashmap.h?
or would there be a better place?

Armel