The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Mar. 03, 2009
Filed:
Nov. 01, 2002
Anders Hejlsberg, Seattle, WA (US);
Eric A. Gunnerson, Bellevue, WA (US);
Peter H. Golde, Bellevue, WA (US);
Chris Anderson, Bellevue, WA (US);
Scott M. Wiltamuth, Seattle, WA (US);
Anders Hejlsberg, Seattle, WA (US);
Eric A. Gunnerson, Bellevue, WA (US);
Peter H. Golde, Bellevue, WA (US);
Chris Anderson, Bellevue, WA (US);
Scott M. Wiltamuth, Seattle, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
A blueprint is described that provides a framework for writing a code generator. A blueprint translator translates the blueprint into one or more classes with source code. The newly generated code can then be compiled. If the user wishes to add additional functionality to a generated class, this is done in a separate source file. At compilation time, the compiler combines the generated class with the user's additions, as if they were written in a single class. Later, if the blueprint is ever changed, the generated code can safely be updated without overwriting the user's additions. Alternately, the user can embed his desired additions or changes directly into the blueprint (embedded code). In this manner, should the blueprint ever be re-compiled, the user's changes will still be present. The partial classes technique can be used in conjunction with the embedded code technique.