Sponsored Content
The Lounge What is on Your Mind? RudiC reaches over 4000 thanks in 6 years. Post 303020193 by Scrutinizer on Saturday 14th of July 2018 10:42:59 PM
Old 07-14-2018
Well done RudiC... Keep it up!
This User Gave Thanks to Scrutinizer For This Post:
 

7 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

DLT 4000 drivers?

I am using a Quantum DLT 4000 tape drive on a PowerMac G4 with OS 10.1.5 I'd like to use the Terminal application, which is based on BSD 4.4, to see the tape drive and write backup tapes to it. First, is there a way to list all the devices attached to the computer? And secondly, is there a way... (0 Replies)
Discussion started by: derekc132002
0 Replies

2. UNIX for Advanced & Expert Users

Extendnet 4000 login Problem/Feature?

Hi there! I've been given a box that works as a DSL gateway/firewall running Extendnet 4000. Now, when logging in to the box through the web interface using default login (admin/admin) everything is fine. When I log in locally though, a wierd thing happens. My login seems to be successful,... (2 Replies)
Discussion started by: D-Lexy
2 Replies

3. UNIX for Dummies Questions & Answers

Unix Command to separate this years files and last years?

Hello - I have a folder that contains files from 2003 till 2010. I am trying to figure out a command that would seperate each years file and show me a count? Even if i can find a command that would give me year by year count, thats good enough too. Thanks (8 Replies)
Discussion started by: DallasT
8 Replies

4. Shell Programming and Scripting

Split string after 4000 char

Hi everybody! I have a large comma separated text file. This file incluede some column which largest than 4000 character(this is not the last column). I tried with sed but i can't do it. I would like to split to 4000 char this column. Thank You for your help! for example: (5 Replies)
Discussion started by: snayper
5 Replies

5. What is on Your Mind?

Congrats to RudiC - 3000 Thanks!

Congratulations to RudiC for crossing the magic boundary of being thanked 3000 times! As someone who often has profited greatly from your insight i stand in awe before this achievement. Thank you for your ongoing dedication and thank you for your willingness to share your knowledge! bakunin ... (15 Replies)
Discussion started by: bakunin
15 Replies

6. What is on Your Mind?

Congratulations RudiC for completing 4000+ THANKS in forums.

Hello All forum members, I would like to take this opportunity to THANK RudiC for his tremendous achievement, guidance, help for helping in forums, let us join our hands together for his GREAT achievement :b: @Rudi sir, How are you sir? you ROCK, please keep up the great work sir :b: ... (1 Reply)
Discussion started by: RavinderSingh13
1 Replies

7. What is on Your Mind?

Don tops the 4000+ thanks...

Sometime today Don Cragun reached 4000+ thanks from different folks. Well done Don, I have learnt a lot from you and other guys on here. Big thanks from we who have benefitted from your expertise. (6 Replies)
Discussion started by: wisecracker
6 Replies
PERLHACKTUT(1)						 Perl Programmers Reference Guide					    PERLHACKTUT(1)

NAME
perlhacktut - Walk through the creation of a simple C code patch DESCRIPTION
This document takes you through a simple patch example. If you haven't read perlhack yet, go do that first! You might also want to read through perlsource too. Once you're done here, check out perlhacktips next. EXAMPLE OF A SIMPLE PATCH
Let's take a simple patch from start to finish. Here's something Larry suggested: if a "U" is the first active format during a "pack", (for example, "pack "U3C8", @stuff") then the resulting string should be treated as UTF-8 encoded. If you are working with a git clone of the Perl repository, you will want to create a branch for your changes. This will make creating a proper patch much simpler. See the perlgit for details on how to do this. Writing the patch How do we prepare to fix this up? First we locate the code in question - the "pack" happens at runtime, so it's going to be in one of the pp files. Sure enough, "pp_pack" is in pp.c. Since we're going to be altering this file, let's copy it to pp.c~. [Well, it was in pp.c when this tutorial was written. It has now been split off with "pp_unpack" to its own file, pp_pack.c] Now let's look over "pp_pack": we take a pattern into "pat", and then loop over the pattern, taking each format character in turn into "datum_type". Then for each possible format character, we swallow up the other arguments in the pattern (a field width, an asterisk, and so on) and convert the next chunk input into the specified format, adding it onto the output SV "cat". How do we know if the "U" is the first format in the "pat"? Well, if we have a pointer to the start of "pat" then, if we see a "U" we can test whether we're still at the start of the string. So, here's where "pat" is set up: STRLEN fromlen; char *pat = SvPVx(*++MARK, fromlen); char *patend = pat + fromlen; I32 len; I32 datumtype; SV *fromstr; We'll have another string pointer in there: STRLEN fromlen; char *pat = SvPVx(*++MARK, fromlen); char *patend = pat + fromlen; + char *patcopy; I32 len; I32 datumtype; SV *fromstr; And just before we start the loop, we'll set "patcopy" to be the start of "pat": items = SP - MARK; MARK++; sv_setpvn(cat, "", 0); + patcopy = pat; while (pat < patend) { Now if we see a "U" which was at the start of the string, we turn on the "UTF8" flag for the output SV, "cat": + if (datumtype == 'U' && pat==patcopy+1) + SvUTF8_on(cat); if (datumtype == '#') { while (pat < patend && *pat != ' ') pat++; Remember that it has to be "patcopy+1" because the first character of the string is the "U" which has been swallowed into "datumtype!" Oops, we forgot one thing: what if there are spaces at the start of the pattern? "pack(" U*", @stuff)" will have "U" as the first active character, even though it's not the first thing in the pattern. In this case, we have to advance "patcopy" along with "pat" when we see spaces: if (isSPACE(datumtype)) continue; needs to become if (isSPACE(datumtype)) { patcopy++; continue; } OK. That's the C part done. Now we must do two additional things before this patch is ready to go: we've changed the behaviour of Perl, and so we must document that change. We must also provide some more regression tests to make sure our patch works and doesn't create a bug somewhere else along the line. Testing the patch The regression tests for each operator live in t/op/, and so we make a copy of t/op/pack.t to t/op/pack.t~. Now we can add our tests to the end. First, we'll test that the "U" does indeed create Unicode strings. t/op/pack.t has a sensible ok() function, but if it didn't we could use the one from t/test.pl. require './test.pl'; plan( tests => 159 ); so instead of this: print 'not ' unless "1.20.300.4000" eq sprintf "%vd", pack("U*",1,20,300,4000); print "ok $test "; $test++; we can write the more sensible (see Test::More for a full explanation of is() and other testing functions). is( "1.20.300.4000", sprintf "%vd", pack("U*",1,20,300,4000), "U* produces Unicode" ); Now we'll test that we got that space-at-the-beginning business right: is( "1.20.300.4000", sprintf "%vd", pack(" U*",1,20,300,4000), " with spaces at the beginning" ); And finally we'll test that we don't make Unicode strings if "U" is not the first active format: isnt( v1.20.300.4000, sprintf "%vd", pack("C0U*",1,20,300,4000), "U* not first isn't Unicode" ); Mustn't forget to change the number of tests which appears at the top, or else the automated tester will get confused. This will either look like this: print "1..156 "; or this: plan( tests => 156 ); We now compile up Perl, and run it through the test suite. Our new tests pass, hooray! Documenting the patch Finally, the documentation. The job is never done until the paperwork is over, so let's describe the change we've just made. The relevant place is pod/perlfunc.pod; again, we make a copy, and then we'll insert this text in the description of "pack": =item * If the pattern begins with a C<U>, the resulting string will be treated as UTF-8-encoded Unicode. You can force UTF-8 encoding on in a string with an initial C<U0>, and the bytes that follow will be interpreted as Unicode characters. If you don't want this to happen, you can begin your pattern with C<C0> (or anything else) to force Perl not to UTF-8 encode your string, and then follow this with a C<U*> somewhere in your pattern. Submit See perlhack for details on how to submit this patch. AUTHOR
This document was originally written by Nathan Torkington, and is maintained by the perl5-porters mailing list. perl v5.18.2 2013-11-04 PERLHACKTUT(1)
All times are GMT -4. The time now is 04:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy