Usted buscó: perl (Inglés - Coreano)

perl
perl

perl modules
펄 모듈

webcast over perl
펄에 대한 webcast

url for perl scripts
펄 스크립트용 url

url for ~perl scripts:
perl 스크립트를 위한 url(~p)

cpan - comprehensive perl archive network
cpan - comprehensive perl archive networkquery

kio_finger perl script not found.
kio_ finger perl 스크립트를 찾을 수 없습니다.

highlighting for rpm spec-files, perl, diff and more
rpm spec 파일, perl, diff 파일 등 하이라이팅

can i generate dll files from php scripts like i can in perl?
6. can i generate dll files from php scripts like i can in perl?

for regular expressions in perl-compatible syntax have a look at the pcre functions.
spliti()

instructions are separated the same as in c or perl - terminate each statement with a semicolon.
각각의 명령은 c나 perl과 같은 기호를 사용하여 구분한다. 즉, 한 문장은 ;(세미콜론)으로 종료한다.

by default, as in perl, a backslash followed by a letter with no special meaning is treated as a literal.
this modifier turns on additional functionality of pcre that is incompatible with perl. any backslash in a pattern that is followed by a letter that has no special meaning causes an error, thus reserving these combinations for future expansion. by default, as in perl, a backslash followed by a letter with no special meaning is treated as a literal. there are at present no other features controlled by this modifier.

perl is a very tried and true language, it 's been around since the late eighties, but php is maturing very quickly.
the biggest advantage of php over perl is that php was designed for scripting for the web where perl was designed to do a lot more and can because of this get very complicated. the flexibility / complexity of perl makes it easier to write code that another author / coder has a hard time reading. php has a less confusing and stricter format without losing flexibility. php is easier to integrate into existing html than perl. php has pretty much all the 'good' functionality of perl: constructs, syntax and so on, without making it as complicated as perl can be. perl is a very tried and true language, it's been around since the late eighties, but php is maturing very quickly.

in either case, the webcast needs an http server offering either perl or asp as scripting. therefore, the exporting option depends on the http server used.
어떤 경우라도 webcast는 perl이나 asp를 스크립트로 제공하는 http 서버가 필요합니다. 따라서 내보내기 옵션은 사용하는 http 서버에 따라 달라집니다.

\<ahelp hid=\"sd:edit:dlg_publishing:page2_cgi\"\>specifies the url (absolute or relative) for the generated perl scripts.\</ahelp\>
\<ahelp hid=\"sd:edit:dlg_publishing:page2_cgi\"\>생성된 perl 스크립트의 url(절대 주소 또는 상대 주소)을 지정합니다.\</ahelp\>