Well, doing some hunting, I have a method conflict somehow that I have found.
*a = PWtest.new* *a.pw* is assignment of a password. I have a module called *Gen* as you've seen, with a method also called *Gen.pw*. It seems the latter is taking precedence somehow. Would the scope of an instance and the clarity of the *Module.methodname* decipher between the two? I'm assuming namespaces are managed so this confusion would not occur. On Tuesday, September 26, 2023 at 11:54:55 AM UTC-4 Jeremy Evans wrote: > On Tue, Sep 26, 2023 at 6:53 AM [email protected] <[email protected]> wrote: > >> A *non-Sequel* class definition has the proper static assignment of *a.pw >> <http://a.pw>*, so this is a difference of *Sequel* vs *non-Sequel* >> class definition, as I see it. > > > If you put together a self contained reproducible example (with the > exception of bcrypt) that shows the issue, I can probably help. If not, I > assume the problem lies outside of Sequel. You didn't even mention whether > you tried the previous example I posted or what the results of it were in > your environment. > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/778fcbcc-2876-4d4c-bbe1-7d897c610de2n%40googlegroups.com.
