tynet-lichat/shirakumo - IRC Chatlog
Search
9:31:18
shinmera
Ideally the user would say "this is a lisp project, it has two files a.lisp and b.lisp" and the system would automatically figure out how to construct the necessary effects dependencies to do hte rest
12:09:27
Colleen
Not sure if this makes sense, but what comes to my mind is iterative helpers/syntax-sugar
12:09:27
SAL9000
Not sure if this makes sense, but what comes to my mind is iterative helpers/syntax-sugar
12:09:46
Colleen
Start by mocking up a simple example (your a.lisp, b.lisp thing, but slightly more complex maybe)
12:09:46
SAL9000
Start by mocking up a simple example (your a.lisp, b.lisp thing, but slightly more complex maybe)
12:10:12
Colleen
That should help you identify common patterns -- thus, the first layer of helpers/syntax-sugar
12:10:12
SAL9000
That should help you identify common patterns -- thus, the first layer of helpers/syntax-sugar
12:10:54
Colleen
then for simple projects, the user can use the highest-level helpers, upgrading to the more complex/lower-level ones as necessary in the future
12:10:54
SAL9000
then for simple projects, the user can use the highest-level helpers, upgrading to the more complex/lower-level ones as necessary in the future
19:24:16
shinmera
Right now I'm dealing with this problem: when you create a component it iterates over its supported operations, and creates effects that it can create in a database.
19:24:39
shinmera
But: now consider something like compile-file, which produces a fasl artefact as output.
21:00:55
Colleen
Shinmera: represent the path as #<fasl-of #P"foo.lisp"> for the purposes of planning, then convert it to "real" fasl path once you know what compiler is used?
21:00:55
SAL9000
Shinmera: represent the path as #<fasl-of #P"foo.lisp"> for the purposes of planning, then convert it to "real" fasl path once you know what compiler is used?