Why Microsoft cozied up to open source at OSCON


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Why Microsoft cozied up to open source at OSCON
# 1  
Old 08-04-2008
Why Microsoft cozied up to open source at OSCON

08-04-2008 11:00 AM
Last month at O'Reilly's Open Source Convention (OSCON), it seemed like Microsoft was everywhere you looked, avouching its interest in open source. Thanks to the company's history -- including some very recent history -- a great many in the open source community viewed the company's presence with mistrust, suspicious of Redmond's motives and apprehensive of what would follow. Surely Microsoft must want something, so what is it?



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Open source project

Hi Guys, This might not be the right place to ask but I want to contribute to some open source project. Can anyone please help me to how to start and where to start? (3 Replies)
Discussion started by: tapan singh
3 Replies

2. Shell Programming and Scripting

Open Source

Hi Friends I'm new to this UNIX - I'm working on the porting project from Solaris To Linux i just want to map some commands from solaris to Linux so can any one please tell me how to get the source code of the commands like "ls", "cu", "du" Regards sabee (1 Reply)
Discussion started by: sabee.prakash
1 Replies

3. Windows & DOS: Issues & Discussions

Microsoft Team Foundation Server (TFS) for Unix source files

Hi, I am using Microsoft Team Foundation server as Configuration management tool for the .NET projects in our team. I would like to add my Unix source files to TFS. Please let me know how can i use TFS for version control of my Unix source files? Thanks for your help (0 Replies)
Discussion started by: rameshmelam
0 Replies

4. News, Links, Events and Announcements

Microsoft Source Code Leaked to Internet

Apparently some of Microsoft's source code is circulating on the Internet. You can see a response from Microsoft here. I would like to remind everyone that according to our rules: "These are not hacker boards so hacker related posts will be promptly deleted or moderated." And this certainly... (1 Reply)
Discussion started by: Perderabo
1 Replies
Login or Register to Ask a Question
source(1T)						       Tcl Built-In Commands							source(1T)

__________________________________________________________________________________________________________________________________________________

NAME
source - Evaluate a file or resource as a Tcl script SYNOPSIS
source fileName source -rsrc resourceName ?fileName? source -rsrcid resourceId ?fileName? _________________________________________________________________ DESCRIPTION
This command takes the contents of the specified file or resource and passes it to the Tcl interpreter as a text script. The return value from source is the return value of the last command executed in the script. If an error occurs in evaluating the contents of the script then the source command will return that error. If a return command is invoked from within the script then the remainder of the file will be skipped and the source command will return normally with the result from the return command. The end-of-file character for files is '32' (^Z) for all platforms. The source command will read files up to this character. This | restriction does not exist for the read or gets commands, allowing for files containing code and data segments (scripted documents). If | you require a ``^Z'' in code for string comparison, you can use ``32'' or ``u001a'', which will be safely substituted by the Tcl inter- | preter into ``^Z''. The -rsrc and -rsrcid forms of this command are only available on Macintosh computers. These versions of the command allow you to source a script from a TEXT resource. You may specify what TEXT resource to source by either name or id. By default Tcl searches all open resource files, which include the current application and any loaded C extensions. Alternatively, you may specify the fileName where the TEXT resource can be found. EXAMPLE
Run the script in the file foo.tcl and then the script in the file bar.tcl: source foo.tcl source bar.tcl Alternatively: foreach scriptFile {foo.tcl bar.tcl} { source $scriptFile } SEE ALSO
file(1T), cd(1T), info(1T) KEYWORDS
file, script ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +--------------------+-----------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +--------------------+-----------------+ |Availability | SUNWTcl | +--------------------+-----------------+ |Interface Stability | Uncommitted | +--------------------+-----------------+ NOTES
Source for Tcl is available on http://opensolaris.org. Tcl source(1T)