New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dump.c cannot dump Unicode stash names #11762
Comments
From @cpansprout$ ./perl -Ilib -Mutf8 -MDevel::Peek -e '*fòò:: = *bǎr::; Dump \%fòò::' Those question marks represent Latin-1 bytes that my UTF-8 terminal could not render. bǎr is output in UTF-8. Flags: Site configuration information for perl 5.15.4: Configured by sprout at Wed Nov 2 09:06:14 PDT 2011. Summary of my perl5 (revision 5 version 15 subversion 4) configuration: Locally applied patches: @INC for perl 5.15.4: Environment for perl 5.15.4: |
From @HugmeirOn Sun Nov 20 16:23:45 2011, sprout wrote:
Howdy all. I'm looking for opinions on how to go about fixing this. SV = PV(0x90d8a94) at 0x90f5b4c That is, "escaped-bytestring"\0 [UTF8 "escaped-character-string"]. Should it also follow that convention for stash names and the like? Or To get the point across, here's something like what the output would $ perl -MDevel::Peek -E '*{"f\xe9::"} = *{"b\x{30cb}::"}; Dump \%{"f First option Second option Third option Personally, I think the first option sucks -- it sort of starts alright Meanwhile, the third makes debugging dependent on having a font that So I will probably go for the second, unless someone has objections and/ |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Thu Feb 02 20:40:07 2012, Hugmeir wrote:
2 sounds good. -- Father Chrysostomos |
From [Unknown Contact. See original ticket]On Thu Feb 02 20:40:07 2012, Hugmeir wrote:
2 sounds good. -- Father Chrysostomos |
From @nwc10On Thu, Feb 02, 2012 at 08:40:08PM -0800, Brian Fraser via RT wrote:
You're intentionally using octal to distinguish things-as-bytes from hex for Because I'm thinking that some (documented, unambiguous) convention like that
Yes, but in both cases the "style" is really about conveying information
Yes, the second looks the best idea (so far) Nicholas Clark |
From @demerphqOn 3 February 2012 14:40, Nicholas Clark <nick@ccl4.org> wrote:
As an aside, there are number of bits of code that use octal for I personally hate it, for some reason I don't think octal anywhere cheer -- |
From @demerphqOn 3 February 2012 17:48, demerphq <demerphq@gmail.com> wrote:
I should have added that the argument I have seen in at least one I personally think for stuff like this the rule should be, if there is I also think that Dump output should be in ASCII unless requested to Also, I will note that the regex engine debug output does not use \ as cheers, -- |
From @nwc10On Sat, Feb 04, 2012 at 11:11:51AM +0100, demerphq wrote:
Although thinking further I realise that that these two *aren't* the same, $ ./perl -Ilib -MDevel::Peek -e '$a = "N" . chr 255; chop $a; Dump($a)'
Thinking about that, I like it. It also avoids any confusion between string Although "\0" will need to be special cased in some fashion if followed by
"printable" ASCII. (As you implied above)
Which might mean a B or U prefix. (As Devel::Peek effectively has a \0 As an aside, Devel::Peek's tests are probably the right place to test this Nicholas Clark |
From @rjbs* demerphq <demerphq@gmail.com> [2012-02-04T05:11:51]
I have the same dislike for the current behavior, and your suggestion seems -- |
From zefram@fysh.orgThis was fixed in commit 0eb335d in -zefram |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#104116 (status was 'resolved')
Searchable as RT104116$
The text was updated successfully, but these errors were encountered: