Bug 639

Summary:	Describe design decisions and implementation reasons
Product:	UIM	Reporter:	YamaKen <yamaken>
Component:	doc	Assignee:	uim-bugs
Status:	RESOLVED MOVED	QA Contact:
Severity:	enhancement
Priority:	medium
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	9643

Description 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);
}

Comment 2 Muneyuki Noguchi 2012-10-28 08:10:02 UTC

Moved to https://github.com/uim/uim/issues/2

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.