The Crystal programming language | http://crystal-lang.org | Fund Crystal's development: http://is.gd/X7PRtI | Docs: http://crystal-lang.org/docs/ | API: http://crystal-lang.org/api/
In vector.cr it starts out like this:
module Origin::Vector(T)
forward_missing_to @data
include Origin::Shared(Float64) # Error: undefined constant Origin::Shared
...
end
The
include compiles if I put it in a macro included though
These are the errors that drive me crazy because I don't see where they are coming from.
I only have 3 files, and this is the last file parsed
shared.cr should have already been loaded and the module defined...
Give me a minute
I didn't think to run that, because the semantic analyzer in nim showed the aforementioned error in my buffer upon saving
s/vim/vim/
err nim -> vim. must be almost that time :/
The test code I have under those 3 requires is:
alias V2 = Origin::Vector2
x = V2.new(2.0, 8.123)
pp! x + x
pp! x == V2.new(2.0, 8.123_001)
pp! V2.rand(V2::ZERO, V2::ONES)
pp! V2.rand
pp! V2::ZERO.zero?
pp! x.clamp
pp! x.same_direction?(x)
pp! V2::LEFT
worked fine for me?
and like
crystal env
CRYSTAL_CACHE_DIR=/home/mfiano/.cache/crystal
CRYSTAL_PATH=lib:/usr/lib/crystal
CRYSTAL_VERSION=1.0.0
CRYSTAL_LIBRARY_PATH=''
CRYSTAL_OPTS=''
i kno why
no nvm
So yeah, if you can figure out why the macro hook makes it work, i might be able to figure out why i get tons of these similar problems
I'd rather use mixins if possible
basically recreating the same structure, but in a diff way
So I guess the 2 solutions I see are
1) Copy the
2) I already forgot because I'm tired :(
1) Copy the
include Origin::Shared into each concrete type instead of once in the Vector mixin.2) I already forgot because I'm tired :(
Well right now, yes it does defeat the purpose. It might get a little hard to model with inheritance later on
Shared is intended to be stuff common to all base math types (vectors, matrices, and quaternions). Vector is stuff common to all vectors (but Vector3 is special and will define more stuff for itself), and then there will be higher order math types making use of these 3 base types or varying dimensions
It's a rather large project, about 20kloc of Lisp
but fair enough
I suppose I could try inheritance tomorrow if you think it is a better fit
Really, I'm used to functional programming and a very different kind of OOP (methods not associated with classes at all with multiple dispatch)