search for: abolish

...n in code has changed to reflect this. > Right. > > But that doesn't make *any sense*. The documentation for primitive types also is still written in a way that would include integers. What purpose does the notion of "primitive" types serve anymore? Why don't we just abolish that from the lexicon and from the code? -Chris

On Dec 6, 2013, at 6:37 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> What purpose does the notion of "primitive" types serve anymore? Why don't we just abolish that from the lexicon and from the code? > > Hi Chris, > > The attached patch removes it from Type.h and updates the last users. > Is that what you were looking for? Yep, LGTM. It would also be nice to remove the mention from LangRef. -Chris

> What purpose does the notion of "primitive" types serve anymore? Why don't we just abolish that from the lexicon and from the code? Hi Chris, The attached patch removes it from Type.h and updates the last users. Is that what you were looking for? Cheers, Rafael -------------- next part -------------- A non-text attachment was scrubbed... Name: t.patch Type: application/octet-stream Si...

On 7 December 2013 12:55, Chris Lattner <clattner at apple.com> wrote: > > On Dec 6, 2013, at 6:37 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >>> What purpose does the notion of "primitive" types serve anymore? Why don't we just abolish that from the lexicon and from the code? >> >> Hi Chris, >> >> The attached patch removes it from Type.h and updates the last users. >> Is that what you were looking for? > > Yep, LGTM. It would also be nice to remove the mention from LangRef. I updated the Lan...

...e it (so sending only by timer I guess), and/or to switch from daily to weekly/monthly/etc. Maybe there are also user settings for each subscriber to tune, I did not check yet. Are there many digest subscribers currently active? WDYT about raising the size threshold significantly (500K? more?) or abolishing it and just going for one digest per day? I guess the setting is there to make heated discussions (much traffic) visible faster. I suppose it does not impact people receiving every message independently. But in practice, with driver logs etc. sometimes making way into text (and replies), we oc...

...e it (so sending only by timer I guess), and/or to switch from daily to weekly/monthly/etc. Maybe there are also user settings for each subscriber to tune, I did not check yet. Are there many digest subscribers currently active? WDYT about raising the size threshold significantly (500K? more?) or abolishing it and just going for one digest per day? I guess the setting is there to make heated discussions (much traffic) visible faster. I suppose it does not impact people receiving every message independently. But in practice, with driver logs etc. sometimes making way into text (and replies), we oc...

I'm not sure if I have a configuration problem or not. I am unable to dial out. When I try to dial in I can hear the phone ring on the dialling phone but Asterisk does not register anything. In zaptel.conf I have loadzone = au defaultzone=au fxsks=1 In zapata.conf language=au context=from-pstn When I do: zap show channels I get: Chan Extension Context Language

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > Are there many digest subscribers currently active? WDYT about raising the > size threshold significantly (500K? more?) or abolishing it and just going > for one digest per day? > > I guess the setting is there to make heated discussions (much traffic) > visible faster. I suppose it does not impact people receiving every message > independently. Either that or avoiding really big digests. I say set the size th...

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > Are there many digest subscribers currently active? WDYT about raising the > size threshold significantly (500K? more?) or abolishing it and just going > for one digest per day? > > I guess the setting is there to make heated discussions (much traffic) > visible faster. I suppose it does not impact people receiving every message > independently. Either that or avoiding really big digests. I say set the size th...

...peline-conflict hazards? > > Yes, definitely. And it should be doing a much better job of it. > > Evan > > > > > -Hal > > > > On Wed, 2011-10-19 at 16:45 -0700, Evan Cheng wrote: > >> Hi Hal, > >> > >> Heads up. We'll soon abolish top-down pre-register allocation scheduler and force every target to bottom up scheduling. The problem is tt list scheduler does not handle physical register dependency at all but it is something that's required for some upcoming legalizer change. > >> > >> If you are interes...

...r x86 and would need some tweaking to work well for other targets. Again, if your target has an itinerary, you probably want the "hybrid" mode. -Andy On Wed, 2011-10-19 at 16:45 -0700, Evan Cheng wrote: >>>> Hi Hal, >>>> >>>> Heads up. We'll soon abolish top-down pre-register allocation scheduler and force every target to bottom up scheduling. The problem is tt list scheduler does not handle physical register dependency at all but it is something that's required for some upcoming legalizer change. >>>> >>>> If you are i...

...rk well for other targets. Again, if your target has an > itinerary, you probably want the "hybrid" mode. > > -Andy > > On Wed, 2011-10-19 at 16:45 -0700, Evan Cheng wrote: > >>>> Hi Hal, > >>>> > >>>> Heads up. We'll soon abolish top-down pre-register allocation scheduler and force every target to bottom up scheduling. The problem is tt list scheduler does not handle physical register dependency at all but it is something that's required for some upcoming legalizer change. > >>>> > >>>> If...

.... > Of course; that *was* the reason the very special treatment for arithmetic > length-1 arrays had been introduced. It is convenient. > > However, *some* of the conveniences in S (and hence R) functions > have been dangerous {and much more used, hence close to > impossible to abolish, e.g., sample(x) when x is numeric of length 1, There's a difference between these two. Giving an error when using a 1x1 matrix as a scalar may detect some programming bugs, but not giving an error doesn't introduce a bug. Whereas sample(2:n) behaving differently when n is 2 than when n...

...on is oriented around solutions designed to work in the traditional telco world. Depending on your companies infrastructure these solutions may be very expensive or completely impossible for your business to implement. Some members of the working group are even of the position that VoIP service be abolished altogether. Your companies direct participation in the hearings is the best way to have an impact. However, we acknowledge that not all companies have the time and/or resources to fully participate lengthy public hearings. It is with this in mind we propose the formation of a Canadian industry...

On 03/31/2015 12:31 PM, Greg Bailey wrote: > On 03/31/2015 09:53 AM, Ryan Qian wrote: >> As a CentOs newbie, I'm not sure, will we still have CentOS 7.1 which >> derive from RHEL 7.1? >> or this is the new naming conversion for CentOS 7. >> >> Thanks! >> -Ryan > > > That was going to be my question as well. According to >

Hi, all I am building a new server. Have installed FC 6 and put in TDM400 card. Checked out latest asteriusk code, run make install in zaptel directory. So far all is fine. Now I am trying to install the drivers. # modprobe zaptel FATAL: Module zaptel not found. Fair enough, no zaptel driver is found on the system. Is there are any known problems with FC6? I did not have much trouble running

Regarding Martin Maechler's proposal: Arithmetic between length-1 arrays and longer non-arrays had silently dropped the array attributes and recycled. This now gives a warning and will signal an error in the future, as it has always for logic and comparison operations For example, matrix(1,1,1) + (1:2) would give a warning/error. I think this might be a mistake. The potential

Originally, the distinguishing feature of "primitive" types was that they were enumerable and not parameterized on anything. Then we moved to arbitrary bit-width integers types to generalize things significantly (the right move IMO). Thus, integers were no longer technically primitive types, and their categorization in code has changed to reflect this. But that doesn't make *any

...at you said. > > And yes, this is how we are now numbering CentOS releases for 7 and > greater. Isn't that illogical ? If there is:- CentOS-7.0-1406-x86_64-DVD.iso then the next one should logically be named:- CentOS-7-1503-x86_64-DVD.iso assuming sub-version numbers have been abolished by Centos. Jumbled confusion, like CentOS-7-x86_64-DVD-1503.iso, is messy and illogical. What is preventing Centos adopting a simple, neat, tidy, sensible and logical approach ? For example: {major version}-{build number}-{architecture}-{media}.iso ? That is method I would use. Thank you....

.../code/unicode-hacks/index.html and in this blog post by Thijs: http://www.fngtps.com/2006/06/easier-unicode-support-in-rails I had to push the trigger on this because too much stuff was breaking with proper Unicode handling. I hope one day (when I am still alive) Matz will do the same and just abolish byte-bound Strings. It''s not likely to happen in the near future. The changes made also mean that YOUR CODE is probably broken NOW if it relies on the patched behavior. If you need the "old" (overriding) string handling to persist, you have to do the following: require RA...