Re: eu 4.0 alpha bugs
- Posted by ChrisB (moderator) Nov 30, 2008
- 1057 views
Hi
Hmm
boiled down, 3 files
jetvet.exu
public include eusqlite3.ew without warning public include datafuncs.ex public include clients.ex
datafuncs contains query_database() clients contains the above code snippet jetvet.exu is the program that starts it all, with all the required includes. There is no include in clients.ex to datafuncs, so datafuncs is included through jetvet.ex
While I can see the advantages of this for reducing include conflicts (and I realise that this is an object() issue, but it does have shades of unresolved conflicts too), I think this is going to cause a lot of headaches for transition to 4.0. Is there any way, for now, of having a directive, like
with 3_include_compatability
that will indicate to the translator to use includes the old style way, then we could have the best of both worlds, or have things gone too far back up now?
Any idea on the [$] issue too?
Chris
