Felix Winkelmann <[email protected]> writes: >> To hide all the other helper procedures and to be able to replace >> it with something else. As it is now ##sys#schedule is already >> available so I don't see any harm in this. Maybe we have different >> expectations about the modularisation of core? > > We do, it seems. > > Can you describe in more detail what you are trying to do?
Sure! My idea has been that we will wrap all internal "functinal blocks" into modules, so that we have a uniform way of controlling access and immediately see where a particular procedure is used in core. This might be tedious or even busy work but I think we could benefit from that. I did not intend to make this available to the user of fixate the API in any way. We still will be free to change anything at will, but we had a couple of bugs where we forgot to include this identifier or the other in the declare statements. At least this way you will get the (annoying) unbound symbol error / warning when compiling, so I think that's a plus. By speaking of the scheduler.scm: There's a foreign-declare statement *within* the (declare) clause. Does that work and what does it do? Kind regards, Christian _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
