| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Don't try and compute the path to the command when it is already specified.
|
| |
|
|
|
|
| |
refs #112
|
| |
|
|
|
|
|
|
|
|
| |
Redefine happens during declaration. The existing langEl is removed from the
map and a newly-declared lel replaces it. If the new list of productions
references [...] the productions from the previous lel are moved into the new
one, in its place. A copy would be preferrable, as move may require some fixup,
but move gives an initial functional implementation. refs #112
|
|
|
|
|
|
| |
Addes an array of exports to runtime data. Also declares each export as an
integer. The value of the export can be passed to colm_get_gloal(). They are
named colm_export_<export-name>. refs #116.
|
| |
|
| |
|
|
|
|
|
| |
These files belong in ragel, however there are some structs we need to keep
here. Trim these files down to the bare so we can tease out what we need.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
A dynamic link is proving complicated on OSX. When the package is configured to
install to a new install location, but make install hasn't happened yet the
link fails This may indicate we are not getting the code we think we are. We
can eschew all these risks with a static link and reserve dynamic linking for
when we are running from the installed location.
This patch also includes some testing fixes
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
cgil: Code Gen Intermediate Language
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Split off ragel, leaving behind libfsm and the rlhc code. Intend to use both of
those components in colm.
|
| |
|
|\
| |
| | |
add flag to support standalone executables
|
|/ |
|
| |
|
|
|
|
|
|
|
|
| |
Rather than using the --transform argument to tar to remove the .pack extension
from the individual files when creating the tarball, simply rename the files
after unpacking. The individual files will then live in the tarball with the
.pack extension, but that's okay. The --transform argument is not available on
osx tar.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Changed the calling convention for colm-wrap (formerly colm-pack) so that we
can substitute the colm program, once packing is implemented there. Makes the
new wrapper args compatible with the existing args for the colm binary.
refs #85
|
|
|
|
|
| |
Sending a newline means a missing ; results in the error getting attributed to
the next line. refs #103
|
|
|
|
| |
refs #103
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The colm language has an ambiguity between literal concatenations and distinct
statements, where the first ends in string/accum/cons/pat and the second is a
bare send. For example:
match P
"a b c d"
"e f g h"
Warn on some of these by checking for an outdent (relative to the first
component) on top level concatenations. If the user does not outdent between
separate intended statements we cannot help with this check.
refs #95
|
|
|
|
|
|
|
| |
In 900189a4d23f0180970f22479f44377973a2d330 we added an option to hack the
parsing of hex literals to allow ranges that cross zero. This was necessary
when alphtype was signed. Moving to an unsigned type eliminates the need for
this.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Switching to unsigned so we can reference chars with the high bit set in the
way that is common when discussing utf and unicode: using hex chars. Negative
values are really uncomfortable and don't lend themselves to specifying ranges.
This change is for the parser and stream/input code only. The collected tree
data still uses char, which makes it convenient to extract the data from a
top-down or bottom-up load. If we change the tree type we need to cast the
pointers all over the loading code.
refs #104 refs #97 refs #81
|
|
|
|
|
| |
We eliminated the use of this field some time ago, but never removed the field
from the struct.
|
| |
|
|
|
|
| |
refs #97
|
|
|
|
| |
refs #97
|
|
|
|
| |
refs #97
|
|\
| |
| |
| |
| | |
Pushing forward with the literal-concatenation patch. This brings back lists of
literals strings at the top level of strings, constructors and patterns.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit brings back string concatenations in match/cons/string literals at
the top level. It does not bring back concatenation of [] lists. For example,
you can write:
match Foo
"hi
"there
BUT NOT:
match Foo
[Hi] [There]
The concatenation (of both forms) was removed when bare sends were added, due
to the ambiguity created. However, removing these concatenations has proven
quite annoying.
This change re-introduces the ambiguity, which maybe we should do something
about by detecting when it is likely via mis-alignments of the strings, or
making some other change to sends.
refs #95
|
| | |
|
| |
| |
| |
| | |
refs #85
|