Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3134 Decide on specification of Puppet Regexp Change By: Josh Cooper Fix Version/s: PUP 4.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3134 Decide on specification of Puppet Regexp Change By: Henrik Lindberg Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title Henrik Lindberg commented on PUP-3134 Re: Decide on specification of Puppet Regexp Ping Peter Huene. I don't remember if we talked about this. in NPUP are you linking the regexp library that is in Ruby? (This will otherwise create many subtle differences). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3134 Decide on specification of Puppet Regexp Moving this from 4.1.0 to 4.x as this is not ready for engineering. Change By: Henrik Lindberg Fix Version/s: PUP4.1.0 Fix Version/s: PUP4.x Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-3134
Decide on specification of Puppet Regexp
Change By:
Henrik Lindberg
ThespecificationcurrentlystatesthatPuppetsupportsRubyregexp.WeshouldconsiderspecifyingindetailwhatthePuppetregexphandles.ThisbecauseotherimplementationsofthePuppetLanguageareotherwiserequiredtobebasedonthenativeimplementationoftheRubyregexppackage. (Wehavealreadylimitedsomeescapesfrombeingusedinapuppetregexp-soPuppetisnot100%rubyregexp). Themainproblemisthatthecurrentpuppetruntime (whileitchecksforsomeescapes, allows other constructs ( suchas posixgroupse.g.{{[[:blank:]]}}tobeusedinRuby1.9.3 ). , The^and$areslightlydifferentthaninother regexp implementationsandtheuseofescapesAandZ/zarerequired (butthosearetheoneswefilterout!!??(unknownreasonwhy;inthespecitissimplystatedthattheyarenotsupported)) .Wealsodonotsupportanymodifierstotheregexp(whichinawayisgoodasitreducesthenumberofincompatibilitiesbecauseoptionsarequitedifferentbetweenimplementations) ,buttheycanbeenteredwithinlineflagsettingsinsidetheregexpdelimiters .Tobe100%accurateavalidatingregexpparserisrequiredthatisspecifictoPuppet-orweneedtotietheregexpimplementationtoaparticularimplementation(whichhasconsequences). Thisisalongtermconcernthatimpactstheabilitytohaveanagent/compilerimplementationinalanguageotherthanRuby.(ItmaybesolvableinCbysimplyusingthesameC-regexplibrarythatisusedbyRuby-butitisunknownhowRubyspecificitisandifitcanbeusedseparately.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to
Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3134 Decide on specification of Puppet Regexp Change By: Kylo Ginsberg Fix Version/s: PUP4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3134 Decide on specification of Puppet Regexp Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3134 Decide on specification of Puppet Regexp Does not need to be implemented but it should be spec'ed. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3134) Decide on specification of Puppet Regexp
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-3134 Decide on specification of Puppet Regexp Issue Type: Improvement Affects Versions: 4.0.0 Assignee: Andy Parker Components: DSL Created: 24/Aug/14 3:57 PM Labels: spec Priority: Normal Reporter: Henrik Lindberg The specification currently states that Puppet supports Ruby regexp. We should consider specifying in detail what the Puppet regexp handles. This because other implementations of the Puppet Language are otherwise required to be based on the native implementation of the Ruby regexp package. (We have already limited some escapes from being used in a puppet regexp - so Puppet is not 100% ruby regexp). The main problem is that the current puppet runtime (while it checks for some escapes, allows other constructs (posix groups e.g. [[:blank:]] to be used in Ruby 1.9.3). The ^ and $ are slightly different than in other implementations and the use of escapes A and Z/z are required (but those are the ones we filter out !!?? (unknown reason why; in the spec it is simply stated that they are not supported)).
