Studio:Perl and COM - Revision history

Timd: Text replace - 'Category:Perl Info' to 'Category:Studio:Perl Info'

2009-08-20T23:52:42Z

Text replace - 'Category:Perl Info' to 'Category:Studio:Perl Info'

← Older revision		Revision as of 23:52, 20 August 2009
Line 11:		Line 11:
	</source>		</source>

	[[Category:Perl Info]]		[[Category:Studio:Perl Info]]

Timd: Perl and COM moved to Studio:Perl and COM

2009-08-18T22:17:17Z

Perl and COM moved to Studio:Perl and COM

← Older revision	Revision as of 22:17, 18 August 2009
(No difference)

Ivailop at 05:58, 8 October 2008

2008-10-08T05:58:51Z

← Older revision		Revision as of 05:58, 8 October 2008
Line 2:		Line 2:

	* We always recommend setting a warn level of 3. If you don't do this, COM errors won't be passed back to the script. In JScript, you always receive COM errors, so warn level 3 brings Perl in line with that behavior.		* We always recommend setting a warn level of 3. If you don't do this, COM errors won't be passed back to the script. In JScript, you always receive COM errors, so warn level 3 brings Perl in line with that behavior.
	* When working with unicode the code page has to be set in order to get Perl/COM to properly pass the pchar value as a unicode character. For example Win32::OLE->Option(CP => ~~Win32::OLE::CP_UTF8~~);		<source lang="perl">
			Win32::OLE->Option(Warn => 3);
			</source>

			* When working with unicode the code page has to be set in order to get Perl/COM to properly pass the pchar value as a unicode character.
			<source lang="perl">
			Win32::OLE->Option(CP => Win32::OLE::CP_UTF8);
			</source>

	[[Category:Perl Info]]		[[Category:Perl Info]]

Ivailop at 05:20, 24 September 2008

2008-09-24T05:20:55Z

← Older revision		Revision as of 05:20, 24 September 2008
Line 1:		Line 1:
	Because of its multiplatform heritage, Perl is not a COM-aware language by default. The Win32::OLE package integrates COM with Perl, however there are some "features" of this library that might not be intuitive to Perl programmers. The most important ones are the options the library provides for error reporting (warning level). For more information see [http://search.cpan.org/~~~jdb/libwin32-0.26/OLE/lib/~~Win32~~/OLE.pm~~ Win32::OLE description].		Because of its multiplatform heritage, Perl is not a COM-aware language by default. The Win32::OLE package integrates COM with Perl, however there are some "features" of this library that might not be intuitive to Perl programmers. The most important ones are the options the library provides for error reporting (warning level). For more information see [http://search.cpan.org/search?query=Win32%3A%3AOLE Win32::OLE description].

	* We always recommend setting a warn level of 3. If you don't do this, COM errors won't be passed back to the script. In JScript, you always receive COM errors, so warn level 3 brings Perl in line with that behavior.		* We always recommend setting a warn level of 3. If you don't do this, COM errors won't be passed back to the script. In JScript, you always receive COM errors, so warn level 3 brings Perl in line with that behavior.

Timd at 17:17, 29 February 2008

2008-02-29T17:17:56Z

← Older revision		Revision as of 17:17, 29 February 2008
Line 5:		Line 5:


	[[Category:~~Scripting~~]]		[[Category:Perl Info]]

Andreo at 21:37, 11 December 2007

2007-12-11T21:37:18Z

← Older revision		Revision as of 21:37, 11 December 2007
Line 1:		Line 1:
	Because of its multiplatform heritage, Perl is not a COM-aware language by default. The Win32::OLE package integrates COM with Perl, ~~but~~ there are some "features" of this library that might not be intuitive to Perl programmers.		Because of its multiplatform heritage, Perl is not a COM-aware language by default. The Win32::OLE package integrates COM with Perl, however there are some "features" of this library that might not be intuitive to Perl programmers. The most important ones are the options the library provides for error reporting (warning level). For more information see [http://search.cpan.org/~jdb/libwin32-0.26/OLE/lib/Win32/OLE.pm Win32::OLE description].

	~~Information under this heading would start with summarizing some of~~ the ~~key points from~~ the Win32::OLE ~~perldoc~~. ~~Some points to cover:~~

	* We always recommend setting a warn level of 3. If you don't do this, COM errors won't be passed back to the script. In JScript, you always receive COM errors, so warn level 3 brings Perl in line with that behavior.		* We always recommend setting a warn level of 3. If you don't do this, COM errors won't be passed back to the script. In JScript, you always receive COM errors, so warn level 3 brings Perl in line with that behavior.
	* ~~I seem~~ to ~~recall there were issues passing unicode strings from autoscript~~ to Perl ~~and it was resolved by changing some other settings in~~ Win32::OLE ~~(I believe) - check with Robert on that.~~		* When working with unicode the code page has to be set in order to get Perl/COM to properly pass the pchar value as a unicode character. For example Win32::OLE->Option(CP => Win32::OLE::CP_UTF8);
	* SetProperty is required for setting properties with arguments, such as with ascript's array types. You might also describe the difference between LetPropery and SetProperty. I don't know if there is anywhere in our interfaces that we are currently required to use LetProperty - ~~if NOT, then maybe we shouldn't mention it~~ (~~to avoid confusion~~).


	~~...and other items could be proposed by SEs in the field working with Perl.~~


	[[Category:Scripting]]		[[Category:Scripting]]

Root at 18:48, 11 December 2007

2007-12-11T18:48:31Z

← Older revision		Revision as of 18:48, 11 December 2007
Line 11:		Line 11:


	[[Category:KB]]		[[Category:Scripting]]

Root at 23:42, 21 June 2007

2007-06-21T23:42:00Z

← Older revision		Revision as of 23:42, 21 June 2007
Line 9:		Line 9:

	...and other items could be proposed by SEs in the field working with Perl.		...and other items could be proposed by SEs in the field working with Perl.


			[[Category:KB]]

Root at 23:24, 19 June 2007

2007-06-19T23:24:43Z

New page

Because of its multiplatform heritage, Perl is not a COM-aware language by default. The Win32::OLE package integrates COM with Perl, but there are some "features" of this library that might not be intuitive to Perl programmers.

Information under this heading would start with summarizing some of the key points from the Win32::OLE perldoc. Some points to cover:

* We always recommend setting a warn level of 3. If you don't do this, COM errors won't be passed back to the script. In JScript, you always receive COM errors, so warn level 3 brings Perl in line with that behavior.
* I seem to recall there were issues passing unicode strings from autoscript to Perl and it was resolved by changing some other settings in Win32::OLE (I believe) - check with Robert on that.
* SetProperty is required for setting properties with arguments, such as with ascript's array types. You might also describe the difference between LetPropery and SetProperty. I don't know if there is anywhere in our interfaces that we are currently required to use LetProperty - if NOT, then maybe we shouldn't mention it (to avoid confusion).

...and other items could be proposed by SEs in the field working with Perl.