<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: CLI in C++: DSL-based Designs</title>
	<link>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/</link>
	<description>Boris Kolpackov's blog about software</description>
	<pubDate>Wed, 22 Apr 2026 11:07:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Boris Kolpackov</title>
		<link>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/#comment-1010</link>
		<author>Boris Kolpackov</author>
		<pubDate>Fri, 23 Oct 2009 18:22:43 +0000</pubDate>
		<guid>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/#comment-1010</guid>
		<description>Hi Jack,

I am not sure what you are want to achieve with XLW. Do you want to be able to access the command line data from Excel?

The CLI language is specific to the concepts of the command line interface and, to a lesser extent, C++. The upside of this is that it is very clean and simple. The downside is that it is hard to reuse for something else.</description>
		<content:encoded><![CDATA[<p>Hi Jack,</p>
<p>I am not sure what you are want to achieve with XLW. Do you want to be able to access the command line data from Excel?</p>
<p>The CLI language is specific to the concepts of the command line interface and, to a lesser extent, C++. The upside of this is that it is very clean and simple. The downside is that it is hard to reuse for something else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/#comment-1009</link>
		<author>Jack</author>
		<pubDate>Fri, 23 Oct 2009 17:40:13 +0000</pubDate>
		<guid>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/#comment-1009</guid>
		<description>I will definitely give it a go because I need that and I think you did a fantastic job with xsd/xsde. 
Also, do you think your project could be adapted for other kind of interfaces? I have xlw in mind (Excel interfacing).
Keep up the good work, it makes developing a real pleasure! =D</description>
		<content:encoded><![CDATA[<p>I will definitely give it a go because I need that and I think you did a fantastic job with xsd/xsde.<br />
Also, do you think your project could be adapted for other kind of interfaces? I have xlw in mind (Excel interfacing).<br />
Keep up the good work, it makes developing a real pleasure! =D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boris Kolpackov</title>
		<link>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/#comment-1006</link>
		<author>Boris Kolpackov</author>
		<pubDate>Thu, 22 Oct 2009 13:17:36 +0000</pubDate>
		<guid>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/#comment-1006</guid>
		<description>Hi Jack,

There would be several issues with XML Schema, similar to YANG. First, it would be very verbose. Second, there is no language mechanism for capturing option aliases. While we could use default values in attributes to model default option values, they will only work for built-in XML Schema types. Then there is the issue of using custom C++ types for options which won't be easy with XML Schema.

I am planning to release CLI 1.0.0 on Sunday. You can try it and then see if you can achieve something that simple and elegant with XML Schema ;-).</description>
		<content:encoded><![CDATA[<p>Hi Jack,</p>
<p>There would be several issues with XML Schema, similar to YANG. First, it would be very verbose. Second, there is no language mechanism for capturing option aliases. While we could use default values in attributes to model default option values, they will only work for built-in XML Schema types. Then there is the issue of using custom C++ types for options which won&#8217;t be easy with XML Schema.</p>
<p>I am planning to release CLI 1.0.0 on Sunday. You can try it and then see if you can achieve something that simple and elegant with XML Schema ;-).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/#comment-1005</link>
		<author>Jack</author>
		<pubDate>Thu, 22 Oct 2009 01:58:00 +0000</pubDate>
		<guid>https://codesynthesis.com/~boris/blog//2009/07/19/cli-cxx-dsl-based-designs/#comment-1005</guid>
		<description>Hi Boris,

Very interesting blog. Why not using an xml schema to represent command/argument/option structure and implement a parser that creates a CLI reader?</description>
		<content:encoded><![CDATA[<p>Hi Boris,</p>
<p>Very interesting blog. Why not using an xml schema to represent command/argument/option structure and implement a parser that creates a CLI reader?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
