You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe design decisions and implementation reasons is required for developers
to answer "Why behaves so?" and to prevent corruption of implicit specification
on code rewriting.
Comment 1 YamaKen 2004-05-19 05:43:45 UTC
I have described a new function to follow the subject. I will continue so for a
week as a test drive.
/** Update custom value from property message.
Update custom value from property message. All variable update is
validated by custom APIs rather than arbitrary sexp
evaluation. Custom symbol \a custom is quoted in sexp string to be
restricted to accept symbol literal only. This prevents arbitrary
Add default destination for libuim output instead of /plugins
Without DESTDIR , uim will use /plugins as output directory.
Let set empty variable will make it use right output directory.
icy
added a commit
to icyfork/uim
that referenced
this issue
Nov 26, 2014
This reverts commit 64480c4, reversing
changes made to 75c12fc.
Reason:
* Changes are only made for PKGBUILD (TheSLinux specific)
* There isn't a clear reason why we do need this change
Moved from https://bugs.freedesktop.org/show_bug.cgi?id=639
YamaKen 2004-05-18 01:15:22 UTC
Describe design decisions and implementation reasons is required for developers
to answer "Why behaves so?" and to prevent corruption of implicit specification
on code rewriting.
Comment 1 YamaKen 2004-05-19 05:43:45 UTC
I have described a new function to follow the subject. I will continue so for a
week as a test drive.
/** Update custom value from property message.
Update custom value from property message. All variable update is
validated by custom APIs rather than arbitrary sexp
evaluation. Custom symbol \a custom is quoted in sexp string to be
restricted to accept symbol literal only. This prevents arbitrary
sexp evaluation.
*/
void
uim_prop_update_custom(uim_context uc, const char *custom, const char *val)
{
if(!custom || !val)
return;
UIM_EVAL_FSTRING3(uc, "(prop-handler %d 'prop-update-custom '%s %s)",
uc->id, custom, val);
}
The text was updated successfully, but these errors were encountered: