On Wed, 9 Jan 2013 12:54:54 -0500
Nick Sabalausky <SeeWebsiteToContactMe@semitwist.com> wrote:
> Yea, this change is definitely a notable step backwards in presentation and usability.
> 

And it doesn't help that, once again, the changelog is showing the *next* release with no indication that it hasn't actually been released.

On 2013-01-09 11:38, Walter Bright wrote:

> Watcha do is something like this:
>
> __thread int x;
> int foo() { return x; }
>
> Compile, disassemble, and look at the code generated and the fixup
> records. Then there's no need to guess :-)

As I said, I don't know assembly but here's the output:

Original code: http://pastebin.com/UKb6etWD

Disassembly with TLS: http://pastebin.com/nkdnE9w6
Disassembly without TLS: http://pastebin.com/vuvEBWWH

Object dump with TLS: http://pastebin.com/PqpPw56a
Object dump without TLS: http://pastebin.com/ki6atzEm

-- 
/Jacob Carlborg

On 1/4/2013 12:10 PM, r_m_r wrote:
> I was wondering if it is possible to integrate some javascript in the changelog
> page to automatically generate the list of fixed issues as suggested by Jonathan
> (As an example, please see the attached file: jq.html).


Thanks for doing this. It's an interesting idea. Some people hate javascript solutions, though :-)

On 1/9/2013 11:02 AM, Jacob Carlborg wrote:
> As I said, I don't know assembly but here's the output:

Good time to learn it!

And I'm not kidding.

On 2013-01-10 06:18, Walter Bright wrote:
> On 1/9/2013 11:02 AM, Jacob Carlborg wrote:
>> As I said, I don't know assembly but here's the output:
>
> Good time to learn it!

Do you have any good books to recommend for this?

I will most likely not have time to learn assembly now. I'm busy with other things and I think I could spend my time better by contributing with other D related things.

Also you said:

"No prob. I'll be happy to make compiler mods as necessary, once the exact problems are identified."

http://forum.dlang.org/thread/kbvsgo$1po3$1@digitalmars.com?page=26#post-kcdvjh:242a1f:241:40digitalmars.com

-- 
/Jacob Carlborg

On 1/10/2013 10:30 AM, Jacob Carlborg wrote:
> On 2013-01-10 06:18, Walter Bright wrote:
>> On 1/9/2013 11:02 AM, Jacob Carlborg wrote:
>>> As I said, I don't know assembly but here's the output:
>>
>> Good time to learn it!
>
> Do you have any good books to recommend for this?

No. But a reasonable way is to just get the instruction set reference from Intel, and single step some D code in assembler mode in the debugger and go instruction by instruction.

> I will most likely not have time to learn assembly now. I'm busy with other
> things and I think I could spend my time better by contributing with other D
> related things.

I think you'll be pleasantly surprised at how knowing assembler will improve your high level coding abilities.


> Also you said:
>
> "No prob. I'll be happy to make compiler mods as necessary, once the exact
> problems are identified."
>
> http://forum.dlang.org/thread/kbvsgo$1po3$1@digitalmars.com?page=26#post-kcdvjh:242a1f:241:40digitalmars.com

Yes, I did. And I know that the compiler will have to be modified to match with Apple's new scheme.

On Thursday, 10 January 2013 at 18:30:10 UTC, Jacob Carlborg wrote:
> On 2013-01-10 06:18, Walter Bright wrote:
>> On 1/9/2013 11:02 AM, Jacob Carlborg wrote:
>>> As I said, I don't know assembly but here's the output:
>>
>> Good time to learn it!
>
> Do you have any good books to recommend for this?
>
> I will most likely not have time to learn assembly now. I'm busy with other things and I think I could spend my time better by contributing with other D related things.
>

I have to concurs with Walter here. Knowing assembly language is a great way to improve you knowledge of programming in general. This is way easier than what most dev think.

I personally know assembly for ARM and x86, and it is clearly helpful.

On 13-01-10 12:13 AM, Walter Bright wrote:
> On 1/4/2013 12:10 PM, r_m_r wrote:
>> I was wondering if it is possible to integrate some javascript in the
>> changelog
>> page to automatically generate the list of fixed issues as suggested
>> by Jonathan
>> (As an example, please see the attached file: jq.html).
>
>
> Thanks for doing this. It's an interesting idea. Some people hate
> javascript solutions, though :-)

Why not create a link to a second page that would contain that javascript so that people can decide to use it or not?  Just adding a link to this on the version number for example. Getting the list that was available in previous releases would just be one more click away.

I would also be possible to add a count of entries on each of those javascript-generated lists for quickly identifying if something has changed since last looking at them.
-- 
/Pierre Rouleau

On Thursday, January 10, 2013 23:37:29 Pierre Rouleau wrote:
> Why not create a link to a second page that would contain that javascript so that people can decide to use it or not?  Just adding a link to this on the version number for example. Getting the list that was available in previous releases would just be one more click away.

People who don't want javascript, disable it, and it's my understanding that you can set up a page to provide alternate content if javascript is disabled, so if we want to use javascript but are worried about people like Nick freaking out about it, that's how I'd expect that we'd deal with it.

- Jonathan M Davis

On 1/10/2013 8:22 PM, deadalnix wrote:
> I have to concurs with Walter here.

I know that must be hard for you, and I admire your sacrifice!

:-)