Okay, it was a little more subtle than that: if your code was already using Compat.jl, then everything would have worked. If not, then fieldnames isn't defined at all (as you found out).
I believe I've fixed this issue, and I've tagged a new version of Match.jl. Please try it and let me know if you still have problems. Cheers! Kevin On Fri, Apr 3, 2015 at 6:32 PM, Kevin Squire <[email protected]> wrote: > Actually, you might just need to run a Pkg.update(). Compat.jl is probably > out if date. You'll need to run Pkg.free("Match") of course. > > On Friday, April 3, 2015, Kevin Squire <[email protected]> wrote: > >> Hi William, >> >> Thanks for the email. I should be able up fix this later today, but could >> you open an issue at the Match.jl repo? >> >> Thanks, >> Kevin >> >> On Friday, April 3, 2015, William Macready <[email protected]> >> wrote: >> >>> Hi Kevin >>> >>> I have come to rely heavily on Match.jl. When I recently upgraded to >>> v0.1.2 I got the error: >>> ERROR: fieldnames not defined >>> >>> When reverting back to v0.0.6 everything runs fine. I'm certainly no >>> Package wizard, but is there something I might be doing wrong? >>> >>> thanks! >>> Bill >>> >>> >>> On Monday, March 30, 2015 at 7:32:36 PM UTC-7, Kevin Squire wrote: >>>> >>>> Hi all, >>>> >>>> Match.jl provides both simple and advanced pattern matching >>>> capabilities for Julia. Features include: >>>> >>>> - Matching against most data types >>>> - Deep matching within data types and matrices >>>> - Variable binding within matches >>>> >>>> Usage generally looks like this: >>>> >>>> using Match >>>> >>>> @match item begin >>>> pattern1 => result1 >>>> pattern2, if cond end => result2 >>>> pattern3 || pattern4 => result3 >>>> _ => default_result >>>> end >>>> >>>> Docs can be found at https://matchjl.readthedocs.org/en/latest/, and >>>> the repository is at https://github.com/kmsquire/Match.jl. >>>> >>>> Version 0.1.0 of Match.jl fixes a few long-standing bugs (and removes >>>> some undesirable code). In the process of cleaning things up, matching >>>> against regular expressions with named captures was removed. While I >>>> rather liked the functionality (it was one of the reasons I created >>>> Match.jl), it relied on `eval` to find global Regex definitions, which >>>> caused a number of other issues. (In my defense, I wrote that code long >>>> before I understood the relationship between macros and eval.) >>>> >>>> I doubt there were many people using Match with regular expression >>>> matching, but if you rely on that functionality, you might want to pin >>>> `Match.jl` at v0.0.6, at least until you update your code. >>>> >>>> Cheers! >>>> Kevin >>>> >>>
