search for: abolished

On Aug 12, 2013, at 2:15 PM, Chandler Carruth <chandlerc at google.com> wrote: > Originally, the distinguishing feature of "primitive" types was that they were enumerable and not parameterized on anything. Right. > Then we moved to arbitrary bit-width integers types to generalize things significantly (the right move IMO). Right. > Thus, integers were no longer

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.

> 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:

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

Hello all, It was brought to my attention that : Something is not right about the digesting system for nut-upsuser. For example, I received 9 digests dated 15 May 2025. The first of these had 3 messages and all the others only one each. I would like to get one digest per day with all of the messages for that day. Maybe the threshold for sending out the digest because it is "too

Hello all, It was brought to my attention that : Something is not right about the digesting system for nut-upsuser. For example, I received 9 digests dated 15 May 2025. The first of these had 3 messages and all the others only one each. I would like to get one digest per day with all of the messages for that day. Maybe the threshold for sending out the digest because it is "too

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

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

Is there documentation somewhere for the bottom-up scheduling? I'm trying to figure out what changes are necessary in order to support it in the PPC backend. Thanks in advance, Hal On Thu, 2011-10-20 at 10:21 -0700, Evan Cheng wrote: > > On Oct 19, 2011, at 7:29 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > > Evan, > > > > Thanks for the heads up! Is

On Oct 25, 2011, at 6:01 PM, Hal Finkel wrote: > Is there documentation somewhere for the bottom-up scheduling? I'm > trying to figure out what changes are necessary in order to support it > in the PPC backend. > > Thanks in advance, > Hal > > On Thu, 2011-10-20 at 10:21 -0700, Evan Cheng wrote: >> >> On Oct 19, 2011, at 7:29 PM, Hal Finkel <hfinkel at

On Tue, 2011-10-25 at 21:00 -0700, Andrew Trick wrote: > On Oct 25, 2011, at 6:01 PM, Hal Finkel wrote: > > Is there documentation somewhere for the bottom-up scheduling? I'm > > trying to figure out what changes are necessary in order to support it > > in the PPC backend. > > > > Thanks in advance, > > Hal > > > > On Thu, 2011-10-20 at

> Radford Nea: > > So it may make more sense to move towards consistency in the > > permissive direction, rather than the restrictive direction. > > > That would mean allowing matrix(1,1,1) < (1:2), and maybe also things > > like matrix(1,2,2)+(1:8). > > Martin Maechler: > That is an interesting idea. Yes, in my view that would >

...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 as...

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. -...

TO everyone who is making use of unicode_hacks! I have made irreversible changes to the plugin so that the routings are no longer overloaded. To call the character-bound routines, you need to use the "chars" or "u" accessors, as outlined in the docs http://julik.nl/code/unicode-hacks/index.html and in this blog post by Thijs: