console.log

[mm765]

Hi,

it seems that the log function works a bit different than other implementations.
1.)
It prints ints with a tailing ".0", for example
a = 10
console.log(a)
"10.0"

2.)
Passing multiple arguments separated by "," writes each argument into a new line.
I think it would be nicer, if arguments were printed on one line, separated by a space (google chrome, for example, does it that way). I have no idea whats the standard here or if there is even a standard :)

Regards,
Matthias

[mschwartz]

There really isn't such thing as an INT in JavaScript. The implementation
may optimize for numbers that are integers.

The change to log() would be trivial.

My implementation of console.dir() is custom, too. It can dump many Java
objects as well as plain old JavaScript ones.

On Sunday, January 17, 2016, mm765 notifications@github.com wrote:

Hi,

it seems that the log function works a bit different than other
implementations.
1.)
It prints ints with a tailing ".0", for example
a = 10
console.log(a)
"10.0"

2.)
Passing multiple arguments separated by "," writes each argument into a
new line.
I think it would be nicer, if arguments were printed on one line,
separated by a space (google chrome, for example, does it that way). I have
no idea whats the standard here or if there is even a standard :)

Regards,
Matthias

—
Reply to this email directly or view it on GitHub
#15.

[mschwartz]

Please see this:

http://speakingjs.com/es5/ch11.html

On Sunday, January 17, 2016, Mike Schwartz mykesx@gmail.com wrote:

There really isn't such thing as an INT in JavaScript. The implementation
may optimize for numbers that are integers.

The change to log() would be trivial.

My implementation of console.dir() is custom, too. It can dump many Java
objects as well as plain old JavaScript ones.

On Sunday, January 17, 2016, mm765 <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

Hi,

it seems that the log function works a bit different than other
implementations.
1.)
It prints ints with a tailing ".0", for example
a = 10
console.log(a)
"10.0"

2.)
Passing multiple arguments separated by "," writes each argument into a
new line.
I think it would be nicer, if arguments were printed on one line,
separated by a space (google chrome, for example, does it that way). I have
no idea whats the standard here or if there is even a standard :)

Regards,
Matthias

—
Reply to this email directly or view it on GitHub
#15.

[mschwartz]

Pushed the fixed console.log().

On Sun, Jan 17, 2016 at 5:43 PM, Mike Schwartz mykesx@gmail.com wrote:

Please see this:

http://speakingjs.com/es5/ch11.html

On Sunday, January 17, 2016, Mike Schwartz mykesx@gmail.com wrote:

There really isn't such thing as an INT in JavaScript. The
implementation may optimize for numbers that are integers.

The change to log() would be trivial.

My implementation of console.dir() is custom, too. It can dump many Java
objects as well as plain old JavaScript ones.

On Sunday, January 17, 2016, mm765 notifications@github.com wrote:

Hi,

it seems that the log function works a bit different than other
implementations.
1.)
It prints ints with a tailing ".0", for example
a = 10
console.log(a)
"10.0"

2.)
Passing multiple arguments separated by "," writes each argument into a
new line.
I think it would be nicer, if arguments were printed on one line,
separated by a space (google chrome, for example, does it that way). I have
no idea whats the standard here or if there is even a standard :)

Regards,
Matthias

—
Reply to this email directly or view it on GitHub
#15.

[mm765]

Thanks - although trivial i haven't yet worked with github, so i do not know how to do push requests and stuff, so for now im gonna have to post things here like this. I hope i will find the time to get into github at some point but that won't be within the next few weeks.

It seems your push didn't get through (i don't get any updates on pulling and also the typo in the latest decaf-mongo doesn't seem to have been fixed yet in the repository ?!)

Best regards,
Matthias

[mschwartz]

If you use bower, then bower update will update the code.

The change I made to mongo was the README file. If I missed something,
point it out please.

On Monday, January 18, 2016, mm765 notifications@github.com wrote:

Thanks - although trivial i haven't yet worked with github, so i do not
know how to do push requests and stuff, so for now im gonna have to post
things here like this. I hope i will find the time to get into github at
some point but that won't be within the next few weeks.

It seems your push didn't get through (i don't get any updates on pulling
and also the typo in the latest decaf-mongo doesn't seem to have been fixed
yet in the repository ?!)

Best regards,
Matthias

—
Reply to this email directly or view it on GitHub
#15 (comment).

[mschwartz]

It should now be pushed properly.

On Mon, Jan 18, 2016 at 10:43 AM, Mike Schwartz mykesx@gmail.com wrote:

If you use bower, then bower update will update the code.

The change I made to mongo was the README file. If I missed something,
point it out please.

On Monday, January 18, 2016, mm765 notifications@github.com wrote:

Thanks - although trivial i haven't yet worked with github, so i do not
know how to do push requests and stuff, so for now im gonna have to post
things here like this. I hope i will find the time to get into github at
some point but that won't be within the next few weeks.

It seems your push didn't get through (i don't get any updates on pulling
and also the typo in the latest decaf-mongo doesn't seem to have been fixed
yet in the repository ?!)

Best regards,
Matthias

—
Reply to this email directly or view it on GitHub
#15 (comment).

[mm765]

Yes, i got it now, thanks !