Type-constrained operations for plug-in types

Patent metadata

Field	Value
Publication number	US-12014190-B2
Application number	US-202017091849-A
Country	US
Kind code	B2
Filing date	Nov 6, 2020
Priority date	Jul 18, 2018
Publication date	Jun 18, 2024
Grant date	Jun 18, 2024

Abstract

Techniques for performing type-constrained operations for plug-in types are disclosed. A runtime environment encounters a request to perform a type-constrained operation that requires evaluating a type constraint associated with a particular plug-in type. The runtime environment lacks sufficient native instructions to evaluate type constraints associated with plug-in types. The runtime environment accesses a plug-in type framework to obtain a particular type descriptor instance associated with the particular plug-in type. The plug-in type framework is designated, prior to encountering any request to perform the type-constrained operation, for obtaining type descriptor instances which define constraints on plug-in types, to an extent that any such constraints exist. The particular type descriptor instance defines a particular type constraint that does not match any single built-in type. The runtime environment performs the type-constrained operation, which comprises using the particular type descriptor instance to evaluate the particular type constraint associated with the particular plug-in type.

First claim

What is claimed is:

1. One or more non-transitory computer readable media comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising:
receiving a string associated with a type descriptor;
retrieving a set of rules for built-in reference type descriptors;
parsing, by a runtime environment, the received string using the set of rules to determine that the received string does not correspond to a built-in reference type; and
responsive to determining that the received string does not correspond to a built-in reference type:
accessing, by the runtime environment, a plug-in type framework to obtain a type descriptor instance associated with a particular type descriptor identified by the received string.

2. The media of claim 1 , wherein parsing the received string comprises:
analyzing the received string to determine that a character from among a set of characters that denotes a beginning of a syntax corresponding to a plug-in type is present in the received string.

3. The media of claim 1 , wherein parsing the received string comprises:
analyzing the received string to determine that a final character of the received string matches one of a set of characters that are permitted to terminate a built-in reference type descriptor;
based on the determination that the final character matches one of the set of characters that are permitted to terminate a built-in reference type descriptor:
analyzing the received string to determine that an initial character of the received string is not one of a set of characters that are used to begin an array; or
analyzing the received string to determine that one or more of a set of characters that denotes a beginning of a syntax corresponding to a plug-in type does not follow the initial character; and

analyzing the received string to determine that not one of a set of characters not permitted in a built-in reference types is present in the received string.

4. The media of claim 1 , wherein parsing the received string comprises:
analyzing the received string to determine that a final character of the received string is not one of a set of characters that are permitted to terminate a built-in reference type descriptor.

5. The media of claim 1 , wherein accessing the plug-in type framework comprises:
determining that the received string corresponds to a particular plug-in type;
calling, using at least a portion of the received string, a bootstrap method associated with the particular plug-in type; and
responsive to calling the bootstrap method, receiving the type descriptor instance.

6. The media of claim 1 , wherein the type descriptor instance is defined based on the plug-in type framework.

7. The media of claim 1 , wherein the type descriptor instance is a metaobject associated with the particular plug-in type, wherein the particular plug-in type corresponds to an overlay of a built-in type in a system of built-in types without modifying or extending a type hierarchy associated with the built-in type.

8. A method comprising:
receiving a string associated with a type descriptor;
retrieving a set of rules for built-in reference type descriptors;
parsing, by a runtime environment, the received string using the set of rules to determine that the received string does not correspond to a built-in reference type; and
responsive to determining that the received string does not correspond to a built-in reference type:
accessing, by the runtime environment, a plug-in type framework to obtain a type descriptor instance associated with a particular type descriptor identified by the received string;
wherein the method is performed by at least one device including a hardware processor.

9. The method of claim 8 , wherein parsing the received string comprises:
analyzing the received string to determine that a character from among a set of characters that denotes a beginning of a syntax corresponding to a plug-in type is present in the received string.

10. The method of claim 8 , wherein parsing the received string comprises:
analyzing the received string to determine that a final character of the received string matches one of a set of characters that are permitted to terminate a built-in reference type descriptor;
based on the determination that the final character matches one of the set of characters that are permitted to terminate a built-in reference type descriptor:
analyzing the received string to determine that an initial character of the received string is not one of a set of characters that are used to begin an array; or
analyzing the received string to determine that one or more of a set of characters that denotes a beginning of a syntax corresponding to a plug-in type does not follow the initial character; and

analyzing the received string to determine that not one of a set of characters not permitted in a built-in reference types is present in the received string.

11. The method of claim 8 , wherein parsing the received string comprises:
analyzing the received string to determine that a final character of the received string is not one of a set of characters that are permitted to terminate a built-in reference type descriptor.

12. The method of claim 8 , wherein accessing the plug-in type framework comprises:
determining that the received string corresponds to a particular plug-in type;
calling, using at least a portion of the received string, a bootstrap method associated with the particular plug-in type; and
responsive to calling the bootstrap method, receiving the type descriptor instance.

13. The method of claim 8 , wherein the type descriptor instance is defined based on the plug-in type framework.

14. The method of claim 8 , wherein the type descriptor instance is a metaobject associated with the particular plug-in type, wherein the particular plug-in type corresponds to an overlay of a built-in type in a system of built-in types without modifying or extending a type hierarchy associated with the built-in type.

15. A system comprising:
at least one device including a hardware processor;
the system being configured to perform operations comprising:
receiving a string associated with a type descriptor;
retrieving a set of rules for built-in reference type descriptors;
parsing, by a runtime environment, the received string using the set of rules to determine that the received string does not correspond to a built-in reference type; and
responsive to determining that the received string does not correspond to a built-in reference type:
accessing, by the runtime environment, a plug-in type framework to obtain a type descriptor instance associated with a particular type descriptor identified by the received string.

16. The system of claim 15 , wherein parsing the received string comprises:
analyzing the received string to determine that a character from among a set of characters that denotes a beginning of a syntax corresponding to a plug-in type is present in the received string.

17. The system of claim 15 , wherein parsing the received string comprises:
analyzing the received string to determine that a final character of the received string matches one of a set of characters that are permitted to terminate a built-in reference type descriptor;
based on the determination that the final character matches one of the set of characters that are permitted to terminate a built-in reference type descriptor:
analyzing the received string to determine that an initial character of the received string is not one of a set of characters

Assignees

• Oracle Int Corp

Inventors

• Rose John Robert
• Goetz Brian

Classifications

• G06F8/437

  Type checking · CPC title

• G06F9/4416

  Network booting; Remote initial program loading [RIPL] · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• G06F9/44526 Primary

  Plug-ins; Add-ons · CPC title