Search
Sunday, 1st of December 2019, 6:42:34 UTC
7:41:50
beach
Good morning everyone!
14:37:37
scymtym
jackdaniel: for your use-case, what would you want the C parser to produce? preprocessed source? a syntax tree of some kind?
14:45:40
jackdaniel
scymtym: it will be easier to describe in terms of a repl. I want to be able to
14:45:46
jackdaniel
> #include <stdio.h>
14:46:07
jackdaniel
> printf("%s xx %d", "bam" 42);
14:46:26
jackdaniel
where first will feed the image with necessary information about printf prototype for inlined call
14:47:05
jackdaniel
> int foobar () { /* function definition */ }
14:47:18
jackdaniel
(prototype infered from the function definition)
14:48:53
jackdaniel
and regarding the "clouseau" label in the "scroll bars" issue I don't understand a purpose of it, I'd imagine that this label would be put for issues which are to be fixed in clouseau, that's why I've asked
14:52:36
scymtym
jackdaniel: sounds like preprocessing then parsing into a syntax tree would be sufficient
14:52:51
jackdaniel
> int bar () { return foo; }
14:53:11
scymtym
regarding the label: sure, we use labels in the way you suggested. i will remove the label
14:53:47
jackdaniel
so the preprocessor directives should be added incrementally and applied to new definitions
14:53:52
jackdaniel
that's at least a use case I have in mind
14:54:26
jackdaniel
ACTION is making potato pancakes, so 80% afk
14:54:41
scymtym
the preprocessor evaluator uses environments so augmenting them incrementally should be easy enough
15:40:12
scymtym
jackdaniel: https://techfak.de/~jmoringe/language.c-1.ogv
Sunday, 1st of December 2019, 18:42:34 UTC