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/
<Guest64> IE each proc added to the hash do not share the same definition
what are these procs used for?
<Guest64> thats hard to explain without going into depth of the project. the procs are basically synonyms of existing libc functions which their pointer address is returned back to the dynamic linker during the binding stage to determine which function symbol points to which function
somethign like
abstract struct Callable
end
struct Proc1 < Callable
def call # define args/return type
end
end
struct Proc2 < Callable
def call # define args/return type
end
end
hash = Hash(String, Callable).new
the gist of it is that you cant have a hash with type of
Proc, would need to specify the types of procs that can be in the hash
i suppose technically the macro approach you wanted to take would work around this by defining a hash literal, which would essentially type itself
<Guest64> could you expand more on this hash literal you speak of?
the type of literal hashes are inferred based on the values in the literal
but hashes with a lot of unioned types is kinda meh
<Guest64> although thats neat that works like that. ill keep that in mind
<Guest64> @Blacksmoke16: I am having a bit of trouble implementing a simple test for your callable suggest: https://play.crystal-lang.org/#/r/biyo im probably not doing this right at all heh
prob not going to be that easy when you add more, as the compiler wont be able to guarantee that the value returned from the hash has that method with those arguments
<Guest64> if it matters im attempting to implement rtld-audit for fun and experience: https://man7.org/linux/man-pages/man7/rtld-audit.7.html
could also ofc have a
#get method that returns the related Callable instance that you could then directly invoke #call on
but i just combined them into 1 method
<Guest64> for example: https://pastebin.com/rez9g1t2 vs https://pastebin.com/sAfrAy4M
:point_up: July 11, 2021 1:45 AM
im still of the opinion you dont even need a macro
<Guest64> i guess the problem i am trying to solve is that i have all these function prototypes that vary radically, but the internal body consists mostly of the same method calls plus a bit of dynamic logic based on the function being called, hence the yeild in the macro. i think in the end i was just exploring different options so that i did not have to
<Guest64> write boilerplate 50+ times
A macro generates code only in the location in which it is executed.
However.....you can make what you want to do work with macros.
Macros have access to constants.
So, if you generate all of your procs, assigned to a constant name, under a common namespace, then in your main.cr you can iterate over
that namespace (see Crystal::Maros::TypeNode in the Crystal API docs), find the names of all of your Proc constants, and build your master hash.
<Guest64> im reading https://crystal-lang.org/api/1.0.0/Crystal/Macros/TypeNode.html atm like wyhaines suggested