Author: claimsbot

1. A method for manufacturing a semiconductor device, comprising the steps of:
defining a groove in a semiconductor substrate, the groove including an upper portion and a lower portion;
forming a sacrificial layer to selectively fill the lower portion of the groove, wherein the sacrificial layer has an amorphous phase;
implanting impurity ions into the semiconductor substrate while the lower portion of the groove is filled with the sacrificial layer such that a channel ion implantation layer is formed on the surface of the lower portion of the groove;
removing the sacrificial layer; and
forming a gate on the semiconductor substrate to fill the groove from which the sacrificial layer is removed;
wherein the implanting is implemented such that the implanted impurity ions are dispersed in every direction at portions of the semiconductor substrate while the lower portion of the groove is filled with the sacrificial layer, and the impurity ions can be doped at a uniform concentration on the surface of the lower portion of the groove.
2. The method according to claim 1, wherein the groove comprises a vertical groove and a spherical groove communicating with a lower end of the vertical groove.
3. The method according to claim 2, wherein the vertical groove corresponds to the upper portion of the groove, and the spherical groove corresponds to the lower portion of the groove.
4. The method according to claim 1, wherein the sacrificial layer comprises an oxide layer having an amorphous phase.
5. The method according to claim 1, wherein the sacrificial layer comprises a photoresist layer having an amorphous phase.
6. The method according to claim 1, wherein the step of forming a sacrificial layer comprises the steps of:
depositing a sacrificial layer on the semiconductor substrate to fill the groove; and
etching the sacrificial layer such that the sacrificial layer remains only in the lower portion of the groove.
7. The method according to claim 6, wherein the step of etching the sacrificial layer is implemented using an etch-back process.
8. The method according to claim 1, wherein the gate has a stacked structure of a gate insulation layer, a polysilicon layer, a metal-based layer, and a hard mask layer.
9. The method according to claim 1, wherein, after the step of forming a gate, the method further comprises the step of:
forming a source area and a drain area in a surface of the semiconductor substrate on both sides of the gate.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A method in an application server for executing a voice messaging application, the method comprising:
receiving a first HTTP request for execution of a prescribed voice messaging application operation for a subscriber;
accessing attribute information for the subscriber from an Internet Protocol (IP) based database server configured for storing subscriber attributes;
accessing an IP-based messaging server for subscriber messaging information based on the accessed attribute information, each stored message on the IP-based messaging server being stored within a corresponding e-mail message as a URL encoded string with the corresponding header information so that each stored message is encoded in the URL encoded string; and
generating an HTML page, for execution of the prescribed voice messaging application operation and having media content and control tags, based on the first HTTP request and the subscriber messaging information.
2. The method of claim 1, wherein the receiving step includes recovering within the HTTP request a browser configuration, and call parameters.
3. The method of claim 2, wherein the recovering step includes identifying the browser configuration as one of a computer browser configuration configured for parsing a prescribed group of media tags and presenting a prescribed group of media types, and a lightweight browser configuration configured for parsing a prescribed portion of the prescribed group of media tags.
4. The method of claim 3, wherein the generating step includes generating the HTML page by selectively supplying media tag types based on the identified browser configuration. Page 3
5. The method of claim 2, wherein the call parameters include a called party identifier, the accessing step including retrieving the attribute information, specifying at least one of subscriber registration status and subscriber messaging preferences, based on the called party identifier.
6. The method of claim 5, wherein the call parameters include a calling party identifier, the accessing step further including retrieving second subscriber attribute information based on the calling party identifier.
7. (canceled)
8. The method of claim 1, wherein the accessing step includes accessing the IP-based database server according to LDAP protocol.
9. The method of claim 1, wherein the step of accessing the IP-based messaging server includes selectively obtaining from the IP-based messaging server at least one of a subscriber name, and a subscriber greeting as a subscriber prompt based on a subscriber identifier obtained from the accessed attribute information.
10. The method of claim 9, wherein the converting step includes converting the subscriber prompt from the corresponding URL encoded string into a media file having at least one prescribed media type.
11. The method of claim 10, wherein the converting step includes converting the subscriber prompt into a Multipurpose Internet Media Extension (MIME) type .wav file playable by a browser.
12. The method of claim 11, wherein the step of generating an HTML page includes inserting a first media tag including the .wav file and a second media tag configured for controlling playing of the .wav file.
13. The method of claim 1, wherein the step of accessing the IP-based messaging server includes determining a presence of a stored message on the IP-based messaging server for the subscriber based on the subscriber messaging information, the generating step including selectively inserting one of a first prompt file specifying no new messages and a second prompt file specifying the determined presence of the stored message, based on the subscriber messaging information.
14. The method of claim 13, wherein the step of accessing the IP-based messaging server further includes identifying, for each stored message, a corresponding message type based on the corresponding header information specifying the a Multipurpose Internet Media Extension (MIME) type, the second prompt file configured for specifying the corresponding message type for each stored message.
15. The method of claim 14, further comprising:
selecting one of the stored messages from the IP-based messaging server;
the converting step including converting the URL encoded string of the selected one message into a media file having a prescribed media type, based on the corresponding MIME type and determined capabilities of a browser having sent the first HTTP request, the generating step including inserting the media file into a media tag with a corresponding media control tag for playback of the media file by the browser.
16. The method of claim 15, wherein the converting step includes converting the URL encoded string to text and executing a text to speech routine for converting the text into an audio file based on the header information specifying text and the determined attributes specifying audio only.
17. (canceled)
18. The method of claim 14, wherein
the converting step includes converting selected header information into an audio file based on determining the MIME type is incompatible with determined capabilities of the browser, the generating step including inserting the audio file into the HTML page for playback by the browser.
19. (canceled)
20. The method of claim 1, further comprising:
receiving a second HTTP request for storage for the subscriber of a message having a prescribed messaging format; and
outputting to the IP-based messaging server an instruction for storage of a standard-format message, containing the message and header information specifying the prescribed messaging format, in a directory specified for the subscriber.
21. The method of claim 20, wherein the outputting step includes:
converting the message into the corresponding a URL encoded string;
generating a the corresponding header that specifies a Multipurpose Internet Media Extension (MIME) type for the prescribed messaging format; and
sending as the standard-format message an e-mail message, including the URL encoded string and the header as an attachment, to the IP-based messaging server according to SMTP protocol for delivery to the directory specified for the subscriber.
22. An application server configured for executing a voice messaging application, the application server including:
a hypertext transport protocol (HTTP) interface for receiving an HTTP request specifying execution of a prescribed voice messaging application operation for a subscriber; and
an application runtime environment configured for dynamically generating, in response to the HTTP request, a first hypertext markup language (HTML) document having media content for execution of the voice messaging application operation for the subscriber based on accessing attribute information for the subscriber from an Internet Protocol (IP) based database server configured for storing subscriber attributes, and based on accessing an IP-based messaging server for subscriber messaging information based on the accessed attribute information,
wherein each stored message on the IP-based messaging server is stored within a corresponding e-mail message as a URL encoded string with the corresponding header information so that each stored message is encoded in the URL encoded string.
23. The server of claim 22, wherein the application runtime environment is configured for determining subscriber registration status and subscriber messaging preferences in response to a called party identifier specified in the HTTP request.
24. The server of claim 23, wherein the application runtime environment accesses the IP-based database server and the IP-based messaging server according to LDAP protocol and IMAP protocol, respectively.
25. The server of claim 24, wherein the application runtime environment is configured for accessing from the IP-based messaging server at least one of a subscriber name and a subscriber greeting as a subscriber prompt based on the HTTP request specifying a condition for a calling party to leave a message for the subscriber, the application runtime environment converting the subscriber prompt into a media file playable by the a browser and inserting the media file into the HTML document.
26. The server of claim 25, wherein the application runtime environment is configured for converting the subscriber prompt stored on the IP-based messaging server from a URL encoded string into an audio file as said media file.
27. The server of claim 24, wherein the application runtime environment is configured for accessing from the IP-based messaging server a message for a subscriber, stored on the IP-based messaging server as an e-mail message having the URL encoded string and corresponding header information that specifies a Multipurpose Internet Media Extension (MIME) type, the application runtime environment converting at least one of the header information and the URL encoded string into a media file having a selected media type based on the MIME type and determined capabilities of an input device used by the subscriber.
28. The server of claim 27, wherein the application runtime environment is configured for converting the header information into an audio file based on determining that the MIME type specifies an image and that the determined capabilities to not support the image.
29. (canceled)
30. The server of claim 27, wherein the application runtime environment is configured for converting the URL encoded string into text and converting the text into an audio file using a text to speech routine, based on the MIME type specifying text and the determined capabilities do not support text.
31. The server of claim 24, wherein the application runtime environment is configured for converting a message supplied by the HTTP request and having a prescribed messaging format into the URL encoded string, generating a header specifying a Multipurpose Internet Media Extension (MIME) type for the prescribed messaging format, and outputting to the IP-based messaging server an e-mail message, including the URL encoded string and the header as an attachment, for delivery to a directory specified for the subscriber.
32. A computer readable medium having stored thereon sequences of instructions for executing a voice messaging application, the sequences of instructions including instructions for performing the steps of:
receiving a first HTTP request for execution of a prescribed voice messaging application operation for a subscriber;
accessing attribute information for the subscriber from an Internet Protocol (IP) based database server configured for storing subscriber attributes;
accessing an IP-based messaging server for subscriber messaging information based on the accessed attribute information, each stored message on the IP-based messaging server being stored within a corresponding e-mail message as a URL encoded string with the corresponding header information so that each stored message is encoded in the URL encoded string; and
generating an HTML page, for execution of the prescribed voice messaging application operation and having media content and control tags, based on the first HTTP request and the subscriber messaging information.
33. The medium of claim 32, wherein the receiving step includes recovering within the HTTP request a browser configuration, and call parameters.
34. The medium of claim 33, wherein the recovering step includes identifying the browser configuration as one of a computer browser configuration configured for parsing a prescribed group of media tags and presenting a prescribed group of media types, and a lightweight browser configuration configured for parsing a prescribed portion of the prescribed group of media tags.
35. The medium of claim 34, wherein the generating step includes generating the HTML page by selectively supplying media tag types based on the identified browser configuration.
36. The medium of claim 33, wherein the call parameters include a called party identifier, the accessing step including retrieving the attribute information, specifying at least one of subscriber registration status and subscriber messaging preferences, based on the called party identifier.
37. The medium of claim 36, wherein the call parameters include a calling party identifier, the accessing step further including retrieving second subscriber attribute information based on the calling party identifier.
38. (canceled)
39. The medium of claim 32, wherein the accessing step includes accessing the IP-based database server according to LDAP protocol.
40. The medium of claim 32, wherein the step of accessing the IP-based messaging server includes selectively obtaining from the IP-based messaging server at least one of a subscriber name, and a subscriber greeting as a subscriber prompt based on a subscriber identifier obtained from the accessed attribute information.
41. The medium of claim 40, further comprising instructions for performing the step of converting the subscriber prompt into a media file having at least one prescribed media type.
42. The medium of claim 41, wherein the converting step includes converting the subscriber prompt into a Multipurpose Internet Media Extension (MIME) type .wav file playable by a browser.
43. The medium of claim 42, wherein the step of generating an HTML page includes inserting a first media tag including the .wav file and a second media tag configured for controlling playing of the .wav file.
44. The medium of claim 32, wherein the step of accessing the IP-based messaging server includes determining a presence of a stored message on the IP-based messaging server for the subscriber based on the subscriber messaging information, the generating step including selectively inserting one of a first prompt file specifying no new messages and a second prompt file specifying the determined presence of the stored message, based on the subscriber messaging information.
45. The medium of claim 44, wherein the step of accessing the IP-based messaging server further includes identifying, for each stored message, a corresponding message type based on the corresponding header information specifying the Multipurpose Internet Media Extension (MIME) type, the second prompt file configured for specifying the corresponding message type for each stored message.
46. The medium of claim 45, wherein the medium further comprises instructions for performing the steps of:
selecting one of the stored messages from the IP-based messaging server;
the converting step including converting the URL encoded string of the selected one message into a media file having a prescribed media type, based on the corresponding MIME type and determined capabilities of the browser having sent the first HTTP request, the generating step including inserting the media file into a media tag with a corresponding media control tag for playback of the media file by the browser.
47. The medium of claim 46, wherein the converting step includes converting the URL encoded string to text and executing a text to speech routine for converting the text into an audio file based on the header information specifying text and the determined attributes specifying audio only.
48. (canceled)
49. The medium of claim 45, wherein
the converting step includes converting selected header information into an audio file based on determining the MIME type is incompatible with determined capabilities of the browser, the generating step including inserting the audio file into the HTML page for playback by the browser.
50. (canceled)
51. The medium of claim 32, further comprising instructions for performing the steps of:
receiving a second HTTP request for storage for the subscriber of a message having a prescribed messaging format; and
outputting to the IP-based messaging server an instruction for storage of a standard-format message, containing the message and header information specifying the prescribed messaging format, in a directory specified for the subscriber.
52. The medium of claim 51, wherein the outputting step includes:
converting the message into a URL encoded string;
generating a header that specifies a Multipurpose Internet Media Extension (MIME) type for the prescribed messaging format; and
sending as the standard-format message an e-mail message, including the URL encoded string and the header as an attachment, to the IP-based messaging server according to SMTP protocol for delivery to the directory specified for the subscriber.
53. An application server configured for executing a voice messaging application, the application server including:
a hypertext transport protocol (HTTP) interface for receiving an HTTP request specifying execution of a prescribed voice messaging application operation for a subscriber; and
means for dynamically generating, in response to the HTTP request, a first hypertext markup language (HTML) document having media content for execution of the voice messaging application operation for the subscriber based on accessing attribute information for the subscriber from an Internet Protocol (IP) based database server configured for storing subscriber attributes, and based on accessing an IP-based messaging server for subscriber messaging information based on the accessed attribute information,
wherein each stored message on the IP-based messaging server is stored within a corresponding e-mail message as a URL encoded string with the corresponding header information so that each stored message is encoded in the URL encoded string.
54. The server of claim 53, wherein the generating means is configured for determining subscriber registration status and subscriber messaging preferences in response to a called party identifier specified in the HTTP request.
55. The server of claim 54, wherein the generating means includes means for accessing the IP-based database server and the IP-based messaging server according to LDAP protocol and IMAP protocol, respectively.
56. The server of claim 55, wherein the generating means is configured for accessing from the IP-based messaging server at least one of a subscriber name and a subscriber greeting as a subscriber prompt based on the HTTP request specifying a condition for a calling party to leave a message for the subscriber, the generating means converting the subscriber prompt into a media file playable by a browser and inserting the media file into the HTML document.
57. The server of claim 56, wherein the generating means is configured for converting the subscriber prompt stored on the IP-based messaging server from the URL encoded string into an audio file as said media file.
58. The server of claim 55, wherein the generating means is configured for accessing from the IP-based messaging server a message for a subscriber, stored on the IP-based messaging server as an e-mail message having the URL encoded string and corresponding header information that specifies a Multipurpose Internet Media Extension (MIME) type, the generating means converting at least one of the header information and the URL encoded string into a media file having a selected media type based on the MIME type and determined capabilities of an input device used by the subscriber.
59. (canceled)
60. The server of claim 58, wherein the generating means is configured for converting the URL encoded string into an audio file based on the MIME type specifying a .wav type.
61. The server of claim 58, wherein the generating means is configured for converting the URL encoded string into text and converting the text into an audio file using a text to speech routine, based on the MIME type specifying text and the determined capabilities to not support text.
62. The server of claim 55, wherein the generating means is configured for converting a message supplied by the HTTP request and having a prescribed messaging format into a URL encoded string, generating a header specifying a Multipurpose Internet Media Extension (MIME) type for the prescribed messaging format, and outputting to the IP-based messaging server an e-mail message, including the URL encoded string and the header as an attachment, for delivery to a directory specified for the subscriber.
63. The server of claim 22, wherein:
the HTTP interface is configured for receiving a second HTTP request for storage for the subscriber of a message having a prescribed messaging format;
the application runtime environment configured for outputting to the IP-based messaging server an instruction for storage of a standard-format message, containing the message and header information specifying the prescribed messaging format, in a directory specified for the subscriber, based on:
(1) converting the message into the corresponding URL encoded string;
(2) generating the corresponding header that specifies the corresponding Multipurpose Internet Media Extension (MIME) type for the prescribed messaging format, and
(3) sending as the standard-format message an e-mail message, including the URL encoded string and the header as an attachment, to the IP-based messaging server according to SMTP protocol for delivery to the directory specified for the subscriber.
64. The server of claim 53, wherein:
the HTTP interface is configured for receiving a second HTTP request for storage for the subscriber of a message having a prescribed messaging format;
the generating means configured for outputting to the IP-based messaging server an instruction for storage of a standard-format message, containing the message and header information specifying the prescribed messaging format, in a directory specified for the subscriber, based on:
(1) converting the message into the corresponding URL encoded string;
(2) generating the corresponding header that specifies the corresponding Multipurpose Internet Media Extension (MIME) type for the prescribed messaging format, and
(3) sending as the standard-format message an e-mail message, including the URL encoded string and the header as an attachment, to the IP-based messaging server according to SMTP protocol for delivery to the directory specified for the subscriber.

1. A machine readable medium including program code stored thereon which, when executed by a machine, causes the machine to perform the operations of:
detecting a non-transactional write operation in code including transactional operations, the non-transactional write operation, when executed, to write to a memory location;
inserting a first strong atomicity operation, when executed, to determine if a processing element to execute the non-transactional write operation owns the memory location; and
inserting a second strong atomicity operation to be executed in response to determining the processing element does not own the memory location, the second strong atomicity operation, when executed, to vector execution to a plurality of write barrier operations, wherein the second strong atomicity operation is not to be executed in response to determining the processing element owns the memory location.
2. The machine readable medium of claim 1, wherein the program code which, when executed by a machine, further causes the machine to perform the operations of:
inserting the plurality of write barrier operations, and wherein the plurality of write barrier operations include: a first write barrier operation, when executed, to acquire the transaction record for the processing element, the first write barrier operation including a call to a function.
3. The machine readable medium of claim 2, wherein the function includes:
a first operation, when executed, to acquire the transaction record;
a second operation, when executed, to determine if a write buffer is full;
a third operation, when executed, to flush the write buffer in response to determining the write buffer is full; and
a fourth operation, when executed, to record the transaction record in the write buffer.
4. The machine readable medium of claim 3, wherein the third operation, when executed, to flush the write buffer includes releasing ownership of a plurality of transaction records held in the write buffer, and wherein the fourth operation, when executed, to record the transaction record in the write buffer includes storing a transaction value and an address associated with the memory location in an entry of the write buffer.
5. A method comprising:
determining if a lock associated with a memory location is owned by a processing element;
in response to determining the lock is not owned by the processing element:
writing an entry to a buffer, the entry including a value of the lock and an address associated with the memory location, and
acquiring ownership of the lock for the processing element; and

executing a non-transactional write operation with the processing element in response to the lock being owned by the processing element.
6. The method of claim 5, wherein determining if a lock associated with a memory location is owned by a processing element comprises determining the value of the lock associated with the memory location and comparing the value of the lock to a processing element value to determine if the lock value indicates the lock associated with the memory location is owned by the processing element.
7. The method of claim 5, further comprising determining the buffer is full; and flushing the write buffer.
8. The method of claim 7, wherein flushing the write buffer comprises flushing a plurality of entries of the buffer and releasing a plurality of locks referenced in the plurality of entries in response to flushing the plurality of entries.
9. The method of claim 15, wherein determining the buffer is full is also in response to determining the lock is not owned by the processing element, and wherein determining the buffer is full comprises polling the buffer to determine if the buffer is full.
10. The method of claim 7, wherein determining the buffer is full comprises handling an asynchronously generated interrupt in response to filling the buffer to determine the buffer is full.
11. A tangible machine readable medium including code, when executed by a machine, causes the machine to perform the operations of:
determining if a processing element owns a software transactional lock for an address associated with a data object before performing a non-transactional write operation;
executing a write barrier for the non-transactional write operation before performing the non-transactional write operation in response to determining the processing element does not own the software transactional lock for the address associated with the data object; and
performing the non-transactional write operation without executing the write barrier in response to determining the processing element owns the software transactional lock for the address associated with the data object.
12. The machine readable medium of claim 11, wherein executing the write barrier comprises:
logging an un-owned value of the software transactional lock and the address in a storage area; and
acquiring the software transactional lock.
13. The machine readable medium of claim 12, wherein acquiring the software transactional lock includes updating the software transactional lock from the un-owned value to an owned value.
14. The machine readable medium of claim 13, wherein the code, when executed by the machine, further causes the machine to perform the operations of: not returning the software transactional lock from the owned value to the un-owned value until a non-transactional lock release event is encountered.
15. The machine readable medium of claim 14, wherein the non-transactional lock release event includes determining a lock release storage element holds a lock release value, and wherein the lock release storage element is to be updated by a second processing element to the lock release value in response to the second processing element attempting to update the transaction record to hold a second owned value to indicate the second processing element owns the memory location when the transaction record holds the first owned value to indicate the processing element owns the memory location.
16. The machine readable medium of claim 14, wherein the storage area includes a write buffer, and wherein the lock release event is selected from a group consisting of overflowing the write buffer, starting execution of a transaction, and attempting to acquire the software transactional lock with a second processing element when the software transactional lock holds the owned value responsive to a first processing element updating the software transactional lock from the un-owned value to the owned value.
17. The machine readable medium of claim 14, wherein the storage area includes a write buffer, and wherein the write buffer is to be flushed in response to encountering the non-transactional lock release event.
18. A method comprising
determining if a processing element owns a software transactional lock for an address associated with a data object before performing a non-transactional write operation;
executing a write barrier for the non-transactional write operation before performing the non-transactional write operation in response to determining the processing element does not own the software transactional lock for the address associated with the data object; and
performing the non-transactional write operation without executing the write barrier in response to determining the processing element owns the software transactional lock for the address associated with the data object.
19. The method of claim 18, wherein executing the write barrier comprises:
logging an un-owned value of the software transactional lock and the address in a storage area; and
acquiring the software transactional lock.
20. The method of claim 19, wherein acquiring the software transactional lock includes updating the software transactional lock from the un-owned value to an owned value.
21. The method of claim 20, further comprising: not returning the software transactional lock from the owned value to the un-owned value until a non-transactional lock release event is encountered.
22. The method of claim 21, wherein the non-transactional lock release event includes determining a lock release storage element holds a lock release value, and wherein the lock release storage element is to be updated by a second processing element to the lock release value in response to the second processing element attempting to update the transaction record to hold a second owned value to indicate the second processing element owns the memory location when the transaction record holds the first owned value to indicate the processing element owns the memory location.
23. The method of claim 21, wherein the storage area includes a write buffer, and wherein the lock release event is selected from a group consisting of overflowing the write buffer, starting execution of a transaction, and attempting to acquire the software transactional lock with a second processing element when the software transactional lock holds the owned value responsive to a first processing element updating the software transactional lock from the un-owned value to the owned value.
24. The method of claim 21, wherein the storage area includes a write buffer, and wherein the write buffer is to be flushed in response to encountering the non-transactional lock release event.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A computing system for parsing a text file to retrieve desired data from the text file, the computing system comprising:
a defining module configured for defining a tree pattern based on the text file, and defining a plurality of character string patterns to identify the desired data;
a loading module configured for loading the text file into a storage system;
a parsing module configured for determining a tree structure corresponding to the text file according to the tree pattern, and retrieving the desired data from the text file according to the tree structure corresponding to the text file and the character string patterns; and
an outputting module configured for outputting the retrieved desired data into the storage system.
2. The system of claim 1, wherein the tree pattern is defined by using extensible markup language (XML), and the character string patterns are defined by using regular expressions.
3. The system of claim 1, wherein the loading module loads the text file into an array, and the parsing module parses the text file in the array.
4. The system of claim 1, wherein the outputting module outputs the retrieved desired data in a predetermined data format.
5. The system of claim 4, wherein the predetermined data format is an XML format.
6. A computer-implemented method for parsing a text file, the method comprising:
defining a tree pattern based on the text file, and defining a plurality of character string patterns to identify the desired data;
loading the text file into a storage system;
determining a tree structure corresponding to the text file according to the tree pattern, and retrieving the desired data from the text file according to the tree structure corresponding to the text file and the character string patterns; and
outputting the retrieved desired data into the storage system.
7. The method of claim 6, wherein the tree pattern is defined by using extensible markup language (XML), and the character string patterns are defined by using regular expressions.
8. The method of claim 6, wherein the text file is loaded into an array.
9. The method of claim 8, wherein the retrieved desired data are output in a predetermined data format.
10. The method of claim 9, wherein the predetermined data format is an XML format.
11. A computer-readable medium having stored thereon instructions that, when executed by a computerized device, cause the computerized device to execute a computer-implemented method comprising:
defining a tree pattern based on the text file, and defining a plurality of character string patterns to identify the desired data;
loading the text file into a storage system;
determining a tree structure corresponding to the text file according to the tree pattern, and retrieving the desired data from the text file according to the tree structure corresponding to the text file and the character string patterns; and
outputting the retrieved desired data into the storage system.
12. The medium of claim 11, wherein the tree pattern is defined by using extensible markup language (XML), and the character string patterns are defined by using regular expressions.
13. The medium of claim 11, wherein the text file is loaded into an array.
14. The medium of claim 11, wherein the retrieved desired data are output in a predetermined data format.
15. The medium of claim 14, wherein the predetermined data format is an XML format.