Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

native callback with object gc #2

Closed
seanshpark opened this issue Apr 28, 2015 · 2 comments
Closed

native callback with object gc #2

seanshpark opened this issue Apr 28, 2015 · 2 comments
Assignees
Labels
enhancement An improvement

Comments

@seanshpark
Copy link
Contributor

I'm adding this issue to discuss in open so may help others to understand and join (to the issues)

Codes can be efficient if some native function is called when JS Object is garbage collected so that some block of memory linked to that Object can be freed. Something like MakeWeak in V8.

API something like this;

typedef bool (*jerry_object_free_callback_t) (const jerry_api_object_t* obj);
bool jerry_api_set_objectfreecb(jerryt_api_object_t* obj, jerry_object_free_callback_t handler_p);
@seanshpark seanshpark added the enhancement An improvement label Apr 28, 2015
@seanshpark seanshpark self-assigned this Apr 28, 2015
seanshpark added a commit that referenced this issue Apr 28, 2015
JerryScript-DCO-1.0-Signed-off-by: SaeHie Park saehie.park@samsung.com
@seanshpark
Copy link
Contributor Author

had to remove unwanted(wrong DCO) branch
hope 48cc9b5 will do.

seanshpark added a commit that referenced this issue Apr 28, 2015
- remove jerry_api_get_object_free_callback(), currenly no usage
- remove object_p parameter with free_callback(), object can mislead users to call APIs which is dangerous this time.

JerryScript-DCO-1.0-Signed-off-by: SaeHie Park saehie.park@samsung.com
@seanshpark
Copy link
Contributor Author

5ec3e2f merged to master

sand1k referenced this issue in sand1k/jerryscript Nov 23, 2015
Add initial statement parsing support.
ktorpi added a commit to ktorpi/jerryscript that referenced this issue Jun 1, 2016
Function descriptions and examples are added to API page.

JerryScript-DCO-1.0-Signed-off-by: István Kádár ikadar@inf.u-szeged.hu
ktorpi added a commit to ktorpi/jerryscript that referenced this issue Jun 6, 2016
Function descriptions and examples are added to API page.

JerryScript-DCO-1.0-Signed-off-by: István Kádár ikadar@inf.u-szeged.hu
LaszloLango added a commit to LaszloLango/jerryscript that referenced this issue Jul 6, 2016
JerryScript-DCO-1.0-Signed-off-by: László Langó llango.u-szeged@partner.samsung.com
polaroi8d referenced this issue in polaroi8d/jerryscript Aug 29, 2016
polaroi8d referenced this issue in polaroi8d/jerryscript Oct 18, 2016
polaroi8d referenced this issue in polaroi8d/jerryscript Oct 24, 2016
grgustaf pushed a commit to grgustaf/jerryscript that referenced this issue Feb 23, 2018
…tial-apis

handle initial flurry of json apis w/o errors
galpeter added a commit to galpeter/jerryscript that referenced this issue Jun 8, 2018
The license checker previously assumed that the
lines of the license will always end with \n
characters. However when checking a file
with \r\n line endings (should only happen for test files)
the checker can incorrectly report invalid license
as the line endings are incorrect.

Additional note jerryscript-project#1: in Python when reading a file
in text mode it can happen that the line endings are
converted to the host system's line ending.
That is the `\r\n` will be converted to `\n` on Linux.
To resolve this problem the io module to disable
the line ending conversion.

Additional note jerryscript-project#2: it is possible that there
are input test files which are not utf-8 conformant
(eg.: to test the parser). These files can't be read
as utf-8 strings and an exception would occur.
By ignoring these errors the tool can check
the file's license. In the license text there is no
invalid utf-8 character so the check will work
correctly.

JerryScript-DCO-1.0-Signed-off-by: Peter Gal pgal.u-szeged@partner.samsung.com
galpeter added a commit to galpeter/jerryscript that referenced this issue Jun 11, 2018
The license checker previously assumed that the
lines of the license will always end with \n
characters. However when checking a file
it could happen that other line endings are
returned (should only happen for test files) thus
the checker can incorrectly report invalid license
as the line endings are incorrect.

Additional note jerryscript-project#1: in Python when reading a file
in text mode it can happen that the line endings are
converted to the host system's line ending.
However on Travis the conversion did not happen when
using the open built-in method. By switching to the
io.open call the conversion is enforced and
all line endings are converted to '\n' regardless of
the host system's line ending.

Additional note jerryscript-project#2: it is possible that there
are input test files which are not utf-8 conformant
(eg.: to test the parser). These files can't be read
as utf-8 strings and an exception would occur.
By ignoring these errors the tool can check
the file's license. In the license text there is no
invalid utf-8 character so the check will work
correctly.

JerryScript-DCO-1.0-Signed-off-by: Peter Gal pgal.u-szeged@partner.samsung.com
yichoi pushed a commit that referenced this issue Jun 11, 2018
The license checker previously assumed that the
lines of the license will always end with \n
characters. However when checking a file
it could happen that other line endings are
returned (should only happen for test files) thus
the checker can incorrectly report invalid license
as the line endings are incorrect.

Additional note #1: in Python when reading a file
in text mode it can happen that the line endings are
converted to the host system's line ending.
However on Travis the conversion did not happen when
using the open built-in method. By switching to the
io.open call the conversion is enforced and
all line endings are converted to '\n' regardless of
the host system's line ending.

Additional note #2: it is possible that there
are input test files which are not utf-8 conformant
(eg.: to test the parser). These files can't be read
as utf-8 strings and an exception would occur.
By ignoring these errors the tool can check
the file's license. In the license text there is no
invalid utf-8 character so the check will work
correctly.

JerryScript-DCO-1.0-Signed-off-by: Peter Gal pgal.u-szeged@partner.samsung.com
ossy-szeged added a commit to ossy-szeged/jerryscript that referenced this issue Oct 24, 2019
# This is the 1st commit message:

python runner for jerry-tests and jerry-test-suite

JerryScript-DCO-1.0-Signed-off-by: Csaba Osztrogonác oszi@inf.u-szeged.hu

# The commit message jerryscript-project#2 will be skipped:

# JerryScript-DCO-1.0-Signed-off-by: Csaba Osztrogonác oszi@inf.u-szeged.hu
# more fixes

# The commit message jerryscript-project#3 will be skipped:

# win fixes
#
# JerryScript-DCO-1.0-Signed-off-by: Csaba Osztrogonác oszi@inf.u-szeged.hu

# The commit message jerryscript-project#4 will be skipped:

# x

# The commit message jerryscript-project#5 will be skipped:

# revert accidentail change

# The commit message jerryscript-project#6 will be skipped:

# lf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement An improvement
Projects
None yet
Development

No branches or pull requests

1 participant