Added in b809136. Jeremy Wohl wrote: > OK, how about some documentation, in the relevant area, to that > effect? "... methods must be ordered prior to static attributes ..." > > thanks, > Jeremy > > On Sep 22, 10:11 pm, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote: > >> This is known, and pretty much unavoidable. The attributes hash actually >> compiles to a method call of the form >> build_attributes(whatever_you_put_in_the_hash), so unless we actually >> parse the Ruby code there's no good way to avoid it. >> >> Jeremy Wohl wrote: >> >>> Hi folks, >>> >>> I notice that hash attribute methods must be specified on the left >>> side of the hash or be left untransmogrified through to an ambiguous >>> compile error. Unit tests only try a left-side example. >>> >>> Known problem or am I doing something stupid? >>> >>> thanks, >>> Jeremy >>> >> > > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
