I want to bring attention to a tool called atexting, which I have been
implementing
for some time. The tool can now be used but is expect to improve and expand
gradually
as well.
This is a tool primarily designed for the purpose of supporting
meta-programming, but
it can be used for many other things as well.
The basic idea is to embed “texting” functions inside plain text and then
interpret these functions in
certain ways to generate texts (which are string-like) suiting one’s
purpose. I will show some examples
in several following posts. Here is the on-line directory for atexting:
I want to bring attention to a tool called atexting, which I have been
implementing
for some time. The tool can now be used but is expect to improve and
expand gradually
as well.
This is a tool primarily designed for the purpose of supporting
meta-programming, but
it can be used for many other things as well.
The basic idea is to embed “texting” functions inside plain text and then
interpret these functions in
certain ways to generate texts (which are string-like) suiting one’s
purpose. I will show some examples
in several following posts. Here is the on-line directory for atexting:
I want to bring attention to a tool called atexting, which I have been
implementing
for some time. The tool can now be used but is expect to improve and
expand gradually
as well.
This is a tool primarily designed for the purpose of supporting
meta-programming, but
it can be used for many other things as well.
The basic idea is to embed “texting” functions inside plain text and then
interpret these functions in
certain ways to generate texts (which are string-like) suiting one’s
purpose. I will show some examples
in several following posts. Here is the on-line directory for atexting:
What this provides is a framework for pre-processing ATS source code. By
framework I mean, that the library provides some infrastructure that can be
extended by the user to provide a custom tool that is capable of handling
certain atextdefs (which interpret the directives of the form
##function(arg0, …, argN), by producing atext AST, which is then spliced
into the output in place of the directive).
Two examples are outputting date/time and syntax-highlighting ATS code
fragments.
I guess it’s possible to implement parser/lexer generators using atexting,
for instance.
Yes, it is meant to be used to pre-process ATS source code. It can process
other forms of text-based files as well.
You often hear people complaining about writing “boilerplate” style of code.
I hope to use the atexting tool to address this problem to some extent.On Friday, February 26, 2016 at 1:31:35 AM UTC-5, Artyom Shalkhakov wrote:
On Sunday, February 21, 2016 at 9:27:46 AM UTC+6, gmhwxi wrote:
I want to bring attention to a tool called atexting, which I have been
implementing
for some time. The tool can now be used but is expect to improve and
expand gradually
as well.
This is a tool primarily designed for the purpose of supporting
meta-programming, but
it can be used for many other things as well.
The basic idea is to embed “texting” functions inside plain text and then
interpret these functions in
certain ways to generate texts (which are string-like) suiting one’s
purpose. I will show some examples
in several following posts. Here is the on-line directory for atexting:
What this provides is a framework for pre-processing ATS source code. By
framework I mean, that the library provides some infrastructure that can be
extended by the user to provide a custom tool that is capable of handling
certain atextdefs (which interpret the directives of the form
##function(arg0, …, argN), by producing atext AST, which is then spliced
into the output in place of the directive).
Two examples are outputting date/time and syntax-highlighting ATS code
fragments.
I guess it’s possible to implement parser/lexer generators using atexting,
for instance.